Documentation overview
Tidetime is self-hosted appointment scheduling for a single company with multiple services and multiple providers. This folder holds the authoritative documentation. It is plain markdown so it reads well on GitHub, and the project website builds its guides from these same files.
Where to start
Section titled “Where to start”- Getting started covers first run, creating the company, and taking a first booking.
- User guide explains day-to-day use: services, availability, and managing bookings.
- Admin guide covers company settings, team roles, email, branding, and the custom domain.
- Integrations covers Google Calendar, Microsoft 365, meeting links, and webhooks.
- Deployment is the production setup with Docker, PostgreSQL, and Caddy.
- Architecture describes how the app is put together, for contributors and operators.
- FAQ answers common questions.
- Troubleshooting helps when something is not working.
- Glossary defines the terms used across these guides.
What Tidetime is, in one paragraph
Section titled “What Tidetime is, in one paragraph”One company runs the instance. Customers open a public booking page, choose a service, pick a provider or let Tidetime assign the least-busy available one, and book an open slot. Providers set their own hours, connect a calendar for conflict checks, and manage their bookings from a dashboard. Owners and admins control the service catalog, the team, branding, email, and integrations. Everything runs on your own server and your own PostgreSQL database.
Project links
Section titled “Project links”- Source code and issues: https://github.com/Sulaiman-Dauda/Tidetime
- Contributing guide
- Security policy
- License