Lagos Life’s interviewer reports a Next.js and Cloudflare D1 starting point, followed by a database move to DigitalOcean and then an application/database move to AWS. That is an attributed build history. The official privacy policy still names DigitalOcean as infrastructure host, so the available sources do not settle the game’s present hosting arrangement.
The interviewer’s public account
In his public r/nextjs post, u/DominusKelvin, who says he publishes The African Engineer and interviewed Shalom, describes three stages:
- Start with Next.js and Cloudflare D1 for a small project.
- Move the database to DigitalOcean as the game grows.
- Move the application and database to AWS after problems that included the application and database being in different locations.
These are the interviewer’s summary of the developer’s account. They are not a deployment log, a load test, or evidence that this guide reproduced the migrations. The related feature’s public preview names Shalom Rayhamen; creator and operator identities are explained separately.
The reported stack
| Area | Technologies named in the interviewer’s post |
|---|---|
| Application | Next.js 16, React 19 and TypeScript |
| Database | PostgreSQL |
| Real-time services | Socket.IO |
| 3D presentation | Three.js through React Three Fiber |
| State and interface | Zustand, shadcn/ui and Tailwind |
The post calls this the current stack at the time of its account. Its absolute publication date was not verified: the packet and live page show inconsistent relative ages. The technology versions above are therefore attributed to the post, not presented as a verified inventory of today’s production build.
Hosting and AI claims remain bounded
The official Privacy Policy’s How We Share Information → DigitalOcean section says the infrastructure is hosted using DigitalOcean. It does not reconcile that statement with the interviewer’s AWS account. Either document could describe a different point or part of the system; the available evidence does not establish which explanation applies.
In Zikoko’s 7 October first-person interview, Shalom describes an eight-hour initial build and recommends Three.js. Her positive comments about AI do not identify a model or tool responsible for specific features. The initial prototype’s reported duration does not measure the work on the evolving game. No full AI-tool history or benchmark is established here.
What the web manifest establishes
The official manifest identifies the application as Lagos Life, gives it a standalone display mode and a start URL on the same service. That supports a web-app delivery description. It does not reveal private server architecture, prove offline play or independently verify the reported frameworks. See browser and home-screen access for the player-facing distinction.
Sources and scope
Prepared from public source material and the screens identified below. This guide does not claim an in-game playtest.
- u/DominusKelvin — public account of interviewing ShalomOriginal interviewer post; absolute post date unverified. Hosting account differs from the official privacy policy.
- Kelvin Omereshone — The Engineering Behind Lagos LifePublic interview preview; supplied cache dates the feature 7 October 2026. Paid portion not accessed.
- Lagos Life — Privacy & Cookie PolicyEffective 1 October 2026; wording checked 16 October 2026.
- Lagos Life — web app manifestSupplied original manifest checked 16 October 2026; does not establish native-store availability.
- Azara Tswanya — Shalom’s first-person build and launch account, Zikoko7 October 2026 interview, as told to the journalist. Figures and build time are creator-reported.
Browse all available guides · Return to the Lagos Life overview