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.
With a closed scheduling tool, the vendor controls the code, your clients' names and emails, and what you pay. You cannot check what happens to a booking once it is made, you cannot run the tool anywhere else, and when a plan changes or a feature moves up a tier, you pay or you start again.
Open source shifts that balance. Tymeslot's code is public, so you, or anyone you trust, can read exactly what it does with your data. You can run it on your own server, and if you would rather not, our managed service runs the same code, so you can leave without starting over.
The whole product is on GitHub: booking pages, calendar sync, payments, embeds and the admin area. Audit it yourself, or hand it to your security team before you decide.
Self-host with Docker, Cloudron or Railway on infrastructure you control, or sign up for the managed service at tymeslot.app, hosted in the EU.
Both run the same code on a standard PostgreSQL database, so no proprietary format stands in the way. There is no self-service export yet; get in touch before you move and we will work out the transfer with you.
Use, study, change and share the code. The main condition is copyleft: if people use a modified version, including over a network, you offer them its source under the same licence.
Calendar sync, video rooms, payments, embeds, themes, webhooks and every interface language are in the open code. None of it is kept back for the managed service.
Docker on any Linux server, a one-click install from the Cloudron App Store, or a Railway template.
The code, issues and pull requests live in the public GitHub repository, and the public changelog records what each release changed.
A self-hosted install sends nothing back to us: no usage reports and no analytics script, and Google reCAPTCHA stays off unless you configure it.
Self-hosted, a whole team shares one instance at no extra cost. You pay for the server, not per head.
In plain words, and not as legal advice: for a business that uses Tymeslot to take its own bookings, the licence asks very little.
Run Tymeslot to take bookings for one person or a whole company, with no licence fee to pay and no permission to ask.
If you modify the code and let other people use your modified version over a network, your clients included, the AGPL asks you to offer them its source under the same licence.
Choosing themes, colours, settings and integrations in the dashboard leaves the source untouched, so there is nothing for you to publish.
You are free to fork the code. The Tymeslot name and logo are trademarks, so a fork goes out under a name of its own.
How Tymeslot, Cal.com and Calendly answer the questions that matter when you want to own your scheduling. Every competitor fact comes from the vendor's own pages.
| Feature | Tymeslot | Cal.com | Calendly |
|---|---|---|---|
| Open source | Yes, GNU AGPLv3: the complete product | Cal.com is closed source; Cal.diy is open source | No: hosted service only |
| Self-hosting | Yes, free with every feature: Docker, Cloudron or Railway | Only the Cal.diy community edition | No: hosted service only |
| Free plan | Yes: unlimited bookings and meeting types | Yes: free forever for 1 user | Yes, limited to 1 event type and 1 calendar |
| Hosting in the EU | Yes, in the EU | EU data residency on request | No: data is stored in US data centres |
Sources checked 2 November 2026.
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.
Drop a Tymeslot booking widget onto any page with one script tag: inline, popup or floating button, styled to match your brand. The widget sizes itself, so there is no iframe height to fiddle with.
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.
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
Open source under the GNU AGPLv3. Self-host it free, or start on the managed service with no credit card.