Cal.com
Open-source scheduling - booking pages, availability, team round-robin. Calendly without the per-seat bill.
One-click deploy, from $25/mo on a Miget plan.
Cal.com is open-source scheduling done properly: personal and team booking pages, fine-grained availability, round-robin and collective events, reminders and workflows, routing forms, and two-way sync with Google, Office 365, and CalDAV calendars. It is the self-hosted answer to Calendly.
The app is effectively stateless - every booking, event type, and connection lives in a managed Postgres - so this template is just the app plus the database. PORT moves it onto Miget’s public port with no wrapper, and migrations run on start.
The reason to self-host is the same as always: scheduling tools meter features per seat, which scales with your team rather than your usage. Cal.com is one flat plan, on your own domain, with the booking data in a Postgres you control.
Upstream project: Cal.com
#what you get
- Personal and team booking pages with availability rules
- Round-robin, collective, and managed event types
- Workflows, reminders, and routing forms
- Two-way calendar sync (Google, Office 365, CalDAV)
- Stateless app on managed Postgres - disposable container
- AGPLv3 core; flat pricing instead of per-seat
#topology
| Service | Role | Public |
|---|---|---|
| calcom | scheduling app (stateless, :5000) | yes |
| db | managed Postgres (citext) - all state | no |
#miget sizing
// this stack needs
3 GiB RAM · 10 GB disk · 2 services
The Next.js app wants ~1.5-2 GiB (large image, slow first boot - allow a generous health-check grace). Postgres holds everything, so the app scales and rolls back cleanly.
Hobby - recommended fit
$25/mo
2 vCPU · 4 GiB · 80 GiB disk
Headroom for your own apps: 8 GiB at $49/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Cal.com on Miget ★ | 4 GiB plan | $25 | this whole stack, flat - no usage meters, and room left for your own apps |
| Calendly | Teams | ~$160 | $16/seat/mo at 10 seats |
| Calendly | Standard | ~$120 | $12/seat/mo at 10 seats |
Scheduling tools meter per seat; Cal.com self-hosted is one flat plan for the whole team.
#vs. other PaaS
Estimated monthly cost of running this exact stack (3 GiB RAM, 10 GB disk, 2 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $25 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$150 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$41 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$40 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$32 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$19 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
calcom -
Set the required variables:
NEXTAUTH_SECRET, session secret (openssl rand -base64 32)CALENDSO_ENCRYPTION_KEY, 32-byte AES key (openssl rand -base64 24)NEXT_PUBLIC_WEBAPP_URL / NEXTAUTH_URL, the https domain
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/calcom
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
What does this save vs Calendly?
Calendly is $12-16/user/month and gates features per seat, so a team multiplies fast. Cal.com self-hosted is one flat plan for everyone, with your booking data on your own infrastructure.
Why does the database need the citext extension?
Cal.com's Prisma migrations create a case-insensitive text type (citext) on start, so the managed Postgres is provisioned with that extension enabled. It is a standard contrib extension - the template wires it for you.
Is the self-hosted version limited?
The core scheduling app is AGPLv3 and fully functional self-hosted. Some enterprise features under the /ee directory need a paid license key, but booking pages, teams, availability, and calendar sync do not.
Ship Cal.com today
One compose stack, 3 GiB of RAM, from $25/month flat, and it runs on your laptop with the same files.