Environment variables
This reference lists every environment variable OpenProfit reads, with its default and purpose, and describes the optional usage ping. Set them on the container, for example with -e flags on docker run.
Required variables
An instance doesn’t start correctly without these two:
| Variable | Default | Purpose |
|---|---|---|
SECRET_KEY |
None | 32 random bytes encoded as base64. Encrypts provider keys and signs sessions. To change it, stop the app and run OLD_SECRET_KEY=<old> SECRET_KEY=<new> bun scripts/rotate-secret-key.ts against the database, or the app can't read the stored provider keys. Everyone signs in again |
APP_URL |
http://localhost:3000 |
Public address of the instance. Sign-in links point here |
Database
OpenProfit uses an embedded Postgres database unless you give it a server:
| Variable | Default | Purpose |
|---|---|---|
DATABASE_URL |
./data/openprofit |
A postgres:// connection string, or a directory path for the embedded database |
Reverse proxy
Sign-in from the CLI and agent sign-up are rate-limited per IP address. Behind a reverse proxy (nginx, Caddy, Traefik, a load balancer), every request seems to come from the proxy unless you set this:
| Variable | Default | Purpose |
|---|---|---|
TRUST_PROXY |
None | The number of proxies in front of the instance, usually 1. OpenProfit then reads the client's address from X-Forwarded-For. Leave it unset when nothing sits in front, or clients can fake their address. Not needed on Railway |
CLIENT_IP_HEADER |
None | A header your CDN sets to the client's address, such as cf-connecting-ip for Cloudflare. It takes precedence over TRUST_PROXY. Set it only when your firewall admits the CDN's addresses alone, or clients can fake their address |
Email and sign-in
Without these, sign-in links print to the server log and only email sign-in is offered:
| Variable | Default | Purpose |
|---|---|---|
RESEND_API_KEY |
None | Sends sign-in links, alerts and the weekly email through Resend |
EMAIL_FROM |
None | Sender address, for example OpenProfit <mail@your_domain_here> |
GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET |
None | Adds sign-in with GitHub. Use your_app_url/api/auth/callback/github as the callback URL |
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET |
None | Adds sign-in with Google. Use your_app_url/api/auth/callback/google as the redirect URI |
SMS alerts
OpenProfit sends SMS alerts through Twilio. Until you set all three variables, the SMS channel doesn't show on the Alerts page. A self-hosted instance has no monthly SMS limit. The alerts guide covers phone verification:
| Variable | Default | Purpose |
|---|---|---|
TWILIO_ACCOUNT_SID |
None | Your Twilio account SID, starting with AC |
TWILIO_AUTH_TOKEN |
None | The auth token for that account |
TWILIO_FROM |
None | The sender: a Twilio number in E.164 format, such as +14155550100, or a Messaging Service SID starting with MG |
Background jobs
OpenProfit runs its scheduled jobs inside the server process:
| Variable | Default | Purpose |
|---|---|---|
SYNC_SCHEDULER |
on |
Set to off to stop the sync, weekly email and usage ping jobs, for example on a second instance that shares the database. The weekly email job runs hourly and sends to each workspace at the day and hour picked in Settings, in that workspace’s time zone |
Public demo
The demo at /demo shows the dashboard with sample numbers. Anyone can open it without signing in, and nobody can change it:
| Variable | Default | Purpose |
|---|---|---|
DEMO |
off, or on with APP_MODE=cloud |
Set to on to serve the demo. The instance keeps one demo workspace with no members and rebuilds it every hour, so its two years of numbers end in the current month. While it's off, /demo redirects to https://openprofit.dev/demo |
Hosted mode
These variables apply only to the hosted version at openprofit.dev. A self-hosted instance leaves them unset:
| Variable | Default | Purpose |
|---|---|---|
APP_MODE |
selfhost |
cloud turns on plans, billing, the sync cadence limits and the benchmarks at /data |
POLAR_ACCESS_TOKEN |
None | Polar organization token used to create checkouts and open the billing portal |
POLAR_PRODUCT_INDIE, POLAR_PRODUCT_PRO |
None | Polar product ids for the two paid plans |
POLAR_WEBHOOK_SECRET |
None | Secret that verifies subscription events sent to /api/polar/webhook |
OUTBOUND_IPS |
None | The server's outbound IP addresses, comma-separated. MongoDB Atlas only answers addresses on its access list, so in cloud mode the Atlas connector appears only when this is set, and its connect page lists these addresses to allow |
Analytics and monitoring
OpenProfit sends nothing to PostHog unless you set POSTHOG_KEY. With it set, the server and the browser each send PostHog their own data:
- Product events: the server records sign-ups, workspaces created, connections added, removed or failing to sync, products created and removed, product assignments and checkouts. Each event carries the user id, the workspace id as a PostHog group, and fields such as the provider or plan. Events never include names, email addresses, amounts or keys. A user who switches off Analytics in Settings sends no events. Scheduled sync failures have no user, so they use the distinct id
workspace-events - Workspace properties: with
APP_MODE=cloud, the server sets each workspace group's properties when the workspace is created and once a day. They hold the plan, base currency, creation date, the member and product counts, and a connection count per provider - Web analytics: the browser loads PostHog on every page in cookieless mode. PostHog stores nothing on the device and counts visitors with a daily hash of IP address and user agent. In your PostHog project, turn on Cookieless server hash mode under Project Settings > Web analytics, or PostHog drops these events
- Session replay: each user has an Analytics switch in Settings, on by default, that also controls product events. While it's on, pages under
/appand/onboardingstart PostHog with in-memory persistence and the user id, add the workspace group, and record replays of those pages only, with all text and inputs masked. PostHog stores nothing on the device, so a full page reload starts a new session. With the switch off, or signed out, the browser stays in cookieless mode. Replays also need session replay turned on in your PostHog project. PostHog never sets cookies, so the site shows no cookie banner
Browser requests go to /ingest on your own domain, so ad blockers let them through. To send them to a PostHog managed reverse proxy instead, set POSTHOG_PROXY.
The server also sends PostHog its own tagged log lines, such as [sync] and [weekly], a trace span for each request and background sync named by route, and server function errors. It replaces email addresses and anything shaped like a key or token first. Provider errors go out as their status code only, and provider and validation errors stay out of error tracking. None of these include a user id.
| Variable | Default | Purpose |
|---|---|---|
POSTHOG_KEY |
None | Project token from your PostHog project settings, starting with phc_ |
POSTHOG_HOST |
https://us.i.posthog.com |
PostHog ingestion host. Use https://eu.i.posthog.com for an EU project |
POSTHOG_PROXY |
/ingest |
Address of a PostHog managed reverse proxy on your own subdomain, such as https://e.example.com |
Usage ping
The usage ping is off until you switch it on in Settings. Once on, the instance sends one request a day to TELEMETRY_URL (default https://openprofit.dev/api/telemetry) containing:
- an instance id: a one-way hash of
SECRET_KEY - the OpenProfit version
- the number of workspaces and products
- the number of connections per provider
It sends no names, amounts, email addresses or keys.