Made by a French
web agency
Tramontane is made by Velours, a digital agency in France. We build websites that get millions of visitors a month, and we needed a European host that runs them as well as we write them.
Velours designs and builds websites. Several of them serve millions of visitors every month, so a slow cache, a broken deploy or a missing log line costs us and our clients real traffic.
We write our sites in Next.js and take up its new features early. Cache Components is one of them: our code uses 'use cache', cacheLife and cacheTag throughout.
Our clients also ask where their data lives and which companies can reach it. We want to answer with a short list of European names.
We looked for a host first
In 2026 we went through the European hosts we could find. Some put a US company in the path of every request, through their CDN or their compute. Others had no preview deployments, or ran only part of Next.js. So we built Tramontane on Scaleway in Paris and bunny.net, for our own sites first.
- previewsA URL for every branch, posted on the pull request.
- full next.jsCache Components, image optimization,
proxy.ts. - shared cacheOne cache for every instance of a site.
- tag purges
revalidateTagclears the CDN too. - no us companyBetween visitors and data: compute, CDN, TLS and database all run by European companies.
Built around Cache Components
Cache Components is how Next.js caches now, and the feature our sites depend on most. On many hosts it only half works: each instance keeps its own cache, or a revalidation leaves stale pages at the CDN.
We know how Next.js works down to its cache layers. We have spent many hours with Vercel's support and engineering teams debugging our sites, mostly cache revalidation. We know how hard it is to get right, and Tramontane is built on what we learned.
Tramontane runs your build through the Next.js Adapter API on our own server. 'use cache' entries live in a shared Redis, so every instance reads the same data. revalidateTag purges exactly the URLs that used the tag. Hashed assets of past deployments stay online, so open tabs keep working after a deploy.
Cache Components is where we started, and Tramontane deploys much more. Next.js before 16.4, Nuxt, SvelteKit, Astro, Remix, React Router and any Node.js server run as they are. Vite, Angular, Gatsby, Docusaurus, Eleventy and plain files ship as static sites, and a Dockerfile runs as is. Each one gets previews, domains, HTTPS, rollbacks, logs and the CDN.
Tested against Next.js itself
We run the deploy test suite from the Next.js repository against Tramontane, with cacheComponents on. Our goal is the full suite, run on every release, with the result published here.
Next.js v16.4.0, October 2026. Most of the 12 suites left expect another platform's headers or are flaky. Edge runtime tests excluded.