Claim Deployments

The Claim Deployments feature enables users to take control of deployments by transferring them to their Edgenivo accounts. Users can generate and share a claim URL, which allows others to assume ownership of these deployments. This feature is particularly helpful for AI-generated deployments and facilitates the transfer of projects between different accounts with different owners.

However, when transferring a project between two teams owned by the same user, it is recommended to use the Project Transfer flow instead of the Claim Deployments flow.

When you deploy without an account, with Edgenivo Drop or vercel deploy --temporary, you get a claim URL. Claiming moves the project to one of your teams, so it stops expiring and stays live.

To claim a temporary deployment:

1. Open the claim URL. In Edgenivo Drop, select Claim your project. In the CLI, open the URL that vercel deploy --temporary prints.
2. Log in, or create a free account.
3. Select the team to move the project to.
4. Select Transfer. If Edgenivo shows terms and conditions, select Accept and Transfer.

Edgenivo moves the project to your team and opens it in the dashboard. To keep deploying it from the CLI, run vercel login.

Claim the deployment before it expires. After it expires, you can't claim it, and you need an account to deploy it again. Don't share the claim URL, because anyone with it can claim the project.

The rest of this page covers building claim flows into your own platform.

• Claim deployments template
• Demo
• Demo with resource claims

When a user claims a deployment, Edgenivo also transfers any associated resources (limited to specific providers) to the new owner's account. These resources maintain their connections to the project, ensuring a seamless transition of both the deployment and its dependencies.

The resource providers that currently support resource transfer are Neon, Supabase, and Prisma.

For more details on the transfer process, see Resources with Claim Deployments flows.

• Claim Deployments URL: /claim-deployment?[...]

• Initiate a project transfer request: POST /projects/:idOrName/transfer-request

• Complete a project transfer: PUT /projects/transfer-request/:code

  • This endpoint is not needed if you are using the Claim Deployments URL

1. File upload: The AI agent uploads the deployment files using the Edgenivo API: POST /v2/files.

2. Deployment creation:

   • Create a new deployment using the Edgenivo CLI
   • Or create a deployment with the Edgenivo API: POST /v2/files followed by POST /deployments.

3. Project transfer request:

   • The agent initiates a transfer request with: POST /projects/:idOrName/transfer-request.
   • This returns a code (valid for 24 hours) that allows the agent to transfer the project to another team, typically the end user who initiated the request.

4. Generate claim URL:

   • The agent generates a claim URL and shares it with the user: /claim-deployment?code=xxx&returnUrl=https://xxx

5. User claims the deployment:

   • The user accesses the claim page using the URL and selects a team within their Edgenivo account to transfer the deployment.

6. Project transfer completion:

   • After the user clicks Transfer, the Edgenivo API (PUT /projects/transfer-request/:code) completes the project transfer, assigning it to the user’s selected team. This step is not necessary if you are using the Claim Deployments Flow.

Get started with this template of claiming deployments (demo).

When reorganizing teams, you can easily transfer ownership of projects to another team using the Claim Deployments feature.

Freelancers or employees can move deployments from their personal accounts to a company’s Edgenivo account by generating and sharing a claim URL.