Operations Source edition 1.1.0
Feature Flags
Choose who can try a feature.
Set boolean feature defaults, target particular customers or verified groups and evaluate the rules on your server. Keep a history of changes and choose a fallback for every feature call.
Example scenario
Let selected customers try a new screen
Keep a feature off by default and enable it for a verified group of customers. Evaluate the saved rule on your server and use the fallback you chose if the request fails. Your app still enforces permissions independently.
From setup to the result
- Choose each feature’s default and the fallback your app should use.
- Sync customer and group memberships from your trusted backend.
- Save targeting rules with a change reason and current edit version.
- Evaluate on the server, inspect the reason and revoke targets when memberships change.
What the package handles
What you can build with it
- Boolean rules with explicit customer and group targeting.
- Server-side decisions using trusted saved memberships.
- An administrator editor, before-and-after history and selected customer feature statuses.
Supported behavior
- Boolean defaults and explicit customer/group targets
- Server-side evaluation using verified saved memberships
- Current-version edits and before-and-after change history
- Staff editor, per-call fallbacks and selected customer-visible feature statuses
Before you choose
Will it fit your project?
Who it is for
- Products introducing features to selected customers.
- Teams that need reviewed changes and a predictable fallback when evaluation is unavailable.
Runtime and connections
Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.
Hosting and PostgreSQL costs are separate from the source purchase. A configured external receiver, if used, has its own requirements and costs.
A useful handoff to your coding agent
How setup works
The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.
- Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
- Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
- Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.
Questions to prepare
- Which customers or verified groups should receive each feature?
- What default and fallback should the app use for each feature?
- Who maintains group membership, reviews changes and chooses customer-visible feature labels?
What your agent checks
- Evaluate two customers with different verified memberships.
- Revoke group membership and verify the documented fallback.
- Reject customer-supplied targeting attributes and stale rule edits.
- Stop the service and verify the integrating app uses its local fallback.
Scope of this edition
Important limits
Flags control feature behavior; the app separately enforces permissions, protected data and paid access. This release has explicit boolean targets, with no percentage rollouts, experimentation analytics, multivariate rules or SDK cache.
- No percentage rollout, multivariate experiments, SDK cache or analytics.
- Flags never grant authorization, paid entitlements or access to protected data; the app must enforce those independently.
- Group memberships must be refreshed or revoked by the app backend. They have no automatic expiry.
- 1000 flags; 200 customer targets and 200 group targets per flag; latest 1000 changes per history request.
- HTTP/network failures require the caller's local fallback; no fabricated server success.
Before you decide
Will this work with my existing app?
The package runs on Node.js 22.13+ and PostgreSQL 17. Your coding agent connects it to your application using the included integration guide and supported interfaces. Check the requirements, supported behavior and limits on this page; compatibility with every framework or hosting provider is not promised.
What will my agent need from me?
Your goals, the relevant app details and permission to configure your own accounts. The setup questions on this page help prepare that handoff. Keep credentials in your own private environment; do not paste secrets into a public support request.
What happens if setup fails?
The package includes verification and troubleshooting resources so your agent can inspect the failure and resume the documented setup. Initial setup and reproducible-defect support lasts 30 days from purchase. The refund policy covers material defects we cannot fix, alongside applicable statutory rights.
Is this a subscription?
Helpful Mods sells the source package once. There is no monthly maintenance subscription or automatic renewal. Hosting and connected services have their own costs. Optional major upgrades require a separate purchase.
Can I buy this now?
Purchases are not open yet. You can inspect the product information and use the library planner while checkout is being prepared. A plan is not an order and does not grant source access.