Build the dashboard while we run the engine underneath it.
ecolyptus Data Mechanic Engine handles the backend for teams building their own energy and sustainability dashboard: meter registration, data collection, storage, processing, and tariff calculation, all handled for you. Bring your own developers and we'll support them, or let our team design and build the front end to your specification. Either way, you host it on your own servers, under your own brand, and you own the IP.
Book a DemoFront ends have never been faster to build, but the data underneath them has not gotten any easier to work with.
Modern tools mean a slick, on-brand dashboard can go from idea to shipped in weeks rather than months, because design systems, component libraries, and rapid prototyping have compressed the front end into the fastest part of the build. None of that touches the part that was always the real bottleneck, which is getting clean, accurate, tariff-aware energy data flowing reliably underneath it. That is still a multi-year infrastructure problem if you build it from scratch, and it is exactly what Data Mechanic Engine replaces.
Meter data arrives messy
Every hardware vendor, protocol, and utility handles registration and intervals differently, which means normalising all of it into one clean, queryable dataset happens before a single chart can render, and that is a project in itself.
Tariffs change after the fact
A retroactive rate correction means recalculating cost across your entire historic dataset, not just today’s reading, and getting this wrong once quietly makes every cost figure on the dashboard untrustworthy.
Scale breaks naive approaches
A dashboard for a handful of meters is a demo, but one for thousands of meters at one-minute resolution, running every day for years, is a genuine data engineering problem where storage, processing, and query performance all compound together.
Gaps and history have to be fixable
Signal drops, meters get swapped, and historic data sometimes needs reprocessing months later, so handling that gracefully without corrupting the record is infrastructure work most teams only discover they need after something has already gone wrong.

Bring your own developers, or let us build it for you.
Some teams just want the engine and the API, and their own developers take it from there. Others want us to design and build the entire front end to their brand and specification, then hand over something they host and own outright. Most sit somewhere in between, and that is exactly how we work, offering as much or as little support as your team actually needs, from a technical scoping call through to a finished, branded dashboard.
Everything a custom dashboard needs, minus the years it usually takes to build it.
Engine integration
Meter registration, data collection, storage, processing, and tariff calculation are all fully managed underneath your dashboard, so your front end only ever renders data that has already been checked, cleaned, and calculated correctly.
Comprehensive APIs
Pull processed data, cost metrics, and CO2 emissions on demand, structured however your dashboard needs it, so you never have to calculate any of it yourself.
Data point management
Manage individual data points, fill gaps automatically, and reprocess historical data on demand, whenever a meter is corrected or a tariff changes retroactively.
Real-time webhooks
Subscribe to events as they happen instead of polling for changes, so your dashboard can react the moment something in the underlying data actually changes.
Third-party migration
Connect to your existing platforms and port every year of historical data across, so switching to Data Mechanic Engine never means starting your record from zero.
Build it your way
Bring your own developers and we will support them, or let our team design and build the entire front end to your specification instead.
From raw meter data to a finished dashboard, in five steps
- 1
Connect your sources
Meters, gateways, or your existing third-party platforms all connect the same way, since Data Mechanic Engine is hardware and platform agnostic.
- 2
The engine takes over
Registration, ingestion, storage, processing, and tariff calculation all run automatically, with gaps and historic data reprocessable at any time.
- 3
Query it through the API
Pull processed data, cost, and CO2 metrics on demand, or subscribe to webhooks for real-time events.
- 4
Build the dashboard
Your team builds the front end, ours does, or somewhere in between, and the choice is entirely yours.
- 5
Host it, brand it, own it
Deploy on your own servers, under your own brand, with the intellectual property entirely yours.
Priced like infrastructure, not like a project.
Data Mechanic Engine is a subscription, typically a fraction of what teams currently spend maintaining backend infrastructure themselves. Front-end development is a one-off cost scoped to your specification, not an ongoing dependency.
- Months to years of backend engineering
- An ongoing team to maintain and patch it
- Every tariff change and edge case becomes your problem
- A subscription, live in weeks
- Infrastructure already proven at scale
- A one-off dashboard build that's entirely yours
Built for teams who want the dashboard, not the years of plumbing behind it
Product and engineering teams who do not want to own energy data infrastructure themselves.
Teams building bespoke dashboards for their own clients, under their own brand.
Companies adding energy or sustainability features to an existing product.
Teams migrating off a legacy platform who need to keep every year of their history.
Add functionality that is entirely your own, not just a different coat of paint.
Because the API and webhooks expose everything the engine already calculates, your developers, or ours, can build entirely new views, reports, and calculations on top of the platform. This goes far beyond changing a logo or a colour palette, and lets you add capabilities that do not exist anywhere else today, built around exactly how your business operates.
