Agent Solutions

Package the work once, and every customer runs it

Integrations, migrations, upgrades, and troubleshooting never end, and today your engineers do them one account at a time. A Solution turns that work into an agent your customer installs and runs on their own systems, under their own approvals.

Pay for the tokens your agents use. No per-seat fee.

you@yourco · archagent

$ brew install ArchAstro/tools/archagent
$ archagent deploy agent billing-agent.yaml
  ✓ v4 · sha256:9f2c…d1 · immutable

# your customer, in their own repo
$ archagent embed start billing-agent
  ✓ v4 · skills installed for claude, codex, cursor

# a week later, inside a customer
! Kepler · payout webhook · needs a human
  → issue #83 filed · your team joins the shared workspace

Real commands. A Solution is config in git, versioned like the rest of your code.

What it looks like

A customer fixes their own bug, and calls you in when it sticks

Northwind publishes a Solution and Meridian, their customer, installs it in a few clicks. Both sides work the same bug in one shared workspace, and nothing else crosses between the companies.

Building one

Config in git, shipped like the rest of your code

1
Build it
Start from a sample or your own runbook. The agents, tools, workflows, knowledge, and rules are config in git.
2
Test it
Run it against a sandbox before it touches a real account, and preview the exact diff on every upgrade.
3
Ship it
Your customer installs a pinned version. You watch every account's run from one place.

Solutions in the docs See published Solutions

Their environment

Your customer stays in control

The Solution runs in a workspace their organization owns, or embedded in their own editor. Either way you never receive direct access to their systems.

Their credentials, their approvals. Sensitive actions pause for a human on their side before anything changes.
Isolated per customer. Each agent runs with its own credentials and memory, scoped to one org.
Pinned and reviewable. They install a specific version. A new release never swaps in under them.

How the platform enforces it

Your brand

A Solution runs under your name: your logo, your colors, your support address, down to the reply-to on every email. Your customer sees ArchAgents only if you want them to.

Pay for the tokens your agents use. No per-seat fee and no per-customer fee. We embed with your team to build the first Solutions, and you own them in git. Workspace creation and payment registration carry no initial charge. Provider-backed usage is billed as you go.

Get started

Map one workflow with us

Bring one manual customer workflow that keeps pulling engineers back in, and we will map it live.

Calls are with a founder, not a sales team.