Editorial

Why we chose hosting in the EU

Why elOS uses Microsoft hosting in Sweden, how European hosting supports our approach to data protection, and what teams should ask a software provider.

Network cables connected to server ports.
Illustrative image. Brett Sayles / Pexels

At elOS, we use Microsoft hosting in Sweden for our work. We chose European infrastructure close to our team in Estonia, with security and data protection central to the decision.

Hosting in the European Union gives that choice a clear regional context. It helps us assess where information is handled, which commitments apply to the services we use and how those services fit our responsibilities. For the organizations getting to know elOS, this article explains the reasoning and the practical questions behind it.

Why European hosting matters to us

Our team works between Europe and Brazil. Keeping our Microsoft hosting in Sweden reflects our preference for infrastructure near our European base and our intention to build with European data-protection requirements in mind.

The European Economic Area includes the EU, Iceland, Liechtenstein and Norway. The GDPR framework applies across this area, with specific conditions for transfers of personal data outside it. Hosting location is therefore a useful part of understanding a service's data arrangements.

Those arrangements include more than a main database. Backups, support access and other providers can also be involved. The European Data Protection Board explains when making personal data available to another organization outside the EEA constitutes an international transfer and which conditions apply.

For us, European hosting is a considered foundation for those decisions. Understanding the full service helps us describe that choice accurately.

Building on that foundation

Infrastructure and application security work together. The hosting provider operates parts of the underlying infrastructure; the application team manages the components and settings under its control. The division depends on the cloud services used.

Microsoft describes this as shared responsibility. Its guidance identifies data, identities, accounts and access management among the responsibilities customers retain. The service model determines how other operational tasks are divided.

At elOS, this means considering the hosting choice alongside permissions, recovery arrangements and the handling of records. The EDPB's security guidance brings these concerns together through confidentiality, integrity and availability, with measures appropriate to the risks involved.

Useful questions when choosing software

Small businesses and nonprofits should be able to understand how a service handles their information. These questions help connect the hosting decision to the way a team will use the application.

Useful questions when choosing software
QuestionWhat a useful answer includes
Where is our information handled?The application and backup locations, support access and other recipients.
Who can access it?Permission settings and how access is changed when responsibilities or team members change.
How can important records be recovered?Backup coverage, recovery procedures and what has been tested.
What happens if we leave?Export formats, deletion arrangements and retention terms.

What to ask about a service

  • Location Where is information held and processed?
  • Access Who can see it, including support?
  • Recovery What happens if a record is lost?
  • Leaving What can you export or remove?

Server location answers only part of the question.

Questions that connect hosting choices with everyday use.

Different ways of obtaining software also bring different responsibilities. A hosted application puts more operational work with the supplier. Building with managed cloud services divides that work between the cloud provider and the development team. Maintaining your own infrastructure requires people to operate, update, monitor and recover it over time. The useful comparison is which arrangement your organization can sustain and which tasks each party accepts.

What this means for elOS

Our first version is in development. European hosting is one of the choices supporting that work, alongside assessing the services, agreements and settings appropriate to the product.

Microsoft's EU Data Boundary documentation describes regional storage and processing commitments for covered services and data categories, including limited circumstances involving transfers outside the boundary. We assess those commitments against the particular services and terms involved, so our explanations reflect what applies to our setup.

We chose EU hosting because location, data protection and operational responsibility matter to us. Our job is to carry those priorities through the application and give participating organizations clear information about the service they will use.

Find official guidance on data protection and cybersecurity for small businesses.

References

  1. European Commission

    Rules on international data transfers

    Explains the EEA scope and mechanisms for transfers outside it.

    Open resource: Rules on international data transfers
  2. European Data Protection Board

    International data transfers

    Explains when a transfer occurs and the additional conditions that apply.

    Open resource: International data transfers
  3. European Data Protection Board

    Secure personal data

    Explains risk-based technical and organizational security measures.

    Open resource: Secure personal data
  4. Microsoft

    Shared responsibility in the cloud

    Describes the division of operational security responsibilities for cloud services.

    Open resource: Shared responsibility in the cloud
  5. Microsoft

    What is the EU Data Boundary?

    Explains the scope of the commitment and points to circumstances involving transfers outside the boundary.

    Open resource: What is the EU Data Boundary?

Found a broken link or a detail that needs correcting? Suggest a correction

Follow by RSS

Questions? hello@elos.is