[ For Enterprises ]
Enterprise infrastructure, run by the people who built it.
Hosting, database, CDN, auth, search and storage on one stack and one contract, in Europe.
- Swiss company · EU data residency
- our cloud, your cloud, or your own datacentre
Who you'd be buying from
Small on purpose, and Swiss.
JAMflow is the platform arm of MooCloud, a Swiss company in Bellinzona that has been running production infrastructure since 2019. We are not a reseller and not a two-hundred-person vendor, and that is the point: whoever picks up your incident is, more often than not, one of the people who configured your stack.
What we won't do is tell you we're bigger than we are. Where this model doesn't fit, this page says so — before week six of your evaluation, not after.
Why consolidate at all
The integrations are already built, and they aren't yours to keep working.
Six suppliers isn't a problem because it's six invoices. It's a problem because of everything that has to keep agreeing in between — and every incident starts with working out whose problem it is. Here is the count that matters.
Separate suppliers
typical setup
6–10services that have to agree with each other
Auth has to agree with the CDN, the CDN with the database, the database with the search index. Every one of those seams is something your team wrote and now maintains.
JAMflow
one environment
1supplier, and the seams arrive already agreed
One contract, one invoice, one point of escalation.
Concentration risk is a fair objection, and we would rather answer it than argue with it: what we run for you is a plain Nuxt project on Nitro that deploys anywhere Nitro deploys, and the services are integrated with each other but not bundled — you can take two of them and leave the rest.
What this model is built for
It works best as a collaboration: your team knows the domain, we know the platform, and both work in the same repository. And one stack underneath does not mean one framework on top — Nuxt and Vue where the front end carries the product, Elysia, Go or Python behind it, React, Svelte or Solid where that is already what your people write. Microservices, git, code review: the ordinary way of working, not a bespoke one.
Where we're the wrong answer
When you want to commission a project and receive it finished, with nobody on your side to talk to along the way. That is a legitimate way to buy software; it is not the way we build it. When the work is low-level machine learning, or Rust, or Java — we don't have those people, and we would rather tell you than quietly subcontract them. And when what you actually need is people on your own platform rather than a platform with a team behind it. Your size is never the reason: the same stack carries a ten-page site and a multi-brand group, and what changes with scale is the contract, the SLA and where it gets deployed.
The whole stack, one topic at a time
Most evaluations turn on one of these six. Start with yours — each one has its own link, so you can send a colleague straight to the answer instead of to the top of the page.
Same stack, same console. You switch on what the project needs.
Serverless, multi-region, warm on the first request
Your applications run on infrastructure that scales on its own, with no servers to size or update. Spikes absorbed without anyone intervening, redundancy included, deploys with no downtime.
- Scaling with no cold start
- The infrastructure scales on actual traffic, not on a plan you bought in advance. An event, a launch, a campaign: it adapts without anyone doing anything.
- Served from close to the visitor
- Requests are answered from the edge location nearest the visitor — 119+ points of presence across 77 countries — with origin compute in Europe, the United States and Asia Pacific.
- Zero-downtime deploys
- New versions go live without interrupting the service. If something goes wrong, the system returns to the previous one.
- Failover you don't have to buy
- Failover is part of the environment, not a tier you upgrade to: if a node or a zone goes, requests re-route without anyone being paged.
No server to manage, no spike to forecast.
Where it runs
Our cloud, your cloud, or your own datacentre
Not every organization can put everything in a public cloud. Where data residency, an existing internal estate or a security policy demands direct control, the same platform runs on dedicated or on-premise environments.
- Managed cloud
- No infrastructure to run. Scaling, backups and security updates are ours; your team ships product.
- Private cloud
- An environment dedicated entirely to your organization, at a cloud provider you choose. Complete isolation, nothing shared with other customers.
- Hybrid
- A fast global frontend on the cloud, sensitive data on your side. For compliance constraints that still want edge performance.
- On-premise
- Data and application stay inside your infrastructure, for security policies that require direct control of the environment.
What it costs
The platform is on the price list. The enterprise part is the SLA.
Compute is metered at CHF 0.01 per RU-hour, storage and egress per GB — the same published rates every customer pays, whether you run one product or forty. There is no enterprise multiplier on the infrastructure. What gets quoted separately is the part that really is bespoke: the response-time commitments, the onboarding, and any deployment that isn't our cloud.
See the full price list →- Compute · 1 RU = 0.25 vCPU + 512 MiB
- CHF 0.01 / RU·h
- Storage
- CHF 0.10 / GB
- Egress, EU and North America
- CHF 0.02 / GB
- SLA, onboarding, deployment outside our cloud
- quoted after the review
How you leave
You can leave. The exit is a redeploy, not a rewrite.
What you end up holding is a plain Nuxt project on Nitro, in your git, with the edge rules and the pipeline versioned next to the code. Any Nuxt team can pick it up, and it deploys anywhere Nitro deploys — including somewhere that isn't us.
Everything comes out: the code from your git, the database as a Postgres dump, the files from object storage — all in standard formats, none of them ours. We would rather be the supplier you stay with because leaving is easy than the one you stay with because it isn't.
What's left to ask
The questions this page hasn't already answered — the ones that come up once the technical evaluation is over.
Ask us something that isn't here →How does the enterprise contract work?
A contract written to your terms — SLA, volume, deployment model and billing model defined together before you start. There is no mandatory catalogue plan and no separate agreement per service: one contract and one invoice for the whole stack.
Can I use only some services without adopting the whole stack?
Yes. Each component works independently. You can start with hosting and the CDN, add auth or AI search on top of an application you already have, and consolidate the rest later — or never. There is no mandatory plan.
Are you ISO 27001 certified?
We work to ISO 27001, and the infrastructure underneath is certified to it: the datacentres to ISO/IEC 27001:2022, and bunny.net, which runs the edge network, to ISO 27001. The certificate in our own name is the one piece we don't hold today — and if your process requires it, we will take it, with the commitment and the date written into the contract. The practice is already there; what's missing is the audit.
Do you offer formal SLAs, and what are the numbers?
Yes, written into the contract per incident severity. Our standard thresholds are one hour for a service-down incident, four hours for a significant degradation and 24 hours for a non-blocking issue, with updates on a fixed cadence until it is closed. Cover is available up to 24/7 and there is more than one tier: we work out which one the product actually needs, and it goes in the contract with the thresholds.
What if JAMflow stops doing this?
Your product keeps running, and not because we promise it. What we deploy is a standard Nuxt application on Nitro, in your git repository, on Postgres — there is no proprietary runtime that only exists here, so any competent Nuxt team can pick it up: ours, yours, or whichever agency you hire next. It deploys anywhere Nitro deploys. We have wound a business down once already: when we closed our Cloudron hosting in 2025 we announced it in May, it took effect on 1 July, and every customer was either rebuilt on JAMflow or handed to the provider who took the platform on.
Have an enterprise project, or evaluating an infrastructure provider?
We'll review your current stack and write up which parts are worth consolidating, with cost and effort attached. It's yours to keep whether you work with us or not.