Check out our latest blogs and stay up to date with the latest online developments. You will find useful tips, updates on our organisation, and go deeper into technology. From Scrum to Craft CMS and from Laravel to Vue.js...
Right now, there’s probably software being built in your company without IT knowing about it. Not by a department secretly buying a system, but by a marketer who builds a customer portal in an afternoon with a few AI prompts, or a controller who creates a calculation tool that’s used by three teams within a week. That’s vibe coding: you describe what you want in plain language, the AI writes the code, and you barely look at what’s under the hood. The promise is faster experimentation without waiting for a packed IT backlog, but every app created out of sight is shadow IT that no one manages, patches, or has checked for security.
The question isn’t whether you can stop this. You can’t, and a ban won’t solve anything. The real question is whether you realize what you’re taking on when you build this kind of software yourself, and when you’re better off with a company that develops professional software.
You have backups. Access management with MFA (multi-factor authentication). Agreements with your hosting provider. Someone who calls if something goes wrong. Ask the team, and the answer is: yes, it’s all arranged. Then a client or regulator asks if you can prove it. When was that recovery procedure last tested? Who owns that process? Where is the agreement with that supplier documented? Everything exists, but it’s scattered across four people, three folders, and a few conversations that were never written down.
That difference—between having things in place and being able to prove it—is what the Cybersecurity Act is about. In this blog, we explain exactly what the law requires, why evidence is the real bottleneck, and what happens if you’re not directly subject to the law but supply to someone who is.
API stands for Application Programming Interface. An API integration is a digital connection that allows two software systems to automatically exchange data, without anyone having to retype anything. You can think of it as a fixed, agreed-upon gateway through which systems send information and commands to each other.
More and more companies work with separate software packages: an accounting program, a CRM, a webshop, an inventory system. If these don't communicate, you end up entering the same data in multiple places. An API integration solves that. In this blog, we explain exactly what an API integration is, how it works, what the benefits are, and when you should consider having a custom API integration built.