Self-hosting
What every app needs, the three ways to deploy one, and how to hand the job to a coding agent.
View as MarkdownCoding agents can read this page at /docs/index.md
Every app in this catalog is open source (MIT) and built to run on your own server or hosting account. You own the data, and nothing phones home. These pages cover deploying an app, connecting email, storage, Google and Stripe, and keeping it running.
Each page works for two readers: you, and a coding agent (Claude Code, Codex, Cursor and similar) that you ask to do the setup for you.
The whole path, start to finish
- Deploy. The fastest way is the app’s one-click Railway template (Scheduler, Invoicing). It creates the app, its Postgres database, storage for uploads, a public HTTPS address and the secret key. Nothing is built on your account. You can also use Docker Compose on your own server, Render, or point a coding agent at the app’s page.
- Create the admin account. Open your app’s address and add
/setup, for examplehttps://scheduler-production-1234.up.railway.app/setup. Enter your organization’s name and your own name, email and password. That first account is the admin, and/setupcloses as soon as it exists. Then invite your team from Settings. Details: first admin. - Add extras when you need them. Every app works without them: email (until it’s set up, emails are printed to the logs), a custom domain, Google sign-in, and Stripe for Invoicing. Each guide ends with “Adding this to an existing deploy”.
Don’t want to run anything yourself? A hosted version, where we run every app for one small yearly price, is planned. Join the waitlist on any app’s page at generic.works.
Pick an app
| App | Open-source alternative to | Guide |
|---|---|---|
| Scheduler | Calendly | Scheduler |
| Invoicing | FreshBooks | Invoicing |
A forms app (an open-source alternative to Typeform) is planned.
What each app needs
Every app has the same shape:
- One Docker image. One process serves the web app, the API, and the background jobs (email reminders, recurring invoices). Ready-made images are published as
ghcr.io/gtalarico/saas-clones/<app>:latest, or build one from the repository root withdocker build -f apps/<app>/Dockerfile .. - One Postgres database. Postgres is the only required service. Use a separate database for each app, because the apps share table names.
- Environment variables for every setting. There are no config files. Three variables are required:
| Variable | What it is |
|---|---|
DATABASE_URL |
Postgres connection string, for example postgres://user:password@host:5432/dbname |
APP_URL |
The public address people use to reach the app, with no trailing slash, for example https://cal.example.com. Filled in automatically on Railway and Render |
AUTH_SECRET |
A random string of at least 32 characters. Generate one with openssl rand -base64 32 |
Everything else is optional, and you can add each piece later without starting over. Each app page has a “Required vs optional” table, and each configuration guide ends with “Adding this to an existing deploy”.
- Email (
SMTP_URL). Without it, emails are printed to the app logs instead of being sent. See the email guide. - File storage (
STORAGE_DRIVER). Logos and profile photos go to local disk by default, which needs a persistent volume. You can use any S3-compatible bucket instead. See the storage guide. - Google sign-in and, for the Scheduler, Google Calendar sync. See the Google OAuth guide.
- Stripe card payments for Invoicing. See the Stripe guide.
The database schema is created and updated automatically every time the app starts. The first person to open /setup becomes the admin. See first admin.
Choose where to deploy
| Railway | Render | Your own server (Docker Compose) | |
|---|---|---|---|
| Good for | The easiest hosted setup | Teams already on Render | Full control, lowest running cost if you already have a server |
| Approximate cost per app | About $5 per month on the Hobby plan | About $13 per month (web service plus database) | Whatever your server costs |
| HTTPS | Automatic | Automatic | You add a reverse proxy such as Caddy (example included) |
| File uploads | Volume or Railway Bucket | S3-compatible bucket | Docker volume (already set up) |
| Guide | Railway | Render | Docker Compose |
Prices change, so check each provider’s pricing page before you commit. Free tiers are not a good fit: the apps need an always-on process to send reminders on time.
If you’re not sure, pick Railway.
Using a coding agent
Each app page starts with a section called “Instructions for AI agents”. It tells the agent which questions to ask you, which commands to run, how to check that the deploy worked, and what never to do (such as committing secrets).
Paste a prompt like this into your agent, and replace the app name and link:
Set up my own copy of the open-source Scheduler (an alternative to Calendly).
Follow https://<docs-site>/docs/scheduler.md step by step.
Ask me before creating anything that costs money, and keep secrets out of git.
You can also point the agent at the Markdown file in a clone of the repository: docs/self-host/scheduler.md in https://github.com/gtalarico/saas-clones.
The agent will need to run commands on your machine (for example git, docker, openssl, or a hosting provider’s CLI) and will ask you for things only you can provide, such as an email provider API key. Some steps happen in web dashboards (Google Cloud Console, Stripe, your DNS provider). The agent will walk you through those.