What we changed in our own company
Before helping other organizations, we reviewed the tools and suppliers we depended on. That work continues.
In 2025, trade tensions and the extraterritorial reach of certain laws prompted us to look more closely at our US suppliers. Our email, documents and part of our work relied on services whose decisions were made elsewhere. We wanted to know what we could bring back to Quebec and what we could operate ourselves. Shelter Bay became its own first project.
Replacing tools while keeping them useful
For many services, we found a suitable replacement. The collaboration suite posed a different problem. It supports exchanges with clients as well as work between colleagues. Changing email can affect calendars and meeting invitations; moving files means reviewing how people share them. We had to consider those uses together.
The open-source software we tried provided useful components, but everyday use still involved too many trade-offs for our team. European suites met some of our needs. They would, however, have placed our email and documents abroad and introduced a new dependency on their operators. We wanted to be able to run the suite here.
Building the tool we were missing
LaSuite, led by the French government, suggested a way forward: bring good open-source software together and pay attention to how people move between tools. We began developing Béluga around our own collaboration needs. Email, documents, calendars and meetings needed to work together in everyday use.
Béluga has been in open beta since September 1, 2026. It is developed and hosted in Quebec. Its website describes the available applications and how to try them. Béluga is proprietary software: we develop the platform that brings its modules together and own its code. Each module, however, relies on a proven open-source component, such as Matrix for messaging or LiveKit for meetings. We explain that distinction because it matters when choosing a provider.
What we take from this work for other organizations
Changing a tool requires understanding the work it supports. It also means identifying the data to move, the access to recreate and the uses to check before leaving a service. A small organization should be able to make those decisions without becoming an expert in its entire infrastructure. Studio’s guidance helps with that preparation.
Cloud provides access to the infrastructure we operate, while Béluga addresses the collaboration need that led us to develop it. These services can be chosen separately. Our experience connects them, but it does not mean every organization should follow the same path we did.
A picture that will keep changing
We still have dependencies. Our servers are manufactured abroad, the data centre building belongs to its operator, and payments go through external providers. Cloud’s web hosting uses licensed commercial software, and a few Béluga features rely on providers outside Quebec. We examine their role in data access and service continuity. The path below sets out what our team controls today and where another organization is involved.
From our first websites to Béluga
Making the web accessible
Our first projects provide websites and hosting for small businesses and non-profits in Port-Cartier and on Quebec’s North Shore. The aim is to give them useful tools they can afford.
Giving the work a structure
The company is incorporated. Referrals bring new work and larger corporate projects. Consulting, design and development remain the starting point for our activities.
Reviewing our dependencies
We begin replacing US suppliers and bringing more tools back to Quebec. The search for a collaboration suite that fits our team leads to the development of Béluga.
Opening Béluga
Béluga enters open beta. The suite developed for our team becomes available to other organizations. It brings together email, files, documents, calendars, contacts, meetings and team messaging, and development continues.
Our servers, our software and the suppliers we still use
We can own a server without owning its building. A backup can remain in Quebec while involving a separate provider. The path follows these responsibilities from the physical location to external services, showing exactly what we operate today.
Building and energy
Our servers are installed at our primary hosting site, a Montréal data centre operated by a Montréal company and supplied by Hydro-Québec’s grid. We rent the space needed for our equipment.
- What we control
- We choose the hosting location and the conditions in which our machines are installed. This places our main infrastructure in Quebec and identifies the operator housing it.
- Current limitations
- The building belongs to its operator, so we remain dependent on services tied to the physical location. Building a Shelter Bay data centre is part of our long-term vision.
Hardware
The servers belong to Shelter Bay. Our team operates that hardware for its own services and for Cloud’s hosting offering. Ownership of the machines is separate from ownership of the building.
- What we control
- We decide how to configure and maintain the servers and when to replace them. We seek to extend their useful life while considering the needs of the services they run.
- Current limitations
- The equipment is manufactured abroad. Owning a server gives us control over its operation, but not over its manufacturers or their supply chains.
Network
Our team operates the infrastructure’s private networks and encrypted access. Those networks connect the services we run; the data centre operator provides the Internet connection.
- What we control
- We organize our networks and manage access to our services. These responsibilities concern our own infrastructure, separately from the transport of communications over the Internet.
- Current limitations
- Connectivity depends on the data centre and the networks it connects to. An interruption there may require another provider’s involvement even when our own servers are working.
Software
Infrastructure functions, including virtualization and identity management, rely on open-source software operated by our team. We also develop Béluga, our collaboration suite: a proprietary platform that brings proven open-source components together.
- What we control
- We operate the infrastructure software and develop Béluga. This lets us act on the application service and on some of the systems that run it.
- Current limitations
- Not all our tools are open source. Cloud’s web hosting and billing use licensed commercial software, and the Béluga platform is proprietary. Licensing therefore needs to be checked separately from hosting location.
Data
Data for our services is hosted on our servers in Montréal. Shelter Bay encrypts backups before sending them to OVHcloud in Beauharnois and keeps the encryption keys.
- What we control
- We operate the services and encrypt backups before transfer. The keys never leave Shelter Bay: that provider stores copies it cannot read.
- Current limitations
- Backups are kept by a separate provider, so restoring them depends on its service being available. Some Béluga features also rely on providers outside Quebec, such as optional meeting transcription; Béluga’s website publishes the list.
Suppliers
We reduce dependencies when suitable alternatives exist. Some services, including payment processing, still rely on external providers. We describe them because they play a part in running our services.
- What we control
- We choose the providers we use and examine what we entrust to them. Their role matters as much as their location in understanding a dependency.
- Current limitations
- Some functions cannot yet be brought back under our operation. Béluga’s website provides information specific to its service, including its detailed list of subprocessors.
Last reviewed : November 17, 2026
Our plans for what comes next