You have no full-time cloud architect, and you don't need one all year round. But there comes a point where infrastructure decisions commit your company for the next five years. That is when we step in: for the length of an engagement, with deliverables your teams take over afterwards without us.
The cloud was never decided, it accumulated. A subscription opened for one project, a second for another, virtual machines created by hand on a Friday afternoon, access granted to people who left the company since.
None of this is serious on its own. The trouble is that the bill climbs without anyone knowing why, nobody can say who has access to what, and a serious outage gets fixed on instinct rather than by procedure. Then a client demands proof of compliance, and everything has to be reassembled by hand.
Putting this right does not call for a rebuild. It calls for someone who has seen the same situation several times before, who sets a framework, and who leaves you the means to hold it.
This is the framework we have applied for twelve years, from large organisations to smaller companies. There is nothing original about it: it simply has the merit of preventing anyone from building before understanding, or migrating before deciding.
An assessment run against a fixed grid, not by feel: what is running, what it costs, who can reach it, what breaks first. Gaps are ranked by severity, not by how easy they are to fix.
What you come away withTwo or three evolution scenarios, with their costs, their risks and what each will rule out later. You choose. We never present a single scenario: a single scenario is not a decision, it is a sale.
What you come away withThe target described as code, deployed in waves, tested at every stage. Then the part that makes the difference: your teams are left with the means to maintain it without calling us back every quarter.
What you come away withEach belongs to a phase, and each has a start, an end and a deliverable you keep. No open-ended billing, no scope creep.
We look at what you actually have, not what the documentation claims. Inventory, costs, access, security, breaking points.
The foundation everything else rests on: subscription hierarchy, network, identities, policies. Described as code, therefore reproducible.
Getting your environment ready to be audited: policies enforced, evidence generated automatically, Law 25 covered.
From ageing physical servers or a licensed hypervisor to the cloud, in waves, with a rollback possible at every step.
What happens the day the main server does not come back up. Backups we have actually restored, not merely scheduled.
A few days a month, on an ongoing basis. To arbitrate architecture decisions as they arise, without hiring a full-time role.
Indicative ranges, based on the scope of a 20 to 250-person company. The exact price is set after the first conversation, once the scope is agreed. An assessment carried out with you is credited against the engagement that follows.
Scope agreed, price agreed, deliverable agreed. Any overrun is on us, not on you.
For the six engagements aboveWe work with your tooling, your rituals and your constraints. Skills transfer happens through the work, not in a closing workshop.
For long-running projectsYou hand over a scope and a set of deliverables; we produce them remotely with validation checkpoints agreed in advance. Your teams stay on their operations.
When your teams are at capacityThe end clients of these engagements are not named: they were carried out under subcontracting agreements, and discretion is part of the job. The sectors and the substance, however, are accurate.
Inventory and decommissioning of end-of-life servers, Active Directory role consolidation, integration with VMware operational management, self-service orchestration of application services.
Technical and managerial lead of a specialist team, architecture design and migration of applications and virtual machines onto a hybrid cloud solution.
Infrastructure analysis against recommended best practice, consolidation architecture for solutions deployed across the group's sites, validation of the operational management matrix.
Transport zones and gateways, logical grouping of workloads, distributed firewall policy organised by category, full topology documentation.
Governance architecture based on policies, reusable blueprints and management groups; multi-region continuity, backup, recovery and an infrastructure evolution strategy.
Cloud architecture roadmaps, infrastructure design and implementation, operating system migration, technical referent for on-site deployment teams.
At a large firm, the senior who meets you is not the one who will do the work. Here it is the same person from the first call to delivery.
And above all: we do not only advise. CloudNorma and Travio are our own products, designed and shipped on the very foundation we propose to you. We apply to our own platforms what we sell you — and we bear the consequences when we get it wrong.
One point of honesty. If your need amounts to a day of configuration, say so: we will point you to an integrator rather than sell you an engagement. Our value starts where a decision commits you for years.
Compliance audit, target architecture, governance automation, or simply picking the right solution — write to us and we'll reply within 48 hours.