How this works: traffic on the left becomes JSON events, the belts carry them to Postcone, and Postcone turns them into a table and suggests charts. Ship a change in station 2 to add a field, then watch a new column and new charts land at the next commit. Click anything to find out what it is. Ship a change in the App station, then walk down the belt below to watch it become a column and new charts. Tap anything to find out what it is.
People using your product
Nobody here knows Postcone exists. They just use your app.
Handles requests, emits events
idle — press play
Ship a change 0/7
Ingest · schema · table
next commit in 10s · a shorter window means fresher data and smaller files
analytics.api_requests 720 rows
Older rows keep NULL for columns added later. Nothing already stored is rewritten.
Proposed from the schema, backed by SQL
6 views suggested from 5 columns. Click one for the query and the reasoning behind it.
| route | events | p95_ms |
|---|---|---|
| /api/feed | 266 | 182 |
| /api/search | 198 | 218 |
| /api/login | 115 | 249 |
| /api/checkout | 94 | 333 |
| /api/upload | 47 | 1552 |
Everything here runs in your browser. No API calls leave the page, the traffic is generated locally, and the SQL runs against the rows this simulation produced.Simulated in your browser. Send real events →