Deployment modes¶

A deployment mode determines who operates Loco and whether the platform serves one customer or multiple customers. Application environments such as staging and production exist within that platform.

Loco's product direction includes three modes. Dedicated provisioning and a packaged self-hosting release are not documented as generally available in this repository. Confirm availability with the project maintainers before selecting a managed installation.

Multi-tenant SaaS¶

Connect to Loco's managed API and dashboard. Your team works with organizations, workspaces, and applications. Loco operates the platform's control plane and Kubernetes infrastructure.

loco login
loco web

See architecture for how the control plane and regional components fit together.

Dedicated¶

A dedicated installation gives one customer a Loco-operated platform. Use the installation's API and dashboard URLs. Instance provisioning, capacity, and operational responsibilities need an agreement with the operator; these docs do not define pricing or service guarantees.

Self-hosted¶

Your team operates the control plane, Kubernetes clusters, networking, certificates, registry, database, and observability. Your team also owns upgrades, backups, capacity, and incident response.

Start with the self-hosting guide. The repository contains Helm charts, environment configuration, and a local development setup; it does not provide a complete production installation command.

Environments within a mode¶

Staging and production are application targets, independent of deployment mode. A dedicated or self-hosted installation can also have staging and production environments. Keep each instance's credentials and endpoints separate. See environments.