Almanac is a native app for Mac, iPhone and iPad that writes down your Cloudflare Web Analytics, App Store Connect and Stripe numbers every day and keeps them in your private iCloud. Its stated purpose is to keep the analytics your vendors throw away: it collects the figures each vendor still serves while those figures are still available, then holds on to them so the record outlives the vendor's own retention window. It is built for people who run websites and apps and want a history they can trust rather than a live dashboard that quietly forgets. Collection runs for everyone from the day of install, whether or not they ever pay, and the history grows every day the app runs.
The product exists because of retention limits. Cloudflare deletes unsampled real-user Web Analytics data after seven days. Past that window the API answers from a one-in-ten sample, and a quiet site returns zero rows rather than fewer rows — while the response still says success: true. The site calls this the seven-day cliff and measured it on one quiet site: five page loads readable at seven days, zero at eight. App Store Connect reaches back about 120 days on a first request, and the days before that were never yours to fetch. Stripe keeps every transaction and never adds up a day for you. Everything older than the retention window is gone — not sparse, not estimated, gone — so the only way to own the history is to record it while it exists.
For Cloudflare Web Analytics, Almanac keeps human page loads split from automation, plus LCP, INP, CLS and TTFB at P75 with Cloudflare's own rating. It keeps every site in the account with a health badge, and it keeps where people came from: sources, pages and countries. Sign-in is through Cloudflare. The app queries an hour inside the retention boundary, because two identical requests minutes apart can land on either side of it, and it refuses to write an estimate into the record — a sampled response arrives as one quiet sentence rather than a number you might mistake for a measurement.
For App Store Connect, connected with an API key (.p8), Almanac keeps impressions and product page views, first-time downloads, redownloads and updates, sales from both Sales and Trends and Analytics, and territories and sources per app, per day. For Stripe, connected with a live restricted key rather than a secret key, it keeps gross, fees, net, refunds and disputes as they settled, the checkout funnel — created, completed, paid and expired — per product, and each currency apart, because euros and dollars do not add. A key without the Checkout permission still collects payments; only the checkout funnel is left out. Each source keeps its own name and its own units, and nothing is blended into one number none of the vendors would recognise.
On the Mac, the app has views for one site, the whole portfolio, one app and all apps. Every kept day of a site is charted with people and automation stacked, and a coverage strip underneath marks each day collected, refused as an estimate, or missed for good. The portfolio view puts every site in the account on one table with people, bots and P75 vitals, and a health badge that can be sorted worst first; opening a badge shows which metric earned it. Charts break at a gap instead of drawing across it, and the two different nulls the API returns — zero for too few samples, minus one for a metric never recorded — are shown as a dash, with Almanac telling you which kind of dash it is.
Almanac also separates people from automation, because headless Chrome runs JavaScript and beacons exactly like a person and vendor dashboards count it as a visitor. The site reports that nine of fourteen loads in one week across its own sites were never people. Behind these choices are five documented ways the Cloudflare API "lies quietly", all measured against a live account: the retention cliff moves between calls; CLS is unitless, so dividing it by a million turns a genuinely poor 0.44 into a perfect-looking 0.0004; two different nulls mean different things; "limit" truncates after sorting by volume, so the quietest site on the quietest day falls off (a capped query reported 39 page loads where the truth was 101, with no error); and "count" is not the denominator, so any "N of M were good" has to divide by the metric's own total.
The method is deliberately conservative. Almanac writes a day down once it is final for that source, by rules that refuse estimates, and it records the sampling it was given rather than guessing. Because seven days of retention means eight days away is a permanent hole, something has to keep running: Almanac stays in the menu bar with its window closed, collects on launch and every six hours, and can start at login. If the Mac is off for a few days nothing is lost, as long as it runs again within six days, because every run re-reads every day Cloudflare still serves; longer than that leaves a gap, and the gap is marked rather than drawn as a zero. iPhone and iPad show the history the Mac keeps, synced through a private iCloud database, and collect whenever you open them.
The outcome is a record you can reason about. Numbers come with their reasons, so a dash is never passed off as a zero and a headless browser is never counted as a person. Your keys live in the Keychain, your history sits on your devices and in your private CloudKit database, and every request goes directly from your device to Cloudflare, Apple or Stripe — Almanac has no server and no account of its own. A built-in MCP server on the Mac lets any MCP client query the kept history, read-only unless you allow more, and every number it hands over says where it came from. Everything you can see exports as CSV or JSON with the collection record beside the rows, so a gap in the file stays readable, and export is never locked.
In practice this covers a handful of workflows. A site owner can look at Core Web Vitals and human traffic for a period that already fell off the Cloudflare dashboard, with the coverage strip showing which days were refused as estimates. An app team can keep impressions, page views and downloads per territory from the day Almanac first asked, with Apple's roughly 120-day backfill behind it. A Stripe user can keep a daily record of gross, fees, net, refunds and disputes per product and per currency, plus the checkout funnel. Someone with several sites can sort the portfolio worst-first by health badge, and an agent or script on the same Mac can query the history through the MCP server.
Almanac is made by Magenta Creations and is not affiliated with Cloudflare, Apple or Stripe; it needs a Cloudflare account with Web Analytics enabled to read web vitals. It runs on macOS 26 and iOS 26 across Mac, iPhone and iPad. The free tier is a real product, not a trial: every source, site and app, the full live portfolio, people and bots, rated vitals, the last 30 days of history for one subject per source, the menu bar collector, the MCP server and export. Pro is $5.99 paid once, with no subscription, and unlocks unlimited history for every subject and source, trends and period comparison past 30 days, and an App Store Connect key synced through iCloud Keychain, on Mac, iPhone and iPad signed in to the same Apple ID. Pro gates the view, never the record.
The takeaway is simple: every day you wait is a day gone. Almanac only keeps what the vendors still hold, so the history starts the day you install it and grows from there — collected honestly, without estimates, and kept in your own iCloud.