Takosumi and Takosumi Cloud
These docs use two names so the software and the official service are not confused.
| Name | Meaning |
|---|---|
| Takosumi | the AGPL-3.0 software published in this repository |
| Takosumi Cloud | the official hosted service at app.takosumi.com |
What the software provides
Takosumi OSS includes:
- plan, apply, state, outputs, and audit records for Git modules
- secure storage and runner delivery for provider connections
- a dashboard, API, CLI, and sign-in
- records for endpoints and permissions between deployments
The module and provider decide which cloud is used. Takosumi OSS does not require one cloud account or provider.
What the operator decides
Two installations of the same software can differ in:
- storage capacity, usage limits, and backup retention
- whether usage is only recorded or also billed
- updates, incident response, support, and SLA
Check an endpoint instead of guessing from an edition name.
curl https://takosumi.example.com/.well-known/takosumiAn authenticated client can also read /v1/capabilities.
What Takosumi Cloud adds
Takosumi Cloud is an official operation of the OSS software. It adds managed service implementations, official capacity, pricing and payment, support, SLA, and abuse controls.
Those are not general OSS contracts. Use the Takosumi Cloud documentation for prices and limits.
Cloud code consumes OSS contracts. The OSS software does not depend on private Cloud code or Stripe.
Takos is a separate product. Its self-hosted product worker does not embed Accounts, deploy-control, the Dashboard, or the runner; it connects to a Takosumi endpoint as an external client.
When you self-host
When you operate Takosumi yourself, you become the operator described above. You manage software updates, secrets, databases, runners, and backups.
Read Self-hosting for topology choices and published setup procedures. Repository-local operator runbooks are not customer-facing product documentation.