Pricing that makes procurement easy.

One Site Unit equals 800 requests. Site Units provide a simple way to select a plan according to expected usage. Actual consumption is measured in requests across both the LuData user interface and API. A Site Unit does not always correspond to exactly one physical site. Consumption depends on the selected datasets, historical period and analytics.

For historical data and TMY source data, one request represents one variable, one year and one location. Examples: 1 variable over 1 year at 1 location = 1 request; 4 variables over 10 years at 1 location = 40 requests; 10 variables over 20 years at 1 location = 200 requests. Forecasting (API only) is metered by variables and forecast days and can use fractional requests; see the forecasting example in the FAQ. Other services have defined request costs (see How requests are consumed).

Forecasting is charged for the variables and forecast days you actually receive, not as one full request per API call. That makes it practical to refresh the latest forecast when a new model run is published (often several times per day) without paying a whole request each time. Example: one variable and a 10-day latest forecast uses about 10 ÷ 365 ≈ 0.03 requests per call. If you update four times in the same day with the same horizon, that day totals about 0.11 requests — not 4. Historical and archived benchmarking runs follow the same proportional rule.

In general, the same request-consumption rules apply through both the LuData interface and API. Exception: snow and soiling estimates inside the Yield simulation UI are included helpers (not metered). The snow and soiling APIs return more detailed assessment data and are metered as listed under How requests are consumed. Forecasting is available through the API only (not the scenario generator UI).

Yes. Analytics protocols (Soiling Assessment, Snow Assessment and PV-yield simulation) are available when enabled for your account. PV-yield is available through the UI and API. Snow and soiling are available as detailed API assessments (metered) and as included helpers inside the Yield simulation UI (not metered). PV-yield runs and detailed snow/soiling API runs consume requests from the plan allowance. On Free Trial, datasets and analytics may be used within the available 800-request trial allowance when enabled for the evaluation.

Request consumption is calculated automatically and displayed in the LuData dashboard. Users can monitor used requests, remaining allowance and usage history at any time.

Estimate annual usage from the datasets, periods and analytics you expect to run, then choose the plan whose Site Unit and request allowance matches that volume. Contact us if you run heavy automation or need a custom allowance.

When you reach the request limit for the current billing cycle, further requests are blocked until the next cycle or until your plan is upgraded. The API returns an error indicating that the plan limit was reached.

No. Unused requests do not roll over to the next billing period. Your cycle usage counter resets at the start of each new billing period.

Billing frequency applies to Launch and Starter. Your plan has an annual Site Unit total (shown on each card). With yearly billing, the full allowance applies for the year and annual payment includes three months free. With quarterly billing, allowance is released each billing quarter (for example, 16 Site Units per year = 4 per quarter). Plans with 3 Site Units or fewer on quarterly billing may access the full annual allowance each quarter. Free Trial, Growth, Pro and Platform / Enterprise are not purchased through the quarterly/yearly toggle.

All paid subscriptions provide access to LuData datasets and terrain services through the UI and API. Forecasting is API-only; other datasets and terrain services are available through both UI and API. Analytics protocols are available when enabled: PV-yield simulation through the UI and API; detailed Snow and Soiling Assessment through the API; and snow/soiling helpers inside the Yield simulation UI. Site Unit allowance, support and commercial rights depend on the selected plan.

A Typical Meteorological Year uses between 10 and 20 years of historical data and between 4 and 10 variables. It therefore consumes between 40 and 200 requests per location. TMY consumption is calculated from the number of historical years and variables selected; it does not have a separate fixed request cost.

Yes. Many teams start with a Free Trial, Launch, or Starter and upgrade once their pipeline is confirmed. Growth, Pro and Platform options are available through sales.

Yes. We can onboard via invoice and procurement-friendly documentation.

Yes. If you require split payments (e.g., 2x per year), purchase order workflows, or a specific billing setup, contact sales and we will adapt the onboarding under Enterprise terms.

Contact us for Growth, Pro or Enterprise. We size Site Unit allowance and terms to your teams, automation needs, and SLA requirements.

Standard subscriptions are intended for internal engineering, research and project-analysis workflows. Customer-facing integration, redistribution, white-labelling or embedding LuData into another commercial platform requires a separate Platform Licence. Raw-data resale, sublicensing and standalone redistribution require explicit contractual approval.

Analytics protocols include Soiling Assessment, Snow Assessment and PV-yield simulation. They are available when enabled for your account, including on Free Trial within the trial allowance. The snow and soiling APIs return more detailed assessment data and are metered, as is PV-yield. Snow and soiling estimates inside the Yield simulation UI are included helpers and are not metered.