The studio

FuryBee is my independent studio. I design, build and host useful software there: tools that run in the browser, article libraries, games, apps and developer products. Today that means 21 live services, with a full brand identity and a public brand kit.

Five universes

• Learn: article libraries on AI, code, infrastructure and security, plus FuryBee News, a news aggregator.
• Create: tools that run in the browser, for developers, images, audio and video.
• Play: FuryBee Arcade (47 games, peer-to-peer, no accounts), BeeBee Kids and Galactic Reigns.
• Build: React and Astro themes, packages, the Chrome extension store (Web Store), Dictea and the brand kit.
• Apps: account-based services, some in beta: FuryBee Voice, FinBoard, profyl.it and Apprends avec BeeBee.

A stance

Almost everything is free: only the themes are paid. The portal and the tools load no analytics scripts, the tools process files on your own device, and everything is hosted in France, in Paris. Part of the work is open source, mostly under the MIT licence: the Tabee (Tab Modifier) Chrome extension, the Dictea desktop app and the php-deps static analysis tool.

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. And it's a permanent testing ground for what I offer my clients.