Pricing that starts where you are.

A DER endpoint is any individual distributed energy resource that Texture monitors and can receive dispatch signals for. This includes each residential or commercial battery system, each solar inverter with two-way communication capability, and each smart meter enrolled in a demand response program. If a household has both a solar inverter and a battery system, those count as two endpoints. Aggregator-managed devices count at the device level, not the aggregator account level.

Yes. The Pilot tier is designed for utilities running an initial DER program evaluation or a bounded geographic pilot. When your program scales past the 5,000-endpoint threshold, or when you are ready to enable AI dispatch capabilities, a contract amendment moves you to Deploy tier. Data continuity is maintained across the transition. There is no migration fee and no re-integration work required.

We offer a structured evaluation period for qualified utilities and cooperatives that want to verify integration before committing to an annual contract. This typically involves connecting Texture to one or two data sources and running the unified view against a subset of your DER portfolio. The evaluation scope and terms are scoped per conversation. Contact us to discuss whether your program profile is a fit.

Annual contracts are sized to your peak enrolled endpoint count. If your DER fleet grows materially during a contract period, we work out an amendment rather than an automatic overage charge. Utilities with highly seasonal programs (summer battery fleets, for example) can discuss seasonal structure in the Utility Scale tier. The Pilot and Deploy tiers are billed based on enrolled endpoint ceiling, not active dispatch frequency.

Deploy tier includes read and write API access to the Texture data layer. Read access lets you pull normalized DER telemetry, dispatch history, and current resource state into your own reporting systems or ADMS. Write access allows programmatic dispatch confirmations and threshold configuration without going through the UI. The API follows a REST/JSON interface with token-based authentication. API documentation is included with Deploy onboarding.