Why XenneX
XenneX is a small independent software studio in New Orleans. We build our own products, and we build software for clients. Here's what that means and why we work the way we do.
I've told the long version of this story before, in Twelve Years of XenneX and in Why I Build Many Things Instead of One Thing. This is the short version: what XenneX is today, and why it works the way it does.
What XenneX Is
XenneX is an independent software studio in New Orleans. I started it in 2014 while I was finishing my Computer Science degree at LSU, and it's stayed small on purpose ever since.
The studio does two things. We build our own products, and we build software for clients. Those two sides feed each other. Everything I learn shipping and maintaining my own apps shows up in client work, and client work keeps me honest about how real businesses actually use software.
The Products
Over the years that's meant a lot of different things: an arcade game that's still on Google Play a decade later, a party game that crossed 100,000 downloads, Redinfinite for browsing Reddit, a deal aggregator, and more. Lately the focus has shifted toward LLM-powered tools, AI workflows, and the cloud infrastructure it takes to run them in production.
What ties them together isn't a category. It's an approach: build something useful, keep it simple, and keep it running. A lot of what I've shipped is still running years later, and that says more about the studio than any single product does.
How We Work With Clients
Client work at XenneX runs on a few commitments that don't change from project to project.
You own it from day one. Everything we write is yours. No license fees, no platform you're locked into.
It runs in your accounts. We deploy to your cloud, so your data never has to touch our servers.
No magic. No proprietary frameworks or clever tooling that only we understand. Any competent engineer should be able to read and extend what we build.
Support if you want it, never required. Ongoing help is there if it's useful. If you'd rather take it from here, you get a clean handoff.
Why Stay Small
The obvious path for a studio like this is to grow: hire, add layers, take on more at once. I've thought about it, and I keep choosing not to. Staying small means the person you talk to is the person building your software. It means every product I ship is one I actually use and maintain. And it means decisions get made by someone who's accountable for the result, not passed through a chain of handoffs.
That's not the right model for every company. It's the right one for this one.
The Bottom Line
XenneX exists to build software that's useful, honest, and built to last, for my own products and for the people who hire us. If that sounds like what you need, I'd like to hear what you're working on.