Pick a Day for an hourly active-user graph (IST), or set From/To. Default is the last 24 hours.
Snapshot
Circles, invites, messages, and secret crush
These counts follow the date and time above. All-time totals are in the line under each number.
Active users by hour
Distinct people who called the API in each IST hour. Hover a bar for the exact count. Use Day / Today / Yesterday above.
Active users
24 hour graph
Each point is one hour, in IST. Active users, signups, and deactivations.
Active users (DAU)New signupsDeactivations
Peak hours
Busiest hours in this window, by distinct people who called the API. Times are IST.
Hourly breakup
One row per hour in the selected window. The busiest hour is highlighted. Times are IST.
Hour
Active users
Signups
Deactivations
API requests
iOS vs Android
Counts from latest device type. Active means an API call in the last 24 hours.
How long users stay active
From signup / latest login / first→last API today. Deactivated users use signup → deactivate time.
Group
Platform
Users
Avg from signup
P50 from signup
Avg API span
Avg from login
Active in the last 24 hours
User
Platform
Status
From signup
From login
API span today
Last active
Activation vs deactivation vs daily active users
Hourly signups, deactivations, and API callers for the last 24 hours.
Active users (DAU)New signupsDeactivations
Retention rainfall, D0–D7
Each row is people who signed up that day. Each drop is the share who used the app on that exact day after signup. D0 is the signup day. A blank cell means that day has not arrived. A larger, darker drop means more people came back. Shows at least the last 14 days of signups.
Churn rainfall, D0–D31
Each row is people who signed up that day. Each drop is the share who deactivated on that exact day after signup. D0 is the signup day. Blank cells have not arrived yet. Larger, darker drops mean more people left that day. Uses at least 45 days of signups so D31 can mature.
When leavers deactivated (days after signup)
Among deactivated accounts in the lookback. D31 includes anyone who left on day 31 or later, capped at the column.
Same-day leavers by hour after signup
Only D0 deactivations. Hour 0 is the first hour after account creation.
Pages / surfaces from API traffic
Inferred from request paths (not client screen events).
Where users were before deactivating
Last API surface in the 30 minutes before /users/me/deactivate.
Surfaces touched 15 min before deactivate
A user can appear in multiple rows.
Recent deactivations
User
Platform
When
Active from signup
Last page
Last path
Top API paths
Path
Requests
Users
Auto-refreshes every 10 minutes · live from api_request_events (IST)
Distinct signed-in users hitting the API in the same minute. Admin and health paths are excluded. Charts use the last 48 hours; peak minutes use the last 7 days.
Peak users in one minute
—
Loading…
Comfortable concurrent users
250
Host guidance · same request rate as measured peaks
Stretch before the database gets tight
~400
3 API workers · Postgres allows 100 connections
HTTP 5xx (last 48h)
—
Loading…
Concurrent means the same minute
Loading…
Signed-in users per hour
Last 48 hours IST. Each point is unique user ids that hour, not people online at the same instant.
API requests per hour
Last 48 hours IST.
Busiest minutes
Last 7 days IST.
Minute (IST)
Users
Requests
Requests / user
Why 250
Comfortable capacity assumes roughly 8–10× headroom above a measured peak minute at ~20–30 requests per user per minute and ~30 ms average latency on this 8-core / 32 GB host, with Postgres and media still fitting.
Live peak will update the headroom bars below.
What runs out first
RAM is not the limit. The API runs 3 Node workers. Postgres allows 100 connections. Past roughly 400 concurrent users at this request rate, workers and the connection cap are the first things to watch.
A heavier home feed, or image work on this same machine, would lower the number.
Headroom versus the peak minute
Comfortable and stretch are guidance. The seen peak is live.
Seen peak
—
Comfortable
250
Stretch
400
Pending means signup OTP was never finished. Ask them to resend OTP in the app, or ignore obvious test/disposable emails.
Photo
Name
Username
Email
Phone
Platform
Gender
Status
Signup OTP
Plan
Subscribed
SMS
Push
Followers
Following
Joined
Subscription
Messages
Stored Direct and Circle messages. Encrypted messages have no text on the server.
Stories
Posts
0 selected
Review every post in one queue. Select multiple rows for bulk approve, reject, or remove.
Live stories
Users with an active story right now.
0 selected
Select stories to remove them from the live feed. Removed stories disappear for all users.
Violence, sexual content/nudity, intellectual property, and harassment reports hide the content for everyone and land here first.
When
User
Event type
Tip / campaign
Title
Delivery
Read
Platform
1. Choose a starting point
Presets fill copy and tip keys. Pick Custom to write your own.
2. Message
Title and body show on the lock screen. Tip key controls dedupe and deep-link routing.
3. Who should get it?
Everyone matched must have an active push token. Seed accounts are excluded. Default status is Active.
Paste usernames’ user IDs from the Users tab. Skip list is applied after every other filter.
Phone preview
Coffybee · now
COFFYBEE
Notification title
Your message will appear here.
4. Preview & send
Always preview the audience before sending.
—
Run preview to see how many devices will get this.
Sending notifies every matched active device. There is no undo.