Platform Teams
You're a platform engineer. Your developers want Railway. Your security team wants Kubernetes. You want to sleep at night.
The Internal Platform Problem
Building an internal developer platform is a full-time job. Multiple full-time jobs, actually. Backstage gives you a portal but not a deployment pipeline. Custom tooling takes months to build and years to maintain. Meanwhile, your developers are SSH-ing into production and running kubectl by hand.
Don't pretend they're not.
The gap between "what developers want" (push code, see it running) and "what platform teams provide" (a 47-page wiki on how to write Helm charts) is where productivity goes to die. You know this. You've seen the Slack messages: "Hey, can someone help me deploy to staging? The wiki is outdated again."
Lucity as Your Internal PaaS
Install Lucity on your existing Kubernetes cluster. Your developers get a dashboard for managing projects, services, and deployments. Your platform team keeps full control of the underlying infrastructure.
Developers connect their repos, deploy with a click, manage environments, and promote between stages. They get the PaaS experience they've been asking for. You get Kubernetes underneath, with standard Helm charts, ArgoCD applications, and GitOps workflows that your team can audit, modify, and extend.
No shadow IT. No developers sneaking off to Railway with the company credit card. No "we built our own deployment tool in a hackathon and now it's critical infrastructure."
Works with What You Have
Lucity doesn't ask you to rip and replace your stack. It integrates with the tools you probably already run:
- ArgoCD: you're likely already using it for GitOps. Lucity creates and manages ArgoCD Applications. Your existing ArgoCD dashboard still works.
- Helm: Lucity generates Helm values, not custom resource definitions. Standard
helm templateworks for debugging. Your team's Helm knowledge applies directly. - Gateway API: the Kubernetes-native successor to Ingress. If you're not on it yet, you were going to migrate eventually anyway.
- CloudNativePG: production-grade PostgreSQL on Kubernetes. Lucity provisions and manages CNPG clusters for developer databases.
It doesn't replace your stack. It adds a developer experience layer on top. Think of it as the friendly UI your developers wanted, backed by the infrastructure your platform team trusts.
No Lock-in, Even Internally
Internal tools have a way of becoming sacred cows. Someone built it, someone maintains it, and eventually everyone is afraid to touch it. With Lucity, that fear doesn't apply.
If your team decides to build something custom, or switch to a different tool, or just outgrows what Lucity provides, run lucity eject. Take the Helm charts, the ArgoCD configs, and the GitOps repo structure with you. Everything Lucity manages is standard infrastructure-as-code.
Lucity is a convenience, not a commitment. That's a better pitch to your architecture review board than "trust us, you'll never want to leave."
Open Source Means Auditable
AGPL-3.0 licensed. Your security team can read every line of code. Run static analysis on it. Audit the container images. Verify that it does what it claims and nothing more.
No black boxes. No phone-home telemetry. No "trust-us-bro" security model. No vendor sales team that needs to be involved when your CISO asks questions.
For regulated industries (financial services, healthcare, government), this isn't a feature. It's a prerequisite.