Our Approach
Most software companies sell what they already built. We build what fits your business — and stays fitting as you grow.
The only technology investment that holds its value is one you own. Not rent. Not subscribe to. Own. Your data, your logic, your infrastructure, and the ability to extend it without asking a vendor for permission.
Four things we don’t negotiate on.
The Multi-Service Principle
A business doesn't interact with its data in one way. A planner needs a strategic view. A field worker needs a task list. A manager needs margins. A sales team needs relationship history. These are completely different interactions with the same underlying data.
The multi-service architecture gives each group its own application, all connected to a single data layer. When a new need comes up, you don't replace the system. You add to it. What's already working stays working.
Data Ownership
When your data lives in a system you don't control, you're exposed to risks that add up over time: regulatory changes, API modifications, pricing increases, and export limitations. You're building your business on foundations you don't own.
We build systems where the data stays in your infrastructure, in standard formats, accessible through documented interfaces. If you ever want to move on, you take everything with you. That's not a risk — it's the deal.
Zero Trust by Design
Zero trust — the principle that every component, user, and service must verify itself on every request — isn't just a security framework. It's an architectural discipline that produces better software.
Each application runs as a separate service with its own scoped access. If one is compromised, the others are not. VPN mesh networks mean your systems are only reachable on networks you have authorized. Nobody gets in through the open internet, including us.
The Long View
We don't build for what's trending. We build for what will still be true in five years. Databases will still be relational. Your data will still need to be yours. Applications will still need to match specific use cases. And security will still have to assume something can go wrong.
The system running your business five years from now should be the same one we start building today. Extended, not replaced.
What changes when the plan comes before the code.
Most teams write code first and ask questions later. We do the opposite. Here is what that actually looks like in practice.
How Albus Started
At 16, Gabriel coded a CRM for a non-profit. 80 users. 7 divisions. 457+ families served. Six years later we'll treat your business with the same care.
Then came two years in the cybersecurity industry. Gabriel contacted over 400 cybersecurity companies in the Netherlands, met with advisors across M&A, finance, and security, and learned how the industry worked from the inside.
What he kept seeing was the same pattern: data locked in silos, business logic rented from vendors, critical operations dependent on platforms that could change terms, raise prices, or disappear overnight. The companies that were most resilient owned their infrastructure. The most vulnerable had optimized for convenience.
The name comes from Albus Corvus — Latin for white raven, a rare and favorable exception to the norm.
If this thinking matches yours, we should talk.
The work we do starts with a conversation. If it’s not a fit, we’ll say so.