ArchAgentsAI agents for FDE, services, and engineering teams
Your customers integratedin days, without dedicated engineers on every account
Your customers need your help to deploy, integrate, migrate and more. Today that pulls your engineers into hand-to-hand combat for each of your accounts. Instead you build Agent Solutions for the manual repeatable work, so your team can focus on building and launching.
- Your team packages the work once. An Agent Solution: an AI agent with the tools and rules that job needs.
- Every customer installs and runs it themselves. Inside their boundary, against their systems, under your brand.
- Your engineers step in if the customer agent needs a human. Everything happens between you and your customer in a shared workspace.
Angels & operators from: Meta Stripe Microsoft GitHub OpenAIand more.
StripeSee it run
Watch a customer run your API migration with your agent
The migration ships as a branded Solution your customer installs and runs from their own coding agent. If it runs into a problem it files an issue back to your team, and every customer’s progress lands on your dashboard. The run below is one customer doing it, start to finish, without an engineer from your side on the account.
- Meridian installs Northwind’s migration Solution from the public listing, into their own workspace.
- Dana runs the migration from Claude Code. When it hits a gap, the solution files one issue back to Northwind.
- Northwind watches every migration land on a live dashboard, customer by customer.
How it works
Package the manual, repeatable work once and run it across all customers
Each customer installs your Solution and runs it against the appropriate scopes in their environment, under their own approvals. The same install opens a shared workspace with you.
Packaged from what your team already does.
The systems and context they control.
Step 1 of 3 · Package
Your company packages an agent, its tools, your workflows, and your team’s playbook into one Solution.
Share the work, not your data or permissions
Each agent runs with its own credentials and memory, so one customer’s data stays isolated from another’s. Every action is logged, sensitive ones wait for human approval, and access is revocable in seconds.
Live in the catalog
Agent Solutions published by Stripe
Stripe has published two Agent Solutions in ArchAgents: a Billing Specialist for investigating Billing bugs and a self-service migration from Orb to Metronome. Customers install and run each Solution in their own environment and bring Stripe in when they need deeper help.
One connected system
Connect what customers need with what engineering builds
ArchAgents connects the work happening with customers to the work happening inside engineering, and gives agents a way to act on both. Each product stands on its own, so start with one and add the others.
Agent Solutions
Acts on the repeatable work inside each customer's organization, with their credentials and approvals.
Integrations, migrations, upgrades, and fixes, packaged once and carrying your brand. If the agent needs a human, your team steps in.
How Solutions workAgent Slack Bot
Captures the questions, problems, and requests emerging in the channels you share with customers.
A per-customer agent that answers from the channel's own history and escalates to your experts. Nothing for your customer to install.
See the Slack agentAgent RoomsBeta
Connects customer signals to what engineering and its coding agents are building, deciding, and shipping.
Everything your team and its agents produce lands in one stream. You write routines over it, and they post a chart or a private heads up, with nobody filing a status update.
Explore RoomsTogether, they create a path from customer signal to engineering action, across company boundaries.
Why not just ship some scripts?
MCP and scripts only go so far
Every customer is a bespoke environment that needs hand holding. Agent Solutions go beyond scripts and MCPs by enabling a continuous connection with each of your customers.
- More engineers or post-salesCost grows with every customer you add, and it is still one account at a time.
- Runbooks and scriptsYou own the glue forever, and there is no isolation, no approvals, and no audit trail when it runs against someone else’s systems.
- Your own agent skillsA skill runs in your context, not your customer’s. There is no safe way into their environment, and no path back to your engineers when the agent needs a human.
How to start
Start easily by converting one manual workflow into an Agent Solution
Bring the workflow that pulls your engineers back most often. We build the first Solution with you, then you own it in git. Your customers get your branded experience for your Agent Solution. See the marketplace.
1
Install the CLI
$ brew install ArchAstro/tools/archagent
$ archagent setupTwo commands. Everything after this happens from your terminal.
2
Work where you already work
> /embed agi_0330DvFL4fFemzVfcdHAgiYour engineers build and run Solutions from Claude Code, Codex, or Cursor. No new tool to learn.
3
Your customer embeds it in their coding agent
$ archagent embed start billing-agent
✓ v4 · skills installed for claude, codex, cursorOne command pulls the Solution’s agent, tools, and skills into Claude Code, Codex, or Cursor.
We embed with your team and build your first Solutions together. You own them in git and deploy them across customers. Pricing is usage-based, with no per-seat or per-customer fees.
FAQ
Common questions
Even the simplest B2B software requires hand-to-hand combat to properly integrate. I lived that at Stripe, Meta, and Microsoft, and it always lands on your most scarce teams. We built ArchAgents so that work runs itself. Bring us your manual workflows and we’ll quickly convert them to Agent Solutions that scale to all your customers.
Vivek Sharma Co-founder, CEO · ex-Stripe, Meta, Microsoft
Get started
Book a demo and bring one stuck account, and we’ll map it live. Or send us a note.
Demos are with a founder, not a sales team.