Hubfly spaceDocs
Console

Project transfer

A transfer gives a whole project to another Hubfly space account or to an organization. Containers, volumes, Boxes, databases, buckets, mail, domains and addresses all move with it, in the same region. Workloads keep running and their URLs keep working: only the owner, the bill and the people with access change.

Moving between your own accounts

Moving a project from your personal account into one of your organizations, or between two organizations you own, is a transfer too: send the offer to your own email address and accept it into the other account.

How a transfer works

  1. The sender previews the transfer, confirms with the project name and a code sent by email, and offers the project to an email address.
  2. Hubfly space emails a single-use link to that address. The offer is valid for 7 days.
  3. The recipient signs in with that address, chooses their personal account or an organization, reviews the cost and accepts.
  4. The owner changes at the next full hour (UTC). Until then the sender keeps paying for the project.

The project's History keeps a record of every transfer.

Who can send and receive

ActionWho
Send a personal projectIts owner.
Send an organization projectAn owner of the organization. The organization must be active.
Accept into your accountThe person whose email address received the offer, with a verified email address.
Accept into an organizationThe recipient, if they are an owner of that organization or hold a role that can both create projects and manage billing.

Sending, accepting, declining and cancelling need a signed-in dashboard session. API keys, access tokens and operators acting on your behalf cannot do them. Reading previews, offers and status works with a personal access token.

Send a project

Open the project, then Settings → Danger zone → Transfer project. The preview lists what moves, which credentials stop working if you lose access, and anything that blocks the transfer right now. Enter the recipient's email address, type the project name and enter the 6-digit code Hubfly space emails you. The code is valid for 15 minutes.

Hubfly space answers the same way whether or not the address has an account, so a transfer never reveals who uses Hubfly space. If the recipient has no account yet, they can sign up with that address and then open the link.

Accept a project

Open the link from the offer email. You see who sends it, each project with its hostnames, custom and mail domains and workloads, and its direct members. Choose where the project goes, then review:

  • Balance: the receiving account needs about 72 hours of the project's running cost.
  • Plans billed to you: recurring plans, such as mail domains, that you pay for from the handover.
  • Members: direct members lose access unless you keep them.
  • Revoked credentials: what stops working at the handover.

The owner change

After you accept, Hubfly space runs the transfer as a job. You can follow it on the project card and in its History.

StepWhat happens
Pausing changesConfiguration changes and deploys are paused. Workloads keep running and stay reachable.
Settling billingWaits for the next full hour and for that hour's usage to be billed to the sender.
Re-checking eligibilityRuns every check again: the sender must still own the project and the receiving account must still qualify.
Revoking regional credentialsStorage access keys and mail sending credentials of the project stop working, and open file sessions close.
Changing ownerThe project, its domains and its addresses move to the new owner in one step.
Updating regional servicesMail, route protection and SQLite (libSQL) database signing keys are updated for the new owner.
Sending notificationsBoth sides get an email.
Resuming changesThe new owner can change and deploy the project.

If something fails before the owner changes, Hubfly space rolls the transfer back and the project stays with the sender. Revoked credentials stay revoked; create new ones.

What changes for the new owner

  • Billing: usage up to the handover hour is billed to the sender, everything after it to the new owner.
  • Monthly Cap: the project's spending cap starts a new period for the new owner.
  • Free tier: free-tier containers count against the new owner's free tier.
  • Deploys from Git: automatic deploys are turned off, because the repository connection belongs to the sender. Link the repository again.
  • Environment variables: every value, secrets included, becomes readable by the new owner.

Change secrets the sender has seen

Root passwords and SSH keys inside Boxes, database passwords and other secrets the sender has seen stay known to them. Change them after the transfer.

Credentials and members

Direct members of the project are removed at the handover unless the recipient keeps them. Organization roles of the receiving organization apply from then on. Both previews list exactly which credentials will be revoked.

CredentialAt the handover
Registry tokens, database access tokens, realtime keys, route access keys and challenge bypass keysRevoked when the person who created them loses access. If the sender chose to rotate all credentials when making the offer, all of them are revoked.
Storage S3 access keys, mail SMTP logins and mail REST keysAll revoked before the owner changes, whoever created them. Create new ones afterwards.
Deployment webhook URLsTurned off. The new owner turns them on again and gets a new URL.
Saved registry logins and Git credentials, database export links, webmail sessionsRemoved or ended.

What can block a transfer

The preview names each blocker and what to do about it. The common ones:

  • A build, deploy, operation or another transfer or move is running, or a terminal or tunnel session is open.
  • The project has GPU instances (they are paid from a personal GPU wallet) or is linked to an AI Builder workspace.
  • A database or realtime server is connected to a project in another account, or a volume is shared across projects. Transfer the projects together as a bundle, or disconnect them first.
  • The sender's balance is not above zero.
  • The project belongs to a sub-account, or its region is under maintenance.
  • On the receiving side: not enough balance, or a limit such as one static IP per account, the number of Mail projects, free mail addresses, or managed databases and realtime servers.

Cancel, decline and expiry

  • The sender can cancel an open offer, or an accepted one until the owner starts changing.
  • The recipient can decline. The sender keeps the project and gets an email.
  • An offer nobody accepts expires after 7 days.

Several projects at once

You can offer up to 20 projects to one address with a single link, for example a web project and the database project it uses. The recipient can accept all of them or some. Each project changes owner in its own job, so they can finish a few minutes apart.

CLI, SDK and API

Check a transfer
curl "https://api.hubfly.space/api/v1/projects/$PROJECT_ID/transfer" \
  -H "Authorization: Bearer $HUBFLY_TOKEN"
Something unclear or out of date? Emailsupport@hubfly.spaceBack to top