Is there a free trial?

We do not offer a self-serve free trial because implementation fit depends on your actual devices, data quality, and connector needs. For qualified projects, we use a guided pilot to validate scope, coverage, and rollout risk before a broader deployment.

How are connections priced?

EDX pricing can be estimated based on incoming connections. A connection is one device or system feed into EDX, either as a real-time stream or as a batch sync. Batch connections are usually lower-cost than real-time streams because they sync on intervals instead of continuously.

Can I add connectors later?

Yes. You can add new connector types at any time. Each new connector type is a one-time fee. Once built, the connector is available across all your projects at no additional cost.

What's an onboarding project?

Onboarding is a focused setup phase for teams that need help mapping devices, configuring connectors, setting governance rules, setting up connection metadata, getting data consent in place where needed, or preparing internal users. Some experienced teams can move ahead without it, but it is often the fastest path for first deployments.

Do you offer volume discounts?

Yes. Per-connection pricing typically becomes more efficient as the number of incoming feeds increases. Enterprise-scale projects get custom pricing based on rollout shape, connector mix, and the share of real-time traffic.

Pricing

Estimate pricing here, contact us for a quote.

Quotes depend on connector needs, incoming connection volume, and rollout complexity. This page is designed to help you judge fit before we scope your exact deployment.

Request pricing See who pricing fits

Best for Production-grade energy data projects, not lightweight self-serve experiments.

Typical first step A scoped walkthrough or guided pilot to validate connector coverage and rollout risk.

Quote Inputs Three drivers shape the price

Connector scope

Which device types already exist and which ones need new integration work.

One-time

Connection volume

How many incoming device and system feeds run through the platform, and how real-time they need to be.

Recurring

Onboarding depth

How much support you need for mapping, connection metadata, consent setup where needed, governance, and production rollout planning.

Optional

Most teams start with a pricing walkthrough that turns their hardware mix and rollout shape into a realistic proposal.

Calculator

Get an indication and book a walkthrough.

Use this to estimate the likely monthly data volume fee and one-time setup range.

Slide incoming connections to estimate monthly telemetry cost
Adjust the mix between real-time streams and batch syncs
Choose whether you want self-onboarding or guided setup
Tell us if you need new connectors beyond the connected network

A connection is one incoming device or system feed into EDX, either as a real-time stream or as a batch sync.

Real-time connections usually cost more than batch connections because they maintain a live stream and process more frequent updates.

Real-time EMS example Solar, battery, meter, charger, and HVAC streams often means 5 live connections feeding an EMS or optimization layer.

Construction site example 1 main meter, 2 submeters, 1 battery, and 2 chargepoints usually means about 6 incoming connections.

Fleet management example 50 EVs typically means about 50 incoming vehicle or charger connections, depending on how the fleet data is exposed.

Incoming connections 25

0 1250 2500

Real-time / batch mix 50% real-time

Mostly batch Mixed Mostly real-time

Self-onboarding

Yes No

New connectors needed

No Yes

If the hardware is already part of the EDX network, connector setup may not be needed.

Estimated monthly range €1,048 - €1,613

Connection licensing based on the number of incoming feeds and the balance between batch and real-time traffic.

Estimated setup range €0 - €0

Includes optional onboarding and any new connector work you may need.

Based on 25 incoming connections, a balanced real-time and batch mix, self-onboarding, and existing connectors.

Request a pricing walkthrough Check connected network

How Pricing Works

Three drivers determine your price.

Component 1

Connectors

Price changes when you need device types that are not already covered. Once built, the connector can be reused across future projects.

One-time setup · Driven by device mix

Component 2

Connection licensing

Monthly cost changes with the number of incoming connections and the balance between scheduled batch syncs and live real-time streams. Higher volumes reduce the per-connection rate.

Recurring usage · Driven by connection count and live data share

Component 3

Onboarding

Setup support depends on how much help you need to map data sources, configure connection metadata, arrange consent where needed, configure governance, and move from pilot to production.

Optional support · Driven by rollout complexity

Fit

See if EDX fits your business case.

Good fit

Teams that need production-grade energy data handling

Teams integrating multiple hardware sources
Pilots that still need production-grade data quality and governance
Buyers who benefit from reusable connectors and controlled partner access

Probably not a fit

Projects looking for a lightweight self-serve utility

Hobby or single-device experiments
Teams expecting an instant self-serve free trial
Projects that only need a one-off export with no ongoing platform value

Next Step

Need a quote for your actual scope?

Tell us about your device mix, rollout stage, and expected telemetry volume. We’ll turn that into a pricing walkthrough or a scoped proposal.

Request a pricing walkthrough Review the platform