Documentation
RoamBridge docs
Everything here describes the product as it actually behaves. Where a rule is deterministic, the rule is stated exactly.
Getting started
RoamBridge needs no account. Open the planner and the workspace is ready; it lives in your browser's local storage from the first stop you add.
Add trip stops
Each stop carries destination, arrival date, days, and expected daily use. These are the assumptions every later calculation shows its work against.
Compare offers
Enter the plans you found - provider, price, data, validity, and the date you saw the price. The comparison calculates each against your trip estimate.
Build the runbook
Create the timed, device-local checklist around each arrival, then rehearse it in the resilience lab before departure.
Print the packet
Export the workspace and print the offline packet. The fallback travels with you, on paper.
Concepts
Stop - one leg of the trip: destination, arrival, days, expected daily use. Offer - a plan you found, with price, data, validity, and the date you recorded it. Runbook - the timed activation checklist around an arrival. Usage entry - a dated record of MB used and cost. Burn-down - the chart of remaining data with an exhaustion estimate from your measured pace. Call-home window - the computed time overlap between your stop's clock and home. Offline packet - the printable fallback: plan, runbook, emergency steps.
Today view
The command view for the current moment: which phase the trip is in, the next runbook tasks, readiness, quote health, and - once traveling - on-the-ground usage. The call-home strip computes the overlap between local time at your stop and at home.
Trip planner
Stops compose into the full itinerary. A departure countdown and day-by-day calendar keep the plan concrete, and expected daily use drives the data estimate used by comparison and burn-down.
Plan comparison
Enter offers you found yourself. RoamBridge calculates each against the trip estimate and shows the working. Exact rule: an undated price is never labeled "live" - it is presented as a number you wrote down, with the date you wrote it down when you provided one.
Activation runbook
Tasks are timed around each arrival and checked off manually. Exact rule: checking a task is manual evidence that you did the step. It is never a claim that a carrier-side activation succeeded - only the network can confirm that.
Usage ledger
Log date, MB used, and cost. The burn-down chart projects an exhaustion estimate from your measured pace across the logged span - including before the trip starts, so a top-up decision can happen early.
Resilience lab
Compare user-entered connectivity strategies across the whole trip and rehearse failure cases before departure. The goal is a plan that survives the dead SIM at immigration, because you already walked through it.
Data formats
The whole workspace - stops, offers, runbooks, usage entries, scenarios - exports as a single JSON file, imports back exactly, and prints as the offline packet. There is no partial export and no server-side copy.
Privacy
Local by default: no analytics, no session recording, no third-party pixels. Trips live in local storage. Deleting the workspace is immediate and total, because the data only ever existed in your browser. The separate eSIM storefront has its own terms at /store/.