Skip to content

Overview

FluxGate documentation

FluxGate separates deploying code from releasing a feature. You ship code with the feature switched off, then decide who sees it, when, and with whose approval, without another deploy.

These docs follow one story from install to production. The Checkout team at Juniper Market, an online grocery, wants to roll out a one-tap express checkout safely: Plus users in Canada first, then a 20/80 split for everyone else, gated by approvals, driven from Jira, with an AI assistant flagging risky changes. Every chapter has a short video and a written guide with the details and examples the video has no time for. To watch all 16 videos in order, open the FluxGate playlist on YouTube.

Start here

  • Want it running now? Follow the developer guide: an empty folder to a first flag evaluation, by copying commands.
  • Want to understand it first? Read What is FluxGate, then follow the chapters in order. Each page builds on the one before.

The cast

UserRole in the storyFluxGate role
adminPlatform adminSystem admin
priyaCheckout developerRequester
samRelease managerApprover

Get started

Install FluxGate and set up who can do what.

Model your release

Describe where code runs, what your app knows about a user, and what you release.

Connect your app

Observe and operate

Enterprise

Identity, resilience and governance for larger organizations. Start with the Enterprise overview: it says which edition each feature needs.

Developer guide

The copy-paste path from an empty folder to a running FluxGate: Developer guide.

Reference