Professionals working together around a table

Our choices as a
European email company.

We develop Orvile in Nantes, France. Three questions guide our work: where to keep email, how to measure its environmental impact and how to support the people who use it.

Our commitments

From Nantes
to Europe.

Today we sell Orvile Mail in France. To support teams elsewhere in Europe, we’re working on language versions and looking for local deployment partners.

From Nantes, a European ambition. Geographical map of Europe. Curves connect Nantes with Dublin, Brussels, Berlin, Madrid and Rome. They illustrate an ambition and do not represent offices or current commercial coverage.

From Nantes, a European ambition.

Technicians working on a computer in a workshop

The resources
behind a message.

An email travels across a network and may spend years on a server and in its backups. AI analysis takes additional computing power. We include each of these in our study.

The study is still under way. We don’t yet have results that would support a claim about a reduction in impact.

Explore the environmental approach

Getting to know
a new email system.

Before a rollout, we ask the team to show us how they work: which mailbox they reply from, where they look for a drawing and who covers when someone is away.

The pilot lets you try those same tasks on the computers and phones you already use.

Plan the transition with your team
A professional helping someone use a computer

Who can open
the folder?

Your company keeps its email on its file server. With your IT lead, you decide who can open each folder and how to back it up.

Explore email

Understand how it works

Local retention does not remove every data flow.

Long-term email retention relies on storage chosen by the company. This needs to be distinguished from the transit required to deliver email, web and mobile access, backups and AI processing.

Each use raises a different question: where does a message travel, where is it kept, for how long and who can access it? The complete architecture needs to be considered when choosing an appropriate deployment.

Prepare deployment with the people responsible.

The discussion involves both the people who use email and those who administer the system. It is an opportunity to examine permissions, retention, data export, backups and each party’s responsibilities.

The contract and data-processing commitments need to match the chosen arrangement. Keeping data locally does not remove the need to define these rules or assess the requirements of your business.

Discuss your project

Decide where your conversations
should remain accessible.

Describe your storage and the people who use it. The team will explain the deployment options.

Request a demonstration