Skip to content

v2.0 · offline-first sync for satellite links

Every sensor, every millisecond, kept at the edge.

A time-series database that runs on the machine itself: a turbine, a reefer truck, a substation. It writes 1.2 million readings a second on one core and syncs when the link comes back.

Install in one lineRead the architecture

turbine-14 · ssh

  1. curl -fsSL get.verglas.dev | sh
  2. verglas 2.0.3 installed, one static binary
  3. verglas ingest --from can0 --streams 212
  4. link down · writing locally · 0 samples dropped
  5. 41.2 GB queued, resumes at next satellite pass

Running on the edge of

  • Nordvik Wind
  • Calder Grid
  • Tessaline Cold
  • Harrow Rail

01The engine

A database that expects the network to fail.

Built for machines at sea, on rails and in fields, where the cloud is a nice-to-have and the disk is all you can count on.

  1. Writes that never wait

    An append-only log on local NVMe takes every reading at sensor speed, with or without a connection, and never drops a sample.

    0samples lost in 412 days

  2. Columnar, compressed

    Delta-of-delta timestamps and XOR floats keep a year of 2 kHz vibration on one small SSD.

  3. Sync that resumes

    When the link returns, Verglas sends what the cloud is missing, in order, from where it left off.

  4. SQL at the source

    Run alarms and rollups where the data lives, in plain SQL with time windows, and send only the answers upstream.

    96%less satellite traffic

Specification

Binary
One static file, no dependencies
Platforms
ARM64, x86-64, RISC-V on Linux 4.19+
Peak ingest
1.6M readings a second, one core
Compression
Delta-of-delta time, XOR floats
Query
SQL with time windows, p99 4 ms
Retention
Raw 7 d, 1 s rollups 1 yr, hourly
Encryption
AES-256-GCM, key in secure element
Sync
Ordered, resumable, down to 9.6 kbit/s

02The console

A whole fleet, one pane of glass.

Every node, every stream and every sync queue in one console. Drill from the fleet to a single bearing in two clicks.

fleet / north-sea-array-2 / turbine-14

  • Query
  • Streams
  • Sync

Streams

  1. nacelle.vibration2 kHz
  2. gearbox.temp10 Hz
  3. blade.pitch.a50 Hz
  4. rotor.rpm100 Hz
  5. grid.export.kw1 Hz

Ingest on this node

1.2M/s

readings a second · 3% CPU

Vibration RMS · last 15 min

Node health

  • Disk used41 GB
  • Compression38×
  • Sync backlog2.1 s
  • Query p994 ms

01

Survives the outage

Writes land on local NVMe and sync in order when the satellite link returns.

02

Alarms at the turbine

A vibration rule fires 4 ms after the reading, not after a round trip.

03

Two seconds behind

The sync queue drains in order over the satellite link and never sends a reading twice.

03Pricing

Pay per node. Queries are free.

No charge per reading, per query or per gigabyte synced. You pay for the machines Verglas runs on.

Save 20% yearly

  1. Bench

    For prototypes and pilots on up to three nodes.

    Free

    Forever, no card needed

    Install Verglas
    • Up to 3 nodes
    • Every engine feature
    • Sync to your own S3
    • Community support

  2. Fleet

    Most fleets

    For production fleets that need the console and fleet sync.

    $14 per node

    Per node, per month

    Start a 60-day pilot
    • Unlimited nodes
    • The fleet console
    • Managed sync over any link
    • Tiered retention
    • Support in 4 hours

  3. Utility

    For grids and operators with air-gapped sites and audits.

    Custom

    From 2,000 nodes

    Talk to us
    • Everything in Fleet
    • Air-gapped deployment
    • IEC 62443 evidence pack
    • A named engineer