Infrastructure · Personal project
FuryBee
35 containers. One infrastructure. One developer.
- Period
- Extensions since 2014; current platform since 2026
- Role
- Design, development and operations, solo
- Stack
- Docker Compose · Traefik · Cloudflare · Prometheus · Grafana · Loki · Alloy · Astro · Nuxt · Node.js · PostgreSQL · Redis · WebRTC
- Links
- furybee.org GitHub
- 35
- containers
- ≈ 20
- public sites and apps
- 230+
- technical articles
Users
Cloudflare · CDN, DNS
Traefik · reverse proxy, TLS
Sites & apps
Real-time
Workers
PostgreSQL · Redis
Observability
Prometheus · Grafana · Loki
Prometheus · Grafana · Loki
The platform
FuryBee brings together about twenty public sites and applications under furybee.org and its subdomains: Chrome extensions, developer tools, WebRTC multiplayer games, audio, image and video tools that run entirely in the browser, voice chat, a news aggregator, a stock portfolio tracker, and 230+ articles on AI, infrastructure, clean code and security.
The infrastructure
Everything runs on a single server: 35 containers that I design and run on my own.
- Docker Compose behind a Traefik reverse proxy (upgraded from v2 to v3 in September 2026), with automatic certificates.
- Cloudflare in front of every domain; the origin server only accepts Cloudflare IP addresses.
- Full observability: Prometheus, Grafana, Loki and Alloy, with alerts.
- Zero-downtime deploys for the real-time games service, pinned image versions, CDN cache purge on every deploy.
Why it matters
It's the same discipline as for a company application, at a smaller scale and without an ops team: anything that isn't automated, monitored and documented eventually breaks.
