ArchAstro Platform
Talk to us

For developers building agent products

The multi-tenant backend for agent products

Build your product once. Give every customer their own users, agents, data, credentials, and integrations, without mixing their work together.

Talk to usRead the developer docs

Your product

One agent application

The product and experience your customers use

Northstar

Support workflow

Running
  • Users
  • Agents
  • Credentials
  • Knowledge
  • Running work

Redwood

Approval requested

Waiting
  • Users
  • Agents
  • Credentials
  • Knowledge
  • Running work

Harbor

Account review

Completed
  • Users
  • Agents
  • Credentials
  • Knowledge
  • Running work
ArchAstro gives every customer their own organization, so you can ship one product without mixing users, data, credentials, or work.
TypeScriptPythonSwiftGo

REST · SSE · realtime

API · SDK · CLI · dashboard

Using Claude Code, Codex, or Cursor?

Give your coding agent the context

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.

Why ArchAstro

The agent is only one part of the product

Once customers arrive, you also need accounts, permissions, credentials, knowledge, long-running work, and a way to debug what happened. ArchAstro keeps those pieces inside the same customer boundary.

Use ArchAstro as the backend for the agent product. Keep your product UI and business systems. ArchAstro puts identity, agents, credentials, knowledge, durable work, and operations inside one customer boundary.

Agent frameworks and runtimes

Best at
Prompts, graphs, model calls, tools, and agent execution.
How it fits
Teams commonly pair them with identity, customer data, integrations, and product operations.

General app backends

Best at
Identity, databases, storage, and application APIs.
How it fits
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.
How it fits
It brings customer identity, agents, credentials, knowledge, workflows, sandboxes, and run history into one organization.

Customer-scoped development

Create resources inside a customer organization

Save the organization ID when a customer signs up. Use it for every agent, credential, knowledge source, and workflow you create for them.

Read the multi-customer guide
NorthstarSelected
Redwood
Harbor

Selected organization

Northstar

org_0aBcDeFgHiJkLmNoPqRsTu

Immutable organization ID

Users
12 active
Agents
3 deployed
Credentials
4 connected
Knowledge
8 sources
Workflows
6 active

Public TypeScript SDK

server-side
import { PlatformClient } from "@archastro/sdk"

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

// Save this immutable ID at onboarding.
const customerOrgId = "org_0aBcDeFgHiJkLmNoPqRsTu"

const agent = await client.agents.create({
  name: "Support Agent",
  org: customerOrgId,
})

const agents = await client.agents.list({
  orgId: customerOrgId,
})
The SDK reads and writes with the saved organization ID. There is no name search before a write.

Durable workflows

See a workflow wait, retry, and resume

A workflow can pause for approval, retry a customer API, and continue from its recorded state instead of starting over.

Customer update workflow

workflow revision 7
  1. Webhook
  2. Retrieve knowledge
  3. Agent decision
  4. Approval
  5. Customer-system update
workflows/customer-update.yamlschema version 1
kind: WorkflowGraph
version: 1

Run timeline

  1. started
  2. waiting for approval
  3. approved
  4. retried
  5. completed
Keep the workflow in source control. Each run keeps its own history.
  1. 01

    Trigger

    Start from an event or schedule.

  2. 02

    Continue

    Wait, branch, retry, or ask for approval.

  3. 03

    Hand off

    Move work between agents, people, and customer systems.

Production operations

Debug the exact run a customer saw

Filter by customer and environment, then inspect the model trajectory, tool calls, API logs, and errors. Reproduce the run in a sandbox when you need to go deeper.

CustomerNorthstar
EnvironmentProduction

Recent runs

Support handoff

Northstar

Completed

Contract review

Redwood

Waiting

Account sync

Harbor

Failed

Selected run

Support handoff · run_01JQ8K5V

Production

Trajectory

Model call · claude-sonnet

Decision · hand off with context

Tool calls

knowledge_search · 184ms

tasks.create · 96ms

API logsActivityErrorsReproduce in sandbox
The customer and environment stay attached throughout the investigation.

Production baseline

The basics are already in the platform

Start with what your first customer needs. Add more without changing how customers are scoped or operated.

Build

Define the agent product and connect the systems it uses.

  • Agents
  • Models
  • Tools
  • MCP
  • Scripts
  • Four SDKs

Scope

Give every customer its own identity and access boundary.

  • Organizations
  • Users
  • Teams
  • Roles
  • SSO
  • Credentials

Run

Keep work moving after the request that started it ends.

  • Tasks
  • Routines
  • Workflows
  • Schedules
  • Approvals
  • Webhooks

Operate

Test and inspect the exact work running for each customer.

  • Sandboxes
  • Evals
  • Captured email
  • Trajectories
  • Logs
  • Errors

Who builds on ArchAstro

Built for teams shipping the same product to many customers

Built on ArchAstro

ArchAgents

ArchAgents runs on ArchAstro. It uses customer organizations, agents, routines, integrations, and shared work without building a separate backend for each customer.

See a product built on ArchAstro

Get started

Tell us what you are building

Talk to usRead the developer docs