Always on, on the device
A small agent gathers logs and metrics locally and writes them to a durable on-disk buffer before anything touches the network.
T+00Index
LINK: UP · BUFFER: 0 · SYNCED
Lose the link. Keep every log line.
Tidemark collects logs and metrics from your edge devices and ships, even over unreliable satellite links. When the connection drops, it keeps collecting. When it returns, it syncs. Built by Kelpwave Labs in Bergen, Norway.
Simulated uplink · 1 device
T+01Method
How Tidemark works
Open water is a hostile network. Tidemark assumes the link will fail and is designed around that, so nothing depends on a connection being there when the data is created.
Buffer through the outage
When the satellite drops, collection continues. Lines are ordered, timestamped at source and kept until the shore side confirms receipt.
Catch up when the link returns
Data is compressed and resumed from the last acknowledged point, so a flaky connection never means starting over or sending duplicates.
T+02Deploy
Self-hosted, if the data has to stay yours
Run the Tidemark collector and store on your own hardware, onboard or onshore. The agent configuration is the same either way.
# point the agent at your own endpoint
tidemark agent init --endpoint https://logs.example.no
tidemark agent buffer --max-size 20GB
tidemark agent start
# LINK: DOWN · BUFFER: 18,204 · COLLECTINGT+03Pricing
Free for your first 10 devices
Start with a pilot vessel or a handful of edge boxes. Pay only when your fleet grows.
Free
€0 / up to 10 devices
- Offline buffering and resumable sync
- Logs and metrics
- Community support
Per device
Usage / based on fleet size
- Unlimited devices
- Longer retention
- Email support from Bergen
Your infrastructure
Custom / annual
- Run collector and store yourself
- Air-gapped deployments
- Priority support
T+04Start
Get your first device reporting today
Leave your email and we will send an install link and a short setup guide.
T+01Problem
Your fleet isn’t in a data center.
Sensors, fish-farm gateways and offshore equipment run far from reliable networks, and satellite links come and go. Tools built for always-on connections leave gaps exactly when you need answers. Your monitoring shouldn’t act like it’s on a rack.
| Where it runs | Always-on tool | Tidemark |
|---|---|---|
| 01Sensors | Gap while offline | Keeps collecting, then syncs |
| 02Fish-farm gateways | Gap while offline | Keeps collecting, then syncs |
| 03Offshore equipment | Gap while offline | Keeps collecting, then syncs |
| 04Ships | Gap while offline | Keeps collecting, then syncs |
Tidemark is designed for the links you actually have.
T+05Fieldwork
Made for the places Wi-Fi never reaches.
Tidemark is for developer teams running workloads on edge devices and ships. That includes sensors, fish-farm gateways and offshore equipment, in places where the connection is a satellite link and not a given.
Tide line · one deviceLink: satellite
| Ref | Environment | Where it sits |
|---|---|---|
| ENV-01 | Edge sensors | Workloads running at the edge, far from a stable network. |
| ENV-02 | Fish-farm gateways | Gateways at the farm, where the satellite link is not a given. |
| ENV-03 | Offshore equipment | Equipment out at sea, reporting whenever the link allows. |
| ENV-04 | Ships | Vessels where the satellite is the connection. |
Don’t see your setup? If it runs workloads and the link comes and goes, this is your table.
Start free