Property 35 of 50

skullsailor.com

The pirate game that served a 502 error for months before a fleet sprint brought it back from the dead.

What this property was

SkullSailor is a pirate-themed 3D browser game — ships, sailing, treasure, the whole flag-and-cutlass fantasy rendered in WebGL. It's the most technically ambitious game in my portfolio by a wide margin: Next.js and TypeScript on the shell, BabylonJS and React Three Fiber doing the 3D heavy lifting, Rapier handling physics, custom shaders in their own directory, and a Capacitor config sitting there for hypothetical iOS and Android builds.…

Evidence recorded in the manuscript

Revenue: zero. The Stripe code has never processed a real purchase as far as I know, and I'd bet heavily on that. Traffic: effectively none — a site that 502s for months performs a kind of SEO self-deletion, and search engines obligingly forgot it existed. Costs: domain renewal, significant build-time server resources, and a real chunk of development hours across the engine, physics, shaders, and the unused mobile scaffolding.…

The lesson recorded after launch

An unmonitored project doesn't fail loudly — it just quietly stops existing, and you pay renewal fees for the corpse. The 502 wasn't the failure; the failure was the months where nothing and no one was responsible for noticing the 502. At portfolio scale you cannot rely on caring about each project individually, because you won't — attention flows to the cash engines, as it should.…

Related property case files