Startups & Small Teams
You're a 5-30 person team shipping fast. You love Railway or Render for the simplicity. But there's this nagging feeling: what happens when you outgrow it?
The Graduation Problem
You start on Railway because it's fast. Connect a repo, set some env vars, deploy. Beautiful. Your CTO makes a sensible call: "We'll worry about infrastructure later. Right now we ship."
Then later arrives. You need custom networking. Your costs spike because the platform marks up every resource. You need EU data residency for a new enterprise customer. You just want more control over how things are configured.
Migrating off Railway means starting from scratch. Your deployment knowledge, your environment configs, your promotion workflows. All proprietary, all left behind. You're not migrating; you're rebuilding. Some teams call this the "PaaS graduation tax," and it's usually a quarter's worth of engineering time that produces zero customer value.
The irony: the platform that was supposed to save you time just cost you months.
The Lucity Path
Same simplicity you're used to: connect a GitHub repo, deploy with a click, manage environments from a dashboard. Auto-detection of languages and frameworks. PR preview environments. Promotion from dev to staging to production.
But underneath, it's all standard Kubernetes. Helm charts, ArgoCD, Gateway API, CloudNativePG. When your needs get complex, you're not hitting a wall. You're just using more of what's already there.
No proprietary runtime. No custom abstractions that only work on one platform. No surprises at 3 AM when you need to debug something and the platform won't let you see what's happening.
Grow into Kubernetes
Start with the dashboard for everything. You don't need to know Kubernetes on day one. That's the whole point.
As your team matures, start peeking at the GitOps repo. Understand the Helm values. See how environments are structured. Add a custom configuration that the dashboard doesn't expose yet.
Eventually, you know your infrastructure inside and out, because it was never hidden from you. It was always standard tools, standard formats, standard practices. You didn't learn "how Railway works." You learned Kubernetes, Helm, and ArgoCD, skills that transfer to any job, any company, any infrastructure.
That's not a side effect. That's the design.
Eject When Ready
Maybe you hire a platform engineer who wants to customize the setup. Maybe you want to run on your own cluster in a specific region. Maybe you just want the confidence of knowing you can leave.
Run lucity eject. You get standard Helm charts, ArgoCD configurations, and a setup guide. Point your own ArgoCD at the repo and keep going. The graduation from PaaS to self-managed Kubernetes is a single command, not a rewrite.
Your deployment history, your environment configs, your database setup. It all comes with you. Because it was always yours.
Self-Host for Cost Control
Lucity is open source under AGPL-3.0. Run it on your own cluster and pay only for the compute you actually use. No per-seat pricing. No usage markup. No surprise bills because your staging environment ran overnight.
For a startup watching burn rate, the difference between "$500/month for a managed PaaS" and "$150/month for the same compute on your own cluster" adds up fast. That's runway. That's one more month before you need to fundraise.
And if you'd rather not manage infrastructure at all, Lucity Cloud is there, with transparent pricing and Swiss hosting. Your choice, not ours.