Self-host orfc
Your data, your cloud. Run orfc on your own infrastructure with Docker or deploy to Vercel.
Docker Compose
Runs anywhere — AWS, GCP, Azure, DigitalOcean, Hetzner, or your own machine. Includes Postgres out of the box.
Requires Docker and Docker Compose. Nothing else.
1. Clone the repo
$ git clone https://github.com/titunian/rfc.git && cd rfc2. Create a .env file
3. Start everything
$ docker compose up -dCommon commands
Vercel + Neon
Serverless deployment with managed Postgres. Free tier available on both.
No Docker needed. Deploy in under 5 minutes.
Fork the repo
Fork titunian/rfc on GitHub
Create a Postgres database
Sign up at neon.tech (free) and create a database. Copy the connection string.
Import in Vercel
Go to vercel.com/new, import your fork, and set Root Directory to apps/web.
Add environment variables
Deploy and push schema
Click Deploy. Then push the database schema:
$ npm run db:pushPoint the CLI to your instance
After deploying, configure the CLI to use your self-hosted instance instead of orfc.dev.
$ orfc config set apiUrl https://your-domain.comEnvironment variables
| Variable | Required | Description |
|---|---|---|
| DATABASE_URL | Yes* | Postgres connection string. *Docker Compose sets this automatically. |
| NEXTAUTH_SECRET | Yes | Random string for session encryption. Generate with openssl rand -base64 32 |
| NEXTAUTH_URL | Yes | Your public URL (e.g. https://orfc.example.com) |
| APP_URL | Yes | Same as NEXTAUTH_URL. Used for generating links. |
| RESEND_API_KEY | No | Resend API key for email notifications |
| RESEND_FROM_EMAIL | No | Sender email for notifications |