Myrk Feature Flags

Description

WordPress feature flags and feature toggles built for development teams shipping on complex sites. No external feature flag service, no Redis, no third-party account — all state lives in your WordPress database.

Define flags in code. Control state from the admin.

Register feature flags in your plugin or theme — version controlled and peer reviewable. Enable, disable, and roll out per environment without code changes or redeploys.

Designed for teams practicing trunk-based development and continuous delivery — merge to main confidently and control what users see from the database.

Coming from a SaaS feature flag service?

Myrk works differently: your codebase is the source of truth. Flags are declared with Myrk::register() in PHP and committed to your repo — they appear in the admin automatically. The admin controls state only; it does not create flags. This keeps your flag inventory version controlled and peer reviewed, the same as everything else in your codebase.

Key features

• Code-registered flags — Myrk::register() in PHP, reviewed in Git
• Per-environment state — uses wp_get_environment_type() automatically
• Progressive rollout — deterministic percentage rollout, no cookies required
• Targeting rules — role, capability, user ID, email domain
• Circuit breaker — Myrk::attempt() wraps risky code with automatic fallback
• Stale flag detection — visual badge for feature toggles inactive 90+ days
• REST API — full CRUD, powers admin UI and CI/CD pipeline automation
• WP-CLI — complete feature flag management from the command line
• No external dependencies — no Redis, no Node, no third-party service

Source Code

The compiled JavaScript in build/ is generated from source files in assets/js/ using @wordpress/scripts (webpack). Both the source and compiled files are included in the plugin zip. To rebuild the compiled assets, install Node.js dependencies with pnpm install and run pnpm build.