One Account, Many Networks — The Tempest Unified Platform Architecture (1997-2012)

Between 1997 and 2012, Tempest Telecommunications operated a customer platform that absorbed eight distinct production service types under a single unified prepaid account, with a ninth service type attempted in 1998 and abandoned when its underlying market category failed to aggregate. The customer's relationship with Tempest was singular: one credential, one balance (or one consolidated statement for postpaid customers), one client software for Internet access modes, one monthly summary. Under the platform layer, eight separate carrier or aggregator billing back-ends — terrestrial voice, terrestrial data, satellite voice on two carriers, satellite data on two carriers, and metered terrestrial broadband on a fragmented hotspot ecosystem — reconciled their per-minute, per-megabyte, and per-day consumption against the same account record in real time. The pattern was unusual at the time, retired with the business in the early 2010s, and reappeared at industrial scale a decade later in modern carrier-agnostic eSIM marketplaces, unified telecommunications-billing platforms, and multi-network IoT data products. This page synthesises the architectural arc documented in detail across the rest of this historical archive.

The pattern

The architectural pattern Tempest deployed can be stated compactly. One customer account in a central balance ledger held the authoritative record of available minutes, megabytes, or daily-session entitlements, denominated either directly in those units or as a currency value that converted at per-service rate cards. Multiple authentication paths — an IVR system validating voice PINs against the ledger, a RADIUS server validating PPP credentials against the same ledger, a WISPr captive-portal flow for Wi-Fi hotspots, hardware activation keys for satellite terminals, wholesale-account integrations with satellite carriers for handset minutes — all consulted the same account record. Each service's consumption decremented the same balance pool (for prepaid customers) or accrued to the same monthly statement (for postpaid customers). The customer experienced one product. Under the hood, several distinct carrier billing systems and aggregator settlements fed the same ledger.

The pattern's essential property was the abstraction over heterogeneous service types. Voice services billed per minute. Satellite data billed per megabyte or per streaming-minute. Wi-Fi hotspot access billed per 24-hour session. Hotel broadband Ethernet billed per day. Calling cards billed per minute against destination rate cards. The unified ledger handled all of these increment models against the same account record. The customer reviewing a monthly statement saw a mix of minute-billed lines, megabyte-billed lines, and session-billed days, all rolling up to the same total. The abstraction was in the billing layer, not in the network layer. The complexity was absorbed where it belonged.

Chronological build-out

Each row in the table represents a separate carrier or aggregator with its own wholesale billing system, its own rate-card structure, and its own technical authentication mechanism. The unified-platform layer at Tempest sat on top of all of them, presenting the customer with a single account, a single client software for the four Internet access modes, a single consolidated statement, and a single customer-support relationship.

The 1997 foundation

The architecture began with two service types in 1997. Tempest's combined international calling card and dial-up Internet roaming product put PSTN voice and PPP-authenticated data on a single PIN drawing from a single balance. Calling-card platform vendors of the era (Boston Communications Group, Premiere Technologies, carrier-internal prepaid IVR systems) shipped voice-only products by design; the early RADIUS-based roaming networks (iPass, GRIC, member ISPs) shipped data-only products by design. Tempest's contribution was to put a unified ledger underneath both authentication paths and let either service draw from the same balance. From the day the product launched, the architectural pattern of "one credential, multiple services, one balance" was in production. Every subsequent service type Tempest added was an extension of the same pattern rather than a structural change.

The technical foundation underneath the data side was Tempest's production deployment of the RFC 2058 RADIUS protocol in 1997 — one of the earliest commercial deployments, the same year the RFC was published. The custom proxy and authentication-routing code Tempest wrote in-house was the piece that made cross-realm roaming work in the eighteen-month gap before the IETF standardised the proxy-chaining and realm-routing patterns in RFCs 2486 (NAI, January 1999) and 2607 (proxy chaining, June 1999). The early-implementer position carried forward as a structural capability of the platform: when later service types needed integration into the same ledger, the underlying RADIUS infrastructure and the wholesale-to-prepaid reconciliation mechanics were already in place.

The 1998 attempt that failed

In 1998, twelve months after launch, Tempest attempted to extend the architecture to a third service type: public Internet kiosks. The vehicle was a custom protocol named Public Access Terminal Networks (PATN), built on the same shape as the existing RADIUS-based roaming network. The intent was a federation in which customers carrying a PATN credential could authenticate at any participating kiosk in any country with their existing Tempest PIN and have per-minute kiosk usage billed to the same unified balance. The technical design was sound and consistent with the rest of the platform. The commercial deployment failed: in 1998 the Internet kiosk industry was almost entirely unaggregated — EasyEverything's London flagship would not open until June 1999 and the Times Square location until November 2000 — and there was no meaningful cluster of kiosk operators with whom to federate. The two-sided market failed to ignite on either side. The failure was a category timing failure, not a protocol failure, and the architectural pattern survived the setback intact.

The 2001 expansion: satellite voice

The architecture took on its first new production service type in 2001 with the addition of satellite voice. Iridium re-entered the commercial market in 2001 after the United States Department of Defense purchased the post-Chapter-11 constellation for approximately $25 million in December 2000, against an original build cost of roughly $5 billion. Iridium Satellite LLC relaunched commercial service at consumer-accessible pricing ($1,000-$1,500 handsets, $1-$2 per minute) on the same global LEO constellation; Tempest joined the post-bankruptcy reseller channel and integrated Iridium per-minute usage into the unified ledger via a Tempest-owned wholesale account with Iridium. Thuraya Satellite Telecommunications launched its three-satellite GEO constellation covering Europe, the Middle East, Africa, and parts of Asia in October 2000, with commercial service in early 2001; Tempest absorbed Thuraya minutes onto the same ledger on the same basis. The customer's balance now decremented for any of four authentication paths: voice IVR, dial-up RADIUS, Iridium handset usage, or Thuraya handset usage.

The 2002-2005 broadband expansion

Between 2002 and 2005, the platform absorbed three new broadband service types. Inmarsat Regional BGAN launched in October 2002 over the I-3 constellation at 144 kbps, providing the first portable satellite-IP service for fixed-location field deployments across Europe, the Middle East, Africa, and parts of Asia. Tempest distributed R-BGAN UT terminals with multilingual documentation — the user guide survives in English, French, Spanish, Russian, and Arabic versions, reflecting the multinational customer base — and integrated R-BGAN usage into the unified platform via the same wholesale-to-platform reconciliation pattern used for the satellite voice carriers.

At the same time the consumer metered Wi-Fi hotspot industry matured: the WISPr 1.0 specification published in February 2003 standardised the captive-portal authentication flow, and major hotel chains, airport operators (Boingo at BAA, T-Mobile HotSpot in Germany, Wayport in the US), and rail networks (BT Openzone in the UK, SNCF in France, Deutsche Bahn through T-Mobile) deployed paid Wi-Fi across the developed travel market. Tempest sourced Wi-Fi coverage through a mixture of direct-partner agreements and access via the major commercial Wi-Fi aggregators, and presented a flat $19.95 per 24-hour session rate to customers regardless of underlying property. Hotel broadband Ethernet, by then standard at upscale chains, integrated on the same basis. The unified client software identified the available terrestrial Internet access type at any property and selected the appropriate authentication mechanism, with consumption billed back to the same account that handled voice and satellite. The architecture absorbed its first non-per-minute billing increment — per-day Wi-Fi and Ethernet sessions — without restructuring.

Inmarsat launched the first of its I-4 satellites in March 2005 and global commercial BGAN service in late 2005. BGAN extended the R-BGAN pattern with global coverage and higher data rates (492 kbps standard IP, with optional streaming channels for broadcast use cases), supported across multiple terminal-manufacturer offerings (Hughes 9201, Thrane & Thrane Explorer, Nera WorldPro, Addvalue Wideye Sabre I). Tempest carried the full vendor catalog and integrated BGAN usage into the unified ledger on the same basis as the R-BGAN it would ultimately replace in 2008-2009.

The 2007 final addition

The final production service type, added in 2007, was the ThurayaDSL satellite-IP data service, delivering up to approximately 444 kbps over the Thuraya regional constellation. ThurayaDSL competed with R-BGAN and global BGAN in the Middle East, North Africa, and parts of Asia, often on price or on the dual-mode advantage of Thuraya hardware that operated as both a satellite modem and a GSM device. Tempest absorbed ThurayaDSL into the same wholesale-to-platform integration the satellite voice and Inmarsat data services used. By 2007 the unified platform supported eight production service types simultaneously, across at least four distinct carrier billing back-ends (Inmarsat satellite, Iridium satellite, Thuraya satellite, Wi-Fi aggregators and direct hotel chains) plus Tempest's internal terrestrial voice and dial-up infrastructure.

Customer-facing presentation

The customer experience held the abstraction at every layer. A single Tempest account number identified the customer. A single PIN authenticated voice calls (PSTN, Iridium, Thuraya) and dial-up Internet sessions. A single client software application carried the customer's credentials, the global directory of available POP access numbers, the Wi-Fi hotspot login profiles, and the hotel-Ethernet activation flows. A single monthly statement consolidated consumption across every service type into the same customer-facing total in the customer's home currency. A single customer-service relationship handled questions about any of the service types. Customers reviewing their usage saw a mix of per-minute voice and dial-up lines, per-megabyte satellite data lines, and per-day Wi-Fi and Ethernet lines, all rolling up to the same account total. None of the underlying carrier heterogeneity surfaced to the customer.

Institutional customer base

The platform served a customer base that ranged from individual road-warrior business travellers through to named institutional accounts. The institutional customers documented for Tempest's 1997-onward dial-up roaming era — the US Agency for International Development (USAID), NATO's Supreme Allied Commander Europe (SACEUR), and the United States Department of State — carried forward into the satellite and Wi-Fi eras as natural extensions of the same customer relationships. A USAID field officer deployed to Sub-Saharan Africa, who had used a Tempest dial-up roaming credential in 1999, could be using a Tempest-resold Iridium handset, a Tempest-resold BGAN terminal, and Tempest-aggregated Wi-Fi in 2005, all drawing from the same balance she had topped up before deployment. The architectural continuity supported customer continuity.

The closeout, 2008-2012

The consumer-facing platform faded across 2008-2012 not from a single cause but from the simultaneous erosion of every service type it integrated. Dial-up Internet collapsed as broadband saturated travel destinations and as cellular data made laptop tethering routine. Metered Wi-Fi collapsed as hotels and airports moved toward free included access. The consumer satellite voice market faded as cellular coverage reached previously remote regions and as smartphone tethering replaced satphones for casual users. The consumer satellite data market consolidated upward toward enterprise contracts directly with Inmarsat, Iridium, and Thuraya. International calling-card volume collapsed as cellular voice rates fell sharply through the international-roaming reform of the early 2010s. By 2012 the platform's core customer base had either consolidated into direct enterprise relationships with the underlying carriers or had been absorbed into the cellular network. Tempest wound down consumer operations through the early 2010s in tandem with the broader closeout of the international traveller connectivity business that had been the company's core product line for fifteen years.

What the pattern became

The architectural pattern Tempest deployed against the international-traveller market in 1997-2012 reappeared in different markets at industrial scale through the 2010s and 2020s. Modern carrier-agnostic eSIM marketplaces let a customer carry a single device whose profile authenticates against many carriers in many countries, with consumption billed back to the marketplace operator on a unified statement. Multi-network IoT data products federate authentication and accounting across cellular carriers for fleet-management applications. Unified telecommunications-billing platforms broker authentication, accounting, and reconciliation across multiple heterogeneous carrier back-ends as a B2B service for enterprises with multinational footprints. Major cloud-provider hyperscalers offer unified APIs over multiple satellite, cellular, and Wi-Fi data services with consolidated billing. The 3GPP family of standards now includes the “converged charging” specification (3GPP TS 32.290) that codifies real-time rating across heterogeneous service types in 5G core networks. Each of these modern systems operates the same conceptual pattern Tempest ran on a much smaller market: one customer relationship, multiple network types, unified real-time reconciliation.

The historical archive preserved on this site documents the 1997-2012 implementation in detail, page by page. The synthesis above is the shape of the architecture; the service-by-service pages are the build-out, the customer stories, the carrier specifics, and the failures.

The complete archive

• RFC 2058 in Production — How RADIUS Made ISP Roaming Possible in 1997 — the technical foundation underneath the dial-up Internet leg of the platform, with institutional customer base (USAID, SACEUR, US State Department) documented.
• One Card, Two Networks — Tempest's 1997 Combined Calling Card and Dial-Up Roaming Product — the founding product that established the unified-balance pattern with PSTN voice and dial-up Internet on a single PIN.
• Public Access Terminal Networks (PATN) — Tempest's 1998 Kiosk Roaming Protocol — the failed 1998 federation attempt; category-timing failure rather than protocol-design failure.
• Two Satellites, One Balance — Tempest's Iridium and Thuraya Prepaid Integration (2001-2012) — the satellite voice leg of the platform; Iridium post-Chapter-11 relaunch in 2001, Thuraya MENA launch in 2001, integration into the unified balance.
• Beyond Voice — Tempest's Satellite Data Terminal Business (Thuraya, RBGAN, BGAN, 2002-2012) — the satellite data leg; R-BGAN 2002-09, BGAN 2005+ with named terminal vendors (Hughes 9201, Thrane Explorer, Nera WorldPro, Addvalue Wideye Sabre I), ThurayaDSL 2007+.
• The Metered Wi-Fi Era — Hotspot Roaming on Tempest's Unified Platform (2002-2012) — the terrestrial broadband leg; WISPr 1.0 from February 2003, $19.95 per 24-hour flat session rate, named hotspot partners.

See also the contemporaneous customer-facing Wi-Fi documentation preserved in the services archive, and the 229-country reference guide in which each country page documents Tempest's services in that specific market.

This page is part of an ongoing historical archive of the 1989–2012 international telecom industry, maintained by Jason Jacoby, a former operator at Interglobe (UK phone cards) and Tempest Telecommunications. Corrections and additions welcome via the contact page.