Most of what we do ends up inside someone else's closed codebase, but a real amount of it is public, and you can read it. We release our own tools under open-source licenses, and we push fixes and improvements back into the open-source projects our work depends on. If you want to know how we write code before you hire us, a lot of it is a git clone away.
Tools we have released
- Slughorn is our MIT-licensed GPU vector-text library, bringing Eric Lengyel's Slug algorithm to OpenGL, OpenSceneGraph, Vulkan, and any GPU-driven pipeline, together with its osgSlug integration for OpenSceneGraph. The source is on GitHub.
- aipython is a small MCP server for co-driving a live Python or IPython session with a human and an AI agent in the same interpreter, with a human-visible tmux backend and a structured Jupyter-kernel backend. The source is on GitHub.
- WrapStar is our body of techniques and tooling for wrapping any C or C++ cleanly for Python, the craft behind bindings that actually feel like Python rather than a thin, leaky shim.
What we contribute upstream
We do not just consume open source, we give back to it. We have contributed performance improvements to OpenSceneGraph, working directly with its creator Robert Osfield to make the engine measurably faster. Our fixes and improvements to osgEarth have been accepted into its public releases, through a long relationship with Pelican Mapping, its authors. And we work at the source level across the open graphics stack, including Mesa and the Linux driver layer, where a display has to be dependable from the silicon up.
Why we work this way
We do not sell an engine or a platform, so our incentives line up with the ecosystem rather than against it. When we fix something in a shared library, everyone downstream gets the fix, our clients included. Open source is also how we stay honest: the code is out there to be read, and it either holds up or it does not.
Find our code
Our public repositories live at github.com/AlphaPixel. For the wider set of tools, standards, and companies we build alongside, see our partners, friends, and open source page.
Who works on it
AlphaPixel is a US-owned small business, founded in 2004, with senior developers who have shipped open and closed-source graphics code for decades. DLA DD2345 / ITAR registered. We take closed-source defense work and open source alike, and we do not sell a product, so our advice is not a sales pitch for one.
Frequently asked questions
Does AlphaPixel release open-source software?
Yes. Most of our work ends up inside someone else's closed codebase, but a real amount of it is public. We release our own tools under open-source licenses and push fixes back into the projects our work depends on.
What open-source tools has AlphaPixel published?
Slughorn, our GPU vector-text library, along with its osgSlug integration for OpenSceneGraph; aipython, a small MCP server for co-driving a live Python session with a human and an AI agent; and WrapStar, our techniques and tooling for wrapping C and C++ cleanly for Python.
What license is Slughorn under?
Slughorn is MIT-licensed. It brings Eric Lengyel's Slug algorithm to OpenGL, OpenSceneGraph, Vulkan, and any GPU-driven pipeline.
Where can I find AlphaPixel's code?
Our public repositories live at github.com/AlphaPixel. If you want to know how we write code before you hire us, a lot of it is a git clone away.
Do you contribute to the open-source projects you use?
Yes. We have contributed performance improvements to OpenSceneGraph, working directly with its creator Robert Osfield, and our fixes to osgEarth have been accepted into its public releases through our relationship with Pelican Mapping. We also work at the source level across the Mesa and Linux driver layer.
Can I see how AlphaPixel writes code before hiring you?
Yes, and we encourage it. Because a meaningful part of our work is public on GitHub, you can read the code and judge whether it holds up before you ever sign a contract.
Why contribute upstream if you sell services?
We do not sell an engine or a platform, so our incentives line up with the ecosystem rather than against it. When we fix something in a shared library, everyone downstream gets the fix, our clients included.
Talk to us
Tell us what you’re building and where it’s stuck. We’ll tell you straight whether it’s something we can help with, and how we’d approach it.
Or see how we run consulting and software development engagements.
