Blog
Notes on subscription infrastructure, written in the open
Posts are Markdown in the revenuedot/docs repository on GitHub, next to the documentation they link to.
2026-09-30 How RevenueDot stays compatible with the RevenueCat SDKThe endpoints the SDK calls, the customer info it decodes, the 4xx/5xx rule that protects purchases, the contract tests, and response signing byte by byte. 2026-09-30 Introducing RevenueDot, an open-source backend for in-app purchasesRevenueDot is an open-source, self-hostable backend for in-app purchases that works with the RevenueCat SDK. Here is why we built it, and what it does today. 2026-09-30 Migrating from RevenueCat without losing a subscriberThe safe order for moving to RevenueDot: import customers and keep your public keys, forward store notifications to run both systems, verify, then switch with an app update. 2026-09-30 Self-host RevenueDot in 5 minutesStart RevenueDot with Docker Compose, seed a Test Store project, make a first purchase with curl, receive the webhook on your laptop, and turn on response signing. 2026-09-30 Why we forked the RevenueCat SDKsRevenueDot maintains MIT forks of all ten RevenueCat SDKs. What the patches change, why every import name stays the same, and how one script keeps the forks in sync with upstream.