Deploy a GitLab repo

Deploy a GitLab repo
live in 2 minutes.

Connect a public GitLab repo and livemy.app builds and deploys it to a live, always-on URL — free SSL, a real database, one-click redeploy or deploy over MCP, and no DevOps. Private code? Upload a .zip.

Deploy your repo — free How it works

No credit card·Public repos·Free plan never sleeps

Why deploy your repo on livemy.app

GitLab stores your code. livemy.app runs it.

A repo is your code, not a running app. Turning it into a live URL usually means a host, a Dockerfile and CI you maintain. livemy.app connects to your public repo and does all of it.

A repo is not a live app

GitLab holds your code but does not run it. livemy.app builds the repo and gives you a shareable, always-on URL with free SSL.

No CI/CD to maintain

Skip the Dockerfile, the deploy YAML and the build pipeline. livemy.app detects your stack and lets you redeploy in one click, no pipeline to maintain.

Public or private, same flow

We never ask for access to your private repos. Connect a public GitLab repo, or download your code as a .zip and deploy that, with secrets kept server-side.

How to deploy a GitLab repo

Three steps, about two minutes

Connect a public repo (or upload a .zip for private code), and livemy.app builds and ships it. Redeploy in one click from the dashboard or over MCP.

1

Connect a public repo

Paste a public GitLab repo URL. Private repo? Download it from GitLab as a .zip and upload that instead — no access needed.

[public repo]] or .zip

2

Auto-detect and build

livemy.app detects the stack — React, Next.js, Node, Flask, Streamlit — and configures the build. No Dockerfile needed.

detected: next.js ✓ build ✓

3

Go live

Free SSL, a live URL, and auto-deploy on every push for connected repos. Add env vars, a database or a custom domain in one step.

✓ live → https://app.livemy.site

From the trenches

5 things that break repos when they go to production

Taking a repo from your machine to a live host trips on the same five things every time. livemy.app handles each one by default.

01

Environment variables

Values that worked in the Lovable preview are not set in production. livemy.app gives you real, encrypted ENV management per deploy, with no hardcoding.

02

Leaked or missing API keys

Keys baked into client code get exposed; keys left behind stop calls cold. livemy.app stores secrets server-side and injects them at build, not in the bundle.

03

Database persistence

Preview data resets and there is nowhere durable to write. livemy.app attaches a persistent database so user data survives a redeploy.

04

Client-side routing 404s

Deep links and refreshes return 404 without a rewrite rule. livemy.app serves SPA fallbacks correctly so /dashboard loads on a hard refresh.

05

Build configuration drift

Node version, build command and output dir differ from the preview. livemy.app pins and detects them so production matches what you tested.

→

Want the deep dive?

We wrote the full field guide: every fix, with the exact settings. Read the deeper guide →

Manual deploy vs livemy.app

What you skip with livemy.app

Capability

Manual setup

livemy.app

Live URL + SSL

~ Configure it yourself

✓ livemy.site, free SSL

Always-on (never sleeps)

~ Depends on your server

✓ Free plan never sleeps

Persistent database

~ Set up and maintain

✓ Durable, attached

Build config

× Write a Dockerfile / CI

✓ Auto-detected

One-click redeploy

× Build a CI/CD pipeline

✓ One click, or over MCP

Private code

~ Grant the host repo access

✓ Public repo or .zip, no access

GitLab repo deployment FAQ

Yes. Connect a public GitLab repo and livemy.app detects the stack — React, Next.js, Node, Flask, Streamlit and more — builds it, and deploys to a live, always-on URL with free SSL. No Dockerfile or DevOps required.

livemy.app does not ask for access to your private repositories. To deploy private code, download the repo from GitLab as a .zip and upload the archive — livemy.app builds and deploys it the same way, and your code stays private.

GitLab Pages only serves static sites — no backend, database or server routes. livemy.app runs full-stack apps from your repo, with a persistent database, env vars and a live URL that never sleeps.

Redeploy in one click from the livemy.app dashboard, or trigger a deploy over MCP. livemy.app does not auto-deploy on git push yet, so you choose when to ship. For a .zip deploy, upload a new archive.

livemy.app starts free and never sleeps. Paid plans are flat from $10/mo, not metered by usage. On a paid plan you can point a custom domain with automatic SSL; the free plan gives you an always-on livemy.site URL.

livemy.app auto-detects most stacks — React, Next.js, Node, Flask, FastAPI, Streamlit, static sites and Docker — and configures the build for you, so server routes, env vars and a database work in production.