01Unified architecture
USB or AP. One verified pipeline.
Mode-specific acquisition stays at the edge. After the shared buffer, validation, health and delivery follow one standard path.
↗ Field operations for unattended GNSS sites
Keep corrections
moving.
Stay in control.
GeoBridge OS turns a supported Raspberry Pi into an observable, recoverable RTCM appliance—with guided setup, honest live health, read-only diagnostics and controlled OTA.
DEVICE HEALTHLIVE
All systems operationalReceiverConnected
DeliverySent / Ack
Station 14V6 ONLINE
THE PRODUCT
Not just online.
Operational.
GeoBridge OS replaces fragile one-off scripts with a repeatable field operating model. It shows what is healthy, what is stale and which layer needs attention.
02Live operations
See whether data is really moving.
Freshness, RTCM groups and up to three independent delivery channels are presented as evidence—not a generic green status light.
↗03Quick diagnostics
Find the failed layer in seconds.
A read-only diagnostic checks system, network, license, receiver, buffer, delivery and OTA without changing the running station.
↗04Field recovery
Recover the data path before the host.
Bounded service recovery and real USB power cycling restore supported receivers while keeping the bridge reachable whenever possible.
↗05Access control
Simple for hosts. Deep for support.
Host and Admin views separate safe daily operation from technical diagnostics, recovery controls and support details.
↗06Controlled releases
Signed updates with a way back.
Immutable, verified OTA packages move through staged gates. Failed health checks stop rollout and preserve rollback evidence.
↗ONE DATA PATH
Different inputs.
One operating truth.
USB and AP keep their own acquisition and recovery logic. The moment RTCM reaches the shared buffer, every station uses the same validation, health and delivery pipeline.
MSM4 / MSM7Coherent message profiles
0 fake motionAnimation follows real freshness
Bounded recoveryNo uncontrolled restart loop
3-way fan-outOne source, independent destinations
OPERATIONAL VALUE
Protect the work
your station does.
GeoBridge is built around continuity, evidence and repeatability. It does not promise rewards; it helps operators reduce avoidable data-path downtime and manage more sites with less uncertainty.
Detect stale RTCM, broken delivery and receiver-side faults before an unnoticed outage consumes the day.
Freshness + sent/ack evidenceSend a verified correction stream to as many as three independently observed destinations without duplicating the acquisition stack.
Up to 3 delivery channelsUse one stable image, controlled OTA, consistent health language and Telegram visibility across repeatable deployments.
Same operating model per siteNetwork rewards, token values and third-party availability can change. GeoBridge improves operational visibility; it does not guarantee earnings.
ONO ESTIMATOR
Model the value.
Keep the claim honest.
Adjust the number of stations and the daily token estimate. Live ONO pricing is requested from CoinGecko; the result is an illustration, not a reward or income promise.
LIVE ONO PRICEFetching…Calculator remains usable in token units.
—
—
—
7-DAY ONO PRICE TREND
Price history is loading.
7 DAYS AGONOW
Important: 28–30 ONO/day is an editable high location-score example, not a guaranteed rate or universal maximum. Actual rewards depend materially on the station's location score as well as network rules, data quality, uptime, validation and third-party changes; they can be lower, delayed or zero. Prices are volatile.
SUPPORTED STATION PROFILES
One operating layer.
Two proven models.
GeoBridge OS standardizes how supported GNSS stations are connected, observed and maintained while preserving the requirements of each hardware profile.
COMPACT PROFILEMGW200
MGW200
A supported compact station profile for deployments where size, simple installation and a consistent RTCM path matter.
- Validated GeoBridge profile
- USB/COM2 compatibility workflow
- Managed health and OTA visibility
REMOTE SITE PROFILEMGW310
MGW310
A supported fixed-site station profile for remote installations that need clear connectivity and operational status.
- Validated GeoBridge profile
- Remote fixed-site deployment path
- Managed RTCM delivery visibility
COMPATIBILITY NOTE
Support depends on the validated hardware and firmware profile. GeoBridge does not replace or modify the station firmware.
DEPLOYMENT FIT
Know what is
validated.
Support is based on a complete combination—not a model name alone. We confirm the station profile, Raspberry Pi, acquisition mode and connectivity before deployment.
Maintained profiles with model-specific acquisition and recovery boundaries.
Validated profilesPI 3PI 4 RECOMMENDEDPI 5 RECOMMENDEDZERO 2 W
The current stable image supports all four platforms. Raspberry Pi 4 and Pi 5 are recommended for new deployments.
One stable operating layerEach mode keeps its own input logic before joining the shared RTCM pipeline.
Mode-specific checksHost visibility, protected Admin access, Telegram monitoring and controlled OTA.
Role-aware accessNOT SURE ABOUT YOUR COMBINATION?
Send the station model, bridge hardware, preferred connection mode and fleet size. We will confirm the supported path before you deploy.
Check deployment fit ↗OPERATIONS CONSOLE
Evidence before
assumptions.
The console separates a working process from a working data path. Daily users see a clean answer; support can inspect each layer without exposing raw system details.
- 01 Honest Live View and data freshness
- 02 Receiver → delivery pipeline state
- 03 Seven-layer Quick Diagnostic
- 04 Host and Admin role separation
REAL PRODUCT UICaptured from an operating GeoBridge site.
SECURE LOCAL ACCESS
Simple for hosts.
Protected for admins.
GeoBridge separates everyday visibility from technical changes. Each role uses its own password and receives only the controls it needs.
See what matters.
Health, Live View, uptime, connectivity and delivery status stay easy to reach without exposing recovery or system controls.
- Daily monitoring
- Read-only operating view
- No technical change authority
Diagnose and recover.
A separate admin password unlocks diagnostics, configuration, support snapshots and protected recovery actions.
- Seven-layer diagnostics
- Protected device controls
- Configuration and support tools
GEOBRIDGE CLOUD BOT
Your sites,
inside Telegram.
A simple, read-only companion for owners and customers. Add a device with its license code, give it a nickname, share selected sites and receive useful alerts without notification storms.
- Online/offline alerts after a five-minute confirmation window
- Device nickname, uptime and last-seen status
- Per-device notifications and safe Telegram-only removal
- Share selected devices without sharing the full account
GeoBridge OSbot
online Connection restored
Garden Station is online again.
Garden Station is online again.
FIELD RESILIENCE
Recover with
clear boundaries.
Recovery is successful only when RTCM and delivery counters move again—not when a service merely says “active”.
Separate missing GNSS data, USB disconnect, stale network and delivery failure.
Keep mode-specific recovery before the shared pipeline so one path cannot corrupt the other.
Use bounded service recovery or supported USB power cycling with cooldown protection.
Require fresh RTCM plus advancing sent and acknowledgement counters before PASS.
FROM ZERO TO STREAM
Deploy in four
clear steps.
GeoBridge OSFIRST-TIME SETUP
01Preparation✓
02Operating mode✓
03Internet✓
04License & access✓
05Primary network✓
06Security✓
PHONE CONNECTED · GeoBridge-Setup
GeoBridge confirms the platform before configuration begins.
✓Supported Raspberry Pi✓SD storage ready✓Network interface✓GNSS link available
Select one acquisition mode. The remaining pipeline stays identical.
●USB ModeFTDI / COM2 connection○AP Mode BetaDedicated station network
Example values are entered automatically for this demonstration.
Connection test passed
The device identity and optional remote access are configured together.
License verified
The real setup uses standard NTRIP destination fields.
Admin and optional Host access remain separate.
Applying secure configurationGeoBridge is getting ready.Settings are saved and the connection is being prepared.
✓GeoBridge is ready.Opening the operations console…
Opening Live View
LIVE RTCM37 satellites 6 message types 3 destinations streaming
Device online- 01
Flash
Write the stable GeoBridge OS image to an SD card.
- 02
Power
Insert the card into the Raspberry Pi and switch it on.
- 03
Join
Connect your phone to the GeoBridge-Setup Wi-Fi network.
- 04
Finish
Follow the guided steps and continue directly to the live dashboard.
BEFORE YOU CLIMB
A field kit that
prevents return trips.
Reliable deployments begin with ordinary components selected carefully. Confirm the complete kit while you still have a desk, screen and spare cable nearby.
- 01Validated bridge
Supported Raspberry Pi with the current GeoBridge OS image.
- 02Stable power
A correctly rated, reliable power supply with enough headroom for attached hardware.
- 03Known-good data path
A real USB data cable for USB Mode or a confirmed dedicated network for AP Mode.
- 04Deployment details
Internet access, license code, destination credentials and local access passwords.
LICENSE & SUPPORT
Software access
with an operating path.
GeoBridge is supplied per supported deployment. Commercial terms depend on fleet size and the confirmed hardware profile, so operators pay for a path we can actually support.
Request deployment terms ↗- Stable GeoBridge OS image
- Guided first-time setup
- Dashboard and Live View
- Controlled OTA updates
- Telegram monitoring access
- Supported recovery workflow
- Compatible station and bridge hardware
- Reliable power and connectivity
- Third-party network credentials
- Permission to use each destination
- Safe physical installation
- Customer-controlled remote access
READY WHEN YOUR SITE IS
Build a repeatable
GNSS operation.
One stable base. One predictable setup. One evidence-driven way to operate every site.
Plan a deployment ↗×Tell us about
REQUEST GEOBRIDGE
Tell us about
your deployment.
Share the size of your fleet and what you need. We will review the request and reply from info@geobridge.network.
Deployment fit review Hardware profile guidance Direct technical response
QUICK ANSWERS
Before you
deploy.
Does GeoBridge modify station firmware?
No. GeoBridge runs on a separate bridge device and does not require a station firmware change.
Which Raspberry Pi models are supported?
The current GeoBridge OS release supports Raspberry Pi 3, Raspberry Pi 4, Raspberry Pi 5 and Raspberry Pi Zero 2 W. Raspberry Pi 4 and Pi 5 are recommended for new deployments.
Can setup be completed from a phone?
Yes. Join the GeoBridge-Setup network and follow the guided first-time setup.
What happens when USB data stops?
GeoBridge distinguishes a receiver-data problem from a USB disconnect, applies bounded recovery where supported and verifies that RTCM delivery actually resumes.
Can a host access advanced recovery controls?
Daily Host views stay intentionally limited. Technical diagnostics and recovery actions remain separated in the Admin support surface.
How are updates delivered?
Approved releases are delivered through controlled OTA channels after staged validation.
Can one operator manage multiple stations?
Yes. GeoBridge uses a consistent device identity, health model and update path across supported deployments. Fleet and volume requirements are reviewed before rollout.
Does GeoBridge guarantee rewards or token income?
No. Rewards, prices and third-party network availability are outside GeoBridge's control. The product is designed to improve data-path continuity, observability and recovery.
Does GeoBridge need my website account password?
No web-account password is required. The device uses only the connection details needed for destinations that the operator chooses to configure.
What does the license include?
The supported deployment path includes the stable image, guided setup, device console, approved OTA updates and the monitoring surfaces described above. Exact commercial terms are confirmed for each fleet.
Who controls remote access?
The operator controls whether optional remote connectivity is enabled. Customer-facing Host access remains separate from protected technical administration.