Site Unit plans · UI + API · Designed for engineering workflows

Pricing that makes procurement easy.

LuData provides environmental and geospatial datasets used for engineering-grade site analysis and is rolling out Analytics model workflows, so users can go beyond datasets alone. It supports solar energy, climate, agricultural and terrain-based studies. Choose a plan based on your annual Site Unit allowance, or contact us for Enterprise usage or platform integrations.

Simple rule: count how many distinct locations you need to study in a year. That is roughly how many Site Units you need. What is a Site Unit?

Included in every plan

Irradiance + Meteo
Satellite + Meteorological data
TMY + Risk
P50 / P90 / P95 profiles
Terrain context
Elevation + horizon profile
UI + REST API
Same access rights on every plan
Integration support
Help connecting LuData to your UI or API workflows
Usage dashboard
Track Site Units used and what remains in your annual allowance
Community support
Discord community for questions, updates and peer help
Need high volume?
Available for automated pipelines, large organizations, or embedded apps

Choose your plan

Pick the plan whose Site Unit allowance matches your annual location count. All plans include UI + API access. How many Site Units do I need?

Quarterly
YearlyGet 1 Quarter Free

Analytics protocols on request

On request

Beyond standard dataset plans, LuData offers API access to analytics protocols: Snow Assessment, Soiling Assessment and PV yield simulation. These are not included on Trial. From Launch onwards, customers may request access; it is granted to selected users only.

Analytics protocols are available through the API and are separate from UI scenario workflows for historical time series, TMY and elevation.

**Technical Advisory Support: Expert advisory sessions are remote technical discussions with LuData experts to support topics such as solar resource assessment, irradiance data quality control, dataset interpretation, or site adaptation.

Need a different payment method or custom terms?

If your organization requires a payment type not shown above (bank transfer, PO, split payments, multi-entity billing), or if you need a custom Site Unit allowance and contract terms, contact us through Enterprise or request a demo. We’ll adapt onboarding to your procurement process.

Typical examples: invoice-based onboarding, semi-annual payments (2x/year), purchase orders, or platform licensing.

Enterprise

Need more volume?

For large organizations, automated pipelines, or procurement requirements. Enterprise plans are contract-based and sized to your usage, teams and integration needs.

Commercial distribution rights allowed.

Custom analytics protocol access

Contact Sales

Typical users: NGOs, governments, corporations, private deployments, custom integrations, or contractual flexibility.

Platform License (Embedded Apps)

If LuData is integrated into your own software platform (OEM / SaaS) or used to serve multiple end users, we provide an annual platform license with a Site Unit bundle and an agreed usage policy.

What’s included

  • • Organization account (multi-users)
  • • UI + API access
  • • Usage dashboard
  • • Commercial distribution rights
  • • Contract terms
  • • Optional: custom datasets

How pricing is sized

We size the license by annual Site Unit allowance and your exceed policy: hard stop, top-up, or overage. We propose the right tier after a short usage discussion.

If you need the technical definition of Site Units (requests / normalization), we provide it in the proposal.

Prices are published to simplify procurement. VAT may apply depending on your billing entity and country.

FAQ

Answers for procurement and technical teams.

What is a Site Unit?
One Site Unit is one geographic location with the standard dataset bundle for a typical study: irradiance and meteorological data, TMY and risk profiles (P50 / P90 / P95), and terrain context (elevation and horizon). Under the hood, usage is counted in API requests. One request is one year of data for one variable at a location. To normalize usage into Site Units, we use a reference of 800 requests per Site Unit today; your dashboard converts requests into Site Units used and remaining. This reference may evolve as datasets and workflows change. Each plan includes a fixed number of Site Units per year. You can work in the UI, the API, or both.
How many Site Units do I need?
Count how many distinct locations you need to study in a year. That is roughly how many Site Units you need. If you revisit the same location with a similar dataset scope, it typically stays within one Site Unit. Contact us if you run heavy automation, many variables, or repeat studies on the same site beyond a standard workflow.
How does quarterly billing affect Site Units?
Your plan always has an annual Site Unit total (shown on each card). With yearly billing, the full allowance applies for the year. With quarterly billing, allowance is released each billing quarter (for example, 8 Site Units per year = 2 per quarter). Plans with 3 Site Units or fewer on quarterly billing may access the full annual allowance each quarter. Your dashboard shows usage for the current billing period.
Do plans include both UI and API access?
Yes. All plans include UI and REST API access under the same entitlement.
Can we start small and upgrade later?
Yes. Many teams start with Trial, Launch, or Starter and upgrade once their pipeline is confirmed.
Do you support invoice-based purchase?
Yes. We can onboard via invoice and procurement-friendly documentation.
Can we pay in installments or use a purchase order?
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.
What if we need very large volumes or automation?
Contact us for Enterprise. We size Site Unit allowance and terms to your teams, automation needs, and SLA requirements.
What is a platform license?
A platform license is for embedded or OEM use (your app queries LuData on behalf of many end users). It’s a contract with an agreed annual Site Unit allowance and an exceed policy.
Can you provide a technical definition of Site Units?
Yes. The summary is in What is a Site Unit? above, including the 800-requests-per-Site-Unit normalization reference. For engineering or procurement, we also document the full normalization rules and edge cases (for example multi-year periods, granularity, or non-standard variables) in the proposal.
What are LuData analytics protocols?
Analytics protocols are API-based workflows beyond standard dataset plans, including Snow Assessment, Soiling Assessment and PV yield simulation. Access is on request from Launch onwards (not on Trial) and granted to selected users only. Additional protocols are planned over time.
Are analytics protocols included in standard plans?
No. Standard plans cover UI and API access to solar datasets, TMY and elevation workflows through Site Units. Snow Assessment, Soiling Assessment and PV yield simulation require analytics access on request. Launch, Starter, Growth and Pro customers may request it; approval is granted case by case.

Send your request

Tell us what you need. We reply with pricing, onboarding steps, and (if needed) a proposal for procurement.

What happens next

  • We confirm the plan (Trial/Launch/Starter/Growth/Pro) or Enterprise scope
  • Procurement-friendly onboarding: invoice / PO / documentation if required
  • Account + access: UI login and API token
  • Usage visibility: dashboard showing remaining Site Units

Payment options

We support invoice-based onboarding and procurement workflows. For custom payment types, contact sales.

Enterprise buyers

We provide contract terms, Site Unit bundles matched to your pipeline.