Everything in the managed cloud, plus the isolation, control, and contractual guarantees regulated and larger organisations need.
Isolated instance & database
Your own deployment and your own database. Data never shares a tenant boundary.
Region of your choice
EU data residency by default; other regions on request. Your data stays where you need it.
Custom domain & white-label
Booking pages on your own domain, in your colours, with no Tymeslot branding.
Single sign-on
OIDC with Entra ID, Okta, Google Workspace, Keycloak, and others. SAML on request.
SLA & dedicated support
Response times agreed in your contract, a named contact, and a private support channel.
DPA & compliance
A signed Data Processing Agreement, GDPR documentation, and help with security reviews.
Managed operations
Updates, backups, and monitoring are handled by us - you just schedule.
Invoicing your way
Annual billing, purchase orders, and bank transfer - not just a card on file.
Open source, with a commercial option
Which licence do you need?
Tymeslot is open source under the GNU AGPLv3, and most organisations never need anything else. You only need a commercial licence to keep your changes private, or to build Tymeslot into a closed-source product.
Most open
Most private
Use it as it is
Free, GNU AGPLv3
Run Tymeslot unchanged, on your own server or on a managed instance run by us.
Allowed
Use it and host it where you like
Not applicable
Modify the code
Not applicable
Keep your changes private
Not allowed
Build it into a closed-source product
What you owe in return
Keep the licence and copyright notices intact.
Support
Community support on GitHub
Modify it in the open
Free, GNU AGPLv3
Change anything you like, as long as your changes stay open source too.
Allowed
Use it and host it where you like
Allowed
Modify the code
Not allowed
Keep your changes private
Not allowed
Build it into a closed-source product
What you owe in return
Anyone who uses your modified version over a network must be able to get its source code under the AGPLv3.
Support
Community support on GitHub
Commercial licence
Priced for your use case
Modify Tymeslot and keep your changes closed, or build it into your own product.
Allowed
Use it and host it where you like
Allowed
Modify the code
Allowed
Keep your changes private
Allowed
Build it into a closed-source product
What you owe in return
The terms of your licence agreement, with no share-alike obligation.
Support
A support contract, integration help, upgrade assistance, and custom development
A plain-language summary, not legal advice: the GNU AGPLv3 text is what counts.
How it works
From first message to go-live
No sales runaround. This is what happens after you get in touch.
1
Tell us what you need
Two minutes on our contact form: your organisation, team size, region, and main requirement.
2
A 30-minute scoping call
We offer you a call within two business days to understand your setup and constraints.
3
A written proposal
Price, region, SLA, and DPA in one document your procurement team can review.
4
Setup and go-live
We set up your instance, domain, and single sign-on, and help you move over from your current tool.
Enterprise questions, answered.
What teams usually ask before deciding whether Enterprise is right for them.
Is Enterprise overkill for a small team?
Team size isn't the deciding factor; your requirements are. A ten-person clinic that must keep patient data isolated is a good fit. A two-hundred-person company with none of the requirements above is usually better served by Cloud Pro.
Do we need Enterprise just for single sign-on?
Not necessarily. If you self-host Tymeslot, you can connect it to any OIDC identity provider yourself. Enterprise is for teams that want single sign-on without running the server, or that need it alongside isolation, an SLA, or a DPA.
What exactly is a dedicated instance?
It's the same Tymeslot as the managed cloud, but run as a private deployment just for you - its own application, its own database, and no shared tenancy. We operate it: updates, backups, and monitoring are handled for you, so you get the control of self-hosting without the maintenance.
Who hosts it, and where?
We do, on infrastructure in the EU: Germany by default. If you need another region, such as the UK or the US, tell us and we'll include it in the proposal. Your instance never shares a database with another customer.
Do you support SAML?
Single sign-on works through OIDC today, which Entra ID, Okta, Google Workspace, Keycloak, and most modern identity providers support. If your identity provider only speaks SAML, tell us and we'll add it as part of your setup.
Do you sign a DPA and support security reviews?
Yes. We sign a Data Processing Agreement, provide the GDPR documentation you need, and answer your security questionnaire.
Can we evaluate Tymeslot before committing?
Yes. Enterprise runs the same software as the managed cloud, so you can create a free account and try the booking experience today. Your technical team can also review the open-source code.
Can we move over from Calendly or Cal.com?
Yes. As part of setup, we help you connect your calendars and video tools, and set up your meeting types and availability.
How is this different from Cloud Pro?
Cloud Pro is our shared, self-serve plan - ideal for individuals and small teams. Enterprise adds isolation, data residency, a custom domain, SSO, a support SLA, and a signed DPA. If you don't need those, Cloud Pro is the better fit.
Can we embed or modify Tymeslot in our own product?
Yes. Under the AGPLv3 you can modify Tymeslot freely, as long as the people who use your modified version can get its source code. If you'd rather keep your changes private, or build Tymeslot into a closed-source product, we offer a commercial licence.
What drives the price?
Enterprise is priced per deployment, based on your region, the size of your team, and the support level you need. After the scoping call, you get a concrete quote in writing.
Let's talk about what you need.
Tell us your region, your team size, and the requirement that brought you here. We'll offer you a scoping call within two business days.