Self-hosted Calendly alternative: meet Tymeslot

A booking link is convenient. Having more control over the application behind that link can be even better. Tymeslot is now available in the Caliber Node app catalog for customers who want a self-hosted meeting scheduling workflow.

Use it to give people a place to choose a meeting type and an available time, rather than negotiating every appointment by email. Caliber Node handles provisioning the app and database; you bring the calendar, email configuration and scheduling rules.

A self-hosted alternative for meeting scheduling

Tymeslot provides booking pages and calendar integrations for arranging meetings. It is an option to consider if you like the booking-link approach of services such as Calendly but want to run your own installation.

That does not make it a drop-in replacement for every hosted scheduling feature. Start with the workflow you actually need, then check the relevant integration documentation before migrating a busy calendar.

What is included in the deployment

Our recipe runs Tymeslot with a private PostgreSQL database and persistent application storage. The web endpoint works without a dedicated IP. The recipe also generates separate application and data-encryption secrets.

Keep those secrets when updating or restoring the installation. In particular, do not replace SECRET_KEY_BASE or DATA_ENCRYPTION_KEY as a routine troubleshooting step: the existing installation depends on them.

Three things to configure before sharing your link

Email, a calendar connection and meeting types are part of setup—not optional finishing touches. In our test, skipping the calendar step left the public booking page unavailable.

1. Configure SMTP. Set SMTP_HOST, SMTP_PORT, SMTP_USERNAME, SMTP_PASSWORD and EMAIL_FROM_ADDRESS through the Environment tab, using your mail provider's settings. Restart to apply the changes. The default localhost setting will not deliver verification or booking messages.
2. Claim the first account. Open /auth/signup immediately, complete email verification and follow onboarding. Review registration settings before sharing the installation publicly.
3. Connect your calendar. Use the integration appropriate to your provider. External integrations need your own credentials; deploying the app does not automatically configure Google or Microsoft OAuth.
4. Create at least one meeting type. Set its duration and availability, and review your profile and time zone.
5. Test as a visitor. Open your public booking page, select a time and complete a trial booking. Confirm it appears in the connected calendar and that both sides receive the expected email.

What we tested

We tested signup, email verification, accepted and rejected logins, onboarding and logout against a disposable installation. With a test CalDAV calendar connected and meeting types configured, a visitor booking reached the confirmation page, produced notification emails in a local mailbox and wrote a calendar event.

We also checked that the account and booking survived an application restart. These were application-protocol tests, not a full visual browser or mobile compatibility review. Google and Outlook OAuth and delivery through a real mail provider were not part of that test.

Choose the workflow that fits

Tymeslot is worth exploring when your starting point is a meeting link and a connected calendar. If your workflow centres on services and multiple appointment providers, our Easy!Appointments catalog entry is another option to evaluate.

Running your own scheduler gives you more operational responsibility as well as control. Keep database and file recovery copies, preserve encryption keys and test changes before relying on them for customer bookings.

Follow the official Tymeslot setup and integration guides for your calendar provider, then explore Cloud Apps to deploy your installation.