Skip to main content
At the end of this guide your app runs on a Kubernetes cluster that Ankra runs for you, at a public HTTPS address, and every change you push to the repository is built, checked and put online by itself. It takes a few minutes. The app runs on a playground, which is free for 24 hours without a card.

Before you start

  • An Ankra account with a confirmed email address.
  • Your code in a GitHub repository with at least one commit. Applications come from GitHub. A repository with no commits is listed as It has no commits yet, so there is nothing to build. No code yet? Try a playground puts a finished starter website online instead.
  • A GitHub account that can install the Ankra GitHub App on the account or organisation that owns the repository. See GitHub.
  • No card. The playground your app runs on starts by itself and is free for 24 hours.

From repository to live address

1

Choose Put my app online

On Where do you want to start? (/next/onboarding), under Put my app online, press Choose my code.Check: the page asks Where is your code? Below it, Somewhere to run it is already starting: a playground, free for 24 hours, no card.
2

Connect GitHub

Press Connect GitHub. GitHub opens and asks where to install the Ankra app and which repositories it may use. Choose the repository, finish on GitHub, and GitHub brings you back.In the repository you pick, Ankra adds its own setup files and changes none of yours. If your organisation already has a GitHub connection, the button reads Pick a repository and you go straight to the next screen.Check: the page asks Which repository? and lists the repositories the Ankra app can read.
3

Pick the repository

Find it under Find a repository, or scroll the list. With more than one GitHub connection, choose one under GitHub connection first. A repository that is not listed needs to be shared with the Ankra app: under Not here?, press Share more repositories.Press the repository. The press starts the setup.Check: the heading reads Getting your app’s name online, and a bar moves through Reading your code, Building and checking it and Putting it online. Once Ankra has read the repository, it shows what it found and the address the app will have under Goes online at.
4

Let the setup pull request go through

Ankra opens a pull request on GitHub that adds only its own files: .ankra/, and a Dockerfile and .dockerignore if the repository has none. Ankra Pipelines builds and scans the app in that pull request. Once its checks pass, Ankra merges it, if your role allows that. Otherwise the pull request waits on GitHub for someone to merge it.Keep the Ankra page open: the setup moves on only while it is open, and carries on when you come back. After 30 minutes the page stops checking and says the setup is paused; press Check again to carry on.Check: the bar reaches Putting it online. If the app is built before the playground is up, the page says Built and checked. It goes online when your playground is up.
5

Open the address

Check: the heading reads Your app is live, under it Built from your repository, and the address with Running on your playground. Press Open it to open the app in a new tab, or Copy address.Under What to do next, Keep it up to date says whether Ankra’s setup files were added to your code on GitHub. Open it in Ankra opens the application’s page, with its builds and logs.
6

Push a change

Change something visible in your app, commit it and push it to the branch Ankra set up. Ankra Pipelines builds and checks the change and Ankra puts it online.Check: the build of your push is listed on the application’s page in Ankra, and once it has gone online the address serves your change.

Verify

From a terminal:
The first line of the answer reports the status your app returns, such as 200. On the first screen, Put my app online now reads Live at your app’s address, and its button is Open my app.

Keep it past 24 hours

Your app runs on your organisation’s playground, so it lasts as long as the playground does. Without a card the playground, and the app on it, is deleted after 24 hours. To keep both, press Keep my playground under the address and save a card: Keep your playground says what that costs.

From the terminal instead

ankra application ship takes a local checkout to a live deployment on a cluster you already have:
It registers the repository as an application when your organisation does not have it yet, waits for the setup analysis and a green build of the branch, deploys it to the cluster and prints the published address. When the setup pull request is not merged yet, it stops and asks you to merge it; run it again afterwards. See ankra application ship.

What can go wrong

Built it with Lovable?

In Lovable, open your project, choose GitHub and connect it. Lovable puts the project in a repository of its own, under your GitHub name and usually named after the project. Pick that repository in step 3: Ankra recognises a Lovable project and sets up its build for you. The page then calls the result a copy of your project, because your customers are not sent to it. If your code connects to a database, such as Supabase, the copy uses that same database, so an order made on the copy is real.

Where to go next

Applications

How an application is built, deployed and promoted between clusters.

Ship your app

Other ways to deliver an app: your own CI, GitOps, several clusters.

Connect your own cluster

Run the app on a cluster you already have.

Ankra Pipelines

What the pipeline in .ankra/ runs on every push.