Our services are hosted in Quebec. Understanding what that means requires a look at the hardware, software and companies involved in running them. We operate some of this infrastructure ourselves and rely on suppliers for the rest.
Servers we own, in Montréal
Our servers are installed at our primary hosting site, a data centre in Montréal. They belong to Shelter Bay, which configures and maintains them.
Owning the hardware lets us decide how to configure it and when to replace it. Manufacturing still depends on companies abroad, and the building belongs to the data centre operator. Building our own data centre is part of our long-term plans.
Our team operates the private networks and encrypted access. Internet connectivity depends on the data centre operator and the networks it connects to. A connectivity incident may require its involvement even when we own the affected server.
Separating hosting from application work
The service chosen also determines what the client will need to administer. Web hosting and a virtual server meet different needs. To compare them, it helps to establish who handles updates, which interventions are included and which tasks remain the organization’s responsibility. The relevant offering’s description and terms provide those answers.
A server’s location therefore does not settle which service to choose. An organization with the skills to administer its applications will make a different choice from one looking for guidance. At Shelter Bay, Cloud describes the hosting services and Studio can help prepare a project. The two brands can be chosen separately.
The software our team operates
The core functions of our infrastructure, such as virtualization and identity management, rely on open-source software we operate. Other tools, including those used for Cloud’s web hosting and billing, are licensed commercial software. Béluga, our collaboration suite, is a proprietary platform built on open-source components and hosted on that infrastructure.
A software model and a hosting location provide different information. The first concerns, among other things, the ability to use or modify the code. The second tells you where the service runs. Evaluating a provider also requires knowing who handles maintenance and which terms govern access to the service.
Options for retrieving data need a separate review. Available formats and the help needed to leave can vary between tools. Organizations should check them against the data they need to keep.
Encrypted off-site backups
We encrypt backups before entrusting them to a separate provider at a second data centre in Quebec. The encryption keys stay with Shelter Bay: that provider stores copies it cannot read. It is therefore part of our infrastructure, even though the servers running our services are in Montréal.
An organization reviewing its own hosting needs to account for the different copies of its data. Backups may be stored somewhere other than the main service. Logs and exchanges with other services can also involve additional suppliers.
A backup also needs to be evaluated against its intended use. Recovering a deleted document and bringing a service back after an interruption are different needs. The data kept, the frequency of copies and the restoration arrangements need to be examined for the service in question. The word “backup” alone does not establish a recovery time.
An organization comparing offerings can start with a specific example of what it needs to recover. It can then ask which copy would be used, who would perform the operation and what needs checking after restoration. That discussion makes responsibilities more concrete than a general statement about protecting data.
The suppliers we still depend on
An external provider handles payment processing. Like hardware manufacturing or Internet connectivity, this function ties us to companies whose decisions are not entirely within our control.
This is why we describe our journey in layers. It shows what our team operates directly and where another provider is involved. That division of responsibilities describes our current setup; we will update it as the infrastructure changes.