Updated pricing policy for Yandex DataLens

Starting December 1, Yandex DataLens introduces a revised pricing policy. Under the new unified service plan, all users will gain access to expanded capabilities, including Neuroanalyst, reports, JavaScript-based customizations in Editor, background chart data export, UI styling, and more. The new plan will be offered free of charge for individual use and for a fee for team work.

• New pricing policy
• Transition timeline
• Discount
• Limiting the number of queries from private embedded objects

New pricing policyNew pricing policy

What will change?What will change?

Pricing will be based on the number of seats within one Yandex DataLens instance.

• Every Yandex DataLens user will need a seat, even if only to view or edit dashboards.
• Seats are issued automatically when new users first log in to Yandex DataLens.
• Seats can be managed by the administrator, see below for details.
• While you can still manage access to objects in Yandex DataLens using roles and access permissions, a seat does not provide access to objects.

Active users and seatsActive users and seats

According to the pricing policy valid until December 1, 2025, you pay only for active DataLens users. An active user is someone whose actions result in a query to a data source, e.g., opening or editing a dashboard, chart, or dataset.

However, the new pricing policy, due to come into effect on December 1, 2025, is going to charge for each seat no matter whether its user is active or not.

Managing seatsManaging seats

Starting December 1, the seat management option will appear in DataLens settings.

The administrator will be able to:

• View the number of seats in the instance, including available (unassigned) ones.
• View the list of users with seats.
• Reassign seats from user to user.
• Increase or decrease the number of seats in the instance.

By March 1, 2026, tools will be released for automatic revocation of inactive seats.

PricesPrices

Within one instance, DataLens will be priced as follows:

• One seat: Free of charge.
• Two or more seats: $8.249997 per seat per month.

Seats are counted towards the month's total. If the instance contains more than one seat, the total charge is calculated as follows:

Number of seats × Cost per seat

You may schedule a cut in the number of seats at any time; however, the change will take effect only on the first day of the following month.

Technical support coverage is determined by the Yandex Cloud support plan you select.

Transition timelineTransition timeline

The transition to the new service plan will be gradual.

User category	Dates	Terms of transition
New users	November 17, 2025	Activation of an instance with a 30-day trial period. Full access to all DataLens features without any team work restrictions. After 30 days, you either link a billing account and purchase seats for team work or scale down to a single seat. Following the end of the trial period, your seat charge for the first month will be calculated in proportion to the number of days left in the month.
	March 1, 2026	For seats, queries from private embedded objects are fixed as follows: 2,000 queries per seat. See details below.
Community plan users (as of November 16, 2025)	December 1, 2025	Transition to the new service plan with an extended trial period until March 1, 2026. Access to all DataLens features without any team work restrictions. Special terms apply for transition to a paid DataLens plan for team work; details below. Following the end of the trial period, your seat charge for the first month will be calculated in proportion to the number of days left in the month.
	March 1, 2026	You either link a billing account and purchase seats for team work or scale down to a single seat. For seats, queries from private embedded objects are fixed as follows: 2,000 queries per seat. See details below.
Business plan users (as of November 16, 2025)	December 1, 2025	Billing shifts from active users to seats.
	March 1, 2026	For seats, queries from private embedded objects are fixed as follows: 2,000 queries per seat. See details below.

DiscountDiscount

As of November 16, 2025, special conditions apply to Community plan users.

If you migrate to the Business plan before December 1, 2025 or end your trial period early between December 1 and December 31, you will get a 50% discount on all seats from that moment until the end of 2026.

Limiting the number of queries from private embedded objectsLimiting the number of queries from private embedded objects

The seat count determines the limit on the number of queries from private embedded objects within one DataLens instance. There is no limit for regular queries made by users in the DataLens interface, as well as queries to publicly embedded objects.

• The following limit will be in effect from March 1, 2026: 2,000 queries from private embedded objects per seat per month. This limit will not apply to each individual seat, but the entire DataLens instance based on the calculation:

  2,000 queries x Number of seats

• Seats are not linked to embedded objects directly; they do not have to be assigned to external viewers of these objects. What matters is the total number of seats purchased within the instance, both free and assigned to users.

  Thus, the more actively a DataLens instance is used (the more of its seats are purchased), the higher the private embedding limit will be.

• If DataLens is used by several users, yet there are many queries to private embeddings, you will have to procure additional seats based on the calculation above.

• Every query for data from a private embedded object is counted. For example, you have an embedded dashboard with 10 charts and 5 selectors. Refreshing the dashboard page will initiate 15 queries.

  You can estimate the number of queries from private embedded objects even now by enabling Usage Analytics. If the total number of such queries exceeds the per-instance limit, you may have to purchase more seats.

See alsoSee also

• Configuring a DataLens service plan
• Service plan features
• Pricing and payment questions