01
AI agents and automation
Give every agent, workflow, or autonomous task an isolated cloud boundary with a revocable machine identity and controlled spend.
Developer platform
Your product. Their isolated cloud.One Hubfly space parent account.
Create API-first sub-accounts for customers, agents, tools, and managed workloads. Every tenant gets its own wallet, projects, infrastructure boundary, audit context, and machine credentials—without another human login.
Project workflow01 / 03
01
SourceIsolated wallets
02
ControlTenant-bound API keys
03
ReleaseOne-level tenancy
Hubfly space projectNetwork · volumes · domains · team access
One project model
Built for platforms
Turn Hubfly space into the infrastructure layer behind your product.
Sub-accounts are designed for developers who need to provision and operate cloud environments on behalf of software—not for adding another person to a team.
02
SaaS customer environments
Provision dedicated projects, services, volumes, domains, and credentials for each customer without creating human Hubfly space users.
03
Preview and test platforms
Create disposable tenant environments for branches, QA runs, integration tests, or customer demos while keeping production resources separate.
04
Managed hosting
Operate infrastructure for clients from one parent account while preserving wallet, resource, and audit isolation per client.
05
Labs and sandboxes
Create controlled environments for workshops, coding labs, and internal developer portals with explicit lifecycle boundaries.
06
Platform integrations
Build control panels, deployment products, and vertical developer tools on Hubfly space using platform and tenant-scoped credentials.
Architecture
A real tenant boundary, not a label on shared resources.
Parent and tenant model
Your parent account
Personal account or organization
Customer A
sub_…
Automation
sub_…
Preview fleet
sub_…
wallet + projects
wallet + projects
wallet + projects
01
Dedicated wallet
Fund each tenant from the parent account. Usage is charged against the same canonical balance that the dashboard and Scheduler enforce.
02
Isolated resources
Projects and their containers, volumes, builds, domains, registry assets, networking, logs, and runtime sessions stay inside the tenant.
03
Durable machine identity
Issue multiple hfsk_ keys, rotate without downtime, revoke immediately, and inspect safe prefixes and last-use metadata.
04
Principal-aware audit trail
Machine activity is attributed to the service principal that performed it—not incorrectly to the human who created the key.
05
Tenant enforcement first
Hubfly space resolves and verifies the effective sub-account before project authorization, preventing guessed IDs and header substitution.
06
Limits and lifecycle
Control tenant count, active keys, projects, spend, and API rate; suspend, resume, rotate, and close through durable lifecycle actions.
Authentication
Use the credential that matches the job.
The creator is not the runtime actor. Hubfly space records durable service principals and stores only credential hashes; plaintext secrets are returned once.
| Credential | Prefix | Tenant scope | Use it for |
|---|---|---|---|
| Sub-account key | hfsk_ | One tenant, fixed at creation | Operate supported resources inside that tenant |
| Platform key | hfpk_ | One personal or organization parent | Manage sub-accounts and target operations with X-HubFly-Subaccount |
| Personal token | hf_ | The issuing human and optional projects | Existing personal and CI workflows |
Sub-account key
- Prefix
- hfsk_
- Tenant scope
- One tenant, fixed at creation
- Use it for
- Operate supported resources inside that tenant
Platform key
- Prefix
- hfpk_
- Tenant scope
- One personal or organization parent
- Use it for
- Manage sub-accounts and target operations with X-HubFly-Subaccount
Personal token
- Prefix
- hf_
- Tenant scope
- The issuing human and optional projects
- Use it for
- Existing personal and CI workflows
Tenant-bound operation
Authorization: Bearer hfsk_…
GET /api/v1/projectsThe key is permanently bound to its tenant. It cannot select or escape to another sub-account.
Platform operation
Authorization: Bearer hfpk_…
X-HubFly-Subaccount: sub_…
GET /api/v1/projectsThe platform key belongs to the parent and explicitly selects an accessible tenant for resource operations.
Coverage
Operate the core cloud surface for every tenant.
Deploy
Projects, containers, builds, deployments, Compose, logs, exec, terminals, and tunnels
Persist
Volumes, scoped file sessions, registry images, credentials, tokens, and scanning
Connect
Subdomains, custom domains, ports, load balancers, firewall, redirects, TLS, and caching
Control
Wallet funding, balance enforcement, usage, audit attribution, suspension, and closure
Deliberate boundaries: GPU wallets and GPU instances, user-owned GitHub OAuth connections, educational membership, personal profile/session APIs, invitations, and payment-method administration are not available to sub-account machine principals.
Lifecycle
Safe from provisioning through retirement.
Every control-plane mutation is designed around explicit authority, idempotency, and recoverable rotation—not a single permanent root secret.
01
Create
Create the tenant with a name and optional parent-scoped external reference.
02
Fund
Transfer paid parent balance into the isolated wallet using an idempotency key.
03
Connect
Issue a tenant key, save the one-time secret, and configure the SDK, CLI, or your service.
04
Operate
Create projects and run containers, builds, volumes, domains, registry, logs, exec, tunnels, and networking.
05
Rotate
Create a replacement key, move traffic, verify last use, and revoke the old credential.
06
Retire
Stop and delete resources, suspend access immediately, or close an empty tenant after its balance checks pass.
Wallets
Fund tenants deliberately. Keep billing boundaries visible.
Transfers atomically debit the parent’s paid balance and credit the tenant in micro-USD. Promotional credit never transfers. Stable idempotency keys prevent a network retry from funding twice, and immutable transfer records preserve the resulting balances for audit.
- $1.00 equals 1,000,000 micro-USD
- Parent and tenant balances lock in deterministic order
- Scheduler charges the same balance shown in the dashboard
- Suspension blocks new mutations but does not automatically stop existing resources
- Closure returns current eligible paid funds after resource and balance checks
Atomic transfer
Parent paid balance
− $25.00
Tenant wallet
+ $25.00
one transaction · one idempotency key · immutable record
Start building
Dashboard when you want it. API when your product needs it.
Create in the profile
Create tenants, fund wallets, rotate keys, and suspend access from Profile → Sub-accounts.
Open dashboardIntegrate the REST API
Use the parent control plane to provision tenants, then operate resources with a tenant or platform key.
API guideUse TypeScript or Go
Typed subaccounts and platformKeys modules plus a client-level subaccountId option are available in both SDKs.
SDK docsDeveloper platform
Build your multi-tenant product on Hubfly space.
Start with one isolated sub-account, connect it with a machine credential, and scale the same model across customers and workloads.