Why Go, HTMX, and SQLite
By Connor McCutcheon
Every framework makes bets on technology. Here are ours.
Go
Go compiles to a single binary. No runtime, no virtual machine, no package manager at deploy time. A Congo app is one file you copy to a server and run. Go's standard library handles HTTP, TLS, templates, and more — we depend on very little outside it.
Go also has the embed package, which lets us bundle the entire framework, templates, and static files into the binary itself. This is how congo init works: the CLI binary carries the framework source inside it and extracts it into your project.
HTMX
Most web apps don't need React. They need server-rendered HTML with a bit of interactivity. HTMX gives you that — any HTML element can make HTTP requests and swap content. No build step, no npm, no bundle. Just attributes on your HTML.
When you DO need rich interactivity (code editors, drag-and-drop, charts), Congo supports React island components that mount into server-rendered pages. Best of both worlds.
SQLite
SQLite is the most deployed database in the world. It's embedded (no server to run), fast for reads, and perfect for single-server apps. We use LibSQL for production, which adds remote replication — local reads at nanosecond speed, writes go to a primary server.
Your app starts with an in-memory database for development. Switch to a file for local production. Switch to a remote replica for distributed systems. Same code, same ORM, same API.
DaisyUI
Tailwind gives you utility classes. DaisyUI gives you components built on Tailwind with semantic naming. Instead of writing bg-blue-500 text-white px-4 py-2 rounded, you write btn btn-primary. Themes are built in — switch between light and dark with one attribute.
The Philosophy
These aren't trendy choices. They're boring, proven, and small. Go is 15 years old. SQLite is 25 years old. HTML is 30 years old. We pick technology that will still work in 10 years, not technology that's exciting this month.
Read more about our philosophy at congo.gg/philosophy.