Why Roblox Bet on a Custom Engine and Luau: The Boring C++ Sandbox Behind 85 Million Daily Players

Short answer: Roblox runs on its own C++ engine plus Roblox Studio and a Lua fork called Luau — not Unity or Unreal — because it is not selling a game, it is running a mall for millions of untrusted kid-made games on phones, Chromebooks, consoles, and PCs at the same time.

That choice looks old-fashioned until you count the constraints: Roblox reported an average of 85.3 million daily active users as of February 2025, and says half of American children under 16 play each month. No licensed engine in 2006 offered free-to-play distribution, one-click multiplayer replication, built-in moderation, and a cash register that takes a cut of every transaction. So Roblox built the cash register itself.

What Roblox actually runs on

• Platform, not a single game: Roblox is an online game platform and game creation system developed by Roblox Corporation, created by David Baszucki and Erik Cassel in 2004 and released September 1, 2006. It ships on Windows, macOS, iOS, Android, Xbox One, Quest 2/Pro, PS4 and PS5.
• Engine: Roblox Studio is described as the platform's game engine and development software, with some engine parts written in C++.
• Language: All games predominantly use Luau, a dialect of Lua 5.1. Luau was deployed August 27, 2019, initially called Faster Lua VM, and open-sourced under MIT on November 3, 2021.
• Business loop: Free-to-play with Robux, user-generated avatar items, limiteds that trade like NFTs, and Developer Exchange where 30,000 Robux can be cashed out — about 345,000 developers earned money in 2020. By July 2020 at least 20 games had been played over a billion times and 5,000 over a million times.

The company history matters: Roblox Corporation was founded in 2004 in Menlo Park after Baszucki's Knowledge Revolution made Interactive Physics and Working Model, started as DynaBlocks beta in 2004, renamed Roblox in 2005. It moved from third-party cloud to proprietary infrastructure after hiring from Dropbox in 2018 and buying mobile-network optimizer PacketZoom, then listed on NYSE as RBLX March 10, 2021 with $3.60 billion revenue in 2024.

That physics-toy lineage is not trivia. It is the engine spec.

Why not Unity or Unreal? Four boring reasons

1. Untrusted code at kindergarten scale.
Unity and Unreal assume a trusted studio. Roblox assumes 2 million+ developers, a majority minors as of 2020, uploading code that will run on a stranger's phone. Luau's standard library has no file-system or OS access by default, enforces memory and infinite-loop limits, and the GitHub docs push safeenv sandboxing to isolate scripts from each other. Luau.org frames this as embeddability: sandboxed by default so embedders can safely execute untrusted user code. No general engine gave them that in 2006.

2. One build must run on a school Chromebook and a PS5.
Luau rejected LuaJIT partly over limited console support and maintenance pain, and built its own VM instead. Benchmarks put Luau's interpreter near LuaJIT's interpreter mode, with LuaJIT's JIT about 1.6x faster in some tests — then Luau added native code generation in October 2023 for x64/ARM64 with 1.5x-2.5x gains on intensive code. That is a political compromise, not a benchmark chase: interpreter everywhere, native where allowed. Unreal's high-end-first scaling would have excluded the exact classroom devices that made Roblox grow.

3. The engine is the store.
If Roblox had shipped on Unity, it would pay a landlord while trying to be a landlord. With its own engine it owns replication, avatar catalog, Robux checkout, and the DevEx haircut. That is why templates ship inside Studio to let anyone publish and why more than 20 million games per year were reported in 2020. Friction is the product.

4. Physics-class DNA.
Baszucki did not come from shooters. He came from 2D physics simulation for education. A block that a 9-year-old can stack, drive through, and sell is more valuable than a photoreal shader that needs a technical artist. The chunky avatar persists because legibility beats fidelity when your creators are children.

What Luau actually changed from Lua 5.1

If you only remember Lua from Garry's Mod or World of Warcraft addons, Luau looks familiar but behaves like a stricter, faster cousin:

• Gradual + structural typing with inference: add : number, : string or leave it dynamic. Strict mode aims to catch errors before runtime; non-strict minimizes false positives while migrating old code. Luau.org calls this safety: refinements and type functions powered by inference to rule out errors and drive autocomplete with minimal annotations.
• New runtime, not a patch: C++ VM from scratch with constant folding, dead-code elimination, peephole optimization, and inline caching, compiling ~950,000 lines/sec on a Ryzen 5900X. GitHub stresses it is largely rewritten, preserves Lua 5.1 API for bindings, but separates compile (luau_compile) from load so you can ship a VM without a compiler.
• Modern syntax without breaking 5.1: +=, string interpolation with backticks added February 2023, if ... then ... else expressions, continue, const + table.freeze.
• Pause-free GC: Incremental collector with PID-controller heap pacing borrowed from Go, plus closure/upvalue/weak-table tuning to cut pauses. This matters for 30-player obbies where a stop-the-world hitch reads as cheating.
• Tooling as first-class: Compiler, type checker, linter and language server shipped open-source, with luau REPL sandboxed and luau-analyze for CI.

The outside validation is telling: Remedy replaced proprietary scripting with Luau in Northlight for Alan Wake 2 and deleted ~80,000 lines, Digital Extremes moved Warframe for GC/memory wins, Giants adopted it for Farming Simulator 2025, and Linden Lab shipped SLua for Second Life in December 2025. GitHub now lists Alan Wake 2, Farming Simulator 2025, Second Life and Warframe as Luau users. Luau is quietly becoming the SQLite of game scripting — not the coolest language, but the only Lua fork that solved consoles + sandbox + types together.

My take: five ideas you will not find in the docs

These are interpretation, not Roblox statements. I label them as such because the task asks for distinct analysis, not recycled conclusions.

1. The type checker is moderation, not just DX.
Everyone praises Luau types for autocomplete. I think the real payoff is support-ticket deflection. When your creators are kids, a crash in front of 20 friends is a moderation event. Strict mode plus lint catches the nil-index before it becomes a 1-star review and a parent email. It is a chat filter for code.

2. Kindergarten-server theory.
Most engines optimize for a trusted team of 50. Roblox optimizes for 2 million strangers, many hostile or careless. Resource limits, no OS access, per-script globals — that is not paranoia, it is daycare architecture. Unity trusts you; Roblox assumes you will while true do end on someone else's iPad.

3. Lag as democracy.
Black Myth: Wukong bets on Nanite to show more. Roblox bets on running at all. Interpreter-first means a 2015 Android can still join Adopt Me, while native code lets a gaming PC run a 200-player shooter smoother. The ceiling is set by the poorest classroom device, not the richest GPU. That is the opposite of prestige-engine thinking, and it is why growth accelerated in the second half of the 2010s and again during COVID.

4. Anti-Unreal economics.
Royalty engines tax the developer. Roblox taxes the transaction. Owning the engine lets it give Studio away free, then take a cut of Robux, limiteds resale, and DevEx. You cannot do that cleanly on someone else's runtime without paying rent twice. The custom engine is a cash-register decision disguised as a tech decision.

5. Boring is a moat.
C++ core that never breaks old games, Lua 5.1 compatibility that never orphans tutorials, blocks that never need retopology — this is deliberate boredom. While every 2024 obby complains about graphics, no 2012 obby stopped working because the renderer changed. That backward compatibility is why parents trust it and why competitors with prettier demos cannot steal the library of 20M+ games per year.

If I were cloning Roblox today, I would not start with graphics. I would start with sandbox + payments + a linter that talks like a teacher.

What indie devs can steal (without building a country)

1. Sandbox before shaders. Ship safeenv-style isolation and per-script timeouts first. Kids and modders forgive ugly; they never forgive a crash that eats inventory.
2. Two typing modes. Offer non-strict for jams and strict for launch. You get fast onboarding and fewer midnight hotfixes.
3. Templates as growth. Roblox Studio's pre-made templates do more for retention than any ad. One obby template beats ten docs pages.
4. Device floor, not ceiling. Profile on the cheapest device your players actually own (often a Chromebook or old Android), then add native/JIT as a bonus, not a requirement.
5. Own the register if you host UGC. If players sell to each other, you need first-party commerce and DevEx-like payout rules from day one. Bolting a store onto a licensed engine later creates fee-on-fee pain.

Try the building intuition in your browser

You do not need Studio to feel why this loop works. These free browser games isolate one Roblox muscle at a time — and they run instantly with no install:

• For block-break-collect-rebuild and Creative vs Survival pacing, play Mine Clone. Start small, gather wood/stone early, then plan a build — the same tolerate-failure loop that lets a 10-year-old publish an obby without fear. Its world-generation-every-time design shows why simple voxels beat high-poly when creators are beginners.
• For decoration-as-ownership (the Adopt Me / Bloxburg house loop), try Craft World. With 300+ blocks and furniture layering, it teaches what Roblox learned: kids do not just build walls, they curate sofas, lanterns and themed rooms. That interior-design itch drives Robux avatar sales more than any gun stat.
• For open-city roleplay plus missions-cash-shop (Brookhaven, Driving Empire in miniature), roam Sandbox City - Cars, Zombies, Ragdolls. Talk to Mission Guy, claim daily cash, buy a bat before a rifle, hijack any car with E. It compresses Roblox's mission → cash → shop → boost economy into a five-minute session.

If you enjoy the building-under-pressure side of Roblox BedWars, add BuildNow GG Freebuild + BoxFight drills: 90s, ramp rushes and box-peeks train the same place-edit-shoot reflex Studio PvP demands, but in a tab.

Limits and open questions

• Performance still cliffs: interpreter-first saves compatibility but intensive physics still needs native code or clever throttling. Large servers shard aggressively for a reason.
• Moderation does not scale with code: sandboxing stops os.execute, it does not stop social engineering. Scams around free Robux, beamers stealing session tokens, and once-per-account rollbacks remain documented problems.
• Age-gating is tightening: ratings now split Everyone / 9+ / 13+ / 17+ with ID verification for 17+, and blocks in China, Turkey, Iraq and others show the country-scale cost of hosting kid UGC.
• Luau's outside wins (Remedy, Warframe) prove portability, but they do not prove Roblox's networking and commerce stack is portable. The language is MIT; the mall is not.

Bottom line: Roblox did not pick a custom C++ engine and Luau because they are exotic. It picked them because no store-bought engine wanted to be a school, a sandbox, a phone OS, and a bank at once. Boring, sandboxed, and payable beats pretty — when your developers are eight and your players are 85 million.