Mardo · the whole product loop
Mardo, end to end.
People arrive. The app checks. Builds move. Licenses land.
The commercial path
From interest to ownership
Different sources, one honest sequence
Pulse
The product moving through time
visits
update checks
ZIP transfers
licenses
Releases & automatic updates
What crossed the wire
Edge requests identify the client and complete response. R2 confirms what storage served.
By release
Versions fetched
| Version | Total | Updater | Tooling | Last seen |
|---|
By client
Who asked
Request evidence
Recent update and archive activity
| When | Request | Client | Country | Status | Bytes |
|---|
Corroborating storage signal
R2 operations
R2 operation totals are useful for confirming object activity. They are adaptively sampled and are not treated as a person or exact download count.
Buy & licenses
What became a purchase
Request activity comes from the edge. Paid licenses and delivery outcomes come from aggregate-only D1 queries.
Mardo.app
Traffic detail
Page views—
P75 load—
Pages
Referrers
Countries
Audience shape