The Sand Energy OS
Today’s energy market runs on disconnected tools for generation, distribution, trading, and billing. Sand replaces them with one operating system - a set of composable domain packages, a unified data model, an AI-native application layer, and an open ecosystem, all running on the same secure foundation.
Why a platform, not another app
Every energy tool on the market today is built the same way - a discrete app, a fragmented data model, ad-hoc integrations. Sand was built the other way around.
The core idea
Domain packages - metering, billing, market operations, VPP coordination, analytics, customer, devices, risk - are the platform’s real product. Each one is a bounded, independent capability that evolves on its own.
An app is simply one particular assembly of those packages, shaped for one stakeholder. Sand Gen, Sand Dist, Sand VPP, and a trading desk all snap together from the same shelf - which is why the next app is always faster to ship than the last.
Composable domain packages
Built apps - not composable themselves, just assembled once
One backbone, every app
A meter reading means the same thing in Sand Gen, Sand Dist, and the marketplace - same asset IDs, same tariff structures, same units, governed centrally instead of duplicated per app.
That is what makes new use cases fast to build: nobody starts from a blank data model. Every new package inherits a data layer that already understands energy - generation, consumption, tariffs, assets, and settlement - out of the box.
How it is built
Sand is built on domain-driven design - clear boundaries between layers so every part of the platform can evolve on its own without breaking the rest.
Common infrastructure, shared by every layer
01
Every tenant runs on its own isolated slice, provisioned automatically on subscription - one customer’s data never leaks into another’s.
02
Every request passes through the API Gateway and is authenticated before it ever reaches a domain package.
03
The Anti-Corruption Layer absorbs the mess of legacy systems and third-party integrations before it can touch the core domain.
04
Security, logging, and observability are common infrastructure, not optional add-ons - every layer is instrumented from day one.
Open by design
Generators, distributors, traders, auditors, business software, and third-party apps all connect through the same open door - no exclusion, no walled garden.
Build, extend, and safely integrate new energy solutions or domain packages on the platform.
Every resource, every API, every doc in one place - built for frictionless onboarding.
AI-assisted low-code and no-code tools tuned for energy workflows, so builders move faster.
Two-way integrations with business software, ERPs, CRMs, and hardware already in your stack.
Deploy, share, and monetize approved energy applications built for Sand - a real marketplace, not a directory.
Sand Gen mints a kWh coin for every verified, metered kilowatt-hour - an asset-backed digital energy unit, patent-pending (PCT/US24/49609), that carries source, time, and carbon intensity into Sand Dist's consumer rails and the wider ecosystem.
Beyond the apps
Will open a shared space where producers, distributors, and utilities discover and monetize value-added services - turning one-off vendor relationships into a connected, transparent marketplace.
Planned modules
Service Listings Discovery
Transactions Shared Standards
Being built for the engineering, maintenance, and technology providers working behind every producer and distributor - giving service partners a direct, structured way to plug into the platform their clients already run on.
Planned modules
Job Workflows
SLA Reporting
Client Integration Marketplace Listing