The vendor stack
One environment instead of separate contracts for storage, mail, chat, meetings and AI, each with its own terms and its own data flows.
Solutions · cloud&more
Canadian-controlled cloud hosting, on hardware we own
cloud&more is the cloud operator of the oceans Group. To us, sovereign cloud means the operator owns the machines and answers three questions in writing. Who owns it? Whose law can reach it? Can you leave? Hugo runs on hardware cloud&more owns, at FibreCentre in Moncton, on our own network. Files, mail, chat, video, voice and AI live in one environment instead of six vendor contracts.
The problem: renting is not owning
Residency tells you where the building stands. It does not tell you who can be compelled to open it. That is why data residency and data sovereignty are not the same question, and why answering the first does not settle the second. Sovereignty is three questions: Who owns it? Whose law can reach it? Can you leave? Location alone scores zero.
The second problem is assembly. Most organisations end up with a file service from one vendor, mail from another, chat from a third, video from a fourth, and an AI tool bolted on last. Every seam is a contract, an integration and a place where data crosses a border nobody wrote down.
How it works
cloud&more operates the infrastructure; the Hugo product suite is what your people actually work in.
Hardware we own
Not rented capacity in someone else's cloud. The machines belong to cloud&more and run at FibreCentre, an independent data centre in Moncton.
One jurisdiction, stated plainly
Each client contracts with a company in their own jurisdiction, and the data stays there. Canada: cloud&more Inc., on hardware we own, under Canadian control. EU and EEA: oceans GmbH, under German and EU law, on dedicated servers in Germany. United States: cloud&more Inc. today, on dedicated servers in the US. Who owns the company and the hardware, whose law can reach it and what leaving costs: in writing, in every offer.
One environment, not six vendors
Files, mail, chat, video calls, voice and the AI layer sit together. There is no integration project between them, because they were never separate.
Migration at your pace
Workloads move when it makes sense, one at a time. You get the exit cost and the exit time from us in writing.
What it replaces
This is the route for organisations that have decided the dependency itself is the problem, not any one provider's terms.
The hiring detour
Companies that want to use AI often start by looking for infrastructure engineers. With the foundation already running, your own people build the thing they wanted in the first place.
The jurisdiction argument
Instead of a debate about regions, you get three answers in writing: who owns it, whose law can reach it, and what leaving costs.
Who this is for
Canadian organisations that want a Canadian operator
Where ownership and jurisdiction are part of the requirement, not a nice-to-have discovered during procurement.
European organisations under GDPR
Where a transfer impact assessment has to be defensible and "the data centre is in the EU" has stopped being a sufficient answer.
Organisations that want AI without rebuilding themselves
Where the goal is to run AI projects on data you control, without first becoming an infrastructure company.
Frequently asked questions
- What is the difference between data residency and data sovereignty?
- Residency is where the data physically sits. Sovereignty is whose law and whose access govern it. A provider can offer residency in Canada or Germany and still be subject to another country's orders. The building answers one question, the operator answers the other.
- Do you own the hardware or rent it?
- In Canada we own it: the machines belong to cloud&more and run at FibreCentre in Moncton. In Germany and the United States the servers are bare metal dedicated to us by a data centre partner. Owning the Canadian hardware is what lets us make a statement about jurisdiction rather than about a region label.
- What availability can we expect?
- Availability is a target in our General Terms, not a promise on a web page. A specific availability is owed only where a separate service level agreement says so, with the figure, the measuring window and the method. We would rather write that down than imply it.
- Can we migrate gradually?
- Yes, and that is the usual case. Most organisations move one workload at a time, the way Schleswig-Holstein did: documents first, then mail, then files.
- Is AI part of this or a separate product?
- Part of it. The AI layer runs in the same environment as your files, mail and chat, on local models on our hardware, which makes it usable on real company data without exporting that data to a third party. privatemode.ai, processed in Europe, is used only if you switch it on.
- What happens to our data if we leave?
- You take it with you. Sovereignty that only works while you stay is not sovereignty. Export paths are part of the setup, and you get the exit cost and the exit time from us in writing.
- How is this different from reselling someone else's capacity?
- A reseller sells you someone else’s capacity with a local invoice. The underlying operator, and therefore the jurisdiction, does not change. We own the machines, which is what makes the answer about applicable law different.
- What exactly is Hugo?
- Hugo is the product suite your people work in: files, mail, chat, video, voice and the AI layer, running on the cloud&more infrastructure. cloud&more is the operator; Hugo is the environment.
Talk to us about your infrastructure
Bring the awkward parts: the workload that cannot move, the contract that runs another two years, the compliance question nobody has answered. That is the conversation worth having.