Open source, because understanding matters.
The code and documentation are there to explore, question, and improve. Each repository sets out its own licence and how to get started.
OMG SOFTWARE
Open source.
Clear boundaries.
A small team.
A shared commitment.
We’re a couple of people building open-source software with security at the centre. We care about what our software does, who can inspect it, and where its limits are.
BUILT TO BE UNDERSTOOD
Communications / Infrastructure / Community / AI evaluation
01 / THE ORGANISATION
A couple of people.
A shared conviction.
Software should be open to inspection.
Security should be part of the work.
OMG Software is a small organisation with a simple purpose: to produce secure, open-source software. We bring that commitment to communications, infrastructure, community software, and AI evaluation.
For us, that means asking difficult questions about trust, testing how systems fail, and explaining what is still unfinished. We want people to understand the software they choose to run.
Security, because trust needs care.
Security is an ongoing responsibility. We aim to make careful design choices, test assumptions, and be clear about the limits of each project.
OUR COMMITMENT
Build in the open.
Keep security at the centre.
02 / THE WORK
Two sides of Matrix.
One considered approach.
Meet our showcase projects: a homeserver
and a desktop client. Then explore our wider work
in monitoring, community software, and AI evaluation.
01 / COMMUNICATIONSBeta
SHOWCASE / MATRIX HOMESERVER
Merovingian
A homeserver with boundaries.
A Matrix homeserver in modern C++26. Built around process isolation, defensive configuration, and documented security boundaries.
For evaluation and testing. Not ready for production.
02 / COMMUNICATIONSEarly development
SHOWCASE / MATRIX DESKTOP CLIENT
Persephone
A considered approach to the client.
A Rust and Tauri desktop Matrix client in early development. Designed with explicit trust boundaries, with Merovingian as a primary integration target.
Early development. Not ready for real use.
Readiness notes
Only Windows is currently built and tested. No milestone has passed its acceptance gates, and no production security controls exist yet.
03 / INFRASTRUCTUREAlpha in progress
TheWatcher
Know what your systems are doing.
Server and endpoint monitoring with user-space agents, metrics collection, runtime configuration, and a web dashboard.
Readiness notes
Alpha is in progress. Beta and a production release are planned. Read the progress tracker and setup documentation for current limitations.
C++ · MonitoringProject overview
04 / COMMUNITYWorking application
Atomiser
Video hosting for your own community.
An invite-only video-hosting application with role-based access, passkeys, and queued video transcoding. Built with Python and FastAPI.
Readiness notes
A working application with local setup and deployment documentation. The README does not declare an alpha, beta, or stable stage. Review the current repository before deploying.
Python · FastAPIProject overview
05 / AI EVALUATIONResearch tooling
LLM Prompt
Injection Testing
Put the trust boundary to the test.
An evaluation harness for language models working with mixed-trust documentation. Explore retrieval errors, artifact laundering, and tool escalation.
Readiness notes
Usable as evaluation and research tooling. Benchmark results measure tested scenarios; they do not establish that a model is safe in every setting.
Python · EvaluationProject overview
Project status checked against public READMEs on 25 October 2026. Follow each repository for the latest details.
03 / HOW WE THINK
The details are
the point.
Security is a discipline, not a badge.
These are the principles we aim to build around.
Make boundaries explicit.
Define what is trusted, what is exposed, and what happens when something fails. Document the decisions behind the design.
Make behaviour testable.
Prefer reproducible builds, useful tests, and operational visibility. Test realistic failure modes alongside the expected path.
Say what is unfinished.
Clear status and honest limitations help people make better decisions. A prototype, a beta, and a release are different things.
04 / GET INVOLVED
Small team.
Room for more perspectives.
You do not need to write code to help.
A clear question, a useful bug report, or better
documentation can move a project forward.
Find a project that matters to you.
Start with the README and readiness notes. Merovingian and Persephone are our main showcase projects. Our other repositories cover monitoring, community video hosting, and AI evaluation.
Explore the projectsHelp us see what we missed.
Read the documentation, examine an assumption, or describe a problem you can reproduce. Check the repository’s security guidance before reporting a potential vulnerability.
Browse repositoriesMake one useful improvement.
A focused test, a documentation fix, or a small code change is a good place to begin. Check the project’s contribution guidance, open issues, and licence first.
Find us on GitHubLET’S BUILD SOMETHING USEFUL
Good software is
a shared effort.
We are a couple of people. The work is open, and thoughtful contributions are welcome. Explore a repository, follow a project, or help make it better.
Find your project on GitHub
Read the project’s README, issues, and
licence before contributing.