Hub Cloud
One operational layer for every small app. Deployment, runtime, access, releases, environment variables, logs and a shared home for the team, in one product.
The path from code to a tool people can use. A small app needs a host, a URL, secrets, access, updates, logs and someone who remembers where it lives.
- 1
The CLI sends the code or connects the repository.
- 2
The org's host builds and runs it.
- 3
Hub gives the app a URL and applies its access rule.
- 4
The dashboard and the CLI keep it operable after launch.
- 5
The workspace makes it findable for the rest of the team.
What is in it.
A folder, a Dockerfile, a compose file or a GitHub repository, built on your org's host.
Access →Every app starts behind the org login. One command makes it public.
Instances →Production, staging or a customer-specific deployment from the same app.
Workspace →Markdown pages at the org root, one of them listing every app.
Private host →A dedicated Docker environment per org, with its limits stated.
For agents →A coding agent runs the same CLI and returns the URL.
Security →What is isolated, which credentials exist and where the boundaries are.
How it works →The deploy, step by step.
FAQ →Short answers, checked against what runs today.
The daily controls are already there.
$ hub deploy $ hub env set crm STRIPE_SECRET_KEY $ hub logs crm --build $ hub shell crm $ hub rollback crm
Every deploy and configuration change is a numbered release. The dashboard shows the same: instances, releases, build logs, service logs, a browser shell, environment names (never values) and members.
Coming next: custom domains, backups, selected-people access, pull-request previews.