OpenFlags tech stack

Fast, self-hosted, edge-ready feature flags for modern teams

openflags.dev ↗Checked Sep 2026

The stack

On its website: HTTP: openflags.dev responds with x-nextjs-prerender; HTTP: www.openflags.dev responds with x-nextjs-prerender source · Oct 2026 ↗
On its website: DNS: resend._domainkey.openflags.dev TXT (record present); DNS: send.openflags.dev MX feedback-smtp.eu-west-1.amazonses.com source · Oct 2026 ↗

“Railway's 'Config as Code' approach is a game-changer for monorepos. It allowed us to define our entire server + dashboard architecture in a single JSON file, making 'One-Click Deploy' a reality for our users.” — the maker, Oct 2026 ↗

“Zeabur's 'Template in Code' system is incredibly powerful. The ability to orchestrate multiple services with their dependencies and domains via a simple YAML file makes it the perfect home for open-source self-hosted tools.” — the maker, Mar 2026 ↗

On its website: HTTP: openflags.dev responds with x-vercel-id; HTTP: www.openflags.dev responds with x-vercel-id source · Oct 2026 ↗

Built on a similar stack

Products that share the most distinctive building blocks with OpenFlags.