plexivo
Sign inContact sales

Deploy to Plexivo button

Add a Deploy to Plexivo button to a public GitHub repository, so anyone can run your app on Plexivo App Runner after reviewing its plan and price.

A Deploy to Plexivo button in your README lets anyone run your public GitHub repository in their own Plexivo account. Plexivo AI reads the code, plans the app and any database it needs, and shows the monthly price. Nothing is created until they approve.

Add the button#

Paste one of these into your README and replace acme/shop with your repository.

Markdown#

markdown
[![Deploy to Plexivo](https://www.plexivo.io/deploy-button.svg)](https://cloud.plexivo.io/deploy?repo=https://github.com/acme/shop)

HTML#

html
<a href="https://cloud.plexivo.io/deploy?repo=https://github.com/acme/shop">
  <img src="https://www.plexivo.io/deploy-button.svg" alt="Deploy to Plexivo" width="176" height="32">
</a>

The button is a small image in Plexivo blue that reads well on light and dark pages.

text
https://cloud.plexivo.io/deploy?repo=REPOSITORY[&branch=BRANCH][&template=SLUG]
ParameterWhat it is
repoRequired. The repository’s address on GitHub, starting https://github.com/, such as https://github.com/acme/shop. The repository must be public.
branchOptional. The branch to deploy. Leave it out for the repository’s default branch.
templateOptional. A name for this button, 2 to 50 characters of lowercase letters, digits and hyphens, such as shop-starter. Accounts created through the button are recorded against it.

What happens when someone clicks it#

  1. Sign in or create an account. Someone who is not signed in to Plexivo creates an account or signs in, then comes back to the deploy page. A new account made this way is recorded against the button’s template.
  2. Plexivo AI reads the repository. It plans a Plexivo App Runner app, with Plexivo Postgres, Plexivo MySQL or Plexivo Cache if the app needs them, and lists each resource with its size and monthly price.
  3. Approve. Nothing is created until they choose Approve & deploy. See Plan, price, approve.
  4. Build and run. Plexivo builds the repository as it builds any app, connects the database, and waits until the app is running. See Builds.

The app is built from the repository as it is at that moment. Later pushes do not redeploy it on their own, because the person deploying has not connected your repository. To follow their own changes, they fork it and deploy the fork from Git.

A new account can start with the 14-day free trial, which covers basic resources. The plan shows whether a resource is covered before anything is created.

Make your repository ready#

  • Listen on PORT. Read the PORT variable and listen on 0.0.0.0. See Listen on PORT.
  • Build from the root. Put a Dockerfile at the root of the repository for full control, or let Plexivo detect your language. See How Plexivo builds your code.
  • Read the database from the environment. A connected Plexivo Postgres database arrives as DATABASE_URL and DATABASE_CA_CERT; Plexivo MySQL and Plexivo Cache have their own variables. Use the CA certificate for TLS. See Connect a database or cache.
  • Name your other settings. List the variables your app needs in a .env.example file. Plexivo reads their names, never values, when it plans. Never commit real secrets.
  • Set up the database at start. Run your schema migrations when the app starts, so a fresh database is ready on the first deploy.
For developers Test your button in a private window before you publish it: you see exactly the plan and price a new user sees.

Next steps#

Deploy from GitConnect a repository so every push deploys. Plexivo AIHow plans, prices and approval work.

Updated 2 November 2026