Remote HART access you can prove.

HartBeat gives authorized teams and vendors a secure remote path to HART field instruments, using the tools they already know, with a tamper-evident, command-aware record of every HartBeat session.

Contact Sales See a sample audit record

  • Connect through an outbound site connector.
  • Work with familiar instrument software.
  • Capture signed, searchable, exportable audit evidence.
  • See who connected, which instrument they reached, and what HART interaction occurred.
How a remote command becomes a record An illustrated pump station with two field instruments and a gateway. A site connector reaches outward to HartBeat, and each command arrives as a new row in a signed audit record. All names are fictional. North Pump Station Your site LT 204 PT 101 Gateway 2 Connector online outbound only HartBeat Audit record Export Search by tag, person, or command LT-204 Read Primary Variable j.rivera, Contractor 14:32:07 Allow LT-204 Read Loop Current j.rivera, Contractor 14:32:19 Allow LT-204 Write Range Values j.rivera, Contractor 14:33:52 Flagged PT-101 Read Primary Variable m.chen, Engineer 14:41:05 Allow PT-101 Write Tag m.chen, Engineer 14:41:30 Allow PT-101 Read Device Variables m.chen, Engineer 14:42:02 Allow

The field-instrument access blind spot.

Plants have modernized remote access to servers, applications, and many OT assets. HART instrument work often still depends on local presence, plant-specific tools, vendor workflows, or remote paths that are hard to govern and harder to reconstruct.

FieldComm Group cites over 40 million HART instruments installed worldwide. Source: FieldComm Group

  • Who touched the instrument?Access often means a technician on site, or a remote setup improvised case by case.
  • What happened?The record is scattered across local tools, service notes, screenshots, and memory.
  • Where is the evidence?A contractor needs working access for an afternoon. Afterwards, nobody can show what they did.

A VPN gets someone in. HartBeat tells you what happened next.

A VPN log ends at the connection. A HartBeat record continues command by command to a signed record. VPN log Signed in Connected No record of what happened at the instrument HartBeat Signed in Session on LT-204 Read, allow Read, allow Write, flagged Each command classified, evaluated, recorded Signed record

Connect. Work. Record. Prove.

A small connector at your site reaches out to HartBeat. Your people sign in, work with instruments through their usual tools, and every command lands in a signed record.

Your site connects outward to HartBeat; your people work through HartBeat; every command is recorded and can be exported. Your site LT204 PT101 FT201 Gateway Connector outbound, encrypted HartBeat 1 Read Primary Variable Read Allow classified, evaluated, recorded Your people Their usual tool 2.84 m m.chenEngineer Signed export Illustration. Fictional site, people, and readings.

Connect

A lightweight site connector links your HART-IP gateway to HartBeat through an outbound, encrypted connection. Nothing on the plant network has to accept connections from the internet.

Work

Technicians sign in with their own identity and work with instruments through a governed HartBeat session, using familiar instrument software.

Record

Every HART command is classified, evaluated against your access policy, and written to the audit trail with the decision and the outcome.

Prove

Search and export a signed, tamper-evident record for troubleshooting, audit support, and accountability.

Built for the work instrument teams already do.

Talk to us about your sites

An engineer at home reads diagnostics from a remote level transmitter. Illustration with fictional data. LT-204, radar level transmitter Session recorded Primary variable 2.84 m Diagnostics Lost echo

Remote support without the drive

A level reading at a remote lift station looks wrong. The on-call engineer signs in from home, reads the diagnostics through their usual tool, and finds the cause. The session is on record by morning.

A team list with an engineer, an auditor, and a named contractor account. Illustration with fictional names. Team m.chenEngineer a.okaforAuditor j.riveraVendor specialistContractor

Governed contractor access

Give a vendor working access without the keys to the kingdom. They work in remote sessions under a named contractor account, and every action is recorded under their own name.

Accountability and dispute resolution

A transmitter’s range changed last quarter and nobody remembers why. Search the audit record and have the who, when, and what in seconds, backed by a signed record instead of a guess.

Three sites, each with an online connector and a count of instruments. Illustration with fictional sites. Sites North Pump Station2 gateways14 instruments Riverside Lift Station1 gateway6 instruments East Reservoir1 gateway9 instruments

Multi-site oversight

One view across distributed sites, their connectors, and the instruments behind each gateway. Discovery fills in the inventory when a new site comes online.

Security posture

HartBeat is designed toward SOC 2 controls and built with IEC 62443 and NIST SP 800-82 principles in mind. We don’t claim certifications we don’t hold.

  • Outbound site connector

    No inbound openings to the plant network.

  • Encrypted, mutually authenticated links

    Site and cloud each prove who they are.

  • Personal sign-in and scoped roles

    Administrator, Engineer, Contractor, and Auditor. Lockout after repeated failures.

  • Tamper-evident audit

    Every record is signed and chained to the one before it.

  • Strict isolation between organizations

    Enforced in more than one layer.

  • Administrators are accountable too

    Privileged actions are signed and recorded, and don’t happen if they can’t be recorded.

What proof looks like.

Two records from one contractor session. The first is a read the policy allows. The second is a write the policy denies: HartBeat flags it and records it permanently.

Sample audit recordIllustrative record. Fictional organization, people, and devices.
  1. When
    14:32:07.418
    Who
    [email protected] (Contractor)
    In which session
    Remote support session #1182
    Where
    North Pump Station, Gateway 2
    Device
    LT-204, radar level transmitter
    What
    1 Read Primary Variable Read
    Outcome
    Carried out
    Under what authority
    Allow read commands permitted for contractors
    Can I trust it?
    ✓ Signed✓ Chained to previous record
  2. When
    14:33:52.106
    Who
    [email protected] (Contractor)
    In which session
    Remote support session #1182
    Where
    North Pump Station, Gateway 2
    Device
    LT-204, radar level transmitter
    What
    35 Write Range Values Write
    Outcome
    Recorded, not blocked
    Under what authority
    Deny write commands not permitted for contractors
    Can I trust it?
    ✓ Signed✓ Chained to previous record
  3. When
    14:34:10.772
    Who
    [email protected] (Contractor)
    In which session
    Session #1182 ended
    What
    Session closed by the contractor
    Can I trust it?
    ✓ Signed✓ Chained to previous record

Every out-of-policy command is flagged and permanently recorded.

Each record is digitally signed when it is written and carries a fingerprint of the record before it, so the records form an unbroken chain. If anyone edits, deletes, or reorders a record later, the signature or the chain no longer checks out. Integrity is mathematical, not “we promise we keep logs.”

Download the sample record (CSV, fictional data)

Try to change the record

Rewrite the second record’s decision from Deny to Allow and see what a reviewer would see.

Plans sized to your instrument fleet.

Every plan starts with a conversation and a guided trial. Tell us about your sites and we’ll scope it with you.

HartBeat plans
PlanPeopleDevicesA good fit for
Basic110A small trial, lab, or single-site evaluation
Premium550A technical team managing a larger instrument group
Organization15150Multi-person, multi-site operational use
EnterpriseCustomCustomLarger deployments, security review, procurement, and custom onboarding

Plans are available for qualified deployments. Enterprise and regulated environments should contact us for architecture review and onboarding.

Some advanced enforcement, monitoring, integrations, and automation features are on our roadmap and are not included unless specifically stated in your plan or agreement.

Questions from OT and security reviewers

Need more depth? We offer an architecture review under NDA.

Do we have to open our network to the internet?

No. The site connector makes an outbound connection; nothing needs to accept inbound traffic from the internet.

Does HartBeat replace our configuration software?

No. Your technicians keep using it through a secure, recorded path.

What exactly gets recorded?

Who, when, which site, gateway, and instrument, which session, which HART command and category, the policy decision and reason, and whether the command was carried out, all signed and chained.

Can the audit record be altered?

Any edit, deletion, or reordering is detectable, because every record is signed and linked to the one before it.

Can HartBeat block a command?

HartBeat evaluates every command against your access policy and permanently records the decision and outcome. Enforcing mode, where out-of-policy commands are withheld, is on our roadmap.

Can we give a vendor access?

Yes. Give them a contractor account: they can work in remote sessions, and everything they do is recorded under their name.

How long do you keep our records?

For as long as you’re a customer. If you leave, you get your records first; we hold them for a 180-day closing period and then delete them permanently.

What do we need for a trial?

See the Trial Readiness Checklist. Contact sales and we will scope it with you.

Set up a trial with our team.

Contact sales to set up a trial: for distributed operators, service teams, and instrumentation groups ready to evaluate governed remote HART access.