Open source
Built for the joy of it. Shared with the community.
MOJM builds its own apps and apps for others. Alongside that, we develop Autoreverse as a side project – and want to give something back to the community with open source code.
We are preparing the Autoreverse server for a complete, traceable release. There is no date yet.
Principles
Why we do it
We learn, we try things out, and we share what comes of it.
-
Self-hosting without insight is just a different kind of trust
If we say “run it yourself and the data is yours”, you have to be able to read what the software does with it. Otherwise we have only moved where the trust sits, not whether it is needed.
-
What runs on your hardware shouldn’t be taken away from you
A server in your home must not depend on us still being around in five years. Open source code is the only promise that still holds when we can no longer make it.
-
Bugs are found by those allowed to look
We are a small team. Outside eyes catch things forty of our own test runs miss – especially in software that runs on strangers’ home networks.
-
We have taken more than we have given
Our products stand on open software – databases, frameworks, libraries, typefaces. Giving some of that back isn’t a marketing decision, it’s a matter of decency.
Our side project
Autoreverse Server
A self-hosted server for audiobooks, music and subscribed podcasts. It runs as a single Node process against a PostgreSQL database, is managed through a German-language web interface and speaks the same API that native clients expect.
Exactly the kind of software where openness isn’t a gesture but a prerequisite: it runs on the home networks of people who don’t know us.
Will be opened
- The complete source code of the Autoreverse server – not a stripped-down community edition
- The database schema and migrations
- The JSON API clients use to talk to the server
- The deployment files we use to run it ourselves
Stays closed for now
- Racqt is a hosted service – its value lies in running it, not in the code
- Anything that touches credentials, keys or customer data
- We don’t rule out further releases, but we don’t promise them either
Status
Where things stand
The code exists
The server runs, is being tested and is the foundation of the app. What’s missing isn’t the software but everything around it: a licence, documentation for outsiders, a clean separation from everything that only concerns us.
We’ll name the licence at release
A licence you later withdraw isn’t a licence. So we only commit publicly once the decision really stands – and then it holds.
Tell us if you want to hear about it
We don’t have a mailing list and won’t build one. Just write to us – we’ll get back to you when the source code is online.
Get in touch