StackRigs

An open index of what developers are actually building

Building Active
Stack
Infrastructure
Hosting
Raspberry Pi 5 (self-hosted)
Database
SQLite with Litestream replication
CDN
Cloudflare
CI/CD
GitHub Actions
Monitoring
Custom Go metrics + Prometheus
AI Tools
  • Claude (claude-sonnet-4-20250514)

    Code review, architecture decisions, writing build log entries

  • GitHub Copilot

    Inline code completion during development

What Works

SQLite on a Pi 5 handles 500+ req/s without breaking a sweat. The single-binary Go deployment means zero dependency management. Cloudflare caching + Litestream backups give us enterprise-grade reliability on a $60 computer.

What Broke

Initial attempt with PostgreSQL was overkill. Memory usage on the Pi was too high and the connection pool kept timing out under load. SQLite with WAL mode solved everything.

What I'd Change

Would start with Astro from day one instead of trying a SPA first. The island architecture is perfect for a content-heavy site like this. Also would set up Litestream earlier instead of manual backups.

Updates

Milestone

First 100 builds indexed

Reached the milestone of 100 build logs submitted. The community is growing organically through word of mouth.

Stack Change

Migrated frontend to Astro 5.18

Moved from the SPA prototype to Astro with islands. Page load times dropped from 2.1s to 340ms.

Infra Change

Added Litestream for continuous backups

SQLite WAL files now replicate to Cloudflare R2 every 10 seconds. Total cost: $0.

Pivot

Dropped PostgreSQL for SQLite

After weeks of fighting connection pooling on the Pi, switched to SQLite. Best decision of the project.

Reflection

Why not just use a spreadsheet?

Considered whether a Google Sheet would suffice. Decided structured data + API access + embeddable badges justified building a proper tool.

Setup

Embed Preview

StackRigs build badge for anarodriguez
<img src="https://stackrigs.com/badge/anarodriguez.svg" alt="StackRigs build badge for anarodriguez" />

Add to your README

Add to your README