Launch
Stage, verify, and ship Solana programs, web frontends, and persistent services.
Choose the target#
| Target | Daemon path | Current boundary |
|---|---|---|
| Solana program | Shipline | Recorded, devnet-first deployment timeline |
| Frontend or static site | Vercel integration | Framework detection, deployment status, and logs |
| API, worker, or database | Railway integration | Service deployment, status, and logs |
Preflight#
- Run the project build, tests, and typecheck before opening the launch flow.
- Review uncommitted changes and confirm the branch you intend to ship.
- Verify environment bindings, wallet funding, RPC target, and deployment account.
- Record the expected program ID, domain, or service endpoint before execution.
Shipline for programs#
Shipline captures preflight, build, test, priority-fee policy, deploy, confirmation, and verification in one timeline. The current automated path targets devnet. A mainnet program deployment remains a deliberate manual step after the devnet artifact is proven.
Web and service deployments#
Connect Vercel or Railway in Settings, select the project, and start the deployment from the command drawer. Daemon keeps deployment status and logs beside the project so a failed build can be traced back to the exact workspace state.
Verify the result#
- Confirm the on-chain program or public URL independently.
- Exercise the primary user flow and one failure state.
- Check runtime logs and environment bindings after the deployment becomes ready.
- Keep the resulting signature, program ID, or deployment URL with the session receipt.