# ArchAstro Platform > Build complete multi‑tenant, multiplayer agentic apps We build ArchAgents, ArchDev, and Intern on the ArchAstro developer platform, and now you can too. Cloud hosted, with token-plus billing: you pay model cost plus 10 percent and nothing else. Built for developers by developers. ArchAstro is the backend for agent products, whether one person uses the product or many companies do. It provides APIs and tools to create customer organizations, manage users and agents, connect accounts each person or organization owns, and run agent work that continues after the request ends. Builders set the model per agent across Anthropic, OpenAI, Google, xAI, Meta, Fireworks, Vertex, and OpenRouter, open-weight models included. ## Build on ArchAstro 1. **Define the agent.** Use YAML configs, the REST API, or the TypeScript SDK to set its identity, model, tools, and routines. 2. **Create a customer organization.** Give each customer its own users, agents, teams, permissions, and resources. 3. **Connect the customer's systems.** Keep their OAuth accounts, credentials, data, and knowledge in their organization. 4. **Run and inspect the work.** Start tasks, routines, and workflows, then inspect run history and errors from the API, CLI, or dashboard. ## What the platform includes ### Agents and models The runtime pieces an agent product needs from its first conversation onward. - Persistent agents - Threads and tools - Model selection - Long-term memory - Computer use ### Identity and access Customer accounts and the people allowed to work inside them. - Customer organizations - Users and teams - Roles and SSO - Domains and invitations - Publishable and secret keys ### Routines and workflows Work that survives the request and can wait for people, systems, or other agents. - Tasks - Event-driven routines - Schedules and automations - Approvals, retries, and waits - Agent and human handoffs ### Knowledge and data Managed context and application state that remain scoped to the customer using them. - Managed ingestion - Hybrid search - Customer-scoped knowledge - Files, custom objects, KV, and datasets ### Connections Let each customer connect its own systems and authorize its own accounts. - Customer-owned credentials - OAuth and refresh - GitHub Apps and MCP - Webhooks - Scripts ### Developer surface Use the interface that fits your product, service, or engineering workflow. - REST, SSE, and realtime channels - SDKs for TypeScript, Python, Go, Swift, and Elixir - CLI and versioned configs - Dashboard and webhooks ### Test and operate Exercise real behavior safely, then follow it through production. - Sandboxes, captured email, and evals - Run history and LLM trajectories - Activity, errors, and API-call logs - Dry runs and workflow validation ## Also included - **Models and tools.** Model routing sets the model per agent across Anthropic, OpenAI, Google, and OpenRouter. Built-in tools cover twenty-three families, from web search to computer use to sub-agents. The MCP client attaches your own servers to an agent and resolves their tools at run time. - **Threads, streaming, and notifications.** Threads and messages carry members, tags, artifacts, read state, and search. Streaming sends server-sent events for agent sessions, routine runs, and the activity feed. Tasks and notifications give you assignable tasks with blockers and comments, and a notification per person. - **Sign-in, keys, and secrets.** SSO, SAML, and 2FA is SAML sign-in per organization, TOTP two-factor, and a policy per organization. API keys and secrets is publishable and secret API keys, plus secrets scoped to a user, a team, or an organization. - **Connections and webhooks.** OAuth connectors reach Google, Microsoft, GitHub, Slack, Zoom, LinkedIn, X, and Stripe, each one authorized by the customer. Webhooks and events are event subscriptions, deliveries you acknowledge, and synthetic events you send yourself. - **Your own records and files.** Custom objects hold your own record types inside the customer boundary. Key-value and files is a scoped KV store and file storage with sharing and refreshable URLs. Artifacts are agent output files, stored with their content, their versions, and an archive. - **Evals, the CLI, and the SDK.** Evals run suites, tasks, and runs over the API, scored against a test copy of the app. The CLI is one command line for developer mode and org mode, over the same API. The TypeScript SDK is a typed client for Node and the browser, published as @archastro/sdk. ## How ArchAstro fits These layers can work together. Pick the ones your product needs. - **Agent frameworks and runtimes.** Best at: Prompts, graphs, model calls, tools, and agent execution. Product boundary: Teams commonly pair them with identity, customer data, integrations, and product operations. - **General app backends.** Best at: Identity, databases, storage, and application APIs. Product boundary: Teams commonly pair them with an agent runtime and tools for long-running work and run-level debugging. - **ArchAstro.** Best at: Agent products used by many customers. Product boundary: It brings customer identity, agents, credentials, knowledge, workflows, sandboxes, and run history into one organization. ## Who it is for - [Software companies](https://developers.archastro.ai/for/software-companies): Give every account its own users, agents, data, credentials, and configuration without building that layer from scratch. - [Consulting and services](https://developers.archastro.ai/for/consulting-and-services): Give every client a separate setup while your delivery team reuses the agents, tools, and workflows that make the engagement work. - [Private equity](https://developers.archastro.ai/for/private-equity): Reuse the operating playbook while every company keeps its own people, systems, data, and credentials. - [Enterprise platform teams](https://developers.archastro.ai/for/enterprise-platform-teams): Offer shared agent infrastructure without asking every business unit to build identity, data access, workflows, and operations again. ## Product proof ArchAgents is a live agent product built on ArchAstro. It uses the platform for organizations, users, agents, workflows, and customer relationships: https://archagents.com ## Next steps - [Developer documentation](https://docs.archastro.ai/docs/start-here/getting-started) - [Tell ArchAstro what you are building](mailto:hi@archastro.ai?subject=Building%20on%20ArchAstro&body=Here%27s%20the%20agent%20product%20we%27re%20building%3A%0A%0ACustomers%20we%20need%20to%20support%3A%0A)