Deployment

Two modes. The same application.

Deployment mode is a governance decision, not a technical constraint imposed on you. NavOps runs as a sovereign cloud hosted in France and as a standalone executable installed at your site — same application, same functional scope.

Hosted in France
At your site

One product

What does not change between modes

All five modules, in full. No feature reserved for one mode.
The data model and export formats: what you produce stays readable in the other mode.
Functional updates follow the same roadmap.
Moving from one mode to the other is an operations task, not a product overhaul.

Both modes

What each mode implies

Hosted in France

Sovereign cloud

Hosted in France, operated by us.

The default mode, and the fastest to get running. The application is operated by us on French infrastructure, with no dependency on an operator subject to extraterritorial law. You keep control of access and of your data; we carry the operations.

It is the right choice when the point is not to repatriate hosting but to get a steering view quickly, without tying up your operations team.

What each mode implies

Your data sits on Scaleway infrastructure in French regions.
Hosting, backups, monitoring and updates are on us.
The service is reachable over the internet, protected by strong authentication.
Nothing to install or maintain: getting started is a matter of days.

What it assumes on your side

That your internal policy allows financial data to be hosted by a French third party.
Outbound internet access for your users.

At your site

On-Premise

A standalone executable, installed at your site.

The mode for organisations whose internal policy forbids hosting financial data externally, or who simply prefer that nothing leaves. A standalone executable: no cluster to administer, no dependencies to install one by one.

The application is the same one as in cloud mode — same modules, same data model, same roadmap. What changes is who operates it.

What each mode implies

The application ships as a standalone executable, installed on your servers.
Your data never leaves your network: nothing is reported back to us.
You choose when each new version is applied.
The service can stay fully offline, with no outbound internet access.

What it assumes on your side

A server you operate, with backups and monitoring in place.
A team able to hold an application update cycle.
Hardening of the host system, which stays your responsibility.

Split of roles

Who does what

The split of responsibilities is the real difference between the two modes. Here it is, with no grey areas.

Operational responsibilities split between the sovereign cloud mode and the On-Premise mode.
Topic	Sovereign cloud	On-Premise
Hosting and infrastructure	NavOps (Scaleway, France)	You
Backups and restore	NavOps	You
Availability monitoring	NavOps	You
Applying updates	NavOps	You, at your own pace
Application security patches	NavOps	NavOps ships them, you apply them
Access and identity management	You	You
Accuracy of the data entered	You	You
Data location	France (Scaleway)	Your own infrastructure

Decision

How to choose

There is no better mode in the abstract. There is the one that matches your internal policy and what you want to operate yourself.

Choose the sovereign cloud if…

you want to start quickly, without tying up your operations team;
hosting in France is enough to satisfy your data policy;
you would rather backups and updates not be your problem.

Choose On-Premise if…

your internal policy forbids hosting financial data externally;
you already operate business applications and can hold an update cycle;
you want to control when new versions are applied.

Read the Security page

Ready to frame your steering?

Open your cockpit, with your own figures.

Subscription and account creation happen inside the application. This site collects nothing: it takes you there.

Try NavOps See the demo

You are heading to app.navops.cloud — a page hosted by the application.