TiloBox
Back to directory
flagd project preview

flagd

A feature flag daemon with a Unix philosophy that delivers flag evaluations over gRPC and HTTP.

LicenseApache-2.0
GitHub stars1.2k
Last commit1 weeks ago
Tags6 topics
Cncf SandboxOpenfeature SidecarDevopsGrpc Feature FlagsFlag DaemonGolang
Overview

Why consider flagd?

flagd is a lightweight feature flag daemon developed by the CNCF OpenFeature project in Go. It operates as a sidecar or standalone service, evaluating feature flag logic in sub-millisecond times over gRPC and HTTP protocols using pluggable sync backends (Kubernetes CRDs, Git, HTTP).

Guided learning

Learn flagd by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of flagd

flagd evaluates feature flags in local Kubernetes pod sidecars, completely removing external SaaS dependencies.

Docker Quickstart

bash
1docker run -d -p 8013:8013 -v $(pwd):/etc/flagd ghcr.io/open-feature/flagd:latest start -f /etc/flagd/demo.flagd.json

flagd is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

flagd FAQs

flagd is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

flagd is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

flagd is listed as an alternative to Split Synchronizer. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.