OpenFlags icon

OpenFlags

OpenFlags is an open-source, self-hosted feature flag platform for modern JavaScript teams. It supports local evaluation, targeted rollouts, and controlled launches while keeping flag data in your own infrastructure.

OpenFlags

Overview

OpenFlags is an open-source, self-hosted feature flag platform for modern JavaScript teams. It is built to help product and engineering teams ship behind flags without depending on a heavy hosted control plane or moving data out of their own stack.

The product centers on local evaluation, percentage rollouts, and targeted activation. Its documented architecture splits the system into a server for flag storage and targeting, a dashboard for managing releases, SDKs for application-side evaluation, and docs for onboarding and implementation guidance.

Core capabilities

Local flag evaluation

OpenFlags evaluates flags locally in the application, which the site describes as zero-latency local evaluation and an extra network hop avoided on every check.

Gradual rollouts and targeting

The product supports percentage rollouts and targeting so teams can release to controlled slices of users instead of turning a feature on for everyone at once.

Self-hosted control plane

The docs describe a self-hosted architecture that keeps flag data, rollout logic, and operational decisions inside your own infrastructure.

JavaScript-first SDKs

The site presents TypeScript packages and JavaScript-first SDKs for use in Bun, React, Next.js, Vite, and Node apps.

Monorepo-based workflow

The quickstart shows a Bun monorepo with separate server, dashboard, and docs apps, making the system straightforward to run and inspect locally.

Lightweight API and admin surface

The public docs describe a simple REST surface and lightweight control plane for flag storage, API access, and targeting rules.

Common use cases

  • Progressive feature launches

    Use OpenFlags when you want to release a feature to a narrow slice of users first, then expand it gradually by percentage as confidence increases.

  • Targeted access control

    Use the dashboard and SDKs to gate a feature for specific users or segments when you need targeted activation instead of an all-or-nothing release.

  • In-house ownership

    Use the self-hosted setup when your team needs to keep flag data and rollout logic inside its own infrastructure for operational or governance reasons.

  • Local development and evaluation

    Use the Bun monorepo and local quickstart when you want to evaluate the platform, understand the workflow, or run the server and dashboard together in development.

  • JavaScript application integration

    Use the JavaScript-first SDKs when your app is built with Bun, React, Next.js, Vite, or Node and you want flag checks to fit the existing application stack.

Pros and Cons

Pros

  • Local evaluation keeps feature checks inside the app and avoids an extra network hop on every request.
  • Self-hosted operation keeps rollout data and runtime ownership in your own infrastructure.
  • Percentage rollouts and targeting support safer, incremental releases.
  • The platform is organized around small, focused parts: server, dashboard, SDKs, and docs.
  • The quickstart shows a clear local workflow for running the monorepo and testing the main apps.

Cons

  • The collected pricing URL currently returns a 404, so pricing details are not available from the public site.
  • The source materials are strongest for JavaScript-based workflows; support for other language ecosystems is not described in the collected pages.

FAQ

What is OpenFlags for?

OpenFlags is described as an open-source, self-hosted feature flag platform. The docs position it for teams that want local evaluation, percentage rollouts, and JavaScript-first SDKs without adopting a heavy hosted control plane.

How do I run it locally?

The quickstart says OpenFlags is a Bun monorepo. To get started locally, install dependencies with `bun install`, run `bun run dev:server`, and in another terminal run `bun run dev:dashboard`; you can also launch the docs app with `bun run dev:docs`.

What is the basic rollout workflow?

The source highlights a simple workflow: create or choose a project, define a feature flag with a stable snake_case key, enable it for a subset of users or by rollout percentage, and evaluate it in the app through the SDK.

Which app stacks does OpenFlags fit best?

The docs and homepage emphasize JavaScript-oriented usage. The site specifically mentions Bun, React, Next.js, Vite, Node.js, and a TypeScript SDK layer.

Does the site show pricing?

The pricing page at `/pricing` currently returns a 404, so the public site does not expose a pricing model in the collected sources.

Quick Facts

Category
Feature flags
Deployment model
Open-source, self-hosted
Primary users
JavaScript product and engineering teams
Core workflow
Local evaluation with rollout targeting
Site domain
openflags.dev
Pricing
Not shown; `/pricing` currently returns 404