The people behind the games.
The studio, the people in it, and how a SoraBlox game actually gets built.
Small team. Short chain. Fast patches.
We are not an agency with a deck. We are the people who write the Luau, tune the economy curve and answer the Discord ticket, usually in the same afternoon.
SoraBlox
Roblox community · founded by @archon79797
0+
Members
Group members get in-game titles and reward drops. It is also where feature requests actually land on the roadmap.
Open the groupSix disciplines, no outsourcing
Everything that touches the player is built by someone who will still be here when it breaks.
Engineering
Luau end to end. Rojo-managed source, typed modules, ProfileService-backed persistence, replicated state that survives a full server. Everything in version control, nothing improvised in Studio at 2am.
Economy design
Curves, sinks, faucets and the arithmetic behind them. We model progression in a spreadsheet before it ever becomes a table, then tune it against live telemetry once players find the hole we missed.
Art and UI
Low-poly assets built for mobile draw calls, and interfaces that read on a phone held at arm's length in a moving car. That is the actual use case, so that is the target.
Community
A Discord that gets answered, a moderation team with real coverage, and a feature pipeline that starts in the complaints channel more often than it starts in a planning doc.
Live operations
Content calendars, seasonal events, code drops, offer testing. The unglamorous machinery that separates a game with a spike from a game with a curve.
Security
Server-authoritative by default, rate-limited remotes, and audited purchase flows. We take exploit reports seriously and patch fast.
Four rules we do not bend
Retention over launch spikes
A front-page day is a rounding error. We build for the player who comes back on day thirty, and we tune the economy until they do.
Data-driven, not data-decorated
Every system ships with instrumentation. If we cannot see the curve, we do not ship the feature.
Small team, short chain
No layers between the person who spots the problem and the person who fixes it. That is why we patch in hours, not sprints.
The community is the roadmap
285,000 members is a feedback loop, not a vanity number. Half our best features were Discord complaints first.
Come find out for yourself.
Join the Discord, play the games, and tell us what's broken. That feedback loop is most of how we build.