Loading…

Varonis Systems (VRNS) backlog: remaining performance obligations

How much revenue Varonis Systems already has under contract, how fast it converts, and who it is with.

Data as of .

Varonis Systems backlog history

$0$500M$1BJun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$1.13B$716M1.6 yrs$423M
30 Jun 2026$1.08B$688M1.6 yrs$420M
31 Mar 2026$1.10B$660M1.7 yrs$416M
31 Dec 2025$1.10B$624M1.8 yrs$428M
30 Sep 2025$931M$609M1.5 yrs$334M
30 Jun 2025$871M$595M1.5 yrs$323M
31 Mar 2025$789M$573M1.4 yrs$296M
31 Dec 2024$730M$551M1.3 yrs$290M
30 Sep 2024$581M$546M1.1 yrs$218M
30 Jun 2024$515M$521M1.0 yrs$209M
31 Mar 2024$426M$506M0.8 yrs$185M
31 Dec 2023$378M$499M0.8 yrs$181M

Questions

What is Varonis Systems's backlog?
Varonis Systems reported $1.13B of remaining performance obligations at 30 Sep 2026, up 21% from a year earlier and up 4% from the previous quarter. That is 1.6 years of trailing revenue already under contract. Book-to-bill last quarter: 1.23.
How fast does Varonis Systems's backlog turn into revenue?
Over the last twelve months Varonis Systems recognised revenue equal to about 68% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.