Feature flags with EU data sovereignty
Flags are part of the production control plane: they encode rollout strategy, customer segments and operational behaviour. MOJAQ hosts feature flags in Helsinki, with no US transfers and a DPA included, so the control data around your releases stays in Europe even when flags touch regional access or specific customer groups.
Boolean flags, rollouts and targeting
Turn features on and off with boolean flags, expose changes gradually with percentage rollouts to shrink blast radius, and use targeting to control access by user, group or environment. Together they let you ship code separately from activation, test in production with a small audience, and pause instantly when something looks wrong.
curl "https://api.mojaq.com/v1/flags/new-checkout?user_id=usr_123" \
-H "x-api-key: $MOJAQ_API_KEY" Release control next to your signals
Flags are most valuable when they connect to the rest of the picture. If a rollout causes errors, your error tracking is right there; if it changes a page, analytics is too; if it affects availability, uptime monitoring catches it. MOJAQ keeps flags in the same EU-hosted platform as those signals, behind one API key, so you can roll forward or back with full context.
Questions
What flag types are supported?
Boolean flags, percentage rollouts and attribute targeting, evaluated through one API.
Where is my data stored?
In Helsinki, Finland, in the EU, with no US transfers and a DPA included.
What does it cost?
Free during the open beta, with no fixed end date.