Cloud & Infrastructure
We design, build, secure and operate infrastructure across your own hardware, Microsoft 365 and cloud. The point is not modern technology in itself, but making change a non-event.
Contact usOperations without drama
Infrastructure is a craft with measurable standards
An environment that exists only as configuration somebody clicked together cannot be recreated, audited or handed over. We describe infrastructure as code because it makes changes reviewable, environments identical and knowledge independent of individuals. That is the difference between operations and luck.
We come from the hosting industry, where uptime is the product and a recovery time is a contractual obligation, not an intention. That background shapes the work: monitoring that sees the problem before users do, backup proven by restoring it, and deployments predictable enough to be boring.
An architecture is also an economic model. Fixed and variable costs must be visible, load scenarios calculated, and the exit cost known before the agreement is signed. Vendor dependency is not a problem in itself. Uninformed vendor dependency is.
Where the field is moving
The cloud calculation has grown up
The debate is no longer for or against cloud. Mature infrastructure management calculates per workload: what does this task cost to run here, what does it cost there, and what does the number look like at double the load and in three years. Some answers point to cloud, some point home again, and both can be right.
The major providers have removed or reduced the fees for moving data out, partly under EU pressure. That makes exit cheaper, but only for those who designed so that exit is possible. An architecture woven into one provider's proprietary services does not move just because a fee is zero.
We put the cost picture on the table before the agreement is signed: fixed and variable costs, load scenarios, and the price of changing your mind. That number often changes the decision, which is precisely why it is rarely in the proposal.
Sovereignty and NIS2 have moved into the architecture
Network and information security requirements are no longer a statement of intent. NIS2 is national law, supervision has begun, and responsibility sits with management personally. At the same time, more customers and authorities ask where data sits and who could ultimately demand access to it.
That turns architecture choices into compliance items and vice versa. Segmentation, central logging, controlled administrative access and documented recovery times are no longer optional extras for most organisations. They are things you must be able to show.
The good news is that the requirements essentially describe sound workmanship. An infrastructure described as code, logged centrally and proven by restoring it satisfies most of the paperwork as a by-product. We build the substance first and let the documentation follow.
Platform work is replacing ticket queues
In many organisations infrastructure is still a queue: you file a ticket, wait, and receive an environment that resembles the previous one, but not quite. That model loses to one where the common needs are automated as self-service, and a new environment is a call, not a negotiation.
The measure of good operations has changed accordingly. The interesting number is not the count of servers, but how long it takes from a change being decided to being in production, how often it fails, and how quickly service can be restored, measured rather than estimated.
Automation is not a goal in itself. The goal is that change becomes a non-event, so attention can go to what the infrastructure carries instead of the infrastructure itself.
Four steps, from starting point to operations
An architecture is also an economic model. We price the number that is rarely in the proposal: what it costs to move away again.
Niels Reinau
Niels founded iCEO after a career spent at IBM, at eBay, and running platforms at DanDomain and Zitcom, two of the largest hosting companies in Denmark. Zitcom is today team.blue Denmark, and DanDomain is one of the brands it still trades under. He works alongside consultants who have been in this industry for twenty-five years. You get that experience directly, not a partner at the pitch and a graduate on the work.