The way out is built in.

Every Lucity project has an Eject button. It downloads your services, databases and domains in a standard format any major cloud can run, without Lucity. You will probably never press it. Here is exactly what happens if you do.

  • No account, no license key, no call home
  • Your project keeps running on Lucity
  • Open source, top to bottom
  1. Click EjectIn the dashboard, on any project. It keeps running on Lucity as before.
  2. Open the zipThe chart, one values file per environment and a build script.
  3. Install itRebuild your images, change a few values, run one helm command.
  4. It runsThe same services, on a cluster of your own. Nothing in them knows Lucity.
A copy, whenever you likeEjecting changes nothing on Lucity. Take an export to keep one, to try your own cluster first, or to move for good.
Runs where Kubernetes runsA cluster of your own, a managed one from a big cloud, or another provider. The list of what it needs is further down.
Honest about the restThe export is your configuration, not your data. Moving for good is manual work, and this page says which.

One zip,
nothing of ours inside.

The export is the chart every Lucity environment is deployed with, plus one file per environment that says how yours is set up. Click through it.

valuesOne file per environment

values/production.yaml

One environment as it runs right now: every service with its image, variables, instances, resources and domains, plus its databases, key-value stores and volumes. The marked lines name things that only exist on Lucity, so you change them.

gateway:                         # yours to change
  name: lucity-gateway
  namespace: lucity-system
imagePullSecrets: [ ... ]           # yours to change
services:
  web:
    image:
      repository: registry.example.com/shop/web
      tag: 9b1e4d0
    replicas: 2
    domains:
      - host: shop.example.com
        issuerRef: { kind: ClusterIssuer, name: ... }  # yours to change
databases:
  postgres:
    main: { instances: 2, size: 10Gi }

The archive holds your variables in plain text, secrets included, along with the passwords of your key-value stores. Keep it where you would keep a password, and out of public repositories.

An honest list,
of what moving takes.

Ejecting copies your configuration. It is not a migration. This is what the zip carries, what you bring, and what becomes your job once we are out of the picture.

In the zip

  • Services with their images, variables, instances, resources and private hostnames
  • Domains with their routes and certificate settings
  • Databases, key-value stores and volumes configured the same, created empty
  • A build script for the images Lucity built from your code

You bring

  • A cluster on Kubernetes 1.33 or newer, with nodes that support user namespaces
  • The open source parts it leans on depending on what the project uses, listed below
  • A registry for the images you rebuild
  • Your data copied with pg_dump and any S3 tool. Volumes have no download, so their files come out through your own service
  • A maintenance window because there is no live migration. Writes stop while the data is copied

Yours from then on

  • Builds and deploys a push no longer deploys anything, so your CI builds and runs helm upgrade
  • Database backups backups and point-in-time recovery are set up again on your side
  • Separation between environments network rules and resource budgets live outside the chart
  • Logs, metrics and a dashboard bring the tools you already like

What the cluster needs

Only what your project uses. Every part is open source, and the readme in the download lists them again.

The full list, with versions

If the project hasThe cluster needs
ServicesKubernetes 1.33 or newer, on nodes with user namespaces (Linux 6.3+, containerd 2.0+ or CRI-O)
Databases, key-value stores or volumesA default StorageClass
PostgreSQL databasesThe CloudNativePG operator
DomainsA Gateway API implementation and a Gateway reachable from the internet
Custom domainsListenerSet support on that Gateway, and cert-manager 1.20+ with an HTTP-01 ClusterIssuer
Autoscalingmetrics-server

Day 1000,
and still your call.

Most platforms get expensive the day you outgrow them, because your setup lives in their dashboard. Here the next step is a choice you make, not a project you start.

  1. day1

    Push, and it is live. A repository becomes a running app with an address and HTTPS.

  2. day30

    A database in one click. Linked to your services, with no passwords copied around.

  3. day365

    Production, with a team. A customer's domain, real traffic and colleagues with access.

  4. day1000

    A reason to change something. Compliance wants your own hardware, or you have grown a platform team.

From here, three ways to go on. It is the same chart underneath all of them.

Stay

We run it.

Keep shipping on Lucity. Nothing about your app changes as it grows, and you can take an export any time, just to have one.

Eject

You run your project.

Install the export on a cluster that fits the list above. Builds, backups and monitoring become yours. The eject guide

Self-host

You run the whole platform.

Lucity is open source. Install it with the same two Helm charts we run, and keep the dashboard, builds and push to deploy. Budget an afternoon for the first install. Self-hosting

Questions about leaving

Still wondering about something? Ask us

No. The project keeps running exactly as before, so you can eject to keep a copy, to try your own cluster first, or to move for good. The export is a snapshot: changes you make on Lucity afterwards need a fresh one.

No. Nothing in the export calls home, needs a license key or talks to Lucity.

No. The export is configuration. Databases, key-value stores and volumes come up empty on your cluster, and bucket files stay in their buckets. The guide shows how to copy each of them.

Yes, a short one that you plan. There is no live migration: writes have to stop while the data is copied, and custom domains wait a minute or two for new certificates after the DNS switch.

Yes. Lucity is open source, so you can install the full platform on your own cluster and keep the dashboard, builds and push to deploy. It is not a one-command install, and the self-hosting guide says what it takes.

Read the way out before you come in.

Download the export of our demo project, shop. It is the same zip the Eject button gives you, with the chart, the values and the build script. If you do not like what is inside, do not sign up.

Download a sample export shop-ejected.zip · 27 KB