Skip to content
Coro Docs

Deployment modes

Coro must work on an engineer laptop and coordinate across a distributed team. Mode changes how durable state lives, where webhooks terminate, and how dashboards authenticate.

Solo

  • Runner, dashboard bundle, SQLite (~/.coro/state.db) on one host.
  • Event delivery often poll-oriented depending on SCM plugin capabilities—fine for demos and lone contributors without public ingress.

Best when you’re proving value before introducing shared infrastructure.

Solo+ cloud-tracked (roadmap wording)

Coming enhancements let solo installs opt into telemetry / account linking hosted by Coro Cloud without promoting the job runtime off your machine—the exact SKU surfaces on release notes.

Treat today’s narrative as “local execution with optional forthcoming cloud bookkeeping.”

Team (hybrid control plane)

  • Each developer retains a runner, but authoritative job coordination, Postgres state, websocket fan-out, and org secrets distribution flow through shared services.
  • Webhooks terminate in managed endpoints with signature validation—no ngrok juggling for SCM apps.

Sizing, security, and operations live in Hybrid mode guide.

When choosing a posture, revisit Plugins and Job lifecycle to understand webhook vs polling nuances.