Architecture and providers

Spine Cloud accepts deployments from the CLI and uses a management API and execution agent to run applications. This map shows logical connections without credentials or internal addresses.

CLI → Management API ← Dashboard
Execution agent → Management API → Identity and storage
Execution agent → Application
Visitor → Portal relay → Tunnel → Application

Components and providers

Component	Role	Recorded environment
Spine CLI	Connect an account, build, and request deployment	Preview development CLI on the developer’s machine
Dashboard	Account approval, applications and deployment history	React on Vercel
Management API	Authentication, ownership, jobs and status	Railway
Identity and storage	Account authentication, metadata and private artifacts	Supabase
Agent	Poll, verify, run and report	Oracle Cloud Infrastructure
Portal	Route public HTTPS traffic to the app	Self-hosted relay and tunnel

Deployment and traffic

Approve a one-time code, then run spine deploy. The API checks ownership and artifact format, encrypts the artifact and stores it privately. The agent polls over authenticated HTTPS, claims the job, decrypts and verifies its hash and format, and starts the app. Internal health and public HTTPS checks precede the success record and address. A queued request alone does not establish that the app is running.

Developer considerations

Consider database connectivity, secret rotation, and sensitive information in application logs.