Varonis self-hosted
Industries
Healthcare

Your data never left the building. Now your security tool is.

Varonis has announced that its self-hosted platform ends on 31 December 2026. If you run it in your own data center, you have a decision in front of you — and moving your file metadata into a vendor cloud is not the only answer.

NetApp

Syslog CEF and REST, into the tool you already run

What is actually changing.

The console moves to the vendor

Customers are being moved to the SaaS platform. After the self-hosted sunset the management console is vendor-hosted.

The metadata goes with it

Event metadata is processed in the Varonis cloud rather than inside your own network.

Disconnected sites are an open question

Support for disconnected self-hosted installs after 2026 is not publicly documented.

The three statements above are Varonis’ own, as published. Check the current wording against their announcement before you plan around it.

Who this is a real problem for.

Regulated
The audit trail has to stay inside the jurisdiction
NIS2, DORA and the GDPR ask who could reach what, and where the record is kept
Decision needed
Disconnected
The site has no outbound connection, by design
Defense, utilities, manufacturing sites and dark rooms cannot call a vendor cloud
Decision needed
Sovereign
The file data may not be processed by a US-parented vendor
A procurement requirement that does not bend for a product roadmap
Decision needed
Everyone else
A migration, a new contract and a new architecture to approve
Work you did not plan, on a date you did not choose
Worth comparing

Let’s solve your data challenges.

Connect with our engineers to find the right approach for your infrastructure.

What ProLion does with the same job.

Moving to the vendor cloud

The platform keeps working, in someone else’s data center, under their change control.

The tool survives. The architecture does not.

Permissions analysis you already know
A migration team for the move
Your metadata is processed outside your network
A disconnected site has nothing to connect to
A new vendor-cloud architecture to get approved

Staying on-premises with ProLion

The same questions answered, on the hardware the files already sit on.

Nothing moves. Nothing leaves.

Effective permissions through every nested group
Every read, write, rename and delete, with user and timestamp
File content, metadata, logs and findings stay in your network
Air-gapped and dark sites supported
Austrian company, EU jurisdiction, no US parent

What a move actually takes.

1 · Run both

ProLion registers as an external engine on the filer and reads the file-operation stream. It changes nothing on the storage and nothing in the data path, so it can run beside what you have today.

2 · Compare the answers

Ask both the questions your auditor asks. Who can reach the share, who actually opened it, what changed last month. Then decide on evidence rather than on a deadline.

3 · Switch when you are ready

A typical install takes a few hours and self-install is supported. There is no agent to roll out and no client to touch.

Talk to an engineer who knows your data.

Four fields, and somebody who knows ONTAP, PowerScale and what FPolicy does. Not a qualification call.

Four fields. No hidden newsletter.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.