Use Cases
Agencies
Ship client projects at PaaS speed, then hand them over as infrastructure the client actually owns.
Every client engagement ends with the same two questions. Where does our data live, and what happens to all of this when you walk away? Most platforms make the first question awkward and the second one impossible, which is how "we'll migrate off later" becomes someone else's problem.
Ship at PaaS speed
Connect the client's repository and deploy. No Dockerfile, no pipeline to build, no infrastructure ticket.
Answer the hosting question
European infrastructure today, with Swiss residency planned. A straight answer for the client's legal team.
Hand it over intact
Eject to standard Helm charts and values. The client runs it themselves, without you in the loop.
The handover problem
You need PaaS speed while you build. Your client, especially in banking, insurance or the public sector, needs data residency and the ability to operate the thing after your contract ends.
Traditional platforms give you the first and quietly deny the second. Deployment config, environment variables, promotion workflow, database setup: all proprietary, all stuck where they are. When the engagement ends you hand over a source repository and a prayer, and the client's new team starts from a blank page.
Raw Kubernetes is the other extreme. Your team should not need to become infrastructure engineers to ship a marketing site with a database behind it. You have deadlines and a fixed budget, not a platform engineering department.
Client repository
Their code, untouched by the platform
Lucity
Builds, deploys, manages environments
Client's own cluster
Helm release, database, bucket
What the engagement looks like
- 1
Connect the repository
Lucity detects the framework and builds from source. First deploy takes minutes, not a sprint.
- 2
Review with the client
Give each environment its own URL. Stakeholders click a link instead of asking you to "put it on the test server".
- 3
Promote, don't rebuild
The image that passed staging is the image that goes to production. Same digest, no surprise rebuild on launch day.
- 4
Hand over and leave
Eject produces the chart, the values, and a setup guide. The client points their own tooling at it and carries on.
What the client actually receives
Eject is not an export button that produces a CSV and a shrug. It writes out the deployment as plain infrastructure-as-code:
The chart and its values
The same Helm chart that was running the application, with the values computed for each environment.
Every environment
Development, staging and production, each with its own configuration, kept separate exactly as they ran.
Databases and storage
PostgreSQL clusters and buckets described as standard operator resources, not platform-specific magic.
A setup guide
Prerequisites, the commands to apply it, and where to change things afterwards.
There is no Lucity dependency in the output. That is the part worth saying out loud in a pitch: the client is not buying a dependency on your agency or on us.
Why this wins work
Ejectability is a commercial argument, not just a technical one. It turns the awkward end-of-contract conversation into a selling point: the client keeps the infrastructure, their in-house team can take over on a Monday, and nothing has to be rebuilt to make that happen.
Agencies that hand over cleanly get called back. That is the whole pitch.