Service Lasso Docs
Service Lasso discovers, configures, runs, observes, and updates local services from declarative service.json manifests. This is the canonical reader documentation for Core and its components. Component repositories own implementation and code-governing specifications; reader guides belong here.
Choose your starting point
First useful result: Getting started → Beginner — Todo app → Intermediate — Make the Todo durable → Advanced — Go Todo API → Advanced — Add Zitadel SSO to Todo → Advanced — Package Todo as a desktop app → Advanced — Provision secrets as RAM files → Configure and recover → Package it. Optional visual demo: Quick start.
Copy a task for your agent or connect MCP.
| I want to… | Start here |
|---|---|
| Run services | Run and manage services for first start, health, logs, recovery, and backup guidance. |
| Build a service | Service authoring overview for the required five-step authoring sequence. |
| Integrate into an app | Use Service Lasso in your app to choose a reference app, inventory, routing, SSO, and package output. |
| Look up a reference | Technical reference for the stable manifest, CLI, API, MCP, state, endpoint, and workflow contracts. |
Component guides
Service Admin and template guides · Use the default stack · Service Admin UI guide · Capture status
Documentation ownership and migration records remaining source migrations and packaged help copies.
Key concepts
Read Key concepts for the service manifest, servicesRoot, workspaceRoot, and Core/app/service ownership boundaries.
First time with Service Lasso
- Read What is Service Lasso? for boundaries and the repo ecosystem.
- Choose how to run it: run the checked-in baseline, use a reference app, or package an app-owned inventory.
- Follow the Quick start.
- Complete first-run setup when the runtime enters setup mode.
- Use the Service Catalog to find the services in the baseline or app inventory.
Documentation boundaries and status
Operational pages explain an operator task and link to the contract that governs it. Reference pages define the exact API, schema, or persistence contract and should not be read as step-by-step runbooks. Plans, draft proposals, historical reviews, and release-specific evidence remain explicitly labelled and are not statements of current shipped behavior.
See the documentation map for the complete page inventory, primary navigation home, classification, and intentional unlisted status. See Contribute and maintain to build or maintain this site.