DataBridgeEU
Sign inStart building
Data access infrastructure for connected products

Unlock your product data — without rebuilding your backend.

DataBridge gives manufacturers a secure, standardised layer for exposing product-generated data to owners, service providers and third-party applications. Connect the systems you already run, and get ownership, consent, scoped access, revocation and audit records as infrastructure.

Start buildingView API
Connectors
REST · Postgres · Webhook · CSV
Export formats
CSV and JSON
Access model
Scoped, expiring grants
Records
Append-only consent and audit

Connected products generate data that nobody can safely share

The engineering is rarely the hard part. The hard part is proving who is entitled to what, for how long, and being able to show it afterwards.

The data exists, but nobody can reach it

Telemetry lands in a database, a broker or a vendor cloud that was never designed to be opened to customers or their service providers.

Every request becomes a project

A fleet operator asks for their own machine data and it turns into a CSV someone assembles by hand, an FTP drop, and a support thread.

Access with no way back

Once an integrator has a database credential, there is no scope, no expiry, and no record of what they read.

How it works

Four steps from an existing backend to a governed access layer.

  1. 01

    Connect what you already run

    Point DataBridge at your REST endpoint, PostgreSQL replica or event stream. Nothing on the device changes.

  2. 02

    Map your payload once

    Translate temp1 into temperature in °C, classified as operational data. The mapping is the contract everything else reads.

  3. 03

    Owners get their data

    Each product owner signs in, sees the units they own, inspects live values and exports history as CSV or JSON.

  4. 04

    Third parties get scoped access

    A repair service requests diagnostic data for 30 days. The owner approves. The API enforces it, and revocation takes effect immediately.

What your system already sends

{
  "machine": "ABC123",
  "temp1": 71.4,
  "runhrs": 4421,
  "err": "0"
}

What DataBridge exposes

  • machinedevice.serialNumberidentifier
  • temp1temperature°Coperational
  • runhrsoperating_hourshmaintenance
  • erralarm_codediagnostic

One layer, three parties, one set of rules

For manufacturers

  • One access layer for every product line, without touching device firmware
  • Ownership recorded as history, so transfers and resales stay traceable
  • Granular data categories with per-field sensitivity and sharing policy
  • Audit trail and evidence exports for internal review and customer questions

For product owners

  • A portal that shows the machines you own and the data they produce
  • Machine-readable export in CSV and JSON, on demand
  • See exactly which third parties hold access, and to what
  • Withdraw access at any time, with immediate effect

For third parties

  • A documented REST API with scoped, expiring credentials
  • Access requests that state purpose, data categories and duration
  • Predictable errors and pagination built for unattended integrations
  • Webhooks for ownership changes, grants and revocations

Built for the integrator

A versioned REST API with scoped keys, predictable pagination and machine-readable errors. Keys are hashed at rest, shown once, and can carry an expiry.

  • Bearer authentication with per-key scopes
  • Consistent list envelopes and offset pagination
  • Stable error codes with a request id on every response
  • Rate limit headers on every call
  • Signed webhooks with replay-resistant signatures
Read the API documentation

Read a device’s latest values

curl https://api.databridge.eu/v1/devices/dev_01J8.../data/latest \
  -H "Authorization: Bearer db_live_..."

Response

{
  "object": "list",
  "data": [
    { "key": "spindle_temperature", "value": 42.3,
      "unit": "°C", "category": "operational",
      "timestamp": "2026-08-16T09:14:02Z" },
    { "key": "operating_hours", "value": 4219,
      "unit": "h", "category": "maintenance",
      "timestamp": "2026-08-16T09:14:02Z" }
  ]
}

Connectors

Planned connectors are labelled as such in the product. Nothing is shown as working before it is.

  • REST API· Available
  • Webhook push· Available
  • PostgreSQL· Available
  • CSV import· Available
  • MySQL· Planned
  • MQTT· Planned

Security is the product

A data-access layer that leaks is worse than no data-access layer. These are architectural properties, not settings.

Tenant isolation by construction

Every record carries its organisation, every query is scoped server-side, and no tenant identifier is ever accepted from the client.

Secrets that cannot be read back

API keys are stored as keyed digests and shown once. Data-source credentials are encrypted with AES-256-GCM and never returned to a browser.

Access that expires and revokes

Grants carry a scope list, a category list and a validity window. Revocation is immediate because authorisation is checked per request.

An append-only record

Consent and audit events are written once. The application exposes no path that edits or deletes them.

Support for data-access obligations

The EU Data Act obliges many manufacturers of connected products to make product-generated data available to users and, at the user’s request, to third parties. DataBridge implements the mechanisms those obligations typically call for: a declared data schema, owner access, machine-readable export, third-party authorisation with purpose and duration, revocation, and an append-only record of what happened.

DataBridge does not certify compliance and does not provide legal advice. Our readiness score measures how completely the technical mechanisms are configured in your workspace — nothing more. Assess your legal obligations with qualified counsel.

Plans

Packaging is defined by device count, integration count and retention. Pricing is agreed per organisation — get in touch and we will scope it with you.

Starter

One product line, one integration, the full access model.

  • Connected devices250
  • Product lines2
  • Data sources1
  • Telemetry retention (days)90
  • Outbound webhooks—
  • Custom data categories—
  • SSO / SAML readiness—

Email support

Pro

Most common

Multiple product lines and production integrations.

  • Connected devices5,000
  • Product lines10
  • Data sources5
  • Telemetry retention (days)365
  • Outbound webhooksIncluded
  • Custom data categoriesIncluded
  • SSO / SAML readiness—

Priority email support

Business

Full fleet coverage with long retention and partner ecosystems.

  • Connected devices50,000
  • Product lines50
  • Data sources25
  • Telemetry retention (days)1,095
  • Outbound webhooksIncluded
  • Custom data categoriesIncluded
  • SSO / SAML readinessIncluded

Named contact, 8×5 response targets

Enterprise

Unlimited scale, bespoke deployment and contractual guarantees.

  • Connected devicesUnlimited
  • Product linesUnlimited
  • Data sourcesUnlimited
  • Telemetry retention (days)Unlimited
  • Outbound webhooksIncluded
  • Custom data categoriesIncluded
  • SSO / SAML readinessIncluded

Dedicated support and onboarding engineer

Billing is not enabled in this release; plans and limits are enforced in the product, payment is handled outside it.

Questions

Do we have to change our devices or firmware?+

No. DataBridge connects to the systems that already receive your product data. If telemetry reaches a database, an API or a broker today, it can reach DataBridge without touching the fleet.

Does this make us compliant with the EU Data Act?+

No software can do that, and we will not claim otherwise. DataBridge implements the technical mechanisms that data-access obligations typically require — owner access, machine-readable export, third-party authorisation, revocation, audit records. Whether your organisation meets its legal obligations depends on your products, contracts and circumstances, and should be assessed with qualified legal counsel.

Who decides what a third party can see?+

The product owner. A third party can request access, stating purpose, data categories and duration. Nothing is readable until the owner approves, and the owner can narrow the request before approving or withdraw it afterwards.

What happens to data we already hold?+

It stays where it is. DataBridge normalises and indexes what it ingests for access purposes; it is an access layer, not a replacement for your historian or data platform.

Can we run this in our own environment?+

The application is a standard Node.js service backed by PostgreSQL and deploys to your own infrastructure or a managed platform. See the deployment documentation in the repository.

Make your connected products accessible.

Create a workspace, connect a data source, and see your fleet’s data flowing through a governed access layer.

Start buildingI am a product owner