Push to git and Tramontane builds and runs your app on European infrastructure, out of reach of the US CLOUD Act. It deploys Next.js, Nuxt, SvelteKit, Astro, static sites and any Dockerfile. Next.js gets full Cache Components support through the Next.js Adapter API.
Next.js v16.4.0 deploy test suite, run against Tramontane with cacheComponents on. Edge runtime tests excluded. October 2026.
We detect the framework when you import a project, and you can change it in settings. Next.js 16.4+ gets the full adapter. Other frameworks get previews, domains, HTTPS, rollbacks, request logs and the CDN, and vercel.json redirects, rewrites and headers work as they are.
A Dockerfile runs as is, so Python, Go, PHP, Ruby or any app that serves HTTP on $PORT can ship. Containers keep no files between restarts: store data in a database or object storage. For Docker apps, the logs are what the app writes to stdout, and preview passwords are not available.
Push to get a preview, merge to ship, roll back without a rebuild. Builds, containers, cache, logs and backups all run on European infrastructure.
Our own server runs your build through the Next.js Adapter API. 'use cache' entries live in a shared Redis, so every instance sees the same cache. When you call revalidateTag, we purge exactly the URLs that used that tag from the CDN. Hashed assets of every deployment are kept, so open tabs never break after a deploy.
async function Products() { 'use cache' cacheLife('hours') cacheTag('catalog') // revalidateTag('catalog') → those pages purged at the edge }
Every push gets its own deployment. The preview link is posted on the pull or merge request. On Pro, you can protect previews with a password.
GitHub, GitLab, Forgejo or Gitea, hosted or self-hosted. Sign-in is by email, so you don't need a GitHub account.
Promote or roll back to any ready deployment on the branch. Traffic moves to the existing container, with no rebuild, and the CDN is purged.
Every request is logged with its status, duration and cache state, kept for 30 days in Paris. On Next.js 16.4+, the app's own logs are attached to the request that wrote them. Observability adds latency percentiles, cache hit rate and CDN traffic.
Tramontane runs on Scaleway in Paris and on bunny.net, a Slovenian company. Neither has a US parent company, so the US CLOUD Act does not apply to what you host.
every provider, and where →| criterion | tramontane | US-owned platforms |
|---|---|---|
| Parent company | European | US |
| CLOUD Act exposure | None | Yes, even in EU regions |
| Compute | Scaleway, Paris | US hyperscalers |
| CDN | bunny.net, Slovenia | US-owned |
| Git host | Any, including self-hosted | Mostly US-hosted |
| Billing | Euros, through Mollie (NL) | Usually US dollars |
The US CLOUD Act, passed in 2018, lets US authorities order any US company to hand over the data it holds, wherever that data is stored. A server in Frankfurt or Paris run by a US company falls under it, and a court can forbid the company from telling you.
Take a Next.js site on Vercel, a US company, deployed to its Frankfurt region. Vercel holds your source code, your environment variables with database and API keys, and request logs with your visitors' IP addresses. A US warrant can require Vercel to hand all of it over, and you may never hear about it. The same applies to every US-owned host.
In June 2025, the legal director of Microsoft France told a French Senate inquiry, under oath, that he could not guarantee French customer data would never be handed to US authorities.
Tramontane, Scaleway and bunny.net are European companies with no US parent, so the CLOUD Act does not reach what you host here.
Teams shipping production apps: 30 projects, always-on production, protected previews, unlimited members.
go pro