Tymeslot is a self-hosted meeting scheduling platform: you define when you are available, publish a booking link, and other people pick a slot without needing an account of their own. It is written in Elixir on Phoenix LiveView, ships as a single container with PostgreSQL inside it, and is developed in the open under the AGPL. The commercial cloud at tymeslot.app runs the same build, so nothing is held back from the self-hosted edition.
.ics invite, configurable reminders, and cancel or reschedule links that need no login.meeting_created, meeting_cancelled and meeting_rescheduled, plus Slack and Telegram notifications./admin without a redeploy.Self-hosting is one Docker command: the published image starts the application together with its own PostgreSQL, and the first account created becomes the administrator. State lives in two volumes – the application directory and the PostgreSQL data directory – so the container itself is disposable. Three values matter on first start: SECRET_KEY_BASE, PHX_HOST and, for anything beyond a first look, DATA_ENCRYPTION_KEY, which decouples stored calendar credentials from the signing secret. SMTP for reminder mail, TLS and an external PostgreSQL are documented in the repository’s Docker guide, and Cloudron and Railway carry one-click installs. The stack is Elixir/OTP with Phoenix LiveView, PostgreSQL 14 or newer, and Oban for background work; there is nothing to compile.
One deployment detail to plan for: calendar providers expect the instance to be reachable on a real hostname with TLS. Google will not accept a bare private IP address or a .local name as an OAuth redirect target, so a home install needs a domain in front of it before Google or Outlook sync can connect. CalDAV servers work with fewer preconditions, and busy-time checks and bookings still work without any calendar connected, though the dashboard warns that the page is not taking bookings until one is.
This is the self-hostable branch of the Calendly family. Cal.com is the larger project with the wider ecosystem and team round-robin scheduling; Cal.rs is a lighter Rust implementation of the same booking-link idea; Calino is a CalDAV client rather than a booking page. Tymeslot’s distinguishing choices are the Elixir/Phoenix stack, the four themed booking pages, and a self-hosted build that is feature-identical to the paid cloud. On the calendar side it is a scheduling front end, not a calendar server – keep the events in Nextcloud, Radicale or Google and let Tymeslot read busy times from them; FluidCalendar covers the other direction, placing a task list into the free time a calendar leaves behind.