Deploy Anything.Control Everything.

A project-based container platform to run apps, APIs, and AI workloads with full infrastructure control, no server management required.

Git, image, template, and compose deploysPrivate project networkingDomains, load balancers, volumes, and HubTunnels

Deploy anything

Built for the runtimes teams already use.

Single containers, full compose stacks, GPU workloads, or static sites Hubfly space runs it all inside private project networks.

Next.js
React
Vue
Nuxt
SvelteKit
Remix
NestJS
FastAPI
Django
Laravel
Express
Astro
Angular
Next.js
React
Vue
Nuxt
SvelteKit
Remix
NestJS
FastAPI
Django
Laravel
Express
Astro
Angular

Compose stacks

Deploy full stacks, not just containers.

Or import your docker-compose.yml in the visual builder. Every service communicates privately over the project network.

Explore all stacks

Platform Model

One project. Every layer.

Deployments, networking, storage, team access, and billing live inside a single project not spread across separate tools.

Deployment model

Four paths, one project.

Git deploy

GitHub repo → build → image → run

1Connect repo2Detect runtime3Build image4Deploy
Docker image

Any registry, public or private

1Pull image2Configure3Set env vars4Deploy
Template

PostgreSQL, Redis, Mongo & more

1Pick template2Review config3Deploy
Compose stack

Multi-service YAML or visual builder

1Import YAML2Wire services3Deploy stack

Hubfly space Project

Private network · Volumes · Domains · Team

Private networkingCustom domainsLoad balancerVolumesEnv varsTeam access

Powerful CLI

Deploy locally. Tunnel privately. Automate the rest.

The Hubfly space CLI is built for teams that want fast deploys from the terminal, secure access to internal services, and enough scripting support to move the routine work out of the dashboard.

Deploy from your machine

hubfly deploy

Build locally, upload the image to Hubfly space, and keep redeploys tied to the same service through `hubfly.build.json`.

Reach private services

hubfly tunnel create

Open short-lived local access to Postgres, Redis, internal APIs, and admin tools without exposing public ports.

hubfly-cli

$ hubfly deploy --project edge-api --region eu-west-1 --yes
Using hubfly-builder v1.7.1
Building image locally from ./hubfly.build.json
Uploading image to the regional builder
Deployment succeeded · bound container updated
$ hubfly tunnel postgres 5432 5432
Tunnel established · localhost:5432 -> postgres:5432

AI integration

Give your coding agent the real Hubfly space deployment model.

Install one portable Markdown skill so your AI agent can inspect the repository, reconcile local and cloud configuration, review the Dashboard deployment plan, and follow the real rollout after you approve it.

Codex · Claude Code · Cursor · Agent Skills-compatible tools

hubfly-cli / SKILL.mdapproval required
01

Inspect

Read the app and its schema-v2 Hubfly space manifest without exposing secrets.

02

Reconcile

Compare managed local fields with the bound cloud container.

03

Plan

Review Dashboard's revision-guarded plan and destructive operations.

04

Follow

After approval, track the deployment session to its real terminal state.

$ “Inspect this app and deploy it with Hubfly space.”
→ Build plan validated
→ Waiting for your approval before deploy

Developer sub-accounts

Build your product on isolated Hubfly space tenants.

Create customer, agent, or automation environments from one parent account. Every tenant gets its own wallet, projects, resources, audit context, and rotatable machine credentials.

Parent platform

hfpk_… + X-HubFly-Subaccount

3 active tenants

Customer A

sub_…

Wallet

$42.18

Agent fleet

sub_…

Wallet

$18.70

Preview API

sub_…

Wallet

$7.25

Scoped keys

Tenant isolation

Machine audit

Comparison

Built between typical PaaS and cloud infrastructure.

More control than a typical app host. Less infrastructure work than wiring raw cloud services yourself.

Typical PaaS

Hubfly space

Hubfly space

Cloud Infra

Deployment paths

Hubfly space

Git, image, template, compose stack

Typical PaaS

Git push only

Cloud Infra

Manual image setup

Private networking

Hubfly space

Per-project, automatic

Typical PaaS

Shared or not available

Cloud Infra

VPC setup required

Persistent storage

Hubfly space

Managed volumes, tiered performance

Typical PaaS

Limited or add-on only

Cloud Infra

Block storage, fully manual

Multi-service stacks

Hubfly space

Compose with visual builder

Typical PaaS

Single container focus

Cloud Infra

Possible but no tooling

Custom domains + SSL

Hubfly space

Included, custom proxy templates

Typical PaaS

Usually included

Cloud Infra

Configure Nginx, Certbot yourself

Load balancing

Hubfly space

Built-in, weighted routing

Typical PaaS

Basic only

Cloud Infra

Provision a separate LB

Team permissions

Hubfly space

5 role templates, 13 permissions

Typical PaaS

Basic or no team model

Cloud Infra

IAM roles, complex setup

GPU workloads

Hubfly space

Built in, same platform

Typical PaaS

Not available

Cloud Infra

Separate GPU instance

Private tunnel access

Hubfly space

HubTunnels via CLI

Typical PaaS

Not available

Cloud Infra

SSH + port forwarding

Usage-based billing

Hubfly space

Per vCPU/GB/hr, free shared tier

Typical PaaS

Fixed tiers, often overpriced

Cloud Infra

Per instance, hard to predict

Fully supported
Partial / manual
Not available

Pricing Snapshot

Usage-based pricing, directly tied to resources.

Full pricing

CPU

$0.004

per vCPU / hour

RAM

$0.002

per GB / hour

Storage

$0.00001536

per GB / hour

Shared tier

360h

free runtime monthly + 1GB storage

Start With Structure

Build, deploy, route, store, and operate in one product.

Hubfly space brings deployments, private networking, storage, billing, domains, tunnels, and GPU workflows into one coherent model.