Solution

RevenueDot Cloud, or the open-source server on Docker and Postgres

RevenueDot Cloud needs no servers, and Pro is free until your apps make $10,000 a month, then 0.5% of revenue above that, never more than $999 a month. The same open-source code (AGPL-3.0) runs as one Docker image next to Postgres 16. An Enterprise license adds every enterprise feature on your own servers, an uptime SLA and a named engineer.

Free until your app makes $10,000 a month. Switching from RevenueCat? Change one line.

The RevenueDot dashboard showing customers, revenue and setup health

One image, one database

A single container plus Postgres 16 with a persistent volume.

Migrations on start

Upgrades are a rebuild and a restart. The server applies database migrations itself.

Open source

The server and dashboard are AGPL-3.0, and the SDK forks are MIT.

Your Postgres

When you run the server yourself, every purchase and customer lives in your Postgres, and the server never calls RevenueDot.

Steps

How to run the RevenueDot server yourself

  1. 01

    Clone the repository and copy the config

    Clone revenuedot/revenuedot, copy .env.example to .env and set POSTGRES_PASSWORD. Do it before the first start: the password is written into the volume then.

  2. 02

    Start the stack

    Run docker compose up -d. It pulls ghcr.io/revenuedot/revenuedot (built for amd64 and arm64 on every change) and starts RevenueDot and Postgres.

  3. 03

    Check health and sign up

    Call /v1/health, then open http://localhost:8787/login and sign up. The first account is the owner, and sign-up closes after it.

  4. 04

    Put HTTPS in front

    Serve the server behind a reverse proxy or load balancer with TLS. The SDKs and the stores need an HTTPS URL.

  5. 05

    Connect the stores and your app

    Add your App Store key and Google Play service account, set the notification URLs the dashboard shows, then install the RevenueDot SDK in your app and set its proxy URL to your server.

Terminal

The three commands

Start RevenueDot with Docker Composeterminal
git clone https://github.com/revenuedot/revenuedot.git
cd revenuedot
cp .env.example .env          # set POSTGRES_PASSWORD before the first start
docker compose up -d          # pulls ghcr.io/revenuedot/revenuedot and starts RevenueDot and Postgres
curl http://localhost:8787/v1/health        # {"status":"ok"}

Architecture

What runs inside the container

PieceWhat it does
revenuedot containerOne process: the SDK API (/v1), REST API (/v2), dashboard sign-in, OAuth for AI clients, store notifications and the dashboard web app. A background job records expirations, runs the daily Google Play voided-purchase check, sends webhooks and alert emails
db container (Postgres 16)Every customer, purchase, event and setting, in the revenuedot-data volume

Run one revenuedot container per database for now: the background job has no lock across processes.

Before production

Production checklist for a server you run

The full list is in Going to production. The technical notes page covers the same stack.

  • A managed Postgres with point-in-time recovery, daily dumps copied off the server, and one test restore.
  • SMTP settings so password resets, invites and alert emails arrive. Without them, emails print to the server log.
  • REVENUEDOT_SIGNING_KEY set, if you ship SDK builds that verify responses.
  • Store credentials checked in the dashboard, and notification status showing Ready for each app.
  • Uptime monitoring on GET /v1/health.

Choice

RevenueDot Cloud or your own server

RevenueDot Cloud needs no servers, and Pro is free until your apps make $10,000 a month, then 0.5% of revenue above $10,000, never more than $999 a month: start for free on RevenueDot Cloud. Cloud and a server you run use the same code, API and schema. A server you run sends no telemetry, and talks only to Apple, Google, Stripe or Amazon if you connect them, your webhook endpoints and any forwarding URL you set.

  • Signatures: a server you run signs with its own key, so set the SDK's entitlement verification to disabled on iOS and Android, or build the RevenueDot SDK with your own public key.
  • Status: the Docker image builds on node:24-slim, and CI starts it against Postgres 16 on every pull request.
  • License: enterprise features on your own servers, such as organizations, single sign-on, SCIM and compliance exports, need an Enterprise license, which also brings a 99.9% uptime SLA, a DPA and a named engineer. Contact sales.

FAQ

Running the server yourself: questions people ask

Can I run the RevenueDot server myself?

Yes. RevenueDot Cloud needs no servers, and the open-source server also runs with Docker Compose next to Postgres 16. Your app installs the RevenueDot SDK and sets its proxy URL to your server; an app on the RevenueCat SDK keeps it and changes that one line.

What do I need to run RevenueDot on my own server?

A machine with Docker and Compose v2, plus Postgres 16, which Compose starts for you. For production use a managed Postgres with backups and put the server behind HTTPS.

What license is the RevenueDot server under?

The server and dashboard are AGPL-3.0, and any company can read the code and run it for its own apps. The AGPL asks you to share changes if you modify the server and offer it to others over a network. Enterprise features on your own servers need an Enterprise license.

How do I upgrade a RevenueDot server I run?

Pull the new code, rebuild the image and restart. Database migrations run automatically when the server starts. Back up Postgres first.

Does a RevenueDot server I run send my data to RevenueDot?

No. It has no telemetry and never calls RevenueDot's servers. It talks to the stores you connect, your webhook endpoints and any forwarding URL you set.

Get started

Start selling subscriptions in your app today.

Building and testing are free, and you can test your first purchase before you have a store account. Pro costs $0 until your apps make $10,000 a month.

Already have an account? Sign in · Switching from RevenueCat? Change one line