Custom FiveM systems
Custom resources and server systems that fit the framework, inventory, and setup already in use.
FiveM systems / web products / tooling
DESIGN / DEVELOPMENT / SUPPORT
I'm Zox, a full-stack developer based in Stockholm. I mainly work on FiveM products, web apps, and developer tools. I like taking a project from the first idea through release and maintenance.
At Orbit Studios, I design and build products, handle framework integrations, and support them after release. The code needs to be practical for players, server owners, and whoever maintains it next.
Understand the existing setup, agree on what done means, then build in small steps that are easy to test.
02 / Services
I work on new builds and existing projects, from FiveM resources and UI to APIs, bots, and internal tools.
Custom resources and server systems that fit the framework, inventory, and setup already in use.
FiveM NUI, web apps, and admin dashboards, covering both the interface and the code behind it.
APIs, Discord bots, automation, and internal tools that reduce repetitive work and connect existing systems.
Fixes and rebuilds for existing projects with performance, compatibility, structure, or usability problems.
03 / Selected work
A selection of products and open-source projects. Some client and private work cannot be shown publicly.
A configurable FiveM HUD that keeps player and vehicle information clear across different frameworks and screen sizes.
A configurable FiveM crafting system with recipes, workstations, progression, and support for common frameworks and inventories.
A Windows app for installing, configuring, and managing an FXServer workspace without jumping between several tools.
One of my first C# projects: a public Counter-Strike 2 economy plugin that works, but is still rough around the edges.
Toolkit
I choose tools based on the job. These are the ones I use most often.
GitHub activity
Contributions from my public repositories over the last twelve months. Private and client work is not included.
How I work
// simple code is easier to maintain.
When something breaks, the cause should be easy to find.
Use clear modules and predictable behavior without adding abstractions that are not needed.
Performance, clear feedback, usability, and reliability are all part of the finished work.
Common questions
About the work I take on, private projects, and existing codebases.
Tell me what you need
A good first message tells me what already exists, what needs to be built or fixed, which dependencies matter, the design and features you have in mind, and what outcome should count as done.
DIRECT CHANNELS
Use whichever is easiest.