Roles that make sense.
Organizations hold projects. Viewers read, members alert and share, admins run projects and keys, owners run owners.
ViewerMemberAdminOwner
Read
Alerts and share links
Projects, keys, members
Owners
The same lens, for the team.
WizeLens Cloud is the dashboard you already know, with accounts, 30 days of history, alerts, share links, and AI access you can scope. Today you run it yourself, on your own Postgres.
npx @wizeworks/lens-cloudBuilt for more than one person.
Everything the in-app dashboard does, plus the parts a team needs.
30 days of history.
Every page is computed on the server, from stats tables, never from a sample.
24 hours7 days30 days
Alerts that say what happened.
Error rate, latency, traffic, new errors, slow queries, or any metric. To webhooks and Slack, when it fires and when it clears.
When error rate is above 2% over 5 minutes in production, tell #alerts on Slack.
Error rate is 3.4% (above 2%)
Share one trace.
A read-only link to one trace, for 1 to 30 days. Revoke it any time.
GET /api/customers-with-orders · trace e8fa3b92
Fast with a lot of data.
Measured at 200 traces a second on Postgres.
0traces on Postgres
0traces a second
< 0 msfor every page
Keys for apps and agents.
Apps send with an ingest key. Agents read with a read key.
wl_ik_…Ingest keyOne project. Apps send data with it.wl_rk_…Read keyProjects you pick. Read-only, for agents and scripts.An audit log.
Who changed what, and every call an agent made.
10:40Ada M. made ingest key orders-api
10:41Jo M. invited [email protected] as member
10:42read key agents called find_n_plus_one
10:43Ravi K. shared trace e8fa3b92 for 7 days
10:44Ada M. set retention to 90 days
10:45read key agents called get_trace
10:46Ada M. made ingest key orders-api
10:47Jo M. invited [email protected] as member
10:48read key agents called find_n_plus_one
10:49Ravi K. shared trace e8fa3b92 for 7 days
10:40Ada M. set retention to 90 days
10:41read key agents called get_trace
Keep what you need.
Retention per organization.
1 day30 days by default400 days
Same dashboard. Pick the size.
Start in your app. Move to the hub or the cloud when you need to. Nothing about the dashboard changes.
In your appThe local hubWizeLens Cloud
Data lives inA SQLite file next to each appOne SQLite filePostgres
How far back24 hours or 2,000 traces7 days30 days (1 to 400)
ServicesFound by following the traceEvery service, plus any OpenTelemetry appEvery service, by project and environment
PeopleYouYour team, with one shared tokenOrganizations, roles, and invites
AlertsNot hereNot hereWebhooks and Slack
Share linksNot hereNot hereRead-only, 1 to 30 days
AI accessOne read-only endpoint per serviceOne endpoint for every serviceRead keys per project, audited
Run it yourself.
One Docker Compose file with Postgres. Put it behind https, create the first account, and you own the first organization.
docker compose -f deploy/docker-compose.cloud.yml up -d- Start it with POSTGRES_PASSWORD and WIZELENS_CLOUD_PUBLIC_URL set.
- Sign up as the first account, then invite your team.
- Make an ingest key per app and set WIZELENS_HUB and WIZELENS_HUB_TOKEN.
- Keys are stored as hashes. The secret is shown once.
- The sign-in cookie is HttpOnly, and secure on https.
- Every change from a browser needs a header another site cannot send.
- Webhooks cannot reach private addresses unless you allow it.
- Passwords, tokens, and keys are redacted before they are stored.
- Every MCP call goes to the audit log, with the key that made it.