Build complete multi‑tenant, multiplayer agentic apps

We build ArchAgents, ArchDev, and Intern on the ArchAstro developer platform, and now you can too. It runs in our cloud with token-plus billing: you pay model cost plus 10% and nothing else. Each customer gets one organization, every query is scoped to it, and tests run two organizations side by side.

Start with $5 of credit Read the docs

onboard-customer.ts

import { PlatformClient } from "@archastro/sdk"

const client = PlatformClient.withSecretKey(
  process.env.ARCHASTRO_SECRET_KEY!,
)

// one agent, inside one customer's organization
const agent = await client.agents.create({
  name: "Support Agent",
  org: customer.archastroOrgId,
})

// one session, for one of that customer's users
const session = await client.agent_sessions.create({
  agent: agent.id,
  user: person.archastroUserId,
  instructions: "Answer from Acme's own documents.",
})

Hand this to your coding agent

Inspect this repository, then read https://docs.archastro.ai/llms-full.txt. Help me evaluate ArchAstro as the backend for this multi-tenant agent product. Ask me for any missing product context. Map the customer boundary, what stays in my code, and what ArchAstro would own. Link to the relevant ArchAstro docs for each recommendation.

The ArchAstro developer console for the Acme Corp app over thirty days: total LLM calls 41,145, total tokens 699.1M, unique agents 3,393, and cache hit rate 58.5 percent, with the tokens-by-type chart.

The ArchAstro developer console for one app over thirty days: LLM calls, tokens, latency, unique agents, cache hit rate, and unique end users, with charts for each, the left rail listing organizations, users, teams, agents, storage, and automations, and the LLM calls drawer open on one call.

The console shows every call, token, and error for one app, filtered by organization and agent.

Isolation. Each end user belongs to one organization, and every query made on their behalf is filtered to it by the platform, not by your code. Tests put two organizations side by side and check that neither reads the other's data. Deleting an organization deletes its data. Docs →
Encryption. OAuth tokens, environment variables, and TOTP secrets are encrypted at rest with AES-256-GCM. Secret API keys are shown once and stored hashed; publishable keys are safe in a client. Docs →
Sign-in. Each organization chooses SAML, Google, GitHub, password, or magic link, and can require TOTP. Every sign-in is logged. Docs →
Hosting. It runs on Google Cloud, and SOC 2 is in progress. Docs →

What is in the platform

Each area links to the docs page that covers it.

Start here

Get access and reach your first customer from the portal, the CLI, or your coding agent.

Build agents

Give an agent an identity, routines, tools, and knowledge, then keep it in files you can review.

Operate

Review what you deployed, test apart from production, and step into a live agent.

Customers

Each customer gets an organization with its own people, sign-in rules, agents, and data.

Integrations

Agents connect to outside services, and each credential has one owner.

API and SDKs

One REST API with server-sent events serves a client for every stack.

Pricing

Pay as you go. Every organization, agent, workflow, and SDK is included.

$5of credit when you sign up, good for 90 days.
$0per month, with no platform fee and no seats.
Cost + 10%for model usage, drawn from credits at provider price.

Top up from $5 to $1,000, or turn on auto-reup. When credits run out, calls stop. There is no overage.

Start with $5 of credit Read the docs