Documentation
Hubfly space documentation
Run Cell workloads and Box virtual machines, store files and media, run managed databases and realtime WebSocket servers, and send, receive or route email. Choose a product guide, then use the API, SDK, or CLI reference when you need to automate it.
The four documentation hubs
The documentation is split into four hubs. Each one has its own navigation, so you only see the pages that belong to what you are working on. Switch between them using the tabs at the top of every page.
Pick a starting point
These are the ways to get a service running. Start with the quick start if you are evaluating the platform, or go straight to the workflow that matches how your service is already built.
Operate what you shipped
These guides cover running Cell workloads and using the Box virtual machines and the managed Storage, Databases, Realtime and Mail products. Each product has its own setup, operation, and API pages.
Container runtime tiers
Every container runs on one of two tiers. The tier decides how the container is scheduled and whether it is allowed to sleep while idle.
| Tier | Default sizing | Runtime behaviour | Best for |
|---|---|---|---|
shared | 0.3 vCPU · 256 MB RAM · 5 GB storage | Shared compute pool, auto-sleep enabled | Development, staging, internal tools, proofs of concept |
dedicated | 1.0 vCPU · 512 MB RAM · 20 GB storage and up | Always on, optional vertical auto-scaling | Production web apps, APIs, databases, anything with an SLA |
A common split
Getting help
Press ⌘K (or Ctrl K) anywhere in the documentation to search every page across all four hubs. If something is wrong, unclear or missing, emailsupport@hubfly.space or reach the team fromthe contact page. Live incidents and maintenance windows are published on the status page.