iglo-tech · a stack for solo projects
Self-hosted tools for people who build and run a product by themselves: a backend, email, uptime monitoring, and help with coding. Each one started as a fix for a need in a real solo project.
A database, an API and an admin screen for your app, in one file.
./iglo-base serve --http 127.0.0.1:8090 --dir /path/to/pb_dataChecks your sites and services and tells you when they go down.
Newsletters, transactional and lifecycle email from your own server.
A fork of T3 Code with reusable workflows for coding agents.
Semantic search over a repository's Markdown notes, as a CLI.
| Product | Job | Replaces | Ships as | Storage | Platforms | License |
|---|---|---|---|---|---|---|
| iglo.base | Backend | PocketBase | Executable, container image | SQLite | linux-x64, linux-arm64, darwin-arm64 | MIT |
| iglo.monitor | Monitoring | Uptime Kuma | Executable | SQLite | See releases | MIT |
| iglo.email | listmonk | Source | SQLite | — | AGPL-3.0 | |
| iglo.code | Coding with agents | T3 Code | Source | — | — | MIT |
| iglo.memory | Project knowledge | — | Executable | Local snapshot | linux-x64 | — |
A project that serves a few thousand people a month has simple needs. It does not need a cluster, a queue service or a team to run it. It needs a few tools that do one job each and stay out of the way.
Each tool started from a need in a solo project, then was published.
Most tools are one executable with their data in SQLite, on one server.
Self-hosted. You run them, you keep the data.
Independently maintained. No support promise, no issue triage process.
How they are built. TypeScript on Bun, SQLite for storage, one executable where possible. Four are derived from known open-source apps.