Data for every traveller on the team, and none of it expires.

What a balance per traveller 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 balance that never expires removes the deletion. Each traveller's gigabytes stay theirs, so what somebody did not use in March is still in their balance in April and still there next year. Finance stops forecasting per trip and starts forecasting per quarter, which is the forecast that holds.

The second thing it changes is the trip itself. Nobody has to buy anything before they fly. The first time a traveller uses their balance in a destination, the app issues that destination's line and it installs in one tap. After that, refills arrive on the line they already have, with no QR code to chase and no expense claim to file.

A set amount per person, and what happens when it runs low

Every traveller holds the gigabytes you allocated, and you can give the field engineer more than the office. Data leaves a balance only as it is used, at that destination's rate, so an allocation lasts exactly as long as the travelling it covers.

Each person's balance is their ceiling, so nobody spends past what you gave them. As it runs low the traveller gets an email, and if it reaches zero they get free rescue data once a month, loaded onto the line they are using, so they can always open the app and ask for more.

Adding data is an email, not a support ticket. Tell us who needs more and how much, and we credit it to that traveller's balance. It reaches the line they already have without a new install, so nobody has to set anything up again to use it.

Most of Europe runs on a single regional line, so a team that crosses several European borders in a week does it on one line rather than one install per country.

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.

Refills come out of the traveller's balance onto the line they already have, automatically while that line is valid, so nobody waits in an arrivals hall for a new install to finish.

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

What a traveller sees abroad

There is nothing to set up at the gate. The first time a traveller uses their balance in a destination, Orbislo issues that destination's line, or a regional line that also covers its neighbours, and they install it with one tap in the app.

In most popular destinations a wallet gigabyte is a full local gigabyte. Dearer networks draw at their own published multiple, shown before the line is issued, so a traveller knows what a day in that country takes from the balance.

If an activation fails, the data goes back to the balance automatically, with no request to file. Data loaded on a line and not used also returns to the balance when the line closes, so a gigabyte bought for one trip is never lost on it.

None of this is a separate product or a higher tier. It is the same wallet every Orbislo customer holds, bought in bulk and invoiced to the company, so your travellers use the same app as everyone else and get the same answers from support.

The same API our own store runs on

There is no special business API. You get the public one, and we build our own store on it, so every endpoint you depend on is one we depend on too.

You can read the destination catalogue, the coverage behind each destination and the prices in every currency we sell in, from the same data our own pages are built from. 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 figures change with it, since the account is bought in gigabytes rather than in seats.

What the account 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 business rate 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 written price, the gigabytes for each traveller and a start date. There is no minimum term, no cancellation fee, and the balances you have paid for stay with your travellers if you stop, because they do not expire.

Accounts under 3 people are usually better served by the consumer wallet, which carries the same per gigabyte rate, the same coverage and the same balance that never expires. We will point you there, and each person can buy the day they need it.

Questions a buyer asks