Everything klickops does, one page at a time.
Each page covers one thing: what it is, when you'd use it, how to do it, every setting, and the gotchas.
Pointing an agent at this? Start at llms.txt or append .md to any page URL for its markdown source.
Start here
Workloads
- Apps A container you deploy, scale, and put on a domain. The starting point for everything else in a project.
- Databases A managed PostgreSQL or Valkey instance that lives inside your project, backed up on a schedule, and reachable from your apps by name.
- Buckets S3-compatible object storage for files an app should not keep on its own disk.
- Volumes Disk that survives a rollout, mounted into an app at a path you choose.
- Scheduled jobs A container that runs on a schedule, does its work, and exits.
Networking
Operations
- Backups and recovery Scheduled recovery points for a project, and how to get one piece back without disturbing the rest.
- When something is wrong The handful of failures that account for most of them, what each looks like, and what to do.
- Alerts and notifications Being told when a workload is in trouble, and choosing where that message lands.
Configuration
Organization
- Members and roles Who is in your organization and what each of them may do.
- Plans and costs What you are charged for, where to see it, and how the plan's limits relate to the bill.
- Getting help Ask the klickops team a question from inside the product. We can already see your projects, so you never have to paste a log.
- Project and organization settings The two settings pages, what each one changes, and the three actions there is no undo for.
Tools
22 pages, all reviewed against the current release.