Analytics, trusted revenue, founder books and selective proof — running inside your own Cloudflare account. Raw events, financial records, credentials and receipts stay there unless you export or publish them.
No usage metering · no session replay · export whenever you choose
Traffic sits beside revenue. Revenue reconciles to records. Records become books. Only chosen proof becomes public.
Cookieless traffic, goals, funnels, journeys, and revenue beside every contributor.
Gross, fees, refunds, net revenue, subscriptions, attribution, and discrepancies.
Expenses, receipts, imports, reconciliation, and bookkeeping-lite without a bank-feed dependency.
Choose exact values or ranges from an explicitly published, pre-computed snapshot.
There is no Minori-operated analytics database between you and the numbers. Each installation lives in the customer’s own Cloudflare account — so we cannot see your numbers, structurally rather than as a matter of policy.
buys the licence and lives on shojum.com — it holds your key, your renewal and your downloads.
is created by you on your own Cloudflare deployment and holds your data. We never see it, and it shares no password with your Shojum ID.
Two separate accounts, on purpose. They share no password and no session — your Shojum password will not sign you in to your own installation, and it is not meant to.
Minori runs in your Cloudflare account, never charges by traffic or revenue, and keeps working on the version you installed even if you cancel.
Your cohort price stays yours for as long as the subscription is active. You will be asked to create a Shojum ID during checkout — that is where your key and downloads live afterwards.
Early customers accept more product risk, so they get the lowest annual price. Each cohort is grandfathered while subscribed — the rung never moves under an existing licence.
Founding price · available now
Early-growth price
Established-product price
Mature anchor price
After checkout your key waits on your Shojum account page. Installing is a GitHub Actions workflow in a repository you own: it deploys straight into your Cloudflare account, and re-running it is how you update.
# .github/workflows/install-minori.yml
- uses: Shojum/minori-install@<commit SHA you reviewed>
env:
MINORI_LICENSE_KEY: ${{ secrets.MINORI_LICENSE_KEY }}
CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
MINORI_SETUP_TOKEN: ${{ secrets.MINORI_SETUP_TOKEN }}No “contact sales,” no revenue percentage, and no surprise bill when your launch succeeds.
In your Cloudflare account, in your D1 database and your R2 buckets. The installer runs as a GitHub Actions workflow in your own repository, using a scoped Cloudflare API token you create and keep — we never handle your tokens, and no visitor data is ever sent to Shojum.
Your installation keeps running exactly as before, with its existing data and features. A lapsed licence closes downloads, updates and support — it never switches your analytics off. Software you host should not stop working because a card expired.
The product becomes more proven and capable over time. Early customers take the greater risk and keep the better price for as long as they keep renewing.
No. Minori does not phone home for usage, cannot see your private business numbers, and has no usage-based tier.
Your own Cloudflare usage, billed by Cloudflare rather than by us. Minori is built for Workers, D1, R2 and Queues, and a free account is enough to start — the expected indie-founder range is roughly $0–5 a month.
Yes. Pricing is per installation, so a second site or a second client is a second licence. Each one gets its own key on your account page.
One customer-owned installation, every current feature, no usage meter — and it keeps running whatever happens to the licence.