Lucity

Lucity is an open-source Platform-as-a-Service (PaaS) that takes the part of Heroku, Vercel and Netlify everyone actually likes - push your code, get a running app - and rebuilds it on open, standard infrastructure that you can host yourself or run as a managed European service. Its tagline says the quiet part out loud: "the PaaS you can leave." That single idea is what makes it interesting, and it's why it earns a place among the European cloud options worth knowing about.

What Lucity Actually Does

The core workflow is the familiar one. You connect a GitHub repository, push code, and Lucity handles the rest: it builds your application, containerises it, and deploys it to a Kubernetes cluster - no hand-written Dockerfiles or Kubernetes manifests required. On top of that it manages multiple environments (development, staging, production and per-pull-request preview environments), provisions managed PostgreSQL databases via CloudNativePG, and sets up custom domains with automatic TLS certificates. There's even a built-in database explorer for browsing tables and running queries. In day-to-day use, it aims to feel as effortless as the US incumbents.

The "Eject" Feature - Why It Stands Out

The headline differentiator is the eject button. Most managed platforms make leaving painful by design: your app is wired into proprietary build systems, config formats and APIs, so migrating away means rebuilding from scratch. Lucity instead exports standard Helm charts and ArgoCD configurations - the exact, portable artefacts the platform uses under the hood. If you outgrow Lucity or simply want to take control, you can lift your entire setup onto any Kubernetes cluster and keep running. That turns "no lock-in" from a marketing line into a concrete, testable promise, and it's a genuinely refreshing stance in this market.

Built on Open Standards

Rather than inventing a closed stack, Lucity orchestrates well-known, battle-tested open-source components: Kubernetes for orchestration, Helm for packaging, ArgoCD for GitOps continuous delivery, CloudNativePG for databases, Zot as the container registry and Gateway API for ingress. The whole platform is licensed under AGPL-3.0 and is fully self-hostable on your own cluster. For teams that value transparency and want to understand - or audit - exactly what is running their infrastructure, this open foundation is a strong selling point.

The European Angle

Lucity is built by zeitlos.software, a Swiss company, and its managed offering, Lucity Cloud, is hosted in Germany - keeping your applications and data within EU jurisdiction. For European businesses that have deliberately moved away from US hyperscalers and US-headquartered PaaS providers, this matters: it removes exposure to foreign data-access regimes and keeps the deployment layer consistent with a European-first stack. The combination of EU hosting, a Swiss vendor and an open licence is exactly the kind of thing this directory exists to highlight.

Who Should Use Lucity

Lucity is a good fit for developers, startups and small-to-medium teams who love the simplicity of Heroku or Vercel but are uneasy about lock-in, pricing surprises or shipping their data to the US. The self-hosted route suits teams that already run Kubernetes and want a friendlier deployment experience on top of it, while Lucity Cloud suits those who want the convenience of a managed European platform without operating the cluster themselves. Because you can start on the cloud and later eject to self-hosting, it's also a sensible choice when you're not yet sure which path you'll need.

Considerations

Lucity is a young platform, and that's reflected in our score. As a relatively new entrant it has a smaller community, less independent track record and a thinner ecosystem than the established US incumbents it competes with - and considerably less than running raw Kubernetes with mature tooling. The self-hosted path still assumes comfort with Kubernetes concepts, so it isn't entirely operations-free. The managed Lucity Cloud is also early-stage, so teams with demanding uptime, scale or support requirements should evaluate its SLAs, regions and pricing directly before betting production workloads on it. None of this undercuts the core proposition - the architecture and the no-lock-in philosophy are sound - but it does mean Lucity is best approached as a promising, fast-moving project rather than a drop-in replacement with a decade of operational history behind it.