Security

Your plant data stays yours.

Imagery and string data affect revenue, valuations and warranty claims. This is how Solvane is designed to protect it, and what is in place today versus on the roadmap.

On-device analysisThe core vision engine runs in the browser. Images don't have to leave the machine to be analysed.

Keys stay server-sideWhen a cloud model is enabled, its API key is read only by the server and never sent to the browser.

EncryptionTLS in transit; encrypted storage at rest on hosted plans.

Tenant isolationEach organisation's data is isolated in the database, never co-mingled.

Role-based accessOwner, engineer, technician and viewer roles, set per site.

SSO / SAMLPortfolio and Enterprise plans, with enforced MFA.

Audit trailUploads, reviews, priority changes and exports are logged.

Data residencyUS or EU regions; UK and private deployment on Enterprise.

Details

Security questions.

Is our imagery used to train models?

No. Your imagery and telemetry are never used to train shared models without written opt-in. Enterprise fine-tuning uses only your own data, in your own tenant.

What leaves our network when we use the on-device engine?

Nothing about the image. Analysis runs in the browser tab. Only the findings you choose to save are stored.

What does the MVP store today?

The live demo keeps its workspace in your browser's local storage, and demo requests are stored on the server that hosts the site. Hosted multi-tenant storage, SSO and audit logging are part of the pilot rollout.

Can we run Solvane on-premises?

Yes, on Enterprise. The application is a Node service plus static front end, with no dependency on a specific cloud.

Need a security review before a pilot?

Talk to us