# Mocco

> Everything a product needs to be built and run, except the code: deploy governance, OTA updates, feature flags, a status page, notifications, in-app messaging and a help center in one workspace. These are the customer guides, as Markdown.

## Getting started

- [What Mocco offers](https://www.mocco.club/docs/start/overview.md): What Mocco offers, grouped by job — Release (deploy governance, OTA and force update, feature flags), Operate (status page, notifications, audit log) and Support (messenger, help center) — plus API keys and SDKs, and where each guide is.
- [Set up a workspace and projects](https://www.mocco.club/docs/start/workspace-and-projects.md): Create a Mocco account, create a workspace, create a project with its handle, register an app for each platform, link repositories, and turn on the products you use.
- [Members and access](https://www.mocco.club/docs/start/members-and-access.md): Who is in a workspace and what owners, admins and members may do, and how roles on the Access page decide who approves gates, protected changes and credential releases.
- [API keys](https://www.mocco.club/docs/start/api-keys.md): A project's publishable and secret API keys — which kind goes where, what each scope allows, binding a flags key to one environment, creating, copying and revoking a key, and how Mocco answers a wrong key.
- [The audit log](https://www.mocco.club/docs/start/audit-log.md): What Mocco records in a workspace's audit log, how to read the Audit page, and how the hash chain shows that no entry was changed or removed.

## Deploy governance

- [Deploy governance overview](https://www.mocco.club/docs/governance/overview.md): How Mocco gates deploys — connect GitHub, describe a pipeline of steps and gates in .mocco.yml, start a run from a commit, approve or reject its gates, and release credentials only to a step behind an approved gate.

## Notifications

- [Notifications overview](https://www.mocco.club/docs/notifications/overview.md): What Mocco notifications do, the three parts of the Notifications screen (channels, sources, activity), and the order to set them up in.
- [Connect Discord](https://www.mocco.club/docs/notifications/connect-discord.md): How to install the Mocco bot in a Discord server, add channels, give the bot access to private channels, re-enable a disabled channel, and choose which events each channel gets.
- [Connect Sentry](https://www.mocco.club/docs/notifications/sentry.md): How to send new Sentry issues to Mocco with a Sentry internal integration, which secret to paste, the events and filter keys you get, and how to check it works.
- [Connect Vercel](https://www.mocco.club/docs/notifications/vercel.md): How to send Vercel deployment events to Mocco with a team webhook (Pro and Enterprise plans), which secret to paste, the events and filter keys you get, and how to check it works.
- [Connect GitHub](https://www.mocco.club/docs/notifications/github.md): How to send GitHub repository or organization webhooks to Mocco, the one-time secret Mocco generates, which events to select, the events and filter keys you get, and how to check it works.
- [Mocco events](https://www.mocco.club/docs/notifications/mocco-events.md): The events Mocco produces on its own for deploy governance (runs and gates), what each message shows, their filter keys, and the Mocco preset.
- [Notifications troubleshooting](https://www.mocco.club/docs/notifications/troubleshooting.md): How to read the Activity tab and what to do for every receipt outcome, every refused delivery, every delivery status and Discord error, disabled channels, and rules that did not match.

## OTA and force update

- [OTA and force update overview](https://www.mocco.club/docs/ota/overview.md): What Mocco's OTA product does today — force update for store apps, and approval-gated publishing with the OTA tool you already use — and the order to set it up in.
- [Force update](https://www.mocco.club/docs/ota/force-update.md): Set a minimum, recommended and blocked versions for each store app, require approval for raising them, review emergency changes, and call the version check from your React Native app.
- [Release a token to your pipeline](https://www.mocco.club/docs/ota/pipeline.md): Store your OTA tool's publishing token in Mocco, allow one pipeline gate to receive it, request it in .mocco.yml, and fetch it from a GitHub Actions workflow after the gate is approved.
- [Gate EAS Update](https://www.mocco.club/docs/ota/gate-eas-update.md): Publish EAS Updates only after a Mocco gate is approved — create a robot token in Expo, store it in Mocco, and run eas update with the released EXPO_TOKEN.
- [Gate CodePush](https://www.mocco.club/docs/ota/gate-codepush.md): Publish CodePush releases (Revopush, Codemagic, Bitrise or a self-hosted code-push-server) only after a Mocco gate is approved, with the access key Mocco releases to the publishing step.
- [Gate hot-updater](https://www.mocco.club/docs/ota/gate-hot-updater.md): Deploy hot-updater bundles only after a Mocco gate is approved, by keeping your storage provider's credentials in Mocco and writing them to .env.hotupdater in the publishing step.
- [Host OTA updates on Mocco](https://www.mocco.club/docs/ota/hosted-updates.md): Serve signed Expo Updates from Mocco to the stock expo-updates client — connect the app, register its signing certificate, publish from CI with mocco-ota, roll out by percentage, and roll back instantly.
- [Move to Mocco-hosted OTA from CodePush or EAS Update](https://www.mocco.club/docs/ota/migrate-to-hosted.md): What changes when you move an app from App Center CodePush or EAS Update to Mocco-hosted updates — the client, the config, signing, channels, CI and the cut-over order.

## Feature flags

- [Feature flags quickstart](https://www.mocco.club/docs/flags/quickstart.md): Create environments and a flag in Mocco, bind a server key to one environment, and evaluate flags locally from Node with the OpenFeature provider, or from flagd.
- [Feature flags in browsers and apps](https://www.mocco.club/docs/flags/browsers-and-apps.md): Use Mocco feature flags from a web page, a React app or a React Native app with a publishable key, the OpenFeature web SDK and Mocco's web or React Native provider; plus the Vercel Flags SDK on the server.
- [Flags as code](https://www.mocco.club/docs/flags/flags-as-code.md): Declare feature flags in your repository with .mocco/flags.yml — pull requests show what merging would do, a merge to the default branch updates unprotected environments at once and leaves protected ones waiting for approval, while the kill switch stays in the console.
- [Clean up stale flags](https://www.mocco.club/docs/flags/stale-flags.md): How Mocco spots feature flags that look ready to remove from your code (never evaluated, not evaluated lately, or fully rolled out) from the evaluation counts its SDKs send, and how to dismiss a hint or turn the counts off.

## Messenger

- [In-app contact with Mocco Messenger](https://www.mocco.club/docs/messenger/contact-us.md): Let your app's signed-in users contact your team from inside the app, and answer them from the Mocco inbox — set up the messenger, sign user ids on your server, call the messenger API from your app, and reply, note, close or block in the console.

## Help center

- [Publish a help center](https://www.mocco.club/docs/help/help-center.md): Set up a public help site for a project, write articles in Markdown with a live preview, import from Mintlify, publish, translate into other languages with a glossary, and restore an earlier version — and how readers reach the site.

## Feedback board

- [Open a public feedback board](https://www.mocco.club/docs/feedback/public-board.md): Put a project's feedback board on the web for your users, where they read ideas, filter them, post their own, vote and comment — how to publish it, how your app signs its users in to it, and what visitors without an account can do.

## Status page

- [Run a status page](https://www.mocco.club/docs/status/status-page.md): Create a status page for a project, list the parts of your service as components, declare incidents and post updates as they move from investigating to resolved, see the deploys around an incident, write a postmortem, schedule maintenance that Mocco starts and ends on time, and let a resumed deploy gate announce maintenance until its run finishes.
- [Monitor your service](https://www.mocco.club/docs/status/monitor-your-service.md): Run the Mocco probe at a private location, create an HTTP or TCP monitor that checks your service every minute, and see what happens when it fails — the components it changes, the draft incident it opens and follows, the alerts it sends — how Mocco watches your monitors right after a deploy, and how a heartbeat monitor alerts when a cron job stops pinging.
- [Let visitors subscribe](https://www.mocco.club/docs/status/subscribers.md): How visitors of your public status page get told about incidents and maintenance by email, signed webhook or Atom feed; what they receive, how they confirm and unsubscribe, how to check a webhook's signature, and what a self-hosted server needs to send email and webhooks.

## Agents (MCP)

- [Connect Mocco to your agent](https://www.mocco.club/docs/mcp/connect.md): Add Mocco's MCP server to Claude Code, Claude Desktop, Cursor, VS Code or any MCP client — what it can see, what it can do, what it will never do, and how to turn the deciding tools on.