RegPermit

A machine-readable, citation-traceable air-regulation and emissions-compliance knowledge layer, plus the workflow outputs it generates: a verified-source regulation corpus (federal 40 CFR subparts alongside state and local rules) that the agent is restricted to answer from; per-facility applicability determinations and Title V obligation sets; generated compliance calendars; permit redline diffs; deviation drafts; stack-test quality-control findings; and automated EPA dispersion-model runs (AERMOD and WebFIRE) with their input file sets and gridded concentration outputs, illustrated on a Commerce City, Colorado site with 1-hour NO2 in ug/m3

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks RegPermit and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Environmental & Facilities ServicesApplication Software
Instruments: equities
Categories

Dataset card

Type: not stated
Format: Multimodal — structured regulatory citations and obligation records, generated documents and redlines, custom workflow definitions, and model input/output file sets with gridded dispersion results over a map basemap
Volume: Regulation corpus spans federal 40 CFR subparts plus state and local air rules across the jurisdictions served; per-facility outputs are workflow-scoped (obligation sets, calendars, redlines, deviation drafts, QC findings) plus full AERMOD runs of roughly a dozen input files each with a gridded output field. Corpus breadth is regulatory-code scale; per-customer output volume is project-paced.
Users: N/A - custom-priced enterprise SaaS scoped per facility with a contact-form entry point; no registration or account count published
History: 2 years
Update frequency: not stated
Growth: Active but earliest-stage - a live product page with a working demo, documented AERMOD execution and cloud plus on-premise deployment options, alongside an explicitly acknowledged pre-certification SOC 2 posture
Launched: ~2024-2026 (the organization record is newly created and the site self-describes as a new company still working through its first SOC 2 audit; no launch date is printed)
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site