Specialty
Cross-server data, persistence, and anti-exploit work for Roblox games under load.
I handle the unglamorous backend that decides whether a game survives growth — persistence, cross-server data, and the server authority that keeps exploiters out.
Cross-server data and persistence systems running at 31k peak players
Proof Metrics
Cross-server
Consistent data at scale
Session-locked
Persistence model
Hardened
Remotes and validation
Who This Fits
Teams that need senior technical ownership.
- -Games hitting DataStore, memory, or cross-server limits
- -Teams dealing with dupes, rollbacks, or data corruption
- -Studios that need exploit mitigation before scale exposes them
Common Problems
The reasons people usually bring me in.
- -Player data corrupting, duplicating, or rolling back
- -Cross-server features that don't stay consistent
- -Remotes and gameplay that exploiters can abuse
What I Deliver
Execution that closes the risk, not just the ticket.
Session-locked persistence and safe data migrations
MemoryStore and MessagingService cross-server systems
Remote validation and anti-exploit hardening
Case Studies
Proof from shipped work.
Engineering Notes
Technical writing that shows how I think.
High-Stakes Projects
Need backend & scale support on a live project?
If the product is already under pressure, send the brief. The best fit is a high-stakes build where reliability, speed, and technical judgment matter.