Fulgur

Fulgur launched in 2017 as a modded multiplayer game server and evolved as the audience, gameplay and product direction changed. It has grown into an online game platform that combines persistent playable worlds with a localized public website, live map, news, account-aware surfaces and community channels.

The platform is developed as a long-running product rather than a single delivery. My work covers product and engineering decisions, web and backend systems, infrastructure, content, community operations and continued development.

A long-running game community cannot be treated like a greenfield launch. Platform changes, migrations and new player-facing features have to coexist with an active product and with the expectations built up since 2017.

The public experience also crosses several boundaries: localized content, server status and player data, authentication, a live map, multiple data stores and production services. Those boundaries need to remain understandable and recoverable without exposing private topology or credentials.

I shaped the public website as a localized Next.js player hub for discovery, server connection, project information, news, rules, support surfaces and the live map. It gives visitors a coherent product entry point while the game servers and community channels remain distinct operational surfaces.

Behind it, typed NestJS and Fastify services connect Redis, PostgreSQL, MySQL and object storage where each is appropriate. The backend migration runs alongside the legacy service and uses domain feature flags, health and readiness checks, contract comparison, staged traffic cutover and an explicit rollback path before old responsibilities are retired.