ENRORequest a demo

For funds, advisers and developersRomanian energy projects

Evidence-first due diligence for energy projects.

Know what the documents establish, what is missing, what conflicts, and what to request next.

Request a demoSee how it reads a permit
  • p. 3The page and sentence behind each figure
  • AwaitingAmbiguous figures wait for a person to decide
  • PilotFounding pilot programme - limited availability

The product

How ELARID handles one figure.

A solar project from the demo organisation, read from a public grid-connection permit.

1 / 3

The figure, with its unit and its page.

ELARID finds the approved export capacity in the permit. It keeps the unit and the page, and shows beside it the comparison the verdict uses.

What we know

The verdict rests on:

  • Kind of site: Consumption and generation p. 1 awaiting confirmation
  • Connection permit issued: 2025-08-19 p. 1 to confirm
  • Export capacity · approved:398.8 kWIdentified figure (0.3988 MW ≤ 1 MW)p. 3 awaiting confirmation

The sentence it was read from.

“p. 3” opens the permit where the figure was read. Every figure keeps that sentence, so anyone can check it in one click.

Export capacity · approved: 398.8 kWp. 3Source
Aviz Tehnic de Racordare (ATR) nr. •••••• din 2025-08-19p. 3

simultană ce (kW) 0,000 398,800 398,800 398,800 398,800 398,800

Redrawn from the row ELARID quotes for this figure

What has to be confirmed first.

The guarantee verdict waits until a person confirms the reading it rests on. Until then, ELARID names what to confirm first.

Guarantee: awaiting confirmation

ELARID does not state the guarantee verdict yet - it rests on a reading a person has to confirm: What this connection is for, Connection permit issued, Export capacity · approved

What to request next

Confirm first: What this connection is forClarification needed

7 readings to confirm in all

The frame is a detail of the full project page, which also answers what is not known, what could affect the deal and what to request next.

Open the full project page

Project page · Demo environment · public documents only

ELARID project page from the demo organisation: the guarantee awaits confirmation; four cards answer what we know, what we don’t know, what could affect the deal and what to request next; below, what would follow once the reading is confirmed.

The problem

Before anyone signs, someone has to read every page.

The permit
The grid-connection permit (ATR) decides how much power a project may export. It can be a scanned PDF, with tables that break across pages.
The comma
The same figure is written differently from one document to the next, and a comma can make it a thousand times larger.
The volume
For ten projects that is hundreds of pages read by hand, and one misread figure changes the decision.

Example · a public grid-connection permit from 2024

The same figure, read two ways.

The figure comes from a real permit that a public authority published. Names are left out. Open “p. 3” to see the original rows.

ATR · page 3bottom
……
Puterea maximă179,280
(kW)
simultană ce
ATR · page 4top
poate fi
evacuata
Puterea maximă ……
The original rows, as published

The number can be read in two valid ways from this document.

1000× apart

Grid-connection permit (ATR), 2024 · p. 3, row continues on p. 4Puterea maximă simultană ce poate fi evacuata

Awaiting confirmationChoose reading A or B, then record it.

ELARID does not choose. A person records the reading with a reason, and it stays on the record with their name.

The original rows, as published

ATR · page 3 · bottom
Bottom of page 3 of the permit: the table of approved power. The row “Puterea maximă simultană ce”, in kW, gives 179,280 for each of the five stages.
ATR · page 4 · top
Top of page 4: the label ends with “poate fi evacuata” on the kVA line, which gives 0,000 for the existing situation and 179,280 for each stage.

Cropped from the public permit. The rest of each page is not shown, and the highlight is ours.

How it works

How a document is read.

  1. Claim

    Documents are read with their tables and scanned pages. What a document states becomes a claim: a power, a date, an amount, a condition.

  2. Evidence

    Each claim keeps the exact sentence and page it came from. One click opens the original at that page.

  3. Conflict

    When documents disagree, both claims stay on screen, each with its source. Nothing is overwritten.

  4. Reviewer

    A person settles what the documents leave open. The decision is recorded with the person’s name, the time and the reason given.

For each project: what is established, what is missing, what conflicts, and what to request next.

Regulatory conclusions are versioned, evidence-linked and designed to surface unresolved legal applicability rather than guess.

Limits

What ELARID will not do

  • Guess a figure the document leaves ambiguous.
  • Fill a missing value with an assumption.
  • Show an amount when its inputs are not established. It says what is missing instead.
  • Overwrite what a document said.
  • Replace legal advice.

Security and data

Where your documents would go, and what is not ready yet.

Each line is marked: in place, demo only, built but not yet enabled, or not yet enabled. Based on our data-handling statement, version 0.3 (draft), 25 October 2026.

Today

A demo on our own machine. Public and synthetic documents only. The product is not hosted yet.

Demo only
Storage

Documents are encrypted before storage. Each time the product serves a document or what was read from it, the access is recorded first.

In place
AI provider

No AI provider reads an organisation’s documents until it is authorised. Model calls go to Google’s Gemini API, which is not pinned to the EU.

Demo only
Pilot

Documents and the database in the EU, and the model only through Google’s EU endpoint. Parts of this are built and tested; no server, database or storage for a pilot is provisioned yet.

Not yet enabled
Full details

Demo today

On our own machine. The product is not hosted yet.

  • Public and synthetic documents only. Each upload asks the person to confirm it, and the wording is recorded.In place
  • Documents are encrypted before storage: AES-256-GCM, a new key for every write.In place
  • The database, which holds the page text and the findings, is not encrypted at rest.Demo only
  • Each time the product serves a document or what was read from it, the access is recorded first.In place
  • No AI provider reads an organisation’s documents until it is authorised. There is no fallback provider.In place
  • Model calls go to Google’s Gemini API, which is not pinned to the EU.Demo only

Confidential pilot architecture

Provisioned only for an agreed pilot.

  • Managed PostgreSQL in Frankfurt (EU), with point-in-time recovery.Not yet enabled
  • Documents in object storage in Nürnberg, separate from the server.Not yet enabled
  • Model calls only through Google’s EU endpoint (Vertex AI), with no other provider to fall back on.Built · not yet enabled
  • A daily encrypted backup to separate storage in Falkenstein (EU).Built · not yet enabled
  • A restore performed on the pilot’s own infrastructure.Not yet enabled
  • A whole engagement erased in one command, with a receipt.Built · not yet enabled

We accept a real document only after nine conditions are met. The list is on the Security page, with the status of each.Read the full statement

Contact

See ELARID on public Romanian project documents.

Request a demo[email protected]

Founding pilot programme - limited availability.

What you will see

  1. A project from our demo organisation, built from public documents, and its four answers: what we know, what we don’t know, what could affect the deal and what to request next.
  2. A figure followed back to the page and the sentence it was read from.
  3. A figure that can be read two ways, and how a person records the reading.
  4. Where your documents would be kept in a confidential pilot, and what is not ready yet.

The demo uses public Romanian project documents, so you can see the product without sending us anything confidential.