Cost is a core design constraint
Usage is calculated in 2-minute micro-buckets and containers automatically sleep when idle — because the most affordable resource is one that isn't running. Billing is integral to our product, not an afterthought.
About
Hubfly space is a container platform designed around a single core idea: a project should be a complete boundary. Everything your application needs to run — networking, storage, image registries, team access, and billing — stays in one place.

Most cloud providers force you to build your stack out of disconnected pieces. You start with compute, piece together networking, attach block storage, configure a container registry, wire up permissions, and then try to decipher the bill. It works, but almost nobody can keep all that complexity in their head.
We built Hubfly space around the concept of a project. Containers inside a project communicate privately, share persistent volumes and custom domains, inherit environment settings, and bill against a single clear balance. Scaling to production is as simple as switching a tier, not rebuilding your infrastructure.
Under the hood, your applications run as cells — native Linux processes isolated by cgroups v2 and custom namespaces, without a heavy container daemon in the way. That's what allows our scale-to-zero model to be cheap enough for a generous free tier, and why tenant isolation is enforced directly by the Linux kernel.
Principles
Usage is calculated in 2-minute micro-buckets and containers automatically sleep when idle — because the most affordable resource is one that isn't running. Billing is integral to our product, not an afterthought.
Your services start completely unreachable. Opening a port, attaching a domain, or bringing up a tunnel is always an explicit action you take, never a default you have to undo.
Deployments, storage volumes, custom domains, container images, team permissions, and billing live together inside your project. There's only one place to check when debugging.
Workloads run in dedicated namespaces with root remapped to an unprivileged host UID and Linux capabilities dropped by default. Security is enforced far below the control plane.
Architecture
Hubfly space isn't a monolith. Each component does one job exceptionally well, working together to deliver a reliable cloud experience.
hubfly-dashboardapiHandles control plane operations, RPC APIs, projects, organization RBAC, and billing.
hubcellGo · cgroups v2 · ext4Lightweight daemonless container runtime, process supervision, and terminal gateway.
hubfly-cliGo · Bubble TeaCLI for deploys, Compose stacks, SSH sessions, and encrypted local-to-cloud tunnels.
hubfly-builderGo · SQLiteAuto-detects project runtimes and handles source-to-image container builds.
hubfly-proxyGo · SQLitePowers regional edge routing, automatic TLS certificates, SWR caching, and firewall rules.
hubfly-schedulerGo · PostgresManages container state reconciliation, usage metering, and billing ledger deductions.
hubfly-filesGo · ReactIn-browser file manager, code editor, and archive utility for persistent storage volumes.
hubfly-sdkTypeScript · GoTyped programmatic client libraries for controlling platform resources.
Who it is for
With 360 free shared hours monthly and automatic sleep mode, your personal projects can stay live online costing nothing until someone visits them.
Dedicated 24×7 containers, load balancing, automated health checks, audit logs, and granular access tokens built for critical workloads.
Manage courses, terms, student assignments, and instant join codes with strict spending limits so student projects never exceed allocated budgets.
Have questions about your workload?
Tell us what you're running and we'll give you an honest answer on whether Hubfly space is the right fit — even if it's not.
Talk to our teamGet started
No credit card needed for the free tier. Push your repository, watch it build in real time, and monitor your usage as it happens.