Partners & Portals

Your brand. Our engine.

Licence CLRD as a portal under your own name, or build it into the software installers already use. You take it to market and own the relationship. CLRD stays in the background and gets every DNO job done.

Two ways to partner

On the front with your brand, or inside your product.

Either way you own the customer. CLRD is the part they never have to think about.

A portal under your brand

Your name on the front.

Licence CLRD as a DNO application portal in your own name: for an independent network operator, a distributor or an installer programme. Installers see your brand. Behind it, CLRD routes, builds, submits and tracks every application.

Built into your software

Your product, doing the DNO work.

Connect a CRM, job platform or installer app over the CLRD API. Jobs go in from your system, and packs, DNO replies and every status change come back to it. Your users never leave your product.

The API

Everything a DNO job needs.

  • Clients, sites and jobs created straight from your own system.
  • Equipment looked up against CLRD's mirror of the ENA registers, generation and load, kept current.
  • Packs generated and downloaded, a document at a time or whole.
  • Submitted to the DNO, with their replies read and answered over the API.
  • Client signatures requested, single line diagrams and site maps supplied.
  • Several companies run from one account, for groups and agencies.

Full reference at clrd.app/api-docs.

Built to be relied on

An API you can put your name on.

  • Versioned. A breaking change only ever ships as a new version at its own address; v1 only gains fields.
  • Every version supported for at least a year after it is deprecated.
  • Each response checked against the published contract on every change we make.
  • Signed webhooks on every status change, with secrets you can rotate and delivery tracking.
  • Safe retries: calls that change something take an idempotency key, so a retry never does it twice.
  • Keys hashed at rest, revocable, read-only if you want, and lockable to your servers' addresses.

The API in use today

DNO work, run from a CRM.

Depth of Light send their jobs to CLRD straight from their own CRM. This is what that looks like.

Case study

Depth of Light · Matt

Forty-five minutes of re-typing, now seconds.

CLRD's Auto-DNO API pulls straight from our job data, so a G98/G99 submission that used to be 45 minutes of re-typing now takes literally seconds to generate the pack and submit. It's totally changed the way I work from my CRM.

28

Applications filed since June

20 sec

Fastest job through the API, start to filed

6 operators

Three DNOs and three IDNOs

Who it's for

Anyone installers already work through.

If installers come to you for kit, software or a connection, CLRD can sit behind it.

Network operators

A branded application portal for installers connecting to your network, every submission built to the ENA forms before it reaches you.

Manufacturers

Make your kit the easy choice. Every device on the ENA register is already in CLRD, referenced correctly in every pack.

Distributors

Offer the DNO paperwork with the kit. Licence CLRD under your name for your trade accounts.

CRM and job platforms

Add DNO compliance without building it. Your customers stay in your product while CLRD does the DNO work.

Installer programmes

One standard across every installer in your network: the same rules, the same pack, on every job.

Software and portal builders

Put a complete DNO application flow inside your own portal, with CLRD as the engine behind it.

How it works

How a partnership comes together.

01

Scope

We work out where CLRD fits: a branded portal, an integration, or both.

02

Build

Your team builds against the documented API, with our engineers alongside for the integration.

03

Go live

We launch with you, with direct technical support throughout.

04

Kept current

When the ENA forms or a DNO's requirements change, CLRD changes with them, and your integration keeps working.

Tell us what you're building.

Using the API for your own company is included on Volume Operations and Multi Team Operations. Licensing CLRD under your brand, or building it into a product you sell, is under a partner agreement, priced to the integration.