Cloider concepts
The concept pages explain how Cloider works underneath the buttons and commands. Read them once and the rest of the documentation makes more sense: why a paused cluster still costs a little, why an API token can't invite members, or why a resource has both a name and an id.
At a glance
| Concept | In one sentence | Page |
|---|---|---|
| The platform | Six products (apps, Kubernetes, databases, object storage, container registry, domains) on shared, managed infrastructure, used from five tools | How Cloider works |
| Accounts and roles | Resources belong to an account; people reach it as the Owner or as Admin or Restricted members | Accounts and roles |
| Billing | Usage is metered continuously, priced per month, prorated to the second and invoiced monthly | Billing model |
| Lifecycle | Every resource moves through statuses such as Creating, Ready, Paused and Terminating | Resource lifecycle |
| Security | Isolation per account, HTTPS everywhere, hashed tokens, trusted sources and a shared responsibility model | Security |
How Cloider works
The platform, the serverless model and how each product runs.
Accounts and roles
Users, accounts, members, roles and the full permission matrix.
Billing model
What is metered, how it is priced, the trial and invoices.
Resource lifecycle
Statuses, pausing, deleting, names, labels and ids.
Security
Isolation, TLS, tokens, trusted sources and who is responsible for what.
Related reference
- Pricing: every price kind and unit.
- Limits and quotas: name lengths, per account maximums and sizes.
- Status values: every status, per product.
- Glossary: every term used in these docs.