How Drasken Cloud is organised
Organisations, projects and resources on Drasken Cloud — who can see what, where billing happens, and how resources are kept apart.
On Drasken Cloud, an organisation holds your team, your billing and your limits; inside it, projects hold the apps, jobs, databases, volumes and domains for one piece of work, kept apart from your other projects. You choose a project in the console's project picker, and every page under Public Cloud shows that project's resources.
What is an organisation?
An organisation is usually your company or team. It has its own members and their roles, its own billing and invoices, and its own limits. You can belong to several organisations and switch between them in the console; each one is billed separately.
What is a project?
A project groups the resources for one product, service or environment — for example Payments API or Website staging. Resources in a project can reach each other privately: an app reaches another app at its private address, and a database is reachable from the project's apps. See Projects.
What can a project hold?
| Resource | What it is |
|---|---|
| App | A container image running as a website, an API or a background worker, on one or more instances |
| Job and cron job | A task that runs to completion, once or on a schedule |
| Database | A managed MySQL, PostgreSQL or Valkey database |
| Volume | A disk for an app's data that survives restarts and releases |
| Backup and snapshot | Copies of databases and volumes |
| Domain | Your own domain served by one of your apps (coming soon) |
| Environment group | Settings and secrets shared by several apps and jobs |
| Registry connection | Credentials to pull private images |
Uptime monitors belong to the organisation and can be linked to a project.
What does it cost?
You pay for what runs, by the hour, never more than the monthly price of each resource. An invoice with GST is issued for each calendar month. See How billing works and Pricing.
Last updated on