We make original games, and the invisible engineering that holds them up.
A washed-up anomaly analyst opens a file marked DO NOT OPEN (SERIOUSLY). The sky comes apart. Sci-fi mystery, dry comedy, and puzzles that are ridiculous without ever being unfair.
We would rather ship one world that stays with you forever than five that don't.
Dark Matt3r Studios started in Irvine, California to make one game properly. Building it meant building the pipeline underneath it — asset handling, automation, systems that could keep a small team moving at the pace of a large one.
Small team, no handoffs between strangers. The people who design a system build it and ship it. Everything is authored by someone who cares whether it is good.
A studio that funds its own titles and owns its pipeline end to end. Games are the reason the studio exists. Engineering is the discipline that keeps it independent.
Every scene is authored, not assembled.
Our worlds are drawn, written and scored by the people whose names are on them. A small team means fewer hands and no committees, and it means every room you walk into was placed there by someone who cared where it went. Nothing in our games is filler, because there is nobody here to hide behind.
Between our own titles we take on a small number of outside engagements. The same team, the same standard — no bench, no handoff to someone you have not met.
Engineering and partnership inquiries get a reply within two business days. Press and publisher notes reach the same inbox.
Current openings, the disciplines we hire into, and how to get on file for the next one.
VIEW OPEN ROLES →Logos, key art, screenshots and studio background. Available on request until the kit is published.
REQUEST THE PRESS KIT →Fractured Skies is in active development. Other titles are in the studio and will appear here when there is something real to say about them. Everything we learn making them gets written down in the devlog.
Calder Rook opens a file he was never meant to find, and the sky over the Salt Flats comes apart. A point-and-click adventure built on absurd puzzle logic, branching dialogue and a mystery with real stakes.
The devlog carries build notes, design decisions and the things that did not work — published while the games are still being made.
A washed-up anomaly analyst opens a file marked DO NOT OPEN (SERIOUSLY). The sky comes apart. A point-and-click adventure about mistakes you cannot undo.
Calder Rook used to analyse anomalies for people with budgets and acronyms. Now he scavenges corrupted data in a rain-soaked coastal city for clients who would rather not give their names. It pays badly and asks nothing of him, which suits him fine.
Then a routine recovery job turns up a packet nobody meant him to see: coordinates to a site that officially does not exist, an audio log of one man arguing with himself, and a warning that gets more frantic every time it loops.
He follows the coordinates, expecting a hoax built to waste conspiracy hunters' time. The illusion breaks. The sky fractures. People begin to vanish. Intelligence operative Mara Voss arrives to contain it, having spent months explaining away impossible weather — and the team sent in behind her lasts under a minute.
The anomalies are not invasions. They are leaks.
Something on the other side is trying to get a message out. Or get out itself. The longer the fractures stay open, the less reliably anything behaves — objects repeat, spaces fold, and events start arriving before their causes.
Reads patterns nobody asked him to read. Reaches for the wrong tool and is somehow right anyway. Would very much like to go back to being unimportant.
Paid to make impossible things look ordinary, and very good at it — right up until the sky opened. Knows more than she is cleared to say.
Three things Calder should have left sealed. In-world artifacts from the game's fiction — screenshots replace them once there are scenes worth showing.
Recommendation: seal, archive, forget. Two of those three were followed. The prior survey team is listed as unavailable for follow-up questions, which is doing a great deal of work in one sentence.
Recovered corrupted. Speaker A and Speaker B share a voiceprint, the timestamps disagree with each other, and the argument appears to be about something that has not happened yet.
Salt Flats, Sector 12. Officially non-existent per Directive 9. The approach road is unmaintained, which is an odd amount of infrastructure for a place with no official existence.
The demo covers the tutorial puzzle, Calder's apartment and the streets around it, reconstructing the anomaly packet, and getting hold of the gear and transport to reach the Salt Flats. It ends the moment the sky fractures for the first time.
Build notes and reveals go out in the devlog first, and the Steam page follows when there is something worth wishlisting. Press and creators can request assets any time.
Notes from every part of the studio — game builds, tooling, print runs. Published as the work happens, not after it has been polished into a press release.
Between our own titles we take on a small number of outside engagements. The same team, the same standard — no bench, no handoff to someone you have not met.
Full-cycle production — prototypes, vertical slices and shipped titles. We build our own games, and we build alongside studios that need senior hands rather than headcount.
Tools, pipelines and platform work beyond the game itself. Software that holds up in production and does not need us standing behind it to keep running.
Agents that act on real systems — internal APIs, records, ticketing — with the permissions, guardrails and audit trail you can hand to a security review.
Prototypes, props, collector pieces and short runs. Modelled, printed and finished in house, from a single part to a small batch.
Original score, ambience and sound design written for the scene rather than licensed to fit it. Composition and implementation handled in the same pass.
The layer between art and engine: shaders, rigs, look development and the tooling that keeps a small art team moving at the pace of a large one.
The people who design it are the people who ship it.
You work with the engineers doing the work, not an account manager relaying messages. Small team, direct line, senior hands on every task.
We take a limited number of engagements at a time because our own titles are always in production. That is a constraint, and it is also the reason the work is good — we only say yes to things we can do properly.
Send a short brief and we will come back with a scoped approach — or an honest no. Replies within two business days.
Independent, based in Irvine, California. We make original titles and the engineering that makes them possible — and we take on a small amount of outside work to keep the lights on and the ownership ours.
Dark Matt3r Studios started in Irvine, California to make one game properly. Building it meant building the pipeline underneath it — asset handling, automation, systems that could keep a small team moving at the pace of a large one.
Small team, no handoffs between strangers. The people who design a system build it and ship it. Everything is authored by someone who cares whether it is good.
A studio that funds its own titles and owns its pipeline end to end. Games are the reason the studio exists. Engineering is the discipline that keeps it independent.
Every scene is authored, not assembled.
Our worlds are drawn, written and scored by the people whose names are on them. A small team means fewer hands and no committees, and it means every room you walk into was placed there by someone who cared where it went. Nothing in our games is filler, because there is nobody here to hide behind.
We hire when a project needs a person, not before.
Openings are listed the moment they exist, and there is never an evergreen posting standing in for one. The careers page carries whatever is currently open, the disciplines we staff up in, and how to get on file for the next round.
VIEW OPEN ROLESTwo original titles in production, and a devlog that covers how they get built.
Small team, no filler hires. When a title needs a discipline we do not have, the role goes up here — and comes down the day it is filled.
We would rather say that plainly than collect applications against a role that does not exist yet. Fractured Skies is being built by the people already here, and the next hire happens when a specific piece of work needs a specific pair of hands.
Open applications are read, kept and revisited — see below.
Not a wishlist — these are the four areas a Dark Matt3r project actually needs hands in, and the ones worth sending work against.
The person who designs a system builds it and ships it. No handoffs to strangers, no specs thrown over a wall, and your name is on what you made.
Small enough that everyone knows what everyone else is working on, and small enough that one wrong hire is felt immediately. We move deliberately on both counts.
We build agentic systems for clients and use automation in our own pipeline. No generative art, audio or writing ships in our games. If that line matters to you, it matters to us too.
Send work, not a cover letter.
Three or four things you are proud of and a sentence on what you did on each. No portfolio site required, no formatting rules, and no need to explain a gap in a timeline. If your work fits something we are planning, you will hear from us before the role is ever public.
One inbox, read by the people doing the work. Engineering and partnership inquiries get a reply within two business days.
Assets on request, no form to fill in.
The downloadable kit goes up when Fractured Skies has art we are happy to put in front of people. Until then, email us and we will send what you need the same week — logos, key art, screenshots, studio background and fact sheet.
REQUEST THE PRESS KIT