Studio
Raveschoot 22, 9080 Lochristi, Belgium +32 9 379 36 08 [email protected] Monday to Friday, 9:00 AM – 6:00 PM
NEXORA Industrial Solutions — Lochristi, Belgium
A studio ledger from East Flanders — six stages of one build, laid flat on the page. NEXORA makes PC games and cross-platform desktop software from the same discipline.
The pipeline, printed
Stages 01–06
What the software has to do, who will use it, and when it needs to exist. Every project starts as a conversation about scope, not a quote; the shape we agree on is a prototype phase, a production phase, and a release phase with a working build at the end of each.
Short experiments test whether an idea has legs before a production budget gets committed. A two-week prototype answers questions six months of planning cannot — one mechanic, a rough look, and an honest decision at the end about whether to continue.
Selection shapes hiring, plugin access, and how hard a port will be in year three. Open-source engines like Godot appeal to lean teams because the source is inspectable; commercial engines bring large middleware libraries and established console pipelines. Neither is automatically right — the choice gets documented either way.
Small, testable pieces that run on a clean machine. The same build tooling carries a simulation game and an industrial tool; portability is the discipline that keeps both honest. If something only works on one machine, it is not finished yet.
Walk through our work processA set of practical choices, not one obvious answer. Browser-game platforms such as Leuven-based CrazyGames reach players who never install anything; itch.io carries prototypes and experimental releases; Steam and consoles have their own expectations about page assets, wishlist timing, and review builds.
A release process the client can repeat without us. A build that runs on a clean machine, storefront work done before the date, and a documented path so version two is a decision rather than a rescue. Software nobody can rebuild is software with a short life.
The desk at eight in the morning — the same light the plates are lit by.
The cross-platform side
The desktop side covers business software, Windows services, and custom tooling for local operations. A Windows service that watches a folder and syncs it to a shared drive is unglamorous and extremely useful. So is a cross-platform utility that runs identically on a receptionist's macOS machine and a workshop's Windows terminal.
Three peers, one stack
Release registers — what runs, what ran
currently runningWindows
Services, tray utilities, and industrial tools where the operator's machine is the target — built to run without an installer nobody can rebuild.
macOS
The same utility on a receptionist's desk as on a workshop terminal. Native behaviour, no surprises, and a build we can sign and hand over.
Linux
Server-side schedulers, background daemons, and industrial tooling that lives where nobody is watching the screen.
The specimen ledger
Open register
The shipping record
Clients come from two directions — small teams and solo developers who need production help, and regional companies that have outgrown spreadsheets and need a tool built for how they actually work. Every project gets senior attention rather than a handoff to a junior bench.
Where we ship from
Raveschoot 22, 9080 Lochristi, Belgium — East Flanders. Work happens from there, and collaboration with external artists, writers, and engineers happens on a project basis from wherever they are.
Getting a project moving
We want to know what the software has to do, who will use it, and when it needs to exist. From there we can propose a realistic shape — a prototype phase, a production phase, and a release phase with a working build at the end of each.
Tell us about the project in plain terms. Scope, users, and timeline are more useful to us than a formal brief.
Before you write
