Multi-tenant by design

Ship agents to your customers, not just your team

Your product already serves many customers. The platform is built the same way: each of your customers can be its own isolated tenant, with its own agents, memory, credentials, and audit trail. Your engineers define agents as code and ship them through the API and SDK, inside the product your customers already use.

  • Organizations, projects, and environments keep each tenant's agents, data, and credentials apart.
  • Agents call functions inside your own app through client-executed tools.
  • Versioned releases, canary rollout, and evaluations before anything reaches a customer.
  • Usage metering, so you can see what each customer's agents consume.

Three ways to run it

Run it yourself, have us set it up, or let us run it

All three use the same source-available platform and the same API, so the choice is about who operates it. Self-hosting is free for your own use under FSL-1.1-ALv2. Offering the platform to your customers under your brand, or reselling it, is covered by a commercial license from us.

Self-hosted

Teams with platform engineers who want full control

Freefor your own use · FSL-1.1-ALv2
Read the source

Run the platform yourself, in your own AWS account, on your own schedule. White-label use for your customers needs a commercial license.

What you get

  • The complete platform source
  • OpenTofu to deploy it on AWS
  • Multi-tenant model, API, SDK, and CLI
  • Approvals, traces, evaluations, and metering
  • Read, modify, and extend it for your own use
White-glove

Set up in your AWS

Teams that want BYOC without the platform work

Fixed scopeone engagement
Plan your setup

We deploy and configure the platform in an AWS account in your AWS Organization, and get your first agent into your product.

Everything in self-hosted, plus

  • Deployment in an AWS account in your org
  • Tenant model designed around your customers
  • First agent integrated into your product
  • Approval, model, and retention policies set up
  • Runbooks and handover to your engineers

Hosted & managed

Teams that want to ship without running infrastructure

Managedongoing platform access
Request access

Use our hosted platform. We run, upgrade, and monitor it; your engineers build agents.

What you get

  • Same platform and API as self-hosted
  • We operate, upgrade, and monitor it
  • Multi-tenant isolation for your customers
  • Usage metering per tenant
  • Invoiced by us, no infrastructure to run

What your engineers get

Everything you'd otherwise build before shipping one agent

Tenant isolation

Organizations, projects, and environments isolate each customer's agents, data, and credentials, with separate environments for dev and prod.

API, SDK, and CLI

Everything the platform does is available through its public API, plus an SDK and CLI for your engineers and your CI.

Agents as code

Agents, tools, and policies live in your repository and ship as immutable, versioned releases you can canary, promote, or roll back.

Tools inside your app

Client-executed tools let agents call functions in your own product. Add MCP servers, HTTP callbacks, or sandboxed code with no network access.

Approvals and policies

Require a person to approve risky actions, and set model policies per environment using your own provider keys.

Traces and evaluations

Every run is traced step by step, and evaluation suites gate each release before your customers see it.

Usage metering

Meter what each tenant's agents consume, so you can understand cost and price your own product with confidence.

Tenant governance

Retention policies, tenant data export, erasure, and signed audit-log exports when your customers or auditors ask.

Channels

Reach your customers in your app, or through Slack, email on custom domains, Telegram, and RCS business messaging.

Tell us what you want your product's agents to do

We'll walk through the tenant model, the tools your agents need inside your app, and which way of running the platform fits your team.