Sovereign Game Production
The title nobody has announced yet cannot go through a cloud service.
NGARi Gaming produces game assets — concept art, textures, sprites, UI, voice, music, trailers — on hardware you own. Every asset's rights position is decided before it renders, and recorded after. Nothing leaves the building, and the record travels with the build.
Why this matters now
Studios are already using generative tools. They are not shipping the output, and the gap between those two facts is the entire problem.
GDC's 2026 State of the Game Industry survey found 36% of developers personally use generative AI and roughly 52% of studios use it — while only about 5% put AI output in front of players. More than half of the developers surveyed said the technology is harming the industry, up from 30% a year earlier.
That is not a quality gap. It is a provenance gap. A studio can generate a texture in an afternoon; what it cannot do is prove, to a publisher, a platform holder or a lawyer, what that texture was made from, which model made it, whose likeness or style it carries, and whether the model's licence permits the release it is about to ship in.
Cloud tools cannot close that gap, because the material they would need to see — the unreleased build, the NDA'd character, the art direction that has not been announced — is exactly the material a studio is contractually forbidden from uploading.
The rights decision happens first
This is the part no generator does, and the reason to run one on your own floor.
Before anything renders, each asset declares what it is and where it comes from: what it is built from, whose voice it clones, whose likeness it depicts, whose style it references, and what the generating model's licence permits. The engine evaluates that against your policy and returns one of three answers:
Permit
The engine sees no barrier it can name. It produces a record — not a clearance, and not a statement that a use is lawful. It will not pretend to be either.
Refuse
A rule is breached, and the engine names it. A cloned voice without recorded consent. A real person's likeness on a release. A third party's title being distributed as a derivative work.
Needs a human
The engine stops and hands it to a person. Absence of a declared basis is never treated as a pass, and an undeclared rightsholder is not an absent one.
Three decisions are fixed and cannot be configured away: consent for a cloned voice, consent for a real person's likeness, and consent for training on someone else's work. Your policy can only ever add restrictions to those — it cannot subtract from them.
Remastering and localisation, honestly assessed
Upscaling a back catalogue, re-voicing a title for a new market, and translating a game that never shipped in your language are all real work. They are also all derivative work questions about somebody else's game, and the engine treats them that way.
Ask it to assess a remaster and it separates four things that this market routinely conflates:
| Question | How it is treated |
|---|---|
| What you may do privately | Usually permissive, and recorded as such |
| What you may distribute | Nearly always needs the rightsholder — a third party's title plus a distribution intent is an outright refusal |
| What the model licence permits | Read from the same catalogue of open-weight models, with each licence class tracked |
| What a person's likeness or style permits | The same fixed floor as everywhere else. A game does not get a weaker consent rule because it is a game. |
The engine will not decide fair use. Ask it to, and it hands the question back. Fair use turns on four statutory factors and the specific facts of a specific use. A deterministic engine that answers it is giving legal advice it is not qualified to give. Ask a lawyer; we will hand them the record.
What runs today
Game asset production is served by the same open-weight stack as the rest of the studio. No gaming-specific model is required, and none is claimed.
| Asset class | State |
|---|---|
| Concept art, textures, sprites, UI | Runs today Text-to-image and image-edit on local weights |
| Trailers, cutscene plates | Runs today Text-to-video on local weights |
| Voice prototyping | Runs today Speech synthesis on local weights, with per-voice consent captured before generation |
| Music, sound | Runs today Music generation on local weights. The 5 Hz planner is skipped on CPU hardware, so this is the diffusion path alone and the output sits far below a release master — a wired invocation, not a quality claim |
| Restoration and upscaling | Runs today Real-ESRGAN x4 on local weights, x4 upscaling through the same engine as the rest of the stack — not a bolt-on. We ran a 128×128 plate to 512×512 on the appliance GPU in 4.26 seconds |
| Frame interpolation | Not installed No aarch64 build of RIFE exists and no binary is on the box, so nothing here pretends to do it. Building it is a modest job — the dependencies are vendored and it would use the GPU — and it is named here rather than implied |
| Level geometry, gameplay code | Not generated Authored, not generated. An "AI game studio" that claims otherwise is overselling |
This table is the honest version, including the rows that say no. A capability list that only ever says yes is a brochure, not a specification.
What this is not
This is not an emulator, and NGARi does not sell one. No ROMs, no BIOS files, no firmware keys, no emulation front-end, and no claim to run anyone else's console software. Game production is a creative pipeline; running a back catalogue is a different business with a different legal posture, and it is not this one.
Nor is it a Content Credentials implementation. Every asset carries a per-asset consent and provenance manifest, and that manifest is signed with Ed25519 — a real public-key signature you can verify offline without asking us. What that does not give you is C2PA conformance, a trusted timestamp or a transparency log: a signature proves a manifest was signed and has not been altered since, not when it was signed, and it cannot detect a signer who signs two contradictory manifests. Publishing a key and having a third party verify it is a separate job, and it is named here as outstanding rather than implied by the word "signed".
Who it is for
Studios under NDA
Unannounced titles, licensed IP and publisher contracts that prohibit uploading assets to a third-party service.
Art and audio outsourcing houses
Producing for clients who now ask, in writing, what the deliverable was made from.
Remaster and preservation teams
Working on catalogues where the rights position has to be documented before the first frame is touched, not defended afterwards.
Bring one production. A vertical slice, a texture set, a localisation pass. We will run it on your hardware, or ours, and hand you the record alongside the assets. [email protected]