Aura

Aura — engineered by ASAPTech

The audit-ready
agentic layer for
energy benchmarking.

Built for building portfolios reporting under Massachusetts BERDO 2.0 and Connecticut benchmarking programs — EUI against regulatory targets, GHG reduction trajectory, and retrofit ROI by comparable buildings.

Buildings emit 37% of global energy-related CO₂[1]. Regulators know it. Lenders know it. LPs know it. What none of them can tell you is whether the kilowatt-hour on your latest utility bill survived OCR without drift, whether the eGRID factor you multiplied it by is the right vintage for the county, or whether the Scope-2 method on this filing is the same one you signed off on last quarter[H].

Aura answers each of those questions, in writing, and leaves the cited evidence behind every answer.

01encoded · primary-source PDFs version-pinned
12frameworks[G]
02cite-coverage · CI fails without @cite
100%[R]
03two-person rule · all outbound actions
2-of-2[P]
04pilot readiness report · human reply
48hSLA[P]

Stats describe the product's engineering posture, not customer count — Aura is in pilot. Market traction belongs on the case-study page when it earns one.

§ 02Operating posture

Build for the
audit you haven't
had yet.

Three rules we don't break

¶ 01Every figure ships with its provenance: source PDF, page, bounding box, extraction model, confidence score, and the human or system that signed it. The methodology drawer isn't a feature behind the number — it is the number[R].

¶ 02Every filing is snapshot-pinned at compile time. The diff against the prior submission is reviewed and signed before send. Two-person rule on anything outbound — files, emails, money[P].

¶ 03Every regulation is encoded from the primary source. We mirror the canonical PDF, version-pin it, and cite the §. A watch-list monitor opens a ticket the moment the source text changes — because SFDR 2.0, CSRD simplification, and CA SB 261 are still moving[S].

Compute the number
once. Cite it
forever.

— Operating principle · Aura
§ 03Four modules — one operating posture

Numbers your auditor doesn't flag,
retrofits your IC actually approves —
and the receipts behind both.

01 / 04REQ-DATA-051

Ingest.

Every kilowatt-hour, with its receipt.

Utility bills, lease abstracts, energy audits, meter feeds, ESPM exports. Two OCR engines vote independently — disagreements queue for human review, never quiet-default. Every field carries its source PDF, page, bounding box, model version, confidence score, and the reviewer who signed it off.[R][Y]

  • Dual-OCR consensus
  • ESPM v26.0
  • ASHRAE 211
02 / 04REQ-PROD-002

Intelligence.

Retrofits priced to the dollar, dated to the law.

Each measure is ranked by hold-period-aware ROI, CRREM stranding delta, and emissions impact. Incentives are line-itemized — IRA § 48, § 179D, C-PACE, and local utility rebates priced into the cash flow before the IC ever sees the page. The model recommends; the operator approves.[C]

  • CRREM v2
  • EnergyPlus
  • IRA §48
03 / 04REQ-COMP-032

Compliance.

Filings that survive last quarter's diff.

GRESB, CRREM, PCAF, CSRD/ESRS E1, IFRS S2, NYC LL97, BERDO 2.0, CA SB 253. Each filing is snapshot-pinned at compile time. The diff against the prior submission is reviewed and signed before send. Nothing leaves the building without its methodology drawer attached.[H][P][E]

  • GHG Protocol
  • PCAF 2025
  • CSRD
04 / 04REQ-AI-041

Agent Aura.

An agent that works through approval, not around it.

Claude-powered. Every tool call is gated by an approval token. Two-person rule on filings, on spend over $10k, and on any change to a published number. Every assistant response cites the section, the page, and the version of the regulation it leaned on — or it does not ship.[A]

  • Claude
  • HITL
  • Two-person rule
§ 04Standards — primary-source, version-pinned, watched

Every framework.
Every § cited.

The canonical PDF is mirrored, hashed, and indexed. A regulated value cannot leave a compliance package without a @cite annotation pointing back to the section it came from — CI refuses to ship the build. Each tile below opens its source.

2026 Regulatory watch-list

  • δ1SEC Climate Rule — defense ended March 2025. Optional.
  • δ2SFDR 2.0 — product-level PAI only, entity PAI removed.
  • δ3CA SB 261 — Jan 2026 deadline not enforced (9th Cir.).
  • 01 · RE Standard 2026

    GRESB

    Real Estate Assessment

  • 02 · v2 (2023, 2025 downscale)

    CRREM

    1.5°C pathways, 44 countries

  • 03 · 3rd Edition, Dec 2025

    PCAF

    Financed emissions — CRE + Mortgages

  • 04 · Corporate + Scope 2 Guidance

    GHG Protocol

    Market-based & location-based

  • 05 · 2023, effective 2024

    ISSB IFRS S2

    Global baseline

  • 06 · Reg (EU) 2023/2772

    CSRD · ESRS E1

    Climate change disclosure

  • 07 · Effective 2024-

    NYC LL97

    $268 / tCO₂e over limit

  • 08 · 2025 / 2030 phase-in

    Boston BERDO 2.0

    Net-zero by 2050

  • 09 · CARB final 2026-02-26

    CA SB 253 · 261

    SB 253 due 2026-08-10

  • 10 · Net-Zero + Buildings

    SBTi

    Target-setting

  • 11 · Reg (EU) 2021/2139

    EU Taxonomy

    Climate Delegated Act

  • 12 · v1.0

    TNFD

    Nature-related (watch)

§ 05Proof — provenance, not logos

This is what
one number
looks like on its
way to a regulator.

Most platforms put their proof in a logo wall. We put ours in the audit trail. Below is the lifecycle of a single Scope-2 figure — ingestion through filing — exactly as Aura records it. Six steps, each independently citable, each independently replayable.

  1. T+0step 01 / 06

    Source pinned.

    Canonical PDF mirrored — PCAF Part A, 3rd Ed. (Dec 2025) — SHA-256 fingerprinted, version-locked, change-watched.[P]

  2. T+1step 02 / 06

    Bill ingested.

    Two OCR engines vote independently. kWh delta under 0.1%, both extractions signed. Disagreements queue for review — they never quiet-default.[R]

  3. T+2step 03 / 06

    Grid factor resolved.

    eGRID subregion vintage selected by county and delivery month. The lookup carries its own provenance record alongside the kWh.[H]

  4. T+3step 04 / 06

    Method matched.

    Scope-2 market-based, identical to last quarter’s filing. Method-drift diff against the prior submission: ∅. If it weren’t, this filing would not compile.[H]

  5. T+4step 05 / 06

    Filing snapshot-pinned.

    Tagged 2026-Q1.gresb. Immutable. Methodology drawer attached. Replay any number on this submission, six years from now, byte-identical.[G]

  6. T+5step 06 / 06

    Two-of-two sign.

    IC and Head of ESG. Both keys touched. Approval token bound to the snapshot hash. Audit log written before send — not after.[P]

Engineering pedigree

Built by ASAPTech.

ASAP Tech LLC has spent the last five-plus years putting data, AI, and cloud platforms into regulated industries — energy and utilities the longest. Aura is the team's opinionated answer to a question they kept being asked: what does an auditable AI workflow actually look like?[P]

  • Founded2018
  • Regulated-industry projects20+
  • CertificationsISO 9001 · ISO 27001
  • USA HQChester Springs, PA
  • India deliveryPune, Maharashtra
  • HyperscalersAWS · Azure · GCP
§ 06Trust — parent posture, product posture

Two stacks
of evidence,
same standard.

Aura inherits its compliance backbone from ASAPTech, a global digital, data, and AI engineering firm with active ISO 9001:2015 and ISO/IEC 27001:2013 certifications. Aura's own attestations sit on top — Type I in hand, Type II on the audit path, signed SBOMs per release, HSM-backed envelope keys, BYOK. We say what is shipped and what is on the way, separately.

ParentASAPTech LLC · live
  • P1ISO 9001:2015Quality management — ASAPTech
  • P2ISO/IEC 27001:2013Information security — ASAPTech
  • P3Chester Springs, PAEST · strategy & delivery leadership
  • P4Pune, INIST · ISO-certified delivery center
  • P5AWS · Azure · GCPHyperscaler partnerships
  • P6Databricks · SnowflakeData platform partnerships
ProductAura · build-stage
  • A1SOC 2 Type IIAudit path · Type I attested
  • A2GDPR · CCPAData residency US · EU · UK · APAC
  • A3SLSA Level 3Signed SBOM per release
  • A4FIPS 140-3 L3HSM-backed envelope keys (BYOK)
  • A5OWASP ASVS L2Application security verification
  • A6WCAG 2.2 AAAccessibility — verified per release
§ 07Access — pilot intake

Send one bill.
Read every footnote.

Drop in a utility bill and a property record. Within 48 hours you'll get a written readiness report against LL97, BERDO 2.0, and CA SB 253 — with §-level citations on every figure and the methodology drawer attached. No pricing wall. No lead-capture theatre. The reply comes from an engineer, signed.

Human reply · SLA 48h