engineering
Dustin Schau
9:12 AM@Acme can you analyze the queries that resulted in opening a PR, week over week? It feels slower lately and I wonder if it's real or if I'm just asking for more.
Now availableYour company. Your agent.
Own your AI
Build your company agent that works alongside your team, powered by the best AI platform
Customers
What our customers say.
"I worked at Amazon for 12 years. We had full business intelligence teams trying to build this for us. I can do this with Adapt in minutes."
Karthika Shankar
Co-Founder, Rosie
"It started with data access, but now every team at Wander runs on Adapt. It has become the operating layer for the entire company."
Nathan Potter
CTO at Wander
"At DoNotPay, a task that previously took a customer support agent 45 minutes (locating a user who had forgotten their account details and emailing them), now takes 1 minute."
Joshua Browder
CEO at DoNotPay
The full stack
Every layer, your own.
One agent runtime, one router, one sandbox layer, full control to customize, control, and extend.
Layer 01 — Apps
One agent: integrated everywhere.
We meet you wherever you work, so you can stay in flow across all of the surfaces where your team gets work done.
bugs
Casey Manos
10:04 AMcross-posting from #sales, we're hearing it from customers too. @Acme can you dig in?
Rachel Taylor10:01 AM
two customers on calls this morning hit 401s on their Salesforce sync. anyone else hearing this?
Posted in #sales · Today
AcmeAPP
10:05 AMOn it — pulling this morning's failed syncs and replaying them in a sandbox.
AcmeAPP
10:18 AMReproduced it in a sandbox: two runs can refresh the same OAuth token at once, and the loser's token gets revoked. Fix is up as PR #482with a regression test that replays the failing syncs. All checks are green; I'll post here the moment it merges.
PR #482 · fix/token-refresh-race · 12 checks passed
serialize token refresh per connection#482
openAcme opened this from the #bugs thread · 2m ago
integrations/oauth.ts
- if (token.expiresAt < Date.now()) {
- - return refreshToken(connection)
- + return withLock(connection.id, () =>
- + refreshToken(connection))
- 12 checks passed
- sandbox-verified
- ran in 41s
Messages · +1 (415) 555-0134
did the token fix merge yet?
Merged 14 minutes ago: checks green, canary healthy, 401s back to zero. I posted the all-clear in #bugs and queued re-runs for the 12 syncs that failed.
perfect, kick off the re-runs
Layer 02 — Models
Don't bet your business on one model.
Send each request to the right model: frontier for the hard problems, fast open-weight for everything else. The router handles keys, retries, streaming, and spend behind one endpoint.
Adaptive routingEvery request is scored and routed to a tier: xfast, fast, balanced, or deep.
Frontier and open-weight, day oneClaude, GPT, and Gemini next to the best open-weight releases. New models are a config change, not a migration.
Zero lock-inA model is a string, not an architecture decision. Your evals pick the winner, not a vendor roadmap.
Mid-stream failoverProvider 500s and rate limits reroute in flight. The user never sees a retry.
Adapt Router
“What’s our uptime?”xfast
“Draft a reply”fast
“Chart signup trends”balanced
“Root-cause the 401s”deep
TierModelBest forp50Cost
- xfastgpt-5.6-luna-lowlookups & FAQs121ms1×
- fastgemini-3.7-flashsummaries & drafts180ms1.3×
- balancedgpt-5.6-sol-mediumanalysis & synthesis388ms~11×
- deepfable-5-xhighhard reasoning412ms~17×
Layer 03 — Infra
A real computer. A real filesystem.
Your agents need a way to execute code. Every agent has access to microVM sandboxes with persistent filesystems, scoped secrets, and cron.
run_7f3a91
Cold start 90ms
- boot sandbox90ms
- mount /state62ms
- load secrets41ms
- router → fable-5-xhigh1.24s
- tool: github.search310ms
- router → kimi-k3-high190ms
- write run.json48ms
- post to slack88ms
total 2.05sretries 0cost $0.0038
Persistent volume
- integrations/84 MB
- knowledge/486 MB
- skills/132 MB
- apps/96 MB
- company.md48 KB
1.1 GB of 10 GBsnapshot 4m ago
Automations
0 9 * * 1standup digest—*/15 * * * *inbox sweep—grain.call.finishedpost call transcriptwebhookstripe.invoice.paidreceipt → CRMwebhook
What you actually shipComing soon
Your company, as code.
One command scaffolds plain TypeScript. No framework to learn, no config screens. Every integration is a file you own, so each team meets the agent inside the tool they already live in.
acme-agent· main
acme/
Yours from the first commit. Read it, fork it, delete what you don't need.
Push and deploy.
Ship it to your own environment, or use Adapt Cloud's managed platform.
Become AI-native.
Instantly.
One command and your agent is live. Every surface, every model, zero infrastructure.
- SOC 2 Type II
- Self-host, VPC, or managed on-prem