# Migrate to Net Forge

> Moving a browser game or its backend to Net Forge, step by step.

Net Forge, the open-source multiplayer browser game engine built for AI coding agents, is published on npm under `@netforge` with source at https://github.com/netnetdev/net-forge.

Source: https://forge.netnet.capital/docs/migrate  
Last updated: 2026-10-23. Checked against @netforge/engine 0.2.0.

Each page maps the concepts you already use to their Net Forge equivalents.

- [From Hathora](https://forge.netnet.capital/docs/migrate/from-hathora.md): Hathora's game server hosting shut down on 2026-05-05. If your game is a browser game in TypeScript, this page shows what moves to Net Forge, what Net Forge does not replace, and the other options.
- [From a Socket.IO prototype](https://forge.netnet.capital/docs/migrate/from-socket-io-prototype.md): A Socket.IO prototype relays events between browsers. Net Forge replaces the hand-written relay with an authoritative room that steps one shared simulation, so movement, hits and scores are decided in one place.
- [From a three.js scene](https://forge.netnet.capital/docs/migrate/from-threejs-scene.md): Net Forge renders with three.js, so a three.js game moves over by splitting it in two: rules go into a declarative src/game.ts that runs on the server and the client, and drawing stays in the template's three.js client.