Stefan Steuer
CEO
About us
Built from partner feedback, not designed on a drawing board.
What octoja can do was told to us by IT service providers who work with it every day. Every major capability goes back to concrete feedback from the partner network — not to a market analysis.
100+
checks out of the box, with no add-on module
4
languages in the interface and in notifications
3
operating systems with one agent
1
dedicated instance per customer
Why octoja exists
We listened before we built.
At the outset there was no product concept, but a question to experienced IT service providers: what would an RMM need to do to genuinely hold up day to day? The answers were remarkably consistent — a system that brings monitoring, remote support, patching and documentation together rather than spreading them across four tools with four logins.
Those conversations produced capabilities you would not design on a drawing board: deployment rings that only promote once a success rate is met. Service hours per alert channel, so that the on-call engineer is reached at night. A restart the user is allowed to defer.
We continue to develop along the same lines: whatever slows partners down day to day goes onto the roadmap — publicly visible and open to comment.
What we stand for
Four decisions anchored in the product
Not mission statements, but commitments you can find in the code.
01
One system rather than a toolbox
Monitoring, patching, software deployment, remote support, inventory and reporting all draw on the same device estate, the same rules and the same permissions. None of it was bought in and set down alongside.
02
Everything is a few clicks away
A command line spanning the whole interface finds customers, devices and users and runs actions directly — open a terminal, take over the screen, trigger an inventory scan, wake a device. Without clicking through menus first.
03
Open rather than walled in
The REST interface is fully documented and permanently available. Anyone who wants to extract their data or build their own automation should be able to do so without asking.
04
Evidence emerges from operations
Access, changes and approvals are logged because that is how the architecture works — not because somebody remembered to switch it on.
How we work
Commitments you can hold us to
Development in Germany, interface and notifications in four languages
One price per device, with every capability included
Sales through certified distributors rather than direct business
A public roadmap and an open feedback forum
A status page showing the real operational state
The team
The Team
Experienced IT professionals with a passion for great software.
Tom Kempin
CTO
Erdinc Akay
COO
Daniel Häfele
Chief Architect
Andreas Eichwald
Developer
Let us talk about your estate
A conversation in which we tell you honestly whether octoja suits your environment — and where it does not.