Deployment

Ship Solana programs through Shipline, and ship web services to Vercel or Railway, without leaving the workspace.

Shipline (Solana programs)#

Shipline runs your Solana program deploy as a single recorded timeline instead of a loose loop of editor → CLI → explorer → retry. Every step, exit code, program ID, and explorer link is captured in one place:

  • Preflight, check workspace readiness, wallet funding, and RPC target
  • Build & test, run the Anchor build and test suite with output kept in the timeline
  • Priority fees, record the fee policy before anything is signed
  • Deploy & confirm, ship to devnet, capture the program ID, and confirm on-chain
  • Verify & export, verify the deployment and export the IDL with explorer links

Shipline is devnet-first: timeline execution targets devnet, and mainnet runs are intentionally blocked in the current slice. When your program is proven on devnet, the mainnet deploy is a deliberate manual step.

Vercel (web frontends)#

Deploy frontend projects to Vercel with a single click:

  • Connect once by linking your Vercel account in Settings > Integrations
  • Deploy by clicking the deploy button in the Command Drawer
  • Monitor deployment status and logs directly in DAEMON

DAEMON automatically detects your framework (Next.js, React, Vite, static sites) and configures the build settings.

Railway#

Deploy backend services and databases to Railway:

  • Connect once by linking your Railway account in Settings > Integrations
  • Deploy by selecting your project and clicking deploy
  • Monitor logs and service status in DAEMON

Use Cases

  • Node.js API servers
  • Database provisioning
  • Background workers
  • Full-stack apps (Vercel frontend + Railway backend)

Workflow#

A typical deployment workflow in DAEMON:

  • Write and test your code in the Monaco editor
  • Run tests with an AI agent or the terminal
  • Commit changes via the visual git panel
  • Ship: Shipline's devnet timeline for Solana programs, one-click for Vercel or Railway

The entire cycle from code to production happens inside one console. Deployment settings are stored per-project and persist across sessions.