What a qube is
A qube is one resource your project needs.
Examples of qubes:
- A domain qube registers and renews a domain on your behalf.
- A DNS qube holds your DNS records.
- An email qube lets you send transactional email from your domain.
- A database qube runs a managed database that your app can connect to.
- A container qube runs a Docker image with a public URL.
- An analytics qube counts visitors to your site without tracking them.
- A monitoring qube watches your services and alerts you when something breaks.
A project is a collection of qubes that belong together. When you set up “my SaaS startup”, that project might have a domain qube, a DNS qube, an email qube, a database qube, and a container qube, all wired up so they reference each other automatically.
Why we use the word “qube”
Section titled “Why we use the word “qube””Most platforms talk about “services”, “resources”, or “addons”. Those words have ten different meanings depending on who you ask. We picked something neutral so we could give it one clear meaning here. A qube is one thing your project depends on.
Qubes vs widgets
Section titled “Qubes vs widgets”Two related ideas you will see in the dashboard:
- Qubes are resources you actually use. They cost money. They show up in your invoices.
- Widgets are read-only views of your data: the analytics chart, the most recent emails, the list of failing checks. They live in the right sidebar and are toggled, not provisioned.
If something costs money, it is a qube. If it just shows you data, it is a widget.