Tobias Krenn

Our developers are highly paid specialists. Their job is to build great software, design architectures, and solve customer problems. What they should not  be doing is spending half their day restarting servers, manually setting up cron jobs, or monitoring services. In many companies—ours included, in the past—the line between "Development" and "Operations" is blurry. The result: Product development stalls because the best people are tied up with server maintenance. The Shift to Smarter Server...

Running an established business teaches you one thing quickly: IT infrastructure often grows faster than the admin team. What started with a single server has grown into a complex landscape of various VPS (Virtual Private Servers) for staging, production, databases, and backups. In the past, every new server meant more manual overhead. Managing SSH keys, applying updates manually, checking log files—tasks that are crucial but consume enormous amounts of time. Time that was missing for...

"Can you quickly export this dataset?" or "Can we update the status of Customer X in the database?" Every developer knows these questions. And every Project Manager knows how much these "small requests" can disrupt a workflow. In our company, we had vast amounts of valuable data that was practically locked in a silo—accessible only to those who spoke fluent SQL. We are not a small startup where everyone does everything. We have specialized teams. It simply makes no sense for a Marketing...