Built on
patient open source.

Avocabo isn’t an open-source product. But we’re built on top of decades of careful work by maintainers who give it away. This page is our small thanks.

If any of the tools below have helped your own work, please consider sponsoring their maintainers. We do.

Runtime & language.

• TypeScript — The language Avocabo is written in. By Microsoft and contributors.
• Bun — Our package manager and the runtime in production. By Oven and contributors.

Framework.

• TanStack Start, Router, Query — The framework holding the front end together. By Tanner Linsley and contributors.
• React — The rendering library. By Meta and contributors.
• Vite & Rolldown — Our build tooling. By Evan You and contributors.
• Tailwind CSS — Our styling system. By Adam Wathan and team.
• content-collections — How we author and ship the legal pages and these notes. By Sascha Wassmer.

Database & storage.

• Drizzle ORM — Type-safe SQL access. By Drizzle Team.
• PostgreSQL — Our database engine in production. By PostgreSQL Global Development Group.
• PGlite — PostgreSQL running embedded in the browser and in tests. By ElectricSQL.

UI, type, and icons.

• Newsreader — Our editorial serif typeface, released under the SIL Open Font License. By Production Type.
• Inter — Our sans-serif typeface, released under the SIL Open Font License. By Rasmus Andersson.
• Phosphor Icons — A flexible, hand-tuned icon family. By Helena Zhang and Tobias Fried.
• BaseUI — Our headless component primitives. By MUI team.

Auth and observability.

• Better Auth — Our authentication library. By Bekacru and contributors.
• Plausible Analytics (Community Edition) — Privacy-friendly analytics, self-hosted on our own servers. By Plausible Insights OÜ.
• Sentry SDK — Error tracking on the client and server. By Sentry team.
• Coolify — How we deploy. Self-hosted PaaS sitting on top of Docker. By Andras Bacsai and contributors.

On Avocabo’s own code.

We are not currently open-source. The product is a small, focused service we run ourselves; the code is a means to an end, not the product. If we change our mind about this someday — say, after launch, when the surface area has settled — this page is where you’ll read about it first.

Thanks.

To everyone whose work we depend on: thank you. We try to use these tools the way you intended, and to give back when we can — through bug reports, sponsorship, and not breaking the stack with churn.