About Roamzy.
One operator + AI-assisted research building a 193-country eSIM catalog with transparent per-MB pricing. Here's how the catalog is written, sourced, and kept honest.
Who runs Roamzy
Roamzy is an independent operator-owned eSIM brand. The catalog, pricing engine, and editorial copy are maintained by a single person with AI-assisted research workflows. There is no marketing team, no content farm, and no PR network — just a tight operator running both the product and the documentation.
This matters because the alternative on travel-eSIM directories is a content-mill business model: hundreds of templated articles written by SEO contractors who never travel and don't audit their own pricing claims. Roamzy is the opposite of that pattern. Every per-MB rate in this catalog matches a wholesale agreement; every country article was written from a structural template against verified country facts.
How the prices are calculated
Per-MB rates published on roamzy.io and per-country article pages come from a single source of truth: data/prices.json. Each entry includes rateUsdtPerMb (raw wholesale + a flat markup) and rateUsdtPerGb (1024 × the MB rate, identity check). When a wholesale rate changes, the auto-sync pipeline propagates the change into every article frontmatter and the cost-math comparison tables — no per-article edit, no opportunity for stale figures to leak into copy.
If a number looks wrong, it's a bug. Email [email protected] with the country slug and we'll fix it within 24h.
How the country articles are written
Each of the 193 country articles follows one of eight structural archetypes (volcano-free tourist, volcanic island, financial hub, backpacker, landlocked steppe, micro-state, Caribbean cruise stop, frontier). The archetype determines section ordering and what's emphasised — Mongolia gets its landlocked-steppe treatment with overland coverage notes; Tuvalu gets its micro-state honesty about wholesale rate reality; Iran gets its frontier voice with practical-not-political positioning.
Body content is generated against verified country facts pulled from Wikidata + a private operator-curated layer (capitals, currencies, plug types, voltages, frequencies, network frequencies). Numerics are never hallucinated; if a fact isn't in the source layer, it doesn't make it into copy.
Cross-article similarity is monitored. Mean intra-locale Jaccard sits at 17–23% (templated competitor sites typically 40–50%). Cross-locale ru↔en Jaccard is 4.6–5.0% — confirming locale articles are natively conceived, not machine-translated.
How country images are sourced
Hero images on country pages come from Unsplash — photographer-curated travel photography under the Unsplash License. Each image links back to the original photographer's profile in the figcaption (per Unsplash API guidelines). Where Unsplash didn't have a strong on-topic photo, fallback images are sourced from Wikimedia Commons under permissive licenses (CC-BY, CC-BY-SA, public domain).
No AI-generated images are used in the catalog. No stock-photo padding, no flag-only fallbacks except as a last resort, no images from copyright-uncertain sources.
Three guarantees that don't have asterisks
- No first-purchase promo. The price you see on day one is the price on day five hundred. There's no welcome discount that flips on the second top-up.
- No fine-print throttling. The first GB and the hundredth cost the same per MB. There's no clause that says "after X GB the speed drops to 256 kbps until cycle reset."
- No auto-renewal. When the balance runs out, the eSIM stops. There's no background charge to a card you forgot about six months later.
These three are an editorial commitment, not just a marketing line — they're the engineering consequence of selling bytes instead of packages. You can't price below this without re-introducing the small print, so we don't.
Corrections, sources, contact
If you find a factual error in a country article (wrong currency, outdated rate, broken cross-link, dead pricing claim, mis-attributed image), please email [email protected] with:
We keep an audit log of corrections at docs/ops-log.md in our internal repo. Every fix lands as a dated, attributed entry — that's the audit trail Google's quality raters look for, and it's also just good editorial hygiene.
- The exact URL on roamzy.io where the error appears
- What the current claim says
- What the correct claim should be (and your source if applicable)
What we don't do
We don't run paid SEO sponsorships in the country articles. We don't accept "guest posts" from tour operators, eSIM resellers, or affiliate networks. We don't include AI-fabricated reviews or aggregateRating scores in our structured data — we only display reviews when they come from real customers, and we don't have those yet (we're new). We don't republish other sites' country guides, even with attribution; if it's worth saying about a destination, we'll say it ourselves with our own framing.
If any of these change, this page will say so before the change ships.