One file. Every stakeholder. Any PV system.

The digital
service book
for solar
assets.

DERpass is an open JSON standard that captures everything about a photovoltaic system — hardware, history, contracts, and grid connection — in a single portable file. Installers hand it over. Operators maintain it. Investors, insurers, and grid operators read exactly what they need.

system-home-001.derpass
{ "derpass_version": "1.0", "jurisdiction": { "primary": "DE" }, "meta": { "system_id": "HOME-001", "name": "Musterstraße 12 · PV", "owner": { "name": "M. Mustermann" }, "location": { "country": "DE", "latitude": 48.137, "longitude": 11.576 } }, "commissioning": { "commissioning_date": "2024-05-15", "dc_capacity_kwp": 12.48, "ac_capacity_kw": 10.0, "module_count": 30, "installer": { "name": "SolarBau GmbH", "cert": "ISFH-2023-4412" } }, "inverters": [ { "id": "INV-01", "manufacturer": "SMA", "model": "Sunny Tripower 10.0", "serial": "STP10-2024-00821", "ac_power_kw": 10.0, "installed": "2024-05-15" } ], "modules": { "manufacturer": "Trina Solar", "model": "Vertex S+ TSM-420", "quantity": 30, "wp_per_module": 416 }, "grid_connection": { "ean": "DE0009200000000000000000012345", "mastr_number": "SEE900012345678", "feed_in_tariff_eur_kwh": 0.0825 }, "events": [ { "date": "2024-11-03", "type": "maintenance", "description": "Annual inspection, cleaned modules", "technician": "SolarBau GmbH" }, { "date": "2025-02-17", "type": "fault", "description": "INV-01 overtemp shutdown, resolved" } ] }

Try the viewer

See a passport
rendered.

Drop any .derpass file or pick one of the examples. The document renders in full — components, history, contracts and all. Your file never leaves your browser.

Runs entirely in browser No upload No account
+

Drop file or click to browse

.derpass

A complete record
that travels
with the asset.

Like a car's service book, a DER Passport captures the full life of a power-generating asset — from commissioning, through maintenance events and ownership changes, to eventual decommissioning. When the system is sold or handed over to a new operator, the passport moves with it.

DERpass defines a open JSON Schema for this record. Any tool that speaks JSON can read, write, or validate a DER Passport. There's no vendor lock-in, no proprietary API, no central registry required.

National profiles (currently DE, NL) layer jurisdiction-specific fields — MaStR numbers, VDE norms, EAN codes — on top of the common core, keeping the standard both generic and locally precise.

At a glance
Format
JSON · validated by JSON Schema draft 2020-12
Extension
.derpass
Current version
Core v1.0
Profiles
DE · NL
License
Open

One file, the full
life of the asset.

A 10 kWp residential system — from commissioning day to property sale.

Day 1
Installer

Passport created at handover

The installer uses the AI prompt to generate a DER Passport from the commissioning report. Hardware specs, MaStR number, and feed-in tariff rate are captured in a single file. The homeowner receives one structured file — not a folder of PDFs.

Generate with AI →
+6 months
O&M Provider

Maintenance event appended

The O&M provider opens the same file, appends a maintenance event to the events array, and returns the updated passport. The content-hash chain records the revision — any silent alteration is detectable.

+2 years
Buyer's insurer

Due diligence in seconds

The buyer's insurer validates the file against the JSON Schema. Component ages, maintenance cadence, and insurance coverage are machine-readable. No questionnaire. No missing documentation. The assessment takes minutes, not weeks.

View the schema →

See the difference.

Two sides of the same problem — the people who create the data, and the people who need to trust it.

See how every player benefits →

Built for the
real world of DER.

Portable by design

One .derpass file carries the complete asset record through ownership changes, grid operator handovers, and installer switches.

Open standard

Built on JSON Schema draft 2020-12. Validate with any off-the-shelf library. No central authority, no registration required.

Complete record

Covers components, metering, grid connection, compensation, insurance, contracts, remote access, and a full event log.

+

Extensible

National profiles for DE and NL layer jurisdiction-specific fields. The additionalProperties model lets you add your own without breaking conformance.

Cryptographically verifiable

Events and file revisions carry optional JWS signatures. A content-hash chain links each revision to the last, enabling tamper detection across handovers.

Human-readable

Drop any .derpass into the viewer to get a rendered, printable document — no software install required.

What a DER Passport
contains.

Eight chapters cover most real-world needs — all are optional beyond the four required fields.

I
Site access
Instructions, PPE, hazards
II
Identification
Owner, operator, location
III
Components
Modules, inverters, storage, arrays
IV
Metering concept
Scheme type, meter list, OBIS codes
V
Grid connection
GCP, protection, DSO, voltage
VI
Consumption
Annual demand, controllable devices
VII
Compensation
Feed-in tariff, PPA, net metering
VIII
External control
Curtailment, EMS, protocols
IX
Generation data
Yield, performance ratio, monthly
X
Insurance
Policies, coverage, premiums
XI
Maintenance
O&M contracts, intervals, due dates
XII
Remote access
VPN, APIs, monitoring portals
XIII
History
Commissioning, repairs, owner changes
XIV
Documents
Datasheets, certificates, agreements
XV
File revisions
Passport history with hash chain
XVI
National extensions
Jurisdiction-specific fields (DE, NL)

One format,
every player.

DERpass removes the translation layer between the parties who install, operate, finance, and regulate distributed energy resources.

Installers & Commissioning Engineers
From handover folder to structured record
Before

Commissioning reports lived in PDF folders on a shared drive. Datasheets were scanned, photos stored on personal phones. Handing over to an O&M provider meant emailing a ZIP archive and hoping nothing was lost in translation.

With DERpass
  • All component data — modules, inverters, storage — captured in a single structured file at commissioning time.
  • O&M handover is a file copy. No re-keying, no missing certificates.
  • Service technicians pull up the current system state on-site — components, wiring, metering concept — without calling the office.
System Operators & O&M Providers
From spreadsheet chaos to an auditable event log
Before

Each managed asset had its own spreadsheet — partially filled by the installer, partially by the operator. Maintenance history sat in a ticket system disconnected from asset data. Owner reports required pulling exports from three different tools.

With DERpass
  • The event log records every maintenance visit, repair, and curtailment event with timestamps and technician signatures.
  • Due maintenance dates are machine-readable — feed them directly into any scheduler or monitoring dashboard.
  • Owner reports are generated from a single canonical file, not assembled from multiple exports.
Grid Operators & DSOs
From form-based registration to structured import
Before

Installers submitted grid connection requests on paper or proprietary online portals. DSO staff re-typed nameplate data into internal systems. Transcription errors caused delays, re-submissions, and weeks of back-and-forth before a system could be connected.

With DERpass
  • The grid connection chapter includes GCP ID, voltage level, protection relay settings, and DSO contact — structured and importable.
  • Metering concept is machine-readable: scheme type, meter list, OBIS codes, and feed-in direction.
  • National profiles (DE: MaStR/BNetzA, NL: EAN/E17) map directly to registration system fields with no re-keying.
§
Lawyers & Notaries
From paper trail to cryptographic provenance
Before

Ownership transfers required collecting scanned contracts, installer certificates, and grid approval letters from multiple parties. Establishing a clean chain of title for a PV asset could take weeks, with gaps in the record being the norm rather than the exception.

With DERpass
  • The revision history chapter records every ownership change with date, parties, and document reference — linked by a hash chain so alterations are detectable.
  • Contracts, insurance policies, and grid approval documents are linked in the Documents chapter with content hashes.
  • Optional JWS signatures on events let parties prove authorship without relying on a central notary.
Investors & Asset Finance
From weeks of due diligence to hours
Before

Assessing a distributed PV portfolio meant requesting technical data from installers, yield reports from operators, and contracts from owners — all in incompatible formats. Data rooms contained PDFs that could not be queried. Bankability assessments stretched over weeks.

With DERpass
  • One file per asset contains the full technical specification, measured yield, performance ratio, and O&M history.
  • The compensation chapter captures feed-in tariff rates, PPA terms, and contract expiry dates — queryable across an entire portfolio in seconds.
  • Insurance coverage and maintenance contracts appear in every conforming file, reducing the due-diligence checklist to a schema validation.
Insurers & Risk Assessors
From questionnaires to structured asset data
Before

Underwriting a PV asset required sending questionnaires to the owner, waiting for answers, and manually verifying them against whatever documentation could be found. Component age, maintenance frequency, and grid protection settings were rarely available in a consistent format.

With DERpass
  • The components chapter provides manufacturer, model, serial number, and installation date for every device — no questionnaire required.
  • The event log shows the actual maintenance cadence and any incidents without relying on the owner's recollection.
  • The insurance chapter records existing policies, enabling renewals and portfolio checks without re-submitting data from scratch.
View all players →

From zero to passport
in three steps.

01

Get the schema

Download the JSON Schema and use it to understand the structure. Any JSON Schema validator will tell you whether your file is valid.

core/v1.0/schema.json
02

Create your file

Only four top-level fields are required: derpass_version, jurisdiction, meta, and commissioning. Add sections as you need them.

"derpass_version": "1.0" "jurisdiction": { "primary": "DE" } "meta": { … } "commissioning": { … }
03

Open in the viewer

Drop your .derpass file into the viewer to see it rendered as a structured, printable document. No upload, no account — runs entirely in your browser.

Open Viewer

Companies building
on DERpass.

Software tools, platforms, and services that produce, consume, or validate .derpass files.

Installer Software

SolarDoc

Commissioning workflow tool that exports a valid DER Passport at job close — modules, inverter specs, and grid data captured in one step.

O&M Platform

FleetWise

O&M management platform that ingests DER Passports at asset intake, appends maintenance events, and returns updated files to asset owners.

Grid Operator Portal

GridLink

DSO connection portal that accepts DERpass grid connection chapters as structured import — no PDF form, no manual re-keying of nameplate data.

Portfolio Analytics

DERinvest

Investor due-diligence tool that aggregates technical specifications, yield history, and compensation terms from DER Passport files across entire portfolios.

Insurance Platform

SolarGuard

Underwriting platform that validates DER Passport files to extract component age, maintenance cadence, and existing coverage — replacing owner questionnaires.

Asset Management

PassportHub

Cloud storage and indexing service for DER Passport files — search, version, and share structured asset records across organisations and ownership transitions.

Common questions.

Is DERpass free to use?+
Yes. DERpass is an open standard — the schema, the examples, and this website are all published under an open license. There is no registration fee, no subscription, and no commercial dependency. Anyone can read, write, and validate .derpass files using off-the-shelf tooling.
Do I need a central server or cloud account?+
No. DERpass is a file format, not a platform. A .derpass file lives on your filesystem, your own server, or wherever you choose to store it. There is no central registry, no API to call home to, and no account to create. The Viewer on this site runs entirely in your browser — your file never leaves your device.
What tools can read and write .derpass files?+
Any tool that handles JSON. The Viewer renders any valid file as a structured, printable document with no install required. For programmatic access, use any JSON Schema validator (ajv, jsonschema, Newtonsoft.Json.Schema, etc.) to check conformance, and plain JSON parsing to read or write. You can also generate files from plain-language descriptions using an AI model.
Can I add fields that aren't in the schema?+
Yes. The schema uses additionalProperties throughout, so you can attach your own fields at any level without breaking conformance. We recommend prefixing custom fields with your organisation's namespace (e.g. x_acme_voltage_offset) to avoid collisions with future schema versions.
Which countries does DERpass support?+
The core schema is jurisdiction-neutral and works globally — any country can be expressed using ISO 3166 codes and the common chapter structure. National profiles for Germany (DE) and the Netherlands (NL) add jurisdiction-specific fields: MaStR numbers, VDE norms, and EAN codes for Germany; SDE++ references and E17 EAN codes for the Netherlands. Additional profiles are under discussion.
Can DERpass describe battery storage, EV chargers, or other DER types?+
The current schema is designed around photovoltaic systems but already includes battery storage as a first-class chapter (capacity, chemistry, cycle count, inverter references). Wind, EV charging, and other distributed energy resource types are on the roadmap as additional profiles that extend the common core.
Who maintains the standard?+
DERpass is developed and published openly at derpass.org. The schema is versioned — currently Core v1.0. Minor additions are backwards-compatible; breaking changes increment the major version number. A file always declares the version it was written against ("derpass_version": "1.0"), so older files remain valid and readable against the version they reference.

Try the viewer now.

Drop any .derpass file and see it rendered as a complete, structured document — components, history, contracts and all.

Open Viewer Schema Reference