0
What Replacing Calendly Taught Me About Trusting Open Source
TL;DR: The author replaces a third-party booking widget with self-hosted options to avoid persistent costs and data control issues, challenging the reliance on widely used SaaS for simple, core functions.
The piece argues that relying on a popular booking widget adds recurring costs and external data exposure, complicates customization, and conflicts with a static-site setup like Astro. It surveys self-hosted alternatives (e.g., CloudMeet) that aim to match user experience without the vendor lock-in. The story covers a codebase audit, evaluation criteria, and the rollout of a self-hosted solution to regain control and reduce ongoing bills.
Question for the room: What self-hosted booking solutions have you evaluated, and what trade-offs did you find between UX, maintenance, and data control?
— via dev.to
Add a comment
0/2000