One data model for solar developers, owners, EPCs and operators. Public data about land, grid and rules is built once and kept current. Your projects sit on top of it. Score every site, re-score the pipeline when the rules or the grid change, track the dates that carry money, and keep the evidence that goes with them.
Transmission lines and substations, feeder hosting capacity over time, interconnection queues, wetlands, flood zones, protected land, habitat, soils, energy communities and program areas, zoning. Elevation, land cover, irradiance and aerial imagery. Wage determinations, credit rules and program rules as tables with effective dates. Zoning bylaws read by Aquifer AI, each value with its citation.
Each project with its technology, size, mount, offtake, program and stage. Its interconnection requests, site control, permits and tax credits. Installed quantities by block and week. Every fact with the record, document page or person it came from and the date. Your data never goes into the shared reference layer.
The grid, the land, the programs and the rules are built once and kept current for everyone. Your projects stand on that layer in your own account, and nothing of yours goes into it. Underneath, the dates that carry money, each with the room left before it.
Technology, DC and AC size, storage, mount, offtake type, program and stage, linked to the site candidate it came from and to the project record every other app uses.
The utility or grid operator, the queue position, the point of interconnection, the study stage, study costs and deposits, the upgrade cost allocation, agreement dates, and the steps left to permission to operate.
Parcels, the counterparty, the type of agreement, the term, option expiry, rent and escalators, and the obligations that come with them.
The authority, the type, the status, application and decision dates, the statutory clock, hearings, conditions and expiry dates. The same object serves any project that needs a permit.
The credit claimed, the begin-construction method and date, the continuity deadline, the placed-in-service-by date, adders, prevailing-wage and apprenticeship status, and sourcing ratios, each with the evidence behind it.
Each fact about a project, from each source that states it, with the record, document page and quote or the person it came from, the date, and whether it was accepted. Two sources that disagree are flagged, never merged.
Piles, racking, modules, wiring, inverters and energized blocks by location, activity or cost code and date, from the field or from forms, rolled up against the schedule of values.
Hard exclusions with their reasons, weighted metrics, and an optional calibration to your own outcomes. Every score names the version of the definition it used, and re-scores only when something it depends on changes.
Every potential site scored against land, grid and rules. The pipeline re-scored as rules and grid capacity change. Deadline and tax-credit tracking with the buffer left on each date. The interconnection record for every request.
A site report for any polygon for the bid. Weather-delay evidence from weather records against the schedule and the daily log. Prevailing-wage evidence from payroll against the county determination. Installed quantities rolled into the pay application. The handover package.
Weather alerts per site, technician routing, production against expected output, and an asset record per inverter and transformer with its warranty.
Placed-in-service-by and continuity dates, option and permit expiries, interconnection agreement deadlines and program deadlines for every project, each with its slip history and the buffer left, and an alert when a forecast crosses one.
Begin-construction evidence, the continuity log, prevailing-wage and apprenticeship records against the wage determination, domestic content and sourcing records, assembled as the work happens and kept current for tax equity, credit buyers and auditors. Evidence, not tax advice.
Weekly quantities per block roll up against the schedule of values and drive the pay application and earned value, shown on the site model in Studio.
One record per request with its study stage, costs, deposits and upgrade allocation, values read from the study PDFs with page citations, and public queue data and hosting-capacity maps on the same map.
As-built drawings, equipment and serial lists, commissioning tests, warranties and O&M documents for handover. The same package plus site control, permits, interconnection agreements and the tax-credit binder for a sale.
The deadline tracker, the portfolio map and the evidence pages.
Read about Canvas →Site scoring maps, the site model and installed quantities on it.
Read about Studio →Certified payroll for prevailing-wage evidence, and progress billing from installed quantities.
Read about Accounting →The handover package, with the asset record behind it.
Read about Coordination →Slip history and the critical path through interconnection and construction.
Read about Scheduling →Reads studies, leases, certificates and bylaws into the model, each value with its citation.
Read about Aquifer AI →Does our data go into the shared reference layer?
No. Reference data is public and shared. Your projects, scores and outcomes live in your own account. Your scores are computed over the shared metrics but stored only in your account, so your data stays private.
What happens when the rules change?
Rules are tables with effective dates, not code. A new wage determination, a changed threshold or a program block update changes the table, and only the metrics, scores and alerts that depend on it are recomputed.
Can an EPC use it without being a developer?
Yes. The bid site report, weather-delay evidence, prevailing-wage evidence, installed quantities to billing and the handover package need none of the development objects. They work from your projects and the public reference data.
Which parts are AI?
AI reads what is unstructured, such as zoning bylaws, study PDFs, leases and certificates, and each value it reads carries the document, the page and the quote it came from. The scoring is rules, weighted metrics and statistics you can inspect, with an optional calibration to your own outcomes.
We use a small number of first-party cookies to understand which pages visitors find useful. No advertising, no third parties. Privacy notice
