Unity / C# consultancy · Straylight Code Ltd
AI made your team faster. Everything downstream has to keep up.
Real engineers with 15+ years shipping on PlayStation, Xbox, PC, mobile and XR, and four years building with AI. Not another AI tool.
What we solve
How we solve it
Start here
We look at what you're running and hand back something you can act on without us.
Then build it
We build it with you, on your repo, and leave you able to extend it.
Every release
Someone senior reads what the automation flags, before it ships.
Why Straylight Code
The work
We started with our own Unity project: architected properly, handed to Claude, and documented as it broke. The writing covers the same ground: what these tools get wrong in Unity, and what to do about it.
A Unity lane defence game that held 60fps in the editor and managed 20 on a mid-range phone. Every cause was readable in the code, and nobody had opened the Profiler.
Read the teardown →The MCP and skills stack for Unity in September 2026, concretely: which servers and skills fix the context blind spot, which ones just add control, and why Unity deprecated its own MCP server in favour of a CLI.
Read the article →Research · Models
We track the tools studios are building with, because a plan's published price rarely tells you what it costs to use. The workings are published in full, and re-checked as prices move.
Every plan worth buying, ranked by capability per dollar, with the cheapest credible place to get each model and the free ones that come close.
FAQ
A fixed price rather than an hourly rate, agreed before any work starts. The figure comes out of a short scoping call, once we both know what the work is.
That's what the first engagement finds out. Usually: what you're paying for and whether it's the right thing, what the tools keep, and which changes are going out without anyone reading them.
Not necessarily. We'll always try and keep what you already have.
A tool does the work. What we build is yours, fits how you ship, and doesn't change when someone's pricing does.
That's how the build works. We do it with your engineers on your repo, so they can change it after we've gone.
That's the ongoing tier. The changes in each release get read before it ships, on whatever cycle you already release on. It doesn't need anything else first.
No. Which tools retain what, and what can't leave the building, is part of the assessment.
We use tools to assist with analysis, but the assessment is ours. The value is in engineering judgment, not automated scanning.
No. Unity runs a lot of training, simulation and visualisation work, and none of this is specific to games.
We specialise in Unity/C#. If you're on another engine, we can refer you to someone who knows it.
30 minutes. We'll ask about your setup, you'll get honest feedback, and we'll tell you whether we can help, and how.
[email protected] · replies within 1 business day