Alban Billiette
Download CV ↓
← All work

Rustaveo

04 / 04

A paid companion web app for the game Rust. It sends raid alerts the second a base is hit, profiles enemy players, and runs a team's base from a shared live map, built on the Rust+ companion protocol.

Year2026
ContextPaid SaaS, built and run solo
RoleSolo (product, backend, frontend, infrastructure)
TagsTypeScript · Fastify · PostgreSQL · React 19 · WebSockets · Docker · Caddy · Chrome extension
The Rustaveo web app: a live map of a Rust server with its grid, monuments and player markers, beside the sidebar for intel, tracking, alerts and automations

Goal

Rust players lose their bases while they sleep. The game’s official companion app (Rust+) can talk to a server, but it only reaches the people who have it open. I wanted a hosted product a whole clan could share: raid alerts that actually wake you up, intel on the players around you, and the base’s switches and alarms on one live map, with nothing to install.

What I built

A full product, from the protocol connection to billing, that I designed, built, shipped and ran on my own.

How it fits together

A browser can’t speak the Rust+ protocol, so Rustaveo is a backend that holds the game connections, and a web app that talks to it. The connection itself uses the open-source rustplus.js client for the reverse-engineered Rust+ protocol. Everything around it is mine.

Browser (React + Vite)
  │  HTTPS (REST) + WSS (live push)
  ▼
Caddy (TLS) ──► Node backend (Fastify)
                 ├─ Steam OpenID login
                 ├─ rustplus.js connection ──► Rust game server
                 ├─ Postgres (servers, credentials, events)
                 └─ serves the built web app (single origin)

The code is one TypeScript monorepo: shared/ for the types used on both sides, server/ for the Fastify API, WebSocket hub and game connections, and web/ for the React single-page app.

Keeping players’ credentials safe

Linking a game account means handling a token that can control a player’s base, so it never reaches the browser.

Shipping it

Releases went out without downtime on Docker and Caddy, which also handles HTTPS. The 680 tests gate every merge, and each deploy is pinned to a commit so a bad release rolls back automatically.

Why it closed

Everything in Rustaveo runs through the Rust+ companion API. In 2026 Facepunch, the studio behind Rust, nerfed that API, and the features the product was built on stopped being possible. Rather than keep charging for a weaker product, I closed it in November 2026: renewals were stopped and unused paid days refunded.

Result

80klines of TypeScript in one monorepo
680tests that gate every merge
Next project → Rustorigin