Open-source first

Flip safely. Learn quickly.

Open-core, self-hostable feature flags and experiments with governance by default. SaaS option when you want zero-ops.

By Juliusz Ćwiąkalski — Open-core + optional SaaS. Pricing page: coming soon.

A flagship sailing through the night sky with a modern toggle motif
FlagshipX hero artwork

Why FlagshipX

Self-hostable & open-core

Maximum control, zero vendor lock-in. Start free, grow at your pace.

Governance by default

Owners, expiry, and audits from day one — keep flags tidy and accountable.

AI-powered cleanup

Eliminate flag debt automatically. Plan changes with confidence.

Built for speed

Client/server parity and low-latency evaluation designs — details in Docs.

How it works

  1. 1

    Add a flag

    Create release, ops, or experiment flags with owner and expiry.

  2. 2

    Target the rollout

    Percentage, tenants, roles, locale, and device — all deterministic.

  3. 3

    Measure and learn

    Emit exposure events and monitor impact with your favorite analytics.

  4. 4

    Clean up safely

    Retire stale flags with governance guardrails and upcoming AI assists.

Tell us what to build next

Take the quick survey — most people finish in 4–6 minutes.

We respect your privacy. See our Privacy Policy.

FAQ

Is there a hosted SaaS? Coming soon
We’re open-core first. A managed SaaS option is planned for teams that want fast enablement and zero infrastructure overhead.
Do you have pricing?
Not yet. We don’t want to bias your feedback — please take the survey. Pricing page is coming soon.
How can I contribute or follow progress?
Check the FlagshipX Docs repo for the charter, roadmap, and specs.
Who’s behind FlagshipX?
The project is led by Juliusz Ćwiąkalski as a solo founder initiative.
How do you handle privacy?
See our Privacy Policy. We use Google Analytics 4 with IP anonymization for aggregate usage insights.