Odin + HTMX
A server-rendered web stack in one binary
An Odin backend renders every page as HTML, HTMX supplies the interaction and SQLite holds the data — no framework, no bundler, no build step.
Overview
Live figures from the demo store, counted by SQLite. Each line is a spread, not a trend: contacts per role, then engagement scores from low to high.
Total contacts
20
5 roles
Active
7
35% of all
Invited
7
35% of all
Avg. engagement
68
score / 100
What you are looking at
The stack behind these pages.
Every page here was assembled as a string by an Odin procedure and sent as HTML. No client-side framework renders it, no bundler packs it, and nothing is read from disk while it runs: htmx, the stylesheet, the icons and the social card are compiled into the binary and served from memory.
HTMX covers what a plain page cannot. The table sorts, pages and edits in place, fields validate as you type, overlays open and toasts arrive — each one a small fragment of HTML swapped into the page over a single request, rendered by the same server that rendered the page. The store is SQLite, linked in as the amalgamation, so a deploy is one file you copy.
The contacts console is a demonstration rather than the point of it. What a fork inherits is underneath: strictly layered packages the compiler keeps honest, the data layer, the token-driven theme system, and the build, test and deploy harness that comes with them. More about the project.
OdinHTMX 4SQLitesingle binaryno build step