How we think
What guides
the work we do.
We have views on what makes retro revival work good, and what makes it hollow. This page is our attempt to explain those views plainly — not as a mission statement, but as a working set of beliefs.
← Back to HomeOur Foundation
Where this all starts.
Neon Anvil came out of a simple observation: most retro arcade revival work gets done by people who understand game development but don't particularly understand what made the original worth reviving. They approach it technically. They deliver something functional. But it doesn't feel right.
That feeling — the thing that's missing — is hard to name but easy to recognize. It's the difference between a rebuild and a revival. We started with the conviction that the feeling is worth protecting, and built everything else around that.
Philosophy
What we believe about transformation.
Old things have value as old things
There's a pressure in revival work to modernize — to make something feel current. We resist that when it conflicts with what the original was. A game from 1984 is interesting partly because it's from 1984. The constraints are part of the content.
Transformation should be earned
When something changes in the course of our work, it changes for a reason we can explain. Not because it was easier, or because a modern tool suggested it, but because we understood the original well enough to know what needed to shift and why.
The creator's voice is not ours to replace
We work on someone else's thing. Our job is to help them realize their vision more clearly — not to substitute our aesthetic for theirs. This shapes every decision we make about what to change and what to leave alone.
Core Beliefs
The things we keep coming back to.
We tell you what we think will work and what we're uncertain about. We don't overstate our confidence in outcomes. If something is likely to be difficult, we say so before we start rather than after we're stuck.
Good revival work usually can't be rushed without losing something. We'd rather give you a realistic timeline than a fast one that turns into a longer one anyway. This isn't reluctance — it's how we protect the quality of what you get.
Constraints aren't limitations to work around — they're often where the interesting decisions live. The best arcade games were made within strict technical constraints, and the best revival work understands those constraints as a design language, not a set of problems.
We keep our services narrowly defined because narrow, well-executed work is more useful than broad, uneven work. Knowing what we won't do makes us better at what we will. Each service has a clear edge, and we stay inside it.
Nostalgia is real and legitimate — but it's not enough on its own to make revival work good. Something that works only as a memory trigger isn't the same as something that works as a game. We aim for the second kind, using the first as a guide.
We take projects seriously because the people who bring them to us take them seriously. Someone's half-remembered favorite mechanic or long-dormant pixel project matters to them, and that means it matters to us while we're working on it.
In Practice
How beliefs become decisions.
We ask before we act
The first conversation is always about understanding what you have and what you want to preserve. We don't start applying solutions until we understand the problem well enough to know what kind of solution it calls for.
We explain our reasoning
When we make a change, we say why. You should understand the logic behind every decision well enough to push back on it if it doesn't sit right. Our job is to serve your project, and that requires transparency.
We hold to a standard before handoff
We don't deliver something because the deadline arrived. We deliver it because it meets the bar we set at the start. If something needs more time, we say so — and we'd rather have that conversation than hand over something half-done.
We stay within the brief
If we notice something outside the scope that we think is worth addressing, we'll mention it — but we won't change it without your say-so. Scope creep benefits nobody, and we've seen enough of it to be careful about keeping things contained.
We keep the vocabulary consistent
Whatever language or terminology you use for your project, we use it too. This sounds small but it matters — it keeps communication clear and makes sure we're all actually talking about the same thing throughout the work.
We leave things in a state you can continue from
Everything we produce — code, guidance, copy — is made to be understandable and extensible by you. The project belongs to you after we're done, and it should be in a state that reflects that.
People First
Every project is someone's thing.
The people who come to us with revival projects aren't always professional developers. Sometimes they're designers, hobbyists, or people who made something years ago and want to bring it back. We don't treat those projects as less serious than commercial ones — if anything, personal projects often carry more weight.
We try to match the pace and style of communication to what suits you. Some people want detailed updates throughout. Some want to be left alone until there's something to review. Both are fine. The point is that the collaboration works for the person we're working with, not just for us.
Evolving Carefully
How we think about change.
We don't resist change for its own sake. New tools, new techniques, new ways of presenting retro work — these are worth paying attention to. But we evaluate them against a simple question: does this serve the project, or does it serve a preference for novelty?
When we adopt something new into our process, it's because it genuinely improves what we can offer — not because it's available or fashionable. This makes us slower to update than some, and we're comfortable with that. Steadiness is part of what we offer.
Integrity
What we mean by being straight with you.
We say when we're unsure
If a project has elements we haven't handled before, we name that upfront. Confidence isn't the same as competence, and we'd rather set accurate expectations than impressive ones.
We tell you when something won't work
If a direction you're considering is likely to produce a result you won't be happy with, we'll say so. This can be an uncomfortable conversation, but it saves time and money and leads to better outcomes.
We own our mistakes
When something we produce needs to be redone because we got it wrong, we redo it. We don't apportion blame or find reasons why the brief was unclear. We fix it.
Working Together
Revival is a shared endeavor.
The retro arcade scene is small, connected, and largely driven by genuine affection for the medium. We're part of that community, not separate from it. When we work on a project, we're contributing to something that has a broader context — the ongoing effort to keep these games and ideas alive and accessible.
We also believe that working collaboratively with creators produces better results than working for them. You know things about your project that we can't know without your involvement. The best outcomes happen when that knowledge flows freely throughout the process.
The Long View
Building things that last.
The work we do is meant to hold up. A restored loop should still feel right in two years. Art guidance should produce a visual language you can extend. A showcase brief should represent the game in a way that doesn't age badly the moment the game gets updated.
This shapes how we approach every deliverable. We think about whether it will still make sense after the conversation that produced it is over — whether the rationale is embedded in the work itself, not just in our heads.
For You
What this means when you work with us.
You don't need to justify caring about the feel of the original. We already understand why that matters.
You'll know what's happening throughout. We communicate clearly and don't go quiet when things get complicated.
The project remains yours. We have no interest in credit, ownership, or creative authority over what you've made.
You get honest assessments, not flattery. If something you're planning is likely to cause problems, we'll say so with enough time to adjust.
The work you receive will be in a state you can continue from — not a black box that only makes sense if we remain involved.
We're a small operation with limited capacity, which means the projects we take on get real attention. Not managed attention. Real attention.
If this sounds right
We'd be glad to hear about your project.
If the way we think about revival work resonates with what you're looking for, reach out and tell us what you have. There's no commitment involved in a first conversation.
Start a conversation