See the governed handoff.
This is the product flow without an account. Follow one AI-built application from a Git repository to a deployment that reaches READY, then inspect the record SpringRoll keeps around it.
Deployment walkthrough
01Bring the repositoryInspect
Codex or Claude keeps writing the application. SpringRoll records the Git source, application owner, data classification, and target environment before the runtime receives a build.
02Register the applicationInspect
The agent calls SpringRoll over MCP. Registration creates a tenant-scoped application record and writes its audit event in the same transaction.
03Request a deploymentInspect
SpringRoll pins the revision, creates the release and deployment records, then hands the build to the configured runtime. A created record is work in progress—not success.
04Wait for READYInspect
The runtime reports deployment state back to SpringRoll. READY is the canonical activation point and the first moment the governed URL is ready to open.
05Review the handoffInspect
The application, source, release, environment, owner, deployment state, and audit history remain together for review, promotion, rollback, or retirement.
What remains after the URL.
The URL is the visible output. The durable product is the governed record around it.
- 01
Source and release. The deployed revision stays identifiable instead of becoming an untraceable upload.
- 02
Ownership and policy. The workspace keeps who owns the application, how it moves between environments, and which approvals apply.
- 03
Runtime state. BUILDING, READY, and failure states remain distinct; SpringRoll does not report a live application before the runtime does.
- 04
Audit history. Registration, deployment, approval, promotion, rollback, and retirement remain attributable in the tenant record.
Build with Codex or Claude. Ship quickly with SpringRoll.
Use the detailed guide for the clean-account path, or create a workspace and connect the coding agent you already use.