Permitting · parcel triage
A data center parcel is not just a zoning question. The permit stack changes with load size, local entitlement posture, generator fleet, water use, wetlands, utility service, interconnection product, and incentives. This v1 turns those facts into a preliminary checklist and shows what Cliff would source-verify next.
Live tool
The exact answer requires county GIS, zoning ordinances, flood and wetlands layers, utility territory, state agency records, and ISO or utility process documents. The instant output tells a developer what to investigate first and where the critical path is likely hiding.
Parcel input
v1 does not geocode APNs yet. It turns a parcel or address plus project facts into a source-backed checklist for the diligence work.
Fast presets
Preliminary output
The parcel still needs geocoding against county, city, zoning, flood, and utility territory records. This is a triage read, not a permit opinion. The next step is source verification against parcel, agency, and docket records.
Category load
Local land use · Needs parcel source
Local land use · Likely
State environmental · Likely
Power and utility · Scenario dependent
State environmental · Likely
Federal floor · Likely
State environmental · Scenario dependent
Local land use · Likely
What Cliff would verify next
Market check
The category exists around the edges. Generic construction permitting, environmental due diligence, zoning/code feasibility, and data center siting all have real companies. The sharper Cliff product is parcel-specific site readiness for data centers, with every conclusion traced to the source record.
Public product
Construction permitting workflow, AHJ research, submittals, tracking, and inspections across contractors, developers, architects, and homebuilders.
Strong generic permitting surface. Cliff's wedge is the data-center-specific stack: power, interconnection, air, water, and live dockets in one cited readout.
Public product
Parcel or KMZ site assessments with federal and state environmental permits, waters, species, flood hazards, and regulator contacts.
Closest adjacent product. Cliff should not copy environmental due diligence; it should join that layer to data center power and approval economics.
Public product
Address and parcel feasibility for building, zoning, code, and high-volume permit issuance workflows.
Useful for ordinary construction and code checks. The missing layer is industrial-scale site readiness for 20-500+ MW loads.
Public product
Data center siting, grid-capacity, parcel intelligence, environmental overlays, and transmission-capacity analysis.
They own important upstream siting layers. Cliff should sit downstream at the permit-stack and regulatory-work-product layer.
Why this can be AI-native
A static checklist is not defensible. The defensible system ingests county ordinances, GIS parcel records, PUC and PSC filings, ISO/RTO tariffs, state air permits, wastewater rules, incentive agreements, board packets, and public comments, then produces a project-specific memo with citations.
Source types
10+
Buyer question
Can this site clear?
Moat
Approval corpus
That is the version to sell at DICE: not "we have a permitting search box," but "send a parcel and a load plan; Cliff returns the source-cited site-readiness memo your investment committee and counsel can interrogate."
Existing permitting pages: state pages · turbine siting · gas feasibility
Parcel diagnostic
Address or APN, planned MW, generator plan, cooling/water assumptions, and target COD. Cliff returns a cited permit-stack memo and the top three critical-path risks.