Skip to main content
Vercel builds and serves your project from its own platform. Ankra builds the same GitHub repository and runs it on your own cluster, behind HTTPS, with every change built and scanned first. You keep pushing to the same repository. Ankra builds every commit.

​
What moves, and what it becomes

The setup pull request contains the Dockerfile, the Kubernetes manifests, the CronJobs, the deploy options (.ankra/ankra.yaml) and the build pipeline (.ankra/pipeline.yaml). Ankra’s AI writes it when you add the repository. You review and merge it.

​
Vercel storage in the Launch Plan

Ankra reads which Vercel storage the code uses and puts one card per service in the project’s Launch Plan. Each card shows how locked in the service is and which choice applies by default. You can change the choice. A portability pull request is opt-in. It adds the open-protocol path beside Vercel’s, and the app keeps using Vercel until you set the new variables. Data is not copied for you.

​
Start from the Vercel project page

The Ankra — Chat & Deploy extension for Chrome puts an Ask Ankra button on your Vercel project page, and also on Lovable, Claude Design and GitHub repository pages. See install the extension.
1

See where the project stands

The button carries a status pill for the project’s repository: Not connected, Analysing, N decisions, Ready to approve, Proving, Proof failed or Live. The same pill appears on the repository’s GitHub pages.
2

Review the Launch Plan

Open Deploy project. The extension fills in the GitHub repository the Vercel project builds and its branch. The Launch Plan panel lists:
  • the decisions only you can make, with their defaults
  • per external service, what stays at Vercel and what Ankra runs open source
  • the result of the proof run of the setup pull request
To change a decision, use Change decisions in Ankra. All configuration stays in Ankra.
3

Bring your variables

Under Bring variables from Vercel, paste a Vercel access token for the project’s team and choose Read variables. The token is used from your browser only and is not stored or sent to Ankra.By default you get the names of the project’s production variables, marked by whether Ankra already has each one. Tick the box to copy the values into the application’s encrypted secrets. Values Ankra already holds are never overwritten. Variables marked sensitive on Vercel cannot be read back, so enter those in Ankra.Values can be copied once Ankra has registered the application, which happens on the first deploy.
4

Approve

Click Approve and deploy. Ankra registers the application, opens the setup pull request, builds and scans the image, and deploys it with the plan’s choices. If the setup pull request or the first build is still pending, the request waits and is sent when Ankra is ready.
Test on the Ankra address before you move your domain. Check the cron routes, the rewrites you moved into next.config, and every variable your app reads.

​
From the CLI

Run the first command in a local checkout of the repository. See Applications and Lovable to Ankra for the rest of the flow, from the setup pull request to automatic deploys.