Skip to content
wolforbit

Handoffs

Transfers and claiming

How the repo, deployment and files move to your client, and what happens when a transfer request runs out.

Early access. Wolforbit is being built now. These docs describe how it works at launch, and details may change.

Transfers need your client to accept

GitHub and Vercel don’t let anyone push a project onto someone else’s account. They send the new owner a transfer request, and the new owner accepts it. Wolforbit is built around that.

When the request is created

Wolforbit creates each transfer request when your client is on the claim page and signed in, not the moment they pay. Requests run out after about a day, so creating them at the right time means your client sees a fresh one.

The GitHub repo

Your client signs in with GitHub on the claim page. That proves which account the repo should go to, so it can never go to a mistyped username. The repo moves to their personal account; they can move it into an organization afterwards.

Vercel and other platforms

Vercel project transfers are planned. Platforms without a transfer feature, such as Netlify or Figma, become guided steps that you mark as done, and the record notes them.

Files

Files are stored privately and can only be downloaded by your client after payment, through links that expire within minutes.

If a request runs out

Your dashboard shows Needs you. Click Send a new request, or your client can simply open the claim page again.