The Git-native, enterprise-ready feature management platform that developers love

---

[!NOTE]
Looking for Flipt v1? You can find the v1 code on the main branch and documentation at docs.flipt.io.

Why Flipt v2?

Finally, feature flags that work with your existing Git workflow.

Flipt v2 is the first truly Git-native feature management platform that treats your feature flags as code. Store your flags in your own Git repositories, use your existing branching strategy, and deploy flags alongside your code using the tools you already know and trust.

🚀 Git-Native by Design

• Own your data: Store feature flags directly in your Git repositories
• Version control: Full history and blame for every flag change
• Branch and merge: Test flag changes in branches before merging to production
• Deploy together: Feature flags deploy with your code using existing CI/CD pipelines

🌍 Multi-Environment with Git Flexibility

• Environment per branch: Map environments to Git branches for seamless workflows
• Environment per directory: Organize flags by microservice or team within a single repo
• Environment per repository: Separate repos for different products or security domains
• Complete isolation: Each environment has its own namespaces, flags, and configurations

⚡ Developer Experience First

• Zero infrastructure: No databases, no external dependencies by default
• GitOps ready: Works with existing Git-based deployment workflows
• Real-time updates: Server-Sent Events (SSE) streaming API for instant flag propagation to client-side SDKs without polling
• Modern UI: Intuitive interface with full Git integration and dark mode support

🔒 Enterprise Security & Control

• Self-hosted: Keep sensitive flag data within your infrastructure
• Secrets management: Secure storage and retrieval of sensitive configuration data (OSS)
• GPG commit signing: Cryptographically sign all flag changes for enhanced security (Pro feature)
• Merge proposals: Code review workflow for flag changes (Pro feature)
• Audit trails: Complete history of who changed what and when
• OIDC/JWT/OAuth: Enterprise authentication methods supported

Flipt v1 vs v2: What's New?

Use Cases

Perfect for engineering teams that want to:

• Ship faster with confidence: Deploy flags with your code using existing Git workflows
• Enable trunk-based development: Merge incomplete features behind flags without risk
• Implement proper GitOps: Treat infrastructure and feature flags as code
• Maintain security compliance: Keep sensitive flag data within your infrastructure
• Scale with multiple environments: Manage flags across dev, staging, and production seamlessly
• Enable team collaboration: Use familiar Git workflows for flag reviews and approvals

Quick Start

See our quickstart guide for more details.

Local

# Install Flipt
curl -fsSL https://get.flipt.io/v2 | sh

# Wizard-driven setup to get you started quickly
flipt quickstart

# Run Flipt server
flipt server

Docker

docker run --rm -p 8080:8080 -p 9000:9000 -t docker.flipt.io/flipt/flipt:v2

Flipt UI will be available at http://127.0.0.1:8080/.

Nightly Builds

[!WARNING]
Nightly builds are automatically generated from the latest v2 branch and should not be considered stable for production use.

To run the latest nightly build:

docker run --rm -p 8080:8080 -p 9000:9000 -t docker.flipt.io/flipt/flipt:v2-nightly

Nightly builds include the latest features and bug fixes but may contain untested changes. Use them for testing new features or verifying bug fixes before the next stable release.

Configuration Example

# config.yml - Git-native setup with secrets management
secrets:
  providers:
    # File-based secrets (OSS)
    file:
      enabled: true
      base_path: "/etc/flipt/secrets"
    # HashiCorp Vault (Pro feature)
    vault:
      enabled: true
      address: "https://vault.example.com"
      auth_method: "token"
      token: "hvs.your_token"
      mount: "secret"

storage:
  type: git
  git:
    repository: "https://github.com/your-org/feature-flags.git"
    ref: "main"
    poll_interval: "30s"
    signature:
      enabled: true
      type: "gpg"
      key_ref:
        provider: "vault"  # Requires Pro license
        path: "flipt/signing-key"
        key: "private_key"
      name: "Flipt Bot"
      email: "bot@example.com"

environments:
  default:
    storage: git
  staging:
    storage: git
    directory: "staging"

For more setup options, see our configuration documentation.

Core Values

• 🔒 Security - HTTPS, OIDC, JWT, OAuth, K8s Service Token, and API Token authentication methods supported out of the box
• 🗝️ Secrets Management - Secure storage and retrieval of sensitive data with file-based providers (OSS) and HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager, Azure Key Vault (Pro features)
• 🎛️ Control - Your data stays in your Git repositories within your infrastructure
• 🚀 Speed - Co-located with your services, no external API calls required
• ✅ Simplicity - Single binary with no external dependencies by default
• 🔄 GitOps Ready - Native Git integration that works with your existing workflows
• 👍 Compatibility - GRPC, REST, Redis, Prometheus, ClickHouse, OpenTelemetry, and more

Key Features

Git-Native Storage

• Store flags directly in Git repositories alongside your code
• Full version control with Git history, blame, and diff support
• Integrates with your SCM (GitHub, GitLab, BitBucket, Azure DevOps, Gitea, etc.)
• GPG commit signing for cryptographic verification of changes

Multi-Environment Management

• Environment per Git branch, directory, or repository
• Complete environment isolation with independent configurations
• Seamless environment promotion workflows

Secrets Management & Security

• Multi-provider secrets management: File-based providers available in OSS, HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager, and Azure Key Vault (Pro features)
• GPG Commit Signing: Cryptographically sign all flag changes with keys from secret providers (Pro feature)
• Secure key storage: Private keys and sensitive data stored securely in Vault or local files
• Multiple auth methods: Token, Kubernetes, and AppRole authentication for Vault

Advanced Flag Management

• Complex targeting rules and user segmentation
• Percentage-based rollouts
• Real-time flag evaluation with Server-Sent Events (SSE) streaming updates for instant synchronization

Developer Experience

• Modern UI with Git integration and dark mode 🌙
• Declarative flag configuration with JSON/YAML schemas
• Comprehensive REST and gRPC APIs

Enterprise & Security Features

• Authentication: OIDC, JWT, OAuth, and more authentication methods supported out of the box
• Observability: OpenTelemetry and Prometheus integration 🔋
• Secrets Management: File-based providers (OSS) with HashiCorp Vault integration available in Pro
• Enterprise Workflows: GPG commit signing, merge proposals, and DevOps integration available in Pro

Ready for enterprise features? Flipt v2 Pro includes advanced workflows, enhanced security, and dedicated support. Get started with a free 14-day trial – no credit card required.

Learn More About Pro Features →

Are we missing a feature that you'd like to see? Let us know by opening an issue!

Integration & SDKs

Check out our integration documentation for comprehensive guides.

Server-Side Evaluation

• REST API - Full HTTP API for any language
• gRPC API - High-performance binary protocol

Client-Side Evaluation

• Local evaluation - Reduce latency with client-side flag evaluation, evaluate flags within your application for extreme speed and reliability.

OpenFeature Integration

Flipt supports the OpenFeature standard for vendor-neutral feature flag evaluation, including the emerging OpenFeature Remote Evaluation Protocol (OFREP) for standardized remote flag evaluation.

Contributing

We would love your help! Before submitting a PR, please read over the Contributing guide.

No contribution is too small, whether it be bug reports/fixes, feature requests, documentation updates, or anything else that can help drive the project forward.

Not sure how to get started? You can:

• Join our Discord, and ask any questions there
• Dive into any of the open issues, here are some examples:
  • Good First Issues
  • Backend
  • Frontend

Review the Development documentation for more information on how to contribute to Flipt.

Flipt v2 Pro

Ready to unlock the full potential of Git-native feature management? Flipt v2 Pro adds enterprise-grade features on top of our solid open-source foundation.

What's Included in Pro

• 🔀 Enterprise DevOps Integration - Native GitHub, GitLab, BitBucket, Azure DevOps, and Gitea workflows with merge proposals and automated PR/MR creation
• ✍️ GPG Commit Signing - Cryptographically sign all changes for maximum security and auditability with verified commit badges
• 🔒 Integrated Secrets Management - Built-in secure storage for GPG keys with HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager, and Azure Key Vault integration
• 🌐 Air-Gapped Environment Support - Annual licenses work seamlessly in air-gapped environments with offline validation
• 🏢 Dedicated Support Channel - Direct access to our engineering team via dedicated Slack channel for faster issue resolution
• ⚡ Priority Development - Your bug reports and feature requests get prioritized
• 🔧 Enterprise Auth - Advanced authentication providers (🔄 coming soon)
• 📊 Advanced Analytics - Enhanced reporting and insights (🔄 coming soon)

Pricing & Trial

• Free 14-day trial - No credit card required to start, includes all Pro features
• Monthly licenses - $200/month with continuous internet connectivity for validation
• Annual licenses - $2,000/year (save $400) with offline validation using license files for air-gapped environments
• No instance limits on paid plans - run Flipt v2 Pro on as many servers as you need
• Cancel anytime - Prorated billing through our Stripe customer portal

Start Your Free 14-Day Trial →

Trial includes up to 5 instances. Upgrade seamlessly to unlimited instances with a paid subscription.

Community

For help and discussion around Flipt, feature flag best practices, and more, join us on Discord.

 

Release Cadence

Flipt follows semantic versioning for versioning.

We aim to release a new minor version of Flipt every 2-3 weeks. This allows us to quickly iterate on new features. Bug fixes and security patches (patch versions) will be released as needed.

Development

Development documentation is available for those interested in contributing to Flipt.

We welcome contributions of any kind, including but not limited to bug fixes, feature requests, documentation improvements, and more. Just open an issue or pull request and we'll be happy to help out!

Licensing

There are currently two types of licenses in place for Flipt:

1. Client License
2. Server License

Client License

All of the code required to generate GRPC clients in other languages as well as the Go SDK are licensed under the MIT License.

This code exists in the rpc/ directory.

The client code is the code that you would integrate into your applications, which is why a more permissive license is used.

Server License

The server code is licensed under the Fair Core License, Version 1.0, MIT Future License.

See our licensing docs and fcl.dev for more information.