Every way online, arranged as one.
Satellite is usually a separate link with its own portal, its own contract and its own support queue. Here it is provisioned from the same API as everything else you buy from us, and answered by the same people.
- Points of presence
- In-region
- Media is anchored in the region it originated, with compute in the same facilities.
- Interconnect
- Direct
- Peering with the networks and carriers we exchange traffic with, rather than through a transit chain.
- Ground stations
- Backbone-attached
- Orbital capacity enters the Lux network at the station, not at a public exchange.
- Provisioning
- One API
- A terminal, a number, a SIM and a trunk are created the same way, under one identity model.
What it means for orbit to be part of the network.
A terminal is provisioned from the same API as a number or a SIM, with the same identity, the same policy and the same audit trail. It appears in the console beside the fibre sites, not in a second portal with a second login.
Traffic joins the Lux network at the ground station. From there to your cloud, your data centre or another site of yours, it stays on infrastructure we route — which is why the latency is a number we can commit to rather than one we observe.
A device keeps its number and its subscriber identity as it moves between a private wireless network, a public one and an orbital link. Hand-off is the network’s problem. The application never learns which transport it is on.
A site that fails over from fibre to orbit does not change vendors mid-incident. The same operations team sees both paths, and the credit for a missed service level comes from the same contract.
Internet wherever it has to be — fixed, wireless, satellite, and the backup link behind it.
Symmetric broadband to sites terrestrial carriers will not quote: mine heads, farms, construction, disaster zones, research stations. Provisioned from the same console as a number or a SIM, and routed onto the Lux backbone at the ground station rather than out to the public internet.
- Service to coordinates a terrestrial carrier will not quote, including sites with no road access
- Round trip to the nearest Lux point of presence suitable for interactive use, including voice
- Terminals ship configured — a site comes up without a truck roll or a network engineer
- Traffic joins the private backbone at the ground station — it does not transit the public internet to reach your cloud
Stabilised terminals for vessels and aircraft, with capacity that follows the route rather than the port. Crew welfare, operational telemetry and passenger service ride the same link, separated by policy rather than by hardware.
- In-motion terminals rated to open ocean and commercial flight profiles
- Route-following capacity commitments rather than per-port contracts
- Operational and passenger traffic separated on the terminal, not by a second dish
- Per-vessel and per-tail reporting through the same API as every other site
Backhaul for mobile operators at sites where trenching fibre never pays back. The tower terminates into the Lux backbone and hands off at the operator’s core, so coverage extends without a civil works programme.
- Carrier hand-off at the operator core, not at a public exchange
- Latency budgets suitable for standard voice and data profiles
- Sites commission on the timescale of a delivery rather than a civil works programme
- Terrestrial and orbital transport under one SLA and one invoice
Automatic cellular — and, where it is deployed, orbital — failover when the primary circuit drops. The site keeps its address and its sessions; the transport underneath changes.
- Detection and cut-over fast enough that sessions survive it
- The public address is retained, so sessions and inbound routes survive
- Failover capacity billed on use, not on standby
A private LTE or 5G network for a site — port, mine, campus, factory floor — with the core hosted by Lux and the spectrum handled for you. Devices roam onto the public network at the gate without changing identity.
- Hosted core; the site runs radios, not a telco
- SIM identity shared with the public network, so a device keeps one identity as it roams
- Site-local breakout keeps machine traffic on the factory floor
One integration, end to end.
- 01Internet
Offices, remote sites, infrastructure and mobile operations, including the places conventional networks do not reach. Fixed, wireless, satellite and redundant — we choose the connection that fits the location rather than selling you the one we happen to carry.
- 02Cellular
SIM and eSIM for fleets, equipment, sensors, backup links and products shipped across borders. One deployment covers the countries you operate in, instead of a separate carrier relationship in each of them.
- 03Voice
Numbers, calling, routing, SIP and programmable voice — the machinery behind a modern communications product. Point it at your people, or hand the number to an agent.
- 04Messaging
Send alerts, receive replies, verify a user, run a two-way thread. SMS, MMS and the delivery infrastructure underneath, on the same platform as everything else you buy here.
- 05AI agents
Agents that talk, text, call your APIs, use tools and finish a task: qualify the lead, book the appointment, update the record, raise the ticket, escalate to a person when it matters. Reachable over voice, messaging, web and API.
- 06Network
Private networking, VPN, routing, failover and multi-network deployments, designed around what has to stay online rather than around one provider’s footprint — and carried with post-quantum key exchange, so traffic captured today is not readable later.
Building on orbit with us?
We carry capacity, run ground infrastructure, and hold the numbering and wireless licences that turn a link into a service. Partnerships go to the address on the right.