From the Cybersecurity Lab to Founding JITIS

The story of JITIS did not begin with a spontaneous business idea. It began with a technical question: How should IT systems be designed so that they do more than simply work—so that they also remain secure, understandable and manageable over the long term?

While studying Electrical and Information Engineering at OTH Regensburg, I worked in the university's cybersecurity lab. That experience made one point particularly clear: networking, systems, software and security cannot be treated as separate disciplines. A vulnerability is rarely isolated. What matters is the interaction between architecture, configuration, access controls, documentation and day-to-day operations.

This perspective still shapes my work today. I do not see security as a product added at the end of a project. It results from clear structures, deliberate technical decisions and systems that can still be understood and maintained after handover.

From Individual Components to a Complete System

My studies provided insight into embedded software, automation and hardware development. Networking increasingly became the connecting discipline: it plays a central role in how devices, applications, locations and people work together reliably.

A period of study in France further sharpened this focus. Working with different technical environments and approaches showed me that a good solution does not depend on individual products alone. It must fit the organisation, remain understandable and prove itself under real operating conditions.

This led to a principle that later became central to JITIS: IT infrastructure should be planned as a complete system. Networks, endpoints, servers, cloud services, identities, telephony, backups and physical security all affect one another. Replacing individual components without considering these relationships often moves problems instead of solving them.

Why This Led to JITIS

Conversations with businesses made it clear that small and medium-sized companies in particular need a pragmatic approach to modern IT. They do not need unnecessary complexity or product lists without context. They need a reliable foundation for their daily work, clear responsibilities and an understandable assessment of benefits, effort and risk.

JITIS was founded to combine technical depth with personal responsibility. Projects should not fail because contacts keep changing or handovers remain unclear. I therefore support projects from the initial assessment through planning and implementation to documentation and ongoing operations.

This does not mean rebuilding every existing environment from scratch. It is often more effective to understand the current systems, prioritise risks and improve the infrastructure step by step. Being open to different vendors and open-source solutions is part of this approach—as is deciding against an interesting technology when it would create unnecessary operational complexity.

What Remains from the Lab

Above all, the work in the cybersecurity lab shaped an attitude: test assumptions, understand relationships and make technical decisions traceable. That same attitude is part of how JITIS works today.

Before making a recommendation, we clarify the company's objective and the risks that are actually relevant. Before implementation, we define an architecture that makes responsibilities and dependencies visible. And a completed project includes clear documentation and a handover that keeps the environment manageable in everyday operations.

JITIS therefore treats networking, IT infrastructure, cloud, communications and security not as isolated services, but as parts of a shared technical foundation.

The Next Step

What began as a technical focus at OTH Regensburg has developed into an IT company that personally supports businesses in Regensburg, the Upper Palatinate and beyond. The standard remains the same: understand technology carefully, plan it clearly and implement it in a way that continues to fit the organisation over time.

If you want to reassess your existing IT, modernise a location or evaluate security and operational risks in a structured way, the collaboration starts with an open conversation about your objective, your current situation and the next sensible step.