For teams that build and run a service
Everything your product needs,
except the code.
Ship it, run it and hear from the people who use it — in one workspace. Deploys, OTA updates, feature flags, alerts, a status page, in-app messaging and your help center share the same team, the same roles and the same history, instead of ten tools that don’t know about each other.
Example · one morning in a workspace
- 09:12Releaseapi deployed to productiongate approved by Minji
- 09:40OperateSentry: CheckoutError is spikingposted to #oncall on Discord
- 09:41ReleaseKill switch: new-checkout offapplied at once · by Ben
- 09:55Support“I can’t pay with my card”new conversation in the inbox
- 10:20SupportHelp article “Payment methods” publishedin English, Korean and Japanese
Use one product, or all of them.
Start with the one you need today and turn on the rest when you need them, per workspace.
Release
Write ≠ ship: changes that add risk wait for the right people.
- Deploy governance Pipelines pause at gates on GitHub Actions. Production credentials exist only after approval.
- OTA and force update Host React Native updates with rollouts and instant rollback, or gate the tool you use today; raise minimum app versions only with approval.
- Feature flags Targeting, segments and rollouts over OpenFeature, with approvals and a kill switch.
Operate
Know what happened, and who did it.
- Status page Components, incidents with updates and postmortems, and maintenance Mocco starts and ends on time. The public page is coming next.
- Notifications Mocco, Sentry, Vercel and GitHub events routed to the Discord channels that need them.
- Audit log Every approval, credential release and production change, in one record.
Support
Hear from the people who use what you built.
Coming next: App reviews · Feedback board · Forum · Deep links · End-user identity
One workspace, not ten tools.
Separate tools each keep their own users, permissions and logs. In Mocco every product starts from the same ones.
One team, one set of roles
Invite people once. The role that approves a deploy also approves a flag change, an OTA release or a raised minimum version.
One record
Every approval, production change and credential release, from every product, lands in the same tamper-evident audit log.
One place to look
Home shows the approvals waiting across products; alerts from Sentry, Vercel and GitHub and your users’ messages arrive in the same workspace.
For your team and your agents.
The console, the public API, the SDKs, the CLI and the MCP server sit on the same services and check the same roles.
SDKs
OpenFeature providers for Node, web and React Native, and a React Native SDK for OTA, messenger and help.
npm install @mocco/openfeature-serverCLI
Publish OTA updates from CI. Your signing key never leaves CI, and Mocco serves exactly the bytes it signed.
npx mocco ota publish --channel stagingMCP
Agents read what Mocco knows. Anything that approves or ships still needs a person.
claude mcp add --transport http mocco https://www.mocco.club/api/mcp
Open source. Self-hostable.
Mocco is AGPL-3.0 and runs on Node and Postgres, on Vercel or your own servers. The SDKs are MIT.