Pricing that scales with your feeder count, not your headcount.

Most utilities are running their first forecasts within 10 to 14 days of starting the integration process. We handle the connector configuration. You provide read access to your SCADA or EMS interval data. The 2-week window includes initial data validation, model training on your historical intervals, and threshold configuration for your first set of feeders.

Your interval data is isolated to your tenant and is not shared across customers or used to train other utilities' models. Data in transit is encrypted using TLS 1.3. Data at rest is encrypted using AES-256. Retention periods and deletion options are configurable. For utilities with strict OT network requirements, the on-prem agent option on the Scale tier keeps all data inside your network boundary.

Yes. Within your tier's feeder cap you can add feeders at any time through the console. If you're approaching the cap (25 feeders on Monitor, 150 on Operate), we'll work with you on upgrading to the next tier or expanding your feeder allocation. We don't charge per-feeder overage fees; the tier caps are the billing boundary.

A typical pilot starts on a subset of your feeders, usually 10 to 20 feeders covering the load patterns you most want to improve visibility on. We run the pilot for 30 to 90 days. During that period you're running on the full Operate tier feature set regardless of which tier you ultimately proceed with. At the end of the pilot we review forecast accuracy, alert quality, and any operational changes your team observed, then scope the production deployment.

Monitor and Operate tiers are offered on annual contracts. The pilot period is billed separately at a reduced rate and does not commit you to a full-year contract. If the pilot results support proceeding, we move to the annual contract for the production deployment. Scale tier contracts are negotiated individually based on deployment scope and multi-site requirements.

No. Ampgrove surfaces dispatch recommendations: the system tells your operators what action to take, when to take it, and what load reduction to expect. Your operators review and approve each recommendation. Ampgrove never executes a dispatch action automatically. This design is intentional: for utility operations, an operator-in-the-loop model maintains both regulatory compliance and operational accountability.