Skip to content
Oryft

Utility data infrastructure · In development

Utility data.
Connected.

Oryft is building the connection layer between utility accounts and the businesses customers choose to share with.

Explore the connection
Sample connection: utility account to Oryft to your applicationIllustrative diagram with sample data. Bills, usage and account details flow from a sample utility account, through Oryft, to your application as normalized fields.SourceSAMPLEUtility accountacct ···· 4821electric · residentialsep bill · $142.18bill · PDFusage · CSVportal exportconsent · normalize · deliveramount_due 142.18usage_kwh 612.4status activeDestinationYour applicationscopebills, usage, accountstateauthorized (sample)Illustrative
Sample data — no live utility connected

01The problem

One connection. Less chasing.

Getting utility data today usually means asking customers for paperwork, decoding it by hand and maintaining a patchwork of integrations.

Today

  1. 01

    Manual bill collection

    Teams ask customers to upload PDFs or forward statements, then follow up each time a month goes missing.

  2. 02

    Fragmented formats

    Every utility presents bills, usage and account details differently, so each source needs its own parsing.

  3. 03

    Connection upkeep

    Portals change, logins expire and one-off integrations quietly break, leaving gaps nobody notices until later.

Proposed

Customer-authorized, standardized access.

The customer grants scoped permission once. The application receives available data in one consistent shape, and the customer can withdraw access at any time.

02How it will work

Permission in. Useful data out.

The planned flow keeps the customer in control at every step, from choosing a provider to deciding what is shared.

  1. 1

    Customer chooses their provider

    Inside your application, the customer will select their utility from the providers Oryft supports. Coverage is expected to grow through pilots.

  2. 2

    Customer authorizes scoped access

    They will see what is shared, with whom and for how long, and approve only that. Nothing outside the scope is requested.

  3. 3

    Your application receives normalized data

    Where a provider makes it available, bills, usage and account details are intended to arrive in one consistent format.

Planned capability. Provider coverage, data availability and access methods will vary and will be confirmed during pilots.

03Interactive sandbox

A connection, explained.

Step through a simulated connection: grant sample access, see what an application could receive, then revoke it.

Disconnected

No sample access granted

No sample connection yet

Connect the sample account to see what an application could receive once a customer grants access.

Source: Sample data — no live utility connected

04Who it's for

Built for the teams building next.

Oryft is being designed for both sides of a connection: the software that uses the data and the utilities that hold it.

Software teams

For energy, finance, property and climate products that need utility data with the customer's permission.

Intended capabilities

  • One planned integration instead of many provider-specific ones
  • Consistent fields for bills, usage and account details
  • Consent status you can check before relying on the data

Utility partners

For utilities that want to give customers a governed, traceable way to share their own data.

Intended capabilities

  • A permission model customers can understand at a glance
  • Visibility into which applications hold access, and for what
  • Fewer ad-hoc requests for statements and exports

Utility admin · concept

Connected applications

Planned · sample data

Permission controls

Planned

  • Example Energy App

    Bills, usage · expires in 84 days

    Active

  • Sample Solar Planner

    Usage · expires in 21 days

    Active

  • Demo Property Portal

    Account · expires in 160 days

    Suspended

Audit trail

Planned

  1. Example Energy App granted bills, usage

    Oct 18 · 14:06

  2. Demo Property Portal suspended by admin

    Oct 17 · 09:41

  3. Sample Solar Planner granted usage

    Oct 15 · 16:22

Conceptual view with sample data. Not a live product.

05Design principles

Trust starts with permission.

These are the principles Oryft is being designed around. They guide what we build and what we will ask pilots to test.

  • Scoped consent

    Customers approve specific data, for a specific recipient, for a specific period. Nothing broader is implied.

  • Revocation

    Withdrawing access should be as easy as granting it, and sharing should stop when access is withdrawn.

  • Traceability

    Each grant, change and revocation should leave a record that customers and partners can review.

Status

Oryft is in development. Coverage, access methods, and security controls will be validated during pilots.

06Pilots

Help shape the first connection.

Oryft is looking for a small number of software teams and utility partners to define early connections together.