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.
The full stack
One agent runtime, one router, one sandbox layer, full control to customize, control, and extend.
Layer 01 — Apps
We meet you wherever you work, so you can stay in flow across all of the surfaces where your team gets work done.
serialize token refresh per connection#482
openAcme opened this from the #bugs thread · 2m ago
integrations/oauth.ts
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
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.
Layer 03 — Infra
Your agents need a way to execute code. Every agent has access to microVM sandboxes with persistent filesystems, scoped secrets, and cron.
total 2.05sretries 0cost $0.0038
1.1 GB of 10 GBsnapshot 4m ago
0 9 * * 1standup digest—*/15 * * * *inbox sweep—grain.call.finishedpost call transcriptwebhookstripe.invoice.paidreceipt → CRMwebhookWhat you actually shipComing soon
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/
Yours from the first commit. Read it, fork it, delete what you don't need.
Ship it to your own environment, or use Adapt Cloud's managed platform.

“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
Thirty minutes with an engineer turns these mockups into a phased rollout on your real systems. No procurement, no pilot fee.

Built by the Adapt team from San Francisco, CA.
The people building it helped scale Postman, Coder, and Apollo.