Usage reports
The short daily report a Gateway sends Every App, what is in it, what is never in it, and how to turn it off.
Once a day, a self-hosted Gateway sends us a short report so we know how many Gateways are running and how many people use them. We use it to decide what to build and to show that Every App is growing.
Reports are on by default. You can read the exact report before it goes, and turn reports off at any time.
What is in it
This is a whole report:
{
"schema": 1,
"install": "5f0c1e9a7b3d4e21a8c6d2f4b9e07a13",
"day": "2026-11-20",
"version": "0.4.2",
"installed": "2026-11",
"members": 7,
"active_members_1d": 3,
"active_members_7d": 4,
"apps": 3,
"mcp_servers": 2,
"app_use_1d": [
{ "app": "openseo", "active_members": 3, "tool_calls": 40 },
{ "app": "other", "active_members": 2, "tool_calls": 7 }
],
"mcp_use_1d": { "active_members": 1, "tool_calls": 20 }
}| Field | What it is |
|---|---|
schema | The version of this list of fields. |
install | A random ID your Gateway made for these reports and nothing else. |
day | The day the counts are for (UTC): yesterday. |
version | The Gateway's version. |
installed | The month the Gateway was set up. |
members | How many people are in the workspace. |
active_members_1d, active_members_7d | How many of them used the Gateway or an app that day, and in the 7 days up to it. |
apps | How many apps are deployed and active. MCP servers aren't counted here. |
mcp_servers | How many MCP servers are connected and turned on. |
app_use_1d | For each of our apps used that day (OpenSEO, OpenCRM, OpenMail, OpenAnalytics, OpenScribe, RepoLens): how many people used it through an AI client or a provider call, and how many AI tool calls it had. All the apps of your own are one row, other. |
mcp_use_1d | The same two counts for all your MCP servers together. None is named. |
Every count is rounded down to one significant digit: 37 members is sent as 30, and 4,812 tool calls as 4000. Member counts stop at 1000.
What is never in it
- Your domain, your Cloudflare account or your Gateway's address.
- Anyone's name or email.
- The names of apps you built, or of MCP servers you connected.
- Tool names, prompts, files, or anything inside an app.
- Which person did what, or at what time of day.
What we can tell
Each report carries a random ID. It tells us that two reports came from the same Gateway, and not whose Gateway it is.
We don't store your domain or the time a report arrived. No other company receives the reports.
See the report
Open Manage workspace, then Usage reports (owners and admins). It shows the next report exactly as it will be sent, and the last one sent. Or:
everyapp telemetryTurn it off
Select Turn off on that page, or:
everyapp telemetry offReports stop at once and the random ID is deleted. everyapp telemetry on turns them back on with a new ID.
Before a Gateway ever sends one
To set up a Gateway with reports off:
everyapp setup --no-telemetryDO_NOT_TRACK=1 in the shell that runs everyapp setup or everyapp update does the same.
For good
To make it impossible to turn on from the page:
everyapp secret set TELEMETRY_DISABLEDEnter 1 when it asks for the value.
When reports start
- A new Gateway sends its first report a day after setup.
- A Gateway that was set up before usage reports existed sends its first report 7 days after the update that brought them. Until then, Manage workspace shows a notice with the date.
A Gateway built from a clone of the repository never sends reports. Neither does the hosted Gateway.
What else talks to us
The CLI, the SDK and your apps send us nothing. The Mac app checks updates.everyapp.com for new versions. This website counts page views: Privacy.
How long we keep reports
25 months. Then they are deleted.