Four Days, One Deploy, No Excuses

Last Friday we shipped the first version of this site. Next.js 16, deployed to Cloudflare's global network of servers via our adapter layer. Bilingual from day one — German and English, locale routing, language tags in the page head so search engines know which version to show where, the full setup. It went live. Then we found a broken page on routes that had been built ahead of time rather than on demand. Found it because we tested it, fixed it the same day, redeployed. That is how it is supposed to work.

The stack choice is not exciting, and that is the point. Cloudflare Workers run your code on servers distributed worldwide — no machines to babysit, no datacenter to worry about. You push code, it deploys, it runs. The boring kind of infrastructure is the good kind.

Days three and four: cache configuration on the data endpoint, retry logic for transient failures, and reproducible builds. Nothing glamorous. The kind of work that means the site behaves the same on the tenth deploy as it did on the first. You can verify this. Hit either language version directly. You get a valid response. The icon loads. The cache settings are there. Evidence is cheap to produce when the code is correct.

Today is the rebrand to Apuna and the public launch. A dedicated deployment on the apuna.dev domain. Logo files converted to their final format at build time so the browser never fetches a broken image on first load. The access gate that was blocking public traffic came off tonight, and both language versions are now live. We did not announce it until it worked. That is also how it is supposed to work.

Four days. A working bilingual site, a found-and-fixed bug, reproducible builds, a clean deploy to a custom domain, and a public launch with no drama. Talk is cheap. The site is at apuna.dev.