Tymeslot is open source. Run the whole platform on your own server with Docker, Cloudron or Railway, and every booking, calendar token and client detail stays on infrastructure you control.
Most scheduling tools are closed SaaS: your availability, your clients' names and emails, and your connected calendar tokens all live on someone else's servers, priced per seat and subject to terms that change without you. For a solo professional that is an annoyance. For a clinic, a law firm, or anyone handling regulated or sensitive data, it is a compliance problem you cannot wave away.
Tymeslot takes the opposite stance. The core product is open source and self-hostable end to end, with every feature included. Point it at your own PostgreSQL database, put it behind your own domain, and it behaves exactly like the managed version, because it is the same code. The server is yours, your clients' data stays on it, and you decide when to upgrade.
Docker for any Linux box, Cloudron for one-click installs with automatic backups and SSL, or Railway from a community template. Same code, same features.
The default Docker image includes PostgreSQL; to use your own, set a database URL. A handful of other environment variables cover the secret key and base URL, and the environment reference documents every option.
Run behind your own reverse proxy or let Cloudron handle certificates automatically. Your booking pages live on your domain, not a shared subdomain.
Add your own Google and Microsoft OAuth credentials, or connect any CalDAV server. Bookings flow straight into your calendars from day one.
One docker-compose file on any Linux server. The default image includes PostgreSQL, and a variant runs the database in its own container if you would rather keep it separate.
One-click install with automatic updates, scheduled backups, and SSL handled for you.
Deploy from the community template in minutes, no server administration required.
Supply your own Google, Microsoft, and OIDC credentials. API keys and tokens are AES-encrypted at rest.
Bring your own PostgreSQL. Back it up, replicate it, and audit it on your own schedule.
Pin a version, test in staging, and upgrade when you are ready. Nothing changes on your server until you decide it should.
Plenty of tools say "open source" and ship a hollow community edition. Tymeslot self-hosts the complete product, and the managed cloud runs the same code.
Calendar sync, payments, themes, embeds, and integrations all work self-hosted. There is no hosted-only feature wall.
Booking pages load no advertising pixels or third-party analytics. Self-hosted, nothing is sent to us at all, and Google reCAPTCHA stays off unless you configure it. That suits healthcare, legal and other sensitive practices.
Run it for one person or a whole team on the same instance. Your costs are your server, not a head-count multiplier.
Every line is public on GitHub under the GNU AGPLv3. Read it, audit it, fork it, or contribute back.
Built the same way as the rest of Tymeslot: open-source, private, self-hostable.
Tymeslot syncs two-way with the calendars you already use. New bookings appear instantly; busy time you block elsewhere disappears from your availability automatically.
Connect your own Stripe account and put a price on any meeting type. Clients pay as they book, and the slot is confirmed only once the payment clears.
Every scheduling feature of Tymeslot is open source under the GNU AGPLv3. Audit the code, fork it and run it on your own server, or let us run it for you.
A booking page looks like a form over a calendar. The hard part is that every calendar system disagrees about which events make you busy, and once my code answered that question in two places, the two answers disagreed too.
Luka Breitig
8 July 2026 · 13 min read
Tymeslot 1.3 turns the built-in calendar into somewhere you can run your day, adds Apple iCloud sync, and relicenses the code under AGPLv3.
Luka Breitig
1 July 2026 · 4 min read
Your Tymeslot booking page now goes into WordPress as a block, a shortcode or a floating button, using the same embed code your dashboard generates.
Luka Breitig
24 June 2026 · 3 min read
Deploy with Docker, Cloudron, or Railway. Open source under the GNU AGPLv3.