From checkout to production in 48 hours.
Here's exactly how.

From the moment we have everything we need from you — your scoped credentials, integration details, and confirmed workspace information. Not from checkout. We'd rather give you an accurate commitment than advertise a countdown we can't control. The order workspace shows exactly what we're waiting on so nothing is ambiguous.

Every deployment includes 30 days of engineer coverage. If something fails or behaves unexpectedly because of how we configured it, we fix it. This coverage applies to the configuration and deployment we delivered — not to changes you make afterwards or to external platform outages.

Yes — and that's the point. Handover includes the runbooks, environment parameters, deployment configs, and a walkthrough so your team can inspect, operate, and modify the deployment independently. You're never locked in. Any competent engineer can take over from where we left off.

Scoped, revocable tokens specific to the integration the agent uses — for example, a Discord bot token with defined permissions, a read-only API key, or a webhook endpoint. We specify exactly what's needed per agent, and it's always the minimum required. We never ask for private keys, seed phrases, passwords to third-party accounts, or admin credentials.

The order workspace has a messaging thread directly to your engineer. Scope changes, additional integrations, or anything outside what was agreed gets discussed there. We quote any additions before doing them — nothing is absorbed silently into your existing agreement.

Often. Contact support with the agent you're considering and the platform, and we'll confirm feasibility before you pay. If we can do it cleanly, we'll tell you. If we can't, we'll say so — we don't take on work we're not confident delivering.

A runbook is a documented operational guide: what the agent does, what each component is, how to restart it if needed, how to rotate credentials, and what to do in specific failure scenarios. It's the difference between a working deployment and a working deployment you can actually maintain. We write them because your team needs to be self-sufficient after the 30-day coverage window.

No. One-off builds are a single payment — you pay once, we build and hand over, and there's no ongoing fee from us. You will have your own hosting and API costs to manage, which the handover documentation covers in detail. If you want ongoing maintenance and monitoring handled for you, that's the managed service model.