calendly charges per seat for one google api call. so i built open-cal, and it's free.

open-cal is a free, open source Calendly alternative: booking pages on your own Google Calendar, one Next.js app, one Supabase database, no seats. We replaced three Calendly accounts with it. Here's how it works and what broke in week one.

An Nayal12 Nov 2026 Β· 5 min read
summarize with AI
The open-cal booking page with a month grid and open times, next to the words calendly, minus the per-seat bill.

open-cal is a free, open source (MIT) Calendly alternative. It puts booking pages on your own Google Calendar with one Next.js app, one Supabase database and one Google service account, and it has no per-seat pricing. We replaced three Calendly accounts with it, and every booking link I share now runs on it.

Underneath, a booking tool does two things. It asks Google which times you're free, and it puts an event on your calendar. Calendly charges per seat for that. So I built it myself, put the whole team on it, and open sourced it.

The open-cal booking page: an event on the left, a month grid with open days in coral, and open times for Thursday, October 29
The live booking page. Times show in the guest's own zone.

What you get

Everything here is in the repo today.

Calendly open-cal
Price Per seat, per month Free, you host it
Your calendar data On their servers Your Supabase, your Google
Invites and Meet links Yes Yes, sent by Google itself
Reschedule and cancel links Yes Yes
Per-event hours and buffers Yes Yes
Payments, round-robin, SMS Yes No. Fork it and add them
Needs An account Google Workspace, Supabase, Vercel

How a booking works

Six steps: the guest opens the page, open slots from free/busy, the guest books, a Google event as the host, the guest's private link, and a sync every 10 minutes
Open slots are weekly hours minus Google free/busy minus buffers.

When a guest opens an event, the page loads every open time for the whole booking window from one free/busy read, so month changes are instant. When they book, the app checks the slot live again, writes the booking, and creates the Google event as the host with a Meet link. If Google says no, the booking row is deleted again and the guest gets a clear try-again message.

One service account serves every host on your team. Each Google call is made as that host, through Workspace domain-wide delegation, so free/busy sees exactly what they see and the event is theirs.

What broke in week one

Real guests find the bugs tests don't. These two are fixed in the repo.

A spam trap that trapped real people. The first version had a hidden "Company URL" field to catch bots. Some guests' browsers autofilled it, the app treated them as bots and returned a fake success, and a real guest saw "You're booked" with no booking behind it. The hidden field is gone. A booking either goes in or the guest sees an error.

A deleted test that blocked a real slot. A guest picked an open time and got "that time was just taken". An old test booking still sat in the database after its calendar event was deleted, so free/busy said free while the database said taken. Now confirmed bookings always count as busy, and a sync job runs every 10 minutes: delete a meeting in Google Calendar and its slot opens again, move it there and the booking moves too.

Run your own in about 20 minutes

You need a Google Workspace super admin, a Supabase account and a Vercel account.

git clone https://github.com/Git-Agni/open-cal.git
  1. Supabase. Create a project, run supabase/schema.sql in the SQL editor, copy the URL and the service-role key.
  2. Google Cloud. Enable the Calendar API, create a service account and download its JSON key.
  3. Workspace delegation. In admin.google.com, give the service account's client ID the calendar scope.
  4. Vercel. Import the repo, add the environment variables, deploy, and create your first page at /admin.
  5. Your domain. Point cal.yourdomain.com at it.

The README has every click. The calendar scope lets the service account act on any calendar in your Workspace, so treat its key like a password.

It needs Google Workspace, any paid plan, because personal Gmail accounts can't use domain-wide delegation. A personal Gmail calendar still works as a busy calendar if you share it with a Workspace host. There are no payments, no round-robin, no Zoom and no embeds. Fork it and add what you need.

FAQ

Is there a free Calendly alternative? Yes. open-cal is free and open source under MIT. You host it on Vercel with Supabase and your own Google Workspace, and pay nothing per seat.

Does open-cal work with Google Calendar? Yes, that's all it works with. It reads free/busy from your Google calendars and creates the booking on the host's calendar with a Google Meet link.

Do guests get calendar invites and reminders? Yes. Google sends the invite, the reminders, the update when a time moves and the cancellation, because the event is a real Google Calendar event.

Can my whole team use it? Yes. One deploy serves every host in your Google Workspace, each with their own page, events and hours. The admin is one password by default.

Does it work with a personal Gmail account? Not as a host, because it needs Workspace domain-wide delegation. A personal Gmail calendar can still block time if you share it with a Workspace host.

What does open-cal not do? Payments, round-robin, team pooling, Zoom, embeds and SMS. It's MIT, so fork it and add them.

more sauce

How to avoid App Store rejection in 2026: the 9 questions Apple asks after a Guideline 4.3 rejection18 min readi open sourced the whole tiktok farming playbook. 32 chapters, free.9 min readi open sourced my iphone farm. here's everything inside it.9 min read

πŸ‘‹πŸ½ Say hi, don't be shy

X me@consumerxaiGram me@consumerxaiLinkIn me/in/annayal