SaaS vs Self-Host
SaaS vs Self-Host — which deployment model fits
Same product, two places to run it. This page is the honest version: what each model costs you in effort, and what it buys you in control.
Fenwave SaaS
Hosted by Fenleap in the EU. Fastest path to a working platform.
Fenwave Self-Host
Helm chart on your cluster. Nothing leaves your perimeter.
| SaaS vs Self-Host | Fenwave SaaS | Fenwave Self-Host |
|---|---|---|
| Hosted by | Fenleap, in the EU | You, on your Kubernetes |
| Time to a working platform | Under a day | 2–3 days via the Helm chart |
| Updates | Applied for you, continuously | You choose when to roll out |
| Where your data sits | EU region, Fenleap-operated | Your infrastructure, never leaves |
| Network requirements | Outbound access from your clusters | Air-gapped installation supported |
| Customisation | Configuration and templates | Full — you can modify plugins |
| Operational burden | None — we run it | A namespace, a database and an upgrade cadence to own |
| Feature set | Complete | Complete — identical |
Choose SaaS if
- You want a platform running this week, not this quarter
- You have no spare capacity to operate another internal service
- EU data residency satisfies your compliance requirements
- Your team is between 10 and 200 engineers
Choose Self-Host if
- Repository names and deployment metadata may not leave your perimeter
- You operate in a regulated sector or an air-gapped network
- You already run platform services and have the capacity to run one more
- You want to modify plugins rather than only configure them
Still not sure?
Tell us about your compliance requirements and cluster topology and we will recommend one — including when the answer is that you do not need us yet.