Transparency
You can see what we are working on and where the project stands at any time. No black box, no surprises on the invoice.

We build software, advise on technology and run what we build, from Kevelaer, for companies across Germany.
Thirty minutes to clarify the goal, the scope and a realistic effort.
We listen, estimate honestly, and say so when an approach does not make sense.
You can see what we are working on and where the project stands at any time. No black box, no surprises on the invoice.
Short paths, small team, no three layers of sign-off. You talk to the people who write the code.
It does not stop at launch. We run, update and extend what we built.
Fast and maintainable: we build interfaces that can still be extended in two years.
A young company with clear commitments.
Artim Industries grew out of a group of developers joining forces. Today we look after clients from the first advice to running systems.
Concrete commitments instead of marketing promises. Hold us to them.
Prices are guide figures. We agree the exact scope in the intro call.
A website or small application with a clear scope. Concept, build, handover.
A web app with user management, a database and interfaces to your systems.
Custom software including cloud operations, monitoring and ongoing development.
Larger undertakings, several systems, or a team on loan. We put the package together with you.
The row pauses on hover so you can read at your own pace.
Methacore finally brings our club administration together in one place. Training groups, dates and attendance are considerably easier to manage, and members can sign up for or withdraw from events themselves. In day-to-day club work that saves us a lot of back and forth.
The course system is particularly practical for us because courses, dates and registrations are brought together clearly. The attendance overview helps too, because you no longer have to collect several lists. In a few places the interface could be a little more intuitive for new users.
Managing SSH access centrally makes a big difference for our team. Instead of maintaining permissions and server access in several places, we can control and trace access from one point. The role-based policies and the audit logging in particular give us far better oversight.
ShellBase takes a lot of complexity out of day-to-day server administration. Servers and access rights can be organised centrally, and the session logs keep what happened on the systems traceable. With several team members that is an enormous relief.
What convinced me most is the combination of central SSH access and a clean audit trail. You can define who may reach which systems and, at the same time, trace what happens inside a session. For infrastructure teams that is considerably clearer than scattered SSH keys.
We wanted to centralise our SSH access more while keeping control over permissions. ShellBase joins exactly those two things. The policies can be defined cleanly and the sessions monitored centrally.
Being able to use relays for different network environments is particularly interesting for us. It lets us connect hybrid environments in a more structured way, without organising SSH access for every system separately.
ShellBase brings considerably more structure to our SSH administration. The central sessions and audit logs are very helpful. For smaller teams the feature set is a little extensive at first, though, and you need a short run-in period.
The technical capabilities are extensive, but fitting it into our existing processes was not quite as straightforward as expected. With policies and roles in particular you first have to engage with the system in depth.
Fundamentally a good solution for central SSH administration. We particularly like the audit logs and the access controls. For simple setups, though, ShellBase is at times more than we actually need.
Managing our server access centrally has tidied up our previous processes considerably. What helps most is that permissions are no longer organised through individual keys alone, and that we have a traceable history of the sessions at the same time.
What convinced us is the combination of access control, monitoring and auditing. We can define centrally which user may reach which server, and still have a traceable overview of the sessions afterwards.
We had several processes that ran on spreadsheets and manual transfers. Artim Industries helped us digitalise them and connect the systems involved through interfaces. What was particularly good is that not everything was digitalised for its own sake — we looked together at what actually pays off.
For us the interesting part was having a custom web app built. Instead of bending an existing product to fit how we work, we now have a solution that mirrors our actual processes and runs in the browser on different devices. Working together was straightforward and technically very clean.
We wanted to put our infrastructure on a more professional footing and to have a reliable contact for day-to-day operations at the same time. Artim Industries built and documented servers and deployment in a structured way. The monitoring in particular helps us, because we no longer notice problems only when a client phones.
Some of our internal processes still consisted of manual steps that cost time every day. Process automation let us drop several of those tasks entirely. What we valued most is that it was examined beforehand which automations genuinely make sense and where a manual process is actually better left alone.
We brought Artim Industries in for the technical architecture and the further development of our application. The independent assessment before implementation was particularly helpful. Nobody tried to sell us as much as possible; instead they said openly which option makes sense in the long run. That advice ended up saving us a lot of development effort.
Being able to use relays for different network environments is particularly interesting for us. It lets us connect hybrid environments in a more structured way, without organising SSH access for every system separately.
ShellBase brings considerably more structure to our SSH administration. The central sessions and audit logs are very helpful. For smaller teams the feature set is a little extensive at first, though, and you need a short run-in period.
The technical capabilities are extensive, but fitting it into our existing processes was not quite as straightforward as expected. With policies and roles in particular you first have to engage with the system in depth.
Fundamentally a good solution for central SSH administration. We particularly like the audit logs and the access controls. For simple setups, though, ShellBase is at times more than we actually need.
Managing our server access centrally has tidied up our previous processes considerably. What helps most is that permissions are no longer organised through individual keys alone, and that we have a traceable history of the sessions at the same time.
What convinced us is the combination of access control, monitoring and auditing. We can define centrally which user may reach which server, and still have a traceable overview of the sessions afterwards.
We had several processes that ran on spreadsheets and manual transfers. Artim Industries helped us digitalise them and connect the systems involved through interfaces. What was particularly good is that not everything was digitalised for its own sake — we looked together at what actually pays off.
For us the interesting part was having a custom web app built. Instead of bending an existing product to fit how we work, we now have a solution that mirrors our actual processes and runs in the browser on different devices. Working together was straightforward and technically very clean.
We wanted to put our infrastructure on a more professional footing and to have a reliable contact for day-to-day operations at the same time. Artim Industries built and documented servers and deployment in a structured way. The monitoring in particular helps us, because we no longer notice problems only when a client phones.
Some of our internal processes still consisted of manual steps that cost time every day. Process automation let us drop several of those tasks entirely. What we valued most is that it was examined beforehand which automations genuinely make sense and where a manual process is actually better left alone.
We brought Artim Industries in for the technical architecture and the further development of our application. The independent assessment before implementation was particularly helpful. Nobody tried to sell us as much as possible; instead they said openly which option makes sense in the long run. That advice ended up saving us a lot of development effort.
Methacore finally brings our club administration together in one place. Training groups, dates and attendance are considerably easier to manage, and members can sign up for or withdraw from events themselves. In day-to-day club work that saves us a lot of back and forth.
The course system is particularly practical for us because courses, dates and registrations are brought together clearly. The attendance overview helps too, because you no longer have to collect several lists. In a few places the interface could be a little more intuitive for new users.
Managing SSH access centrally makes a big difference for our team. Instead of maintaining permissions and server access in several places, we can control and trace access from one point. The role-based policies and the audit logging in particular give us far better oversight.
ShellBase takes a lot of complexity out of day-to-day server administration. Servers and access rights can be organised centrally, and the session logs keep what happened on the systems traceable. With several team members that is an enormous relief.
What convinced me most is the combination of central SSH access and a clean audit trail. You can define who may reach which systems and, at the same time, trace what happens inside a session. For infrastructure teams that is considerably clearer than scattered SSH keys.
We wanted to centralise our SSH access more while keeping control over permissions. ShellBase joins exactly those two things. The policies can be defined cleanly and the sessions monitored centrally.
We had several processes that ran on spreadsheets and manual transfers. Artim Industries helped us digitalise them and connect the systems involved through interfaces. What was particularly good is that not everything was digitalised for its own sake — we looked together at what actually pays off.
For us the interesting part was having a custom web app built. Instead of bending an existing product to fit how we work, we now have a solution that mirrors our actual processes and runs in the browser on different devices. Working together was straightforward and technically very clean.
We wanted to put our infrastructure on a more professional footing and to have a reliable contact for day-to-day operations at the same time. Artim Industries built and documented servers and deployment in a structured way. The monitoring in particular helps us, because we no longer notice problems only when a client phones.
Some of our internal processes still consisted of manual steps that cost time every day. Process automation let us drop several of those tasks entirely. What we valued most is that it was examined beforehand which automations genuinely make sense and where a manual process is actually better left alone.
We brought Artim Industries in for the technical architecture and the further development of our application. The independent assessment before implementation was particularly helpful. Nobody tried to sell us as much as possible; instead they said openly which option makes sense in the long run. That advice ended up saving us a lot of development effort.
Methacore finally brings our club administration together in one place. Training groups, dates and attendance are considerably easier to manage, and members can sign up for or withdraw from events themselves. In day-to-day club work that saves us a lot of back and forth.
The course system is particularly practical for us because courses, dates and registrations are brought together clearly. The attendance overview helps too, because you no longer have to collect several lists. In a few places the interface could be a little more intuitive for new users.
Managing SSH access centrally makes a big difference for our team. Instead of maintaining permissions and server access in several places, we can control and trace access from one point. The role-based policies and the audit logging in particular give us far better oversight.
ShellBase takes a lot of complexity out of day-to-day server administration. Servers and access rights can be organised centrally, and the session logs keep what happened on the systems traceable. With several team members that is an enormous relief.
What convinced me most is the combination of central SSH access and a clean audit trail. You can define who may reach which systems and, at the same time, trace what happens inside a session. For infrastructure teams that is considerably clearer than scattered SSH keys.
We wanted to centralise our SSH access more while keeping control over permissions. ShellBase joins exactly those two things. The policies can be defined cleanly and the sessions monitored centrally.
Being able to use relays for different network environments is particularly interesting for us. It lets us connect hybrid environments in a more structured way, without organising SSH access for every system separately.
ShellBase brings considerably more structure to our SSH administration. The central sessions and audit logs are very helpful. For smaller teams the feature set is a little extensive at first, though, and you need a short run-in period.
The technical capabilities are extensive, but fitting it into our existing processes was not quite as straightforward as expected. With policies and roles in particular you first have to engage with the system in depth.
Fundamentally a good solution for central SSH administration. We particularly like the audit logs and the access controls. For simple setups, though, ShellBase is at times more than we actually need.
Managing our server access centrally has tidied up our previous processes considerably. What helps most is that permissions are no longer organised through individual keys alone, and that we have a traceable history of the sessions at the same time.
What convinced us is the combination of access control, monitoring and auditing. We can define centrally which user may reach which server, and still have a traceable overview of the sessions afterwards.