Mardo · the whole product loop

Mardo, end to end.

People arrive. The app checks. Builds move. Licenses land.

Website visits — Cloudflare RUM Human arrivals measured in the browser.

Buy page visits — mardo.app/buy/ Visits that reached the purchase decision.

Successful ZIP GETs — HTTP 200 archive responses Updater, pipeline, and browser clients labeled separately below.

Licenses issued — Paid orders in D1 Completed purchase records, with no customer identity exposed.

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.

Update checks—all clients

Mardo updater checks—identified app builds

Updater ZIPs—automatic updater

Release-tool ZIPs—curl and tooling

Archive data—successful ZIP responses

By release

Versions fetched

edge HTTP

Version	Total	Updater	Tooling	Last seen

By client

Who asked

user agent

Request evidence

Recent update and archive activity

no IP addresses

When	Request	Client	Country	Status	Bytes

Corroborating storage signal

R2 operations

adaptive · 31 days

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.

Checkout attempts—POST /api/checkout

Sessions created—successful checkout responses

Rejected—4xx checkout responses

Paid licenses—issued in this range

Emails delivered—license delivery status

Delivery failures—failed license email status

Recovery requests—successful endpoint responses

Recoveries sent—recorded in D1

Mardo.app

Traffic detail

browser RUM

Page views—

P75 load—

Referrers

Countries

Audience shape