FAQ
The questions everyone asks.
Straight answers about how Autopilot Software Development works, what you own, and what happens if you leave.
The Rule of Relax
One app = one codebase, one production deployment.
Answers
No fine print.
One codebase, one production deployment. That is one app, and Autopilot runs it end to end. Need a second app? That is a second lane, or a Fleet.
The request queue is unlimited: stack up as many features, fixes, and changes as you want. We work one active build lane at a time so quality holds, and the queue never stops moving. Turbo and Max add lanes.
Onboarding is Ignition: we stand up the architecture, repo, CI/CD, security baseline, and a deployed v0 foundation in 30 days or less. Feature requests start in week one, not after a long discovery phase.
v0 is your deployed foundation: the architecture, the repository with CI/CD, the security baseline, and a running application in production you can build on immediately.
You do. Complete your annual term and the full repository transfers to you, free, with no exclusivity. Your code was always yours.
Cancel early and you pay three months of fees or the remaining balance, whichever is less. Your code transfers to you on payment. No drama.
Powered by Ramjet, Disruptica's autonomous development engine, embedded in your app. Your team makes requirements, follows tickets, turns vibes into features, and asks questions about the app; Ramjet builds them, and your human pilot reviews and ships every deploy. It is our technology, not a product you configure.
Yes. A takeover starts with a code-health audit inside Ignition. We stabilize what you have, and the SLA activates once it is on solid ground. Inherited a mess? That is normal.