Delivery & Handover
What you receive at production cutover, how source code ownership works, and what the 6-month QA window covers.
Overview
Handover is where vendor lock-in is decided. DevStudio delivers full source code, infrastructure-as-code, the eval set, prompts, deployment docs, and a runbook to your own accounts from day one — there are no vendor-locked layers. This page covers exactly what you own at cutover, what the 6-month QA window includes, how model upgrades are handled, and what happens during a critical incident.
Key things to know about delivery
You own everything at cutover
Full source code in your GitHub org from commit one, infrastructure-as-code in your cloud accounts, the eval set, prompts, orchestration logic, deployment docs, and a runbook. You can replace us at any milestone and continue.
The 6-month QA window is concrete
It covers production fixes, quarterly Token Audits, and business-hours on-call for production-impacting issues. Net-new features and model upgrades are separate, clearly-scoped change requests.
Model upgrades are gated by the eval set
On every upgrade we re-run the full eval set on the new model and only cut traffic over once accuracy recovers, so you are not surprised by silent regressions.