Open source · MIT license
Your infrastructure. Full Salebell.
Host the website on your own VPS or Vercel, connected to a Supabase project in your own account. VPS + Supabase guide · Vercel + Supabase guide. Custom domains are optional on Vercel.
Self-host apps, integrations, event history, revenue estimates, CSV export and raw Apple notification forwarding without a Salebell subscription. You pay for and operate your infrastructure and delivery providers.
For guided Vercel installation, run npm run deploy from a checkout with Git and Node.js 22.6 or later. It uses your own Vercel and Supabase CLI logins. No Marketplace integration, shared OAuth registration or Docker is required. A VPS website can run with Node.js or Docker.
Advanced alternative: run the full stack
The steps below run Supabase itself, the dashboard and notification receivers on your server with Docker Compose. This alternative does not require a Supabase or Vercel account.
1. Prepare your server
- Install Git, Node.js 22.6 or later, and Docker Engine with Docker Compose v2.
- Point two domain names at your server's public IP: one for the dashboard and one for the API.
- Open ports 80 and 443 and make sure no other service uses them. HTTPS certificates are set up automatically.
For example, use salebell.example.com for the dashboard and api.salebell.example.com for the API. Replace both examples below with your hostnames.
2. Install on the server
git clone https://github.com/salebell/salebell salebell
cd salebell
npm run self-host -- init \
--site-url https://salebell.example.com \
--api-url https://api.salebell.example.com \
--email owner@example.com
npm run self-host -- upUse your email address for --email. The installer creates your configuration and owner account, builds the dashboard and checks the services. Wait for Salebell is ready at .... No separate npm install or Supabase CLI is required.
3. Sign in
Read your generated password on the server:
cat deploy/owner-passwordOpen your dashboard's /login page and sign in with your email and that password. No email code is needed. Public registration is closed by default.
Keep deploy/.env and deploy/owner-password private. To change settings later, edit the existing deploy/.env and run npm run self-host -- up again.
4. Connect your first app
- Open your instance and sign in with the owner credentials.
- Import an app with an App Store Connect team key, or enter its name and bundle ID manually.
- Connect Version 2 Apple notifications. Preserve your existing backend's URLs through forwarding before replacing them.
- Make a sandbox purchase and confirm the event appears. If you use the optional Apple test, confirm its notification arrives.
- Choose an alert channel and send a test alert, or skip alerts and use the dashboard alone.
Read the app connection guide. Your instance generates URLs using its configured website origin.
5. Save a backup
npm run self-host -- backupCopy the entire backup directory printed by the command to private storage outside this server. It contains your database, credentials and encryption material. Updates, backups and recovery ↗.
Optional: iPhone alerts
The shared iPhone app implementation supports your own instance through Settings → Server. When a compatible distribution is available, enter your HTTPS website URL, Supabase API URL and public key, then sign in to that backend. You do not need another managed account, APNs keys or your own app publication.
Shared-app push depends on the managed Salebell relay. The implementation is in the repository; App Store/TestFlight distribution and live relay operation still require operator qualification. This website offers a download only when its operator configures one. Connection, privacy and relay setup ↗.
One backend and user are active per phone. Sign-out and switching wait for central revocation; if the relay is unavailable, retry when connectivity returns. Privately maintained direct-APNs apps remain an advanced option on independent backends. Slack, Discord, Telegram, Pushover, PostHog and webhooks work independently of iPhone push.
Apple in-app purchases and subscriptions are supported. Google Play RTDN is available in preview. Google Play setup and limitations ↗.
Prefer managed cloud?
Cloud Free covers one app. Cloud Pro adds more apps and integrations, full history and CSV export. Self-hosting remains available under MIT.