One pool of data for the whole company, and nothing in it expires.

What pooling actually changes

The usual way a company buys travel data is a plan per trip per person. Somebody flies to Frankfurt, buys a 10 GB plan, uses 8 GB of it, comes home, and the rest is deleted on day 30. Multiply that by a sales team and the waste is not a rounding error, it is the largest line in the bill.

A pool removes the deletion. You buy into one balance, everybody draws from it, and what nobody used in March is still there in April and still there next year. Finance stops forecasting per trip and starts forecasting per quarter, which is the only forecast that was ever going to be accurate.

The second thing it changes is provisioning. Nobody has to buy anything. A new starter is added in the admin console, gets a profile that installs once, and it keeps working in every destination after that without a purchase, a QR code or an expense claim.

Caps per person, and what happens at the ceiling

Every person on the account carries a monthly ceiling that you set, in gigabytes, and you can set a different one for the field engineer and for the office. The default alert fires at 80 percent of the cap, to the traveller and to whoever administers the account.

At the ceiling the profile does not cut off. It drops to 1 Mbps and keeps working, so somebody in a taxi from an airport at midnight can still open a map and a messaging app. Cutting a traveller off entirely to enforce a policy is a decision made by a person who has never been the traveller.

Going over the cap is a request, not a support ticket. The traveller taps once, the administrator gets it, and we hold ourselves to a decision inside 4 working hours. If nobody answers, the extra is granted rather than denied, and the request is on the invoice for review. Silence should not strand somebody abroad.

Caps can also be set per destination, so a team that flies to two countries a month does not carry a policy written for a team that flies to forty.

One invoice, and what is on it

One consolidated invoice a month, on net 30, with your VAT or GST registration on it and a purchase order reference if you use one. Not a card receipt per employee per trip.

The invoice carries a line per traveller and, underneath it, a line per destination. That means the cost of the Singapore trip is a number rather than an archaeology project across eleven expense claims.

The same breakdown comes out as CSV and through the API, keyed on your own employee identifier rather than ours, so it reconciles against your expense system without anybody retyping a name.

Top ups draw down the pool automatically when it falls below a floor you set, so a traveller is never the person who discovers the company ran out of data.

Single sign on, at no extra cost, at any size

Spend controls that a finance team can actually operate

Policy sits on the account rather than in a document nobody reads. You can allow or block destinations, set a per person monthly ceiling, set a company monthly ceiling, and require approval above either.

Alerts go out at 80 percent of any ceiling by email, by webhook, or into Slack. You can add your own thresholds on top.

Every purchase, top up, cap change and approval is written to an audit log with who did it and when, exportable, and retained for 24 months.

None of this is a separate product or a higher tier. It is on the account from the first day, because a company that cannot see its spend has not bought a cheaper product, it has bought a slower incident.

The same API our own store runs on

There is no special business API. You get the public one, plus the admin endpoints, and we build the store on it ourselves so it cannot quietly rot.

You can create a member, issue a profile, set or change a cap, read usage per person per destination, pull the invoice lines, and receive webhooks on activation, on the 80 percent alert and on a cap request. Rate limits run from 120 requests a minute at the smallest size to 2,400 at the largest.

The coverage dataset behind every speed and destination number on this site is public and machine readable, so an internal tool can decide which country is worth a policy exception without asking us.

What a team of 5, 20 and 100 gets

Worked at 5 GB a person a month, which is what our own travelling staff average. Change the assumption and the pool changes with it, since a pool is bought in gigabytes rather than in seats.

What the pool costs, against buying a plan per person

The wallet column is our own consumer price for the same data bought individually. The ticket column is what an expiring single trip plan of the same size costs across the largest sellers, checked on 24 August 2026 and rounded to the nearest half dollar. The last column is what the pool saves against that ticket, before counting the fifth of a plan that typically goes unused and is deleted.

How to start

Tell us the headcount that travels, the destinations they go to, and roughly how much data a person uses a month. If you do not know the last one, the assumption in the tables above is 5 GB a person a month, which is what our own travelling staff average.

We come back with a pool size, a monthly figure and a start date. There is no minimum term, no cancellation fee, and the balance you have paid for stays yours if you stop, because it does not expire.

Accounts under 3 people are better off on the consumer wallet, and we will say so rather than sell you an admin console you do not need.

Questions a buyer asks