Documentation
What the platform does, how access is organised, and how to get something running. Written against what exists today — pages describing work in progress say so at the top.
Start here
What the platform is, and the shortest path to something running.
Working with projects
How access, ownership and billing are organised.
- Projects and rolesHow access, ownership and namespaces are organised, and what each role can actually do.
- WorkloadsWhat a deployed workload is, what you can change after it is running, and what is fixed on purpose.
- Logs and shell accessReading a workload's logs, getting a shell inside it, and what the platform deliberately will not let you do.
- Object storageEach project gets a bucket. How to put things in it, how to mount it into a workload, and the one way it is not a disk.
- Public endpointsGiving a workload a URL on the internet, and why that URL still asks who you are.
- Quotas and limitsWhy a workload can be accepted and still not start, and where to look when it does not.
Build on it
Driving the platform from your own code.
Account
Credits, security, and the record of what happened.
- Credits and billingWhat credits are, the three ways to get them, and what happens to a running workload when they run out.
- Account securityTwo-factor authentication, recovery codes, passwords and SSH keys — and what each one protects.
- Audit logEvery change to your project, who made it, and whether it worked — including the attempts that did not.