Travel Connectivity
Partner Enablement
Network Infrastructure
API Solutions
Sudarva Connect
Sudarva GoComing soon
Guides
Support
About Sudarva
History of Internet
CareersHiring
Insights
Contact Us
One network. Every journey.

Infrastructure that powers the future of travel.

Sudarva is the technology infrastructure that connects travel businesses, partners and travellers across Asia and beyond.

The gap

A connectivity API isn't a
travel platform.

Plugging into a network gets you data. Running a travel business needs everything that happens around it.

What a connectivity API gives you
03
What travel actually needs
05

Three things versus everything else. The asymmetry is the whole argument.

Where we sit

The layer between networks and channels.

Networks
Sudarva.
Provisioning · KYC · Metering · Settlement
Channels
What we do

Four capabilities. One platform.

Who it's for

Built for the travel channel.

Most platforms split their offering by telco type. We split by travel channel — same slot, opposite meaning.

For partners

Provisioning in one call.

Our API isn't public — it's provided internally to onboarded partners. One request provisions a profile, runs KYC and starts metering. Webhooks stream usage; settlement reconciles itself.

provision.sh
Why we exist

The infrastructure that makes global travel seamless.

About us

Sudarva is a travel-tech infrastructure company — the wholesale data distribution layer that lets any travel business offer seamless connectivity without becoming a telecom company.

Somewhere between a mobile network and a traveller standing in an airport with a dead phone, there's a gap.

Networks sell data to companies that understand telecom. Travel businesses understand travellers. Neither was built to talk to the other — so every travel company that wants to offer connectivity ends up building the same plumbing from scratch. Provisioning. Identity. Metering. Settlement. Reconciliation. All of it, before a single byte is sold.

That's backwards. Distribution shouldn't be something each company reinvents. It should be infrastructure.

That's what we're building.

What we're building

Sudarva is a wholesale data distribution layer. Not a product. Not an app. A layer.

It sits between the networks that carry data and the channels that reach travellers, and it does the work neither side was built to do: turning a raw network profile into something an agent can sell, a traveller can verify, a partner can be paid for, and a business can account for.

Any travel business, anywhere, can offer connectivity without becoming a telecom company.

What comes next

The layer isn't only for data.

Once distribution, identity and settlement exist as infrastructure, the same rails can carry anything a traveller buys away from home — tickets, transfers, stays, experiences. Anything a channel needs to sell, meter and settle.

Data is where we started, because it's the hardest part. It isn't where we stop.

How we build

Principles, not slogans.

The team

The one thing we keep sealed.

Every great brand has a formula it never prints on the label. A recipe locked in a vault, known to a few, never handed out. The people who build Sudarva are ours.

We don't publish the roster, the org chart, or the names. Not out of secrecy for its own sake — because the team is the recipe, and the recipe stays safe in our hands.

Sealed roster
Classified
+ the rest, redacted
How the team works

We navigate like migratory birds.

The founder believes in migratory birds. They cross continents with no map handed to them — holding formation, trading the lead, trusting the season and each other. No worn trail. No single footprint to step into.

The tech team works the same way. We take turns at the front, share the draft behind whoever's leading, and keep moving toward something that isn't on any chart yet. Nobody here is following.

We're not here to follow a trail. We're here to leave one — to make something new in the history of how travel connects.

The long view

Infrastructure is a long promise.

The businesses that build on this layer are trusting it to be here in ten years — still metering correctly, still settling on time, still connected when a traveller is standing in a foreign airport at 2am. A promise that size isn't made in an announcement. It's made in the architecture, and it's made early, or it isn't made at all.

So the layer was built before it was named. Every hard part first: the metering, the ledgers, the settlement, the part where nothing breaks when two companies disagree. Not because the unglamorous work is noble — because it's the only part that has to be right forever.

What comes next is scale. More countries. More channels. More volume than anyone planned for. That's the work now.

Failure was never the end of anything. It was information, arriving early. Impossible is just a sentence people finish too early — because the impossible becomes possible the moment you stop looking outside for the answer and start looking within. Failure is only the receipt of hard work. Fear the work, and your dream stays a dream. Face the failure, and the dream comes true.

— Founder and CEO, அருண் ராஜ்

Build on the layer.

Become a partner
Before you apply

What we mean when we say freedom.

Freedom is the most misused word in this industry.

It has come to mean beanbags. Work from anywhere. Unlimited leave that nobody takes. Those are comforts, and comfort is a fine thing — but comfort is not freedom. A comfortable person can still be trapped. Most are.

Freedom is the ability to decide your own life. Where you live. Who you take care of. What you say no to. What you build.

That ability is not given to you by a policy document. It is earned. Which means real freedom — the kind you can actually spend — starts with the freedom to earn.

But earning alone is not it either

A person with money and no aim is not free. They are only loose.

Drifting looks like freedom from the outside. It isn't. Without an aim, every day is a choice made again from zero, and a life made of resets goes nowhere. Effort without direction is just motion, and motion is exhausting.

An aim converts effort into direction. Direction is what makes a dream reachable instead of decorative.

That's the part most people have backwards. They think the aim is the cage and freedom is escaping it. It's the opposite.

The aim is the thing that sets you free.

It's what lets you work on one hard problem long enough for it to actually move. And watching something move because you moved it is the closest thing to freedom a working life offers.

So this is what we're offering

Not comfort.

An aim worth having. Work that compounds into skill nobody can take from you. And the means to build the life you actually want.

That's the trade. It's a real one. It isn't for everyone.

Who this is for
People who want to own a hard problem, not a job description.
People who would rather build the thing right than be seen building it.
People with a dream expensive enough that they need to earn — and specific enough that they know what for.
Who it isn't for
Anyone who needs someone else to supply the aim.
One more thing

You won't find us on social media. There's no feed, no company page, no one posting about culture.

That isn't a stance against anyone else's choices. It's arithmetic: the hours go into the layer, or they go into being seen going into the layer. We picked one.

The founder writes in public. The company doesn't market itself. Those are different things.

So if you want to know what we're like, there's only one way to find out. Apply, and talk to us.

Open roles

05

Every band is real and stated up front — salary plus equity with a strike price and vesting spelled out at offer. The freedom to earn is a promise we keep with a number.

Apply

Tell us what you'd own.

No cover letters. Pick a role, show us something you've built, and tell us the aim you're chasing. We read every application ourselves.

Sudarva.
Application received

Thank you. We’ve sent a confirmation to your email. If there’s a fit, we’ll be in touch within a week.

Guides

Get access to
Sudarva Connect.

A private API for onboarded partners. Four steps from first conversation to your first provisioned eSIM.

01Start here

Contact sales.

Everything begins with a conversation. Tell us about your business, your travel channel and your expected volume — there is no self-serve sign-up.

Partner access is granted by our team, not a form.
Contact sales
02

Partner portal & keys.

Once approved, log in to the partner portal and generate your API keys. You get a Live key for production and a Test key for the sandbox.

Confirm access

Developer Analytics, Wallet, My Inventory, My Packages and Countries should all open.

Live key

Label it "Production". Copy sk_connect_… once — it isn't shown again.

Test key

Label it "Sandbox". Copy sk_connect_test_… for fixture runs.

Authorization
curl https://api.sudarva.io/connect/v1/profiles   -H "Authorization: Bearer sk_connect_…"
# or
  -H "X-API-Key: sk_connect_…"
03

Fund your wallet.

Live assign and subscription calls debit your wallet. Request a recharge before Live traffic — sandbox is funded automatically.

Live

Open Wallet and request a recharge. Admin approval funds your balance before production calls.

Sandbox

Test keys auto top-up a sandbox balance on the first Connect call — no portal recharge needed.

04

Postman & first call.

Import the collection, point it at your endpoint, and run your first provisioning request against the sandbox.

  1. Download the collection from the API Reference in the portal.
  2. Set baseUrl to your assigned Connect endpoint.
  3. Set connectApiKey = live secret; connectTestApiKey = test secret.
  4. Use primary Connect folders for Live; use the SANDBOX folder for fixture runs.
Ready when you are.

Access still starts with a conversation. Tell us what you're building and we'll open a line.

Contact sales
Support

How can we help?

Browse by topic

Popular articles

Still stuck?

Partner support responds within one business day. Live incidents are escalated to the on-call team in real time.

Sudarva Connect

The connectivity management platform for travel.

Launch a fully branded eSIM business on infrastructure that's already running.

The platform

Sudarva Connect brings global data, eSIM provisioning and day-to-day operations into one API-driven layer.

Any travel business can launch a fully branded eSIM service — without upfront infrastructure, carrier contracts or telecom expertise.

One integration. 184 countries. Your brand on top.

Who it's for

Travel platforms, OTAs, agencies and operators that want connectivity as part of their own product — under their own brand, their own pricing, their own experience.

Built for how travel businesses actually operate: at launch, and as they scale across markets.

What it does

Skip the retail roaming markup.

A normal SIM routes home across every border and pays retail roaming on every byte. Sudarva's multi-profile network infrastructure connects each traveller to a network in-market instead.

One eSIM, many profiles — coverage across 184 countries and 459 networks, without the retail roaming penalty travellers usually pay.

Why it matters

Connectivity without becoming a telco.

Launching connectivity used to mean carrier deals, billing systems, compliance and provisioning. Connect removes all of it — you bring the customers and the brand; the infrastructure is already built.

Ready to launch on Sudarva Connect?

Tell us about your channel and we'll open a line. Partner access starts with a conversation.

Contact us
The long arc

The history of the internet.

It began with a simple, radical idea: that a message could travel without its messenger. Two hundred and thirty years later, six billion people are online. This is how the connective layer of the modern world was actually built — decade by decade, protocol by protocol.

Reading time · 14 min Updated · July 2026 Filed under · Networks
6.0B
People online, 2026
73%
Of world population
2.1B
Still offline
~600
Submarine cable systems
01 — Before the wire

Separating the message from the messenger

1792 — 1900

For all of recorded history, information moved at the speed of a horse, a ship, or a running man. The first true break came in 1792, when Claude Chappe strung a chain of semaphore towers across France. Operators read the pivoting arms of the next tower through a telescope and repeated the signal onward. A message crossed the country in minutes instead of days.

It was not electric, but it was the first system built for one purpose only: to move information faster than a person could carry it. Every network since is a refinement of that idea.

Electricity arrived in 1837, twice over. In Britain, Cooke and Wheatstone installed a working telegraph on the Great Western Railway. In the United States, Samuel Morse built a single-wire system and, more importantly, a code — a way of reducing language to two symbols, short and long. Cooke and Wheatstone got to a public installation first. Morse won, because his design needed one wire where theirs needed six.

Reduce the alphabet to two states, and any wire on earth becomes a sentence.

The logic of Morse code, 1844

The telephone followed in 1876, in one of the most bitterly disputed patent races in engineering history — Bell filing hours ahead of Elisha Gray, with Antonio Meucci's earlier working device lost to an unpaid renewal fee. By 1901, Marconi had pushed a signal across the Atlantic without any wire at all.

By the turn of the century the world had voice, distance and wireless. What it did not have was a way for machines to talk to each other.

02 — The packet

A network with no centre

1961 — 1969

Telephone networks were built on circuits: to talk, you opened a dedicated line and held it open. It worked for voice and was catastrophically wasteful for data, which travels in bursts. Worse, a circuit-switched network has a centre — and anything with a centre can be cut.

The answer emerged independently in three places. Leonard Kleinrock at MIT worked out the queueing mathematics. Paul Baran at RAND, thinking about communications surviving a nuclear strike, described a distributed mesh with no central node. And Donald Davies at Britain's National Physical Laboratory arrived at the same structure and gave it the name that stuck: the packet.

Break a message into small labelled pieces. Let each piece find its own route. Reassemble at the other end. If a node dies, the packets simply go around it. It is the single most consequential idea in the history of networking.

  • 1966ARPA funds a four-node experimental network to test the theory.
  • 29 Oct 1969The first message is sent from UCLA to Stanford Research Institute. The operator types L, then O — and the system crashes before the G. The first word ever sent over the network was, accidentally, "LO".
  • Dec 1969ARPANET reaches four nodes: UCLA, SRI, UC Santa Barbara, Utah.
Worth noting

The persistent myth is that ARPANET was built to survive nuclear war. Baran's research was; ARPANET itself was funded for a duller and more human reason — expensive computers were scarce, and researchers wanted to share them remotely.

03 — The protocol

The rules that made networks a network

1971 — 1986

By the early 1970s several packet networks existed — ARPANET, radio networks, satellite links — and none of them could speak to the others. The problem was no longer building a network. It was building an inter-network.

In 1974, Vint Cerf and Bob Kahn published the design for a protocol that assumed nothing about the networks beneath it. It would not require them to be reliable, fast, or even similar. It only required that they pass packets. That design became TCP/IP, and its indifference to the underlying medium is precisely why it is still running the world half a century later — over copper, fibre, radio, and satellite links its authors never imagined.

  • 1971Ray Tomlinson sends the first network email and chooses @ to separate user from machine — a symbol nobody was using for anything else.
  • 1973Robert Metcalfe designs Ethernet at Xerox PARC, solving the local half of the problem.
  • 1 Jan 1983Flag Day. ARPANET switches from NCP to TCP/IP overnight. Machines that had not been updated simply stopped working. This is the internet's actual birthday.
  • 1983–84Paul Mockapetris invents DNS, replacing a single hand-maintained file of every host on the network with a distributed naming system.
  • 1986NSFNET builds a national backbone and connects the university system, becoming the spine the public internet would inherit.

For twenty years the network existed and almost nobody outside research institutions could use it. It had addresses, routing and names. It had no front door.

04 — The web

The door opens

1989 — 1999

In March 1989, a British physicist at CERN named Tim Berners-Lee circulated a proposal for managing the laboratory's tangled documentation. His manager's written response has become famous: "Vague but exciting."

What he built combined three things — a way to address a document (URL), a way to fetch it (HTTP), and a way to write it with links to other documents (HTML). The first website went live at the end of 1990. It explained what a website was.

The decisive moment was not technical. On 30 April 1993, CERN placed the web into the public domain — no licence, no royalty, no owner. Had it been patented, the internet as we know it would almost certainly not exist.

Vague but exciting.

Mike Sendall, on Berners-Lee's proposal, 1989
  • 1993Mosaic, the first browser to display images alongside text, makes the web comprehensible to non-specialists.
  • 1995NSFNET is decommissioned and the backbone passes to commercial carriers. Amazon and eBay launch. India's public internet opens on 15 August, via VSNL.
  • 1998Google is founded, and ICANN takes over the naming system.
  • 2000–01The dot-com crash erases enormous paper value — and leaves behind the fibre, the habits and the engineers.
05 — The pocket

The internet stops being a place you go

2004 — 2016

The second decade of the web changed who was writing it. Platforms replaced pages: Facebook in 2004, YouTube in 2005. In 2006, Amazon began renting out its own spare infrastructure, and the cost of starting something on the internet collapsed from millions to a credit card.

Then, in 2007, the internet moved into a pocket. The smartphone did not add a new way to access the network — it removed the idea of accessing it at all. Connectivity stopped being a destination and became an ambient condition.

The consequences were largest where fixed-line infrastructure had never arrived. Across South Asia and Africa, hundreds of millions of people came online without ever having owned a computer. In 2016, India's data market was upended almost overnight when the price of mobile data fell through the floor; the country added internet users at a pace no market had seen before.

The shape of the shift

For its first thirty years the network was designed for machines that stayed still. Every assumption — fixed addresses, stable routes, reliable power — was built around that. The mobile era inverted it, and much of the last decade of network engineering has been spent catching up.

06 — Now

Six billion, and the two billion missing

2017 — 2026

In 2026 the internet passed a threshold it had been approaching for a decade: more than six billion people online, roughly 73% of everyone alive. India alone accounts for around a billion of them, with penetration crossing 70%.

The last few years have layered three shifts on top of each other. 5G pushed capacity to the edge. Generative AI, arriving in public hands at the end of 2022, became the fastest-adopted consumer technology in the network's history and began reshaping what the traffic on it actually consists of. And eSIM quietly severed the last physical link between a device and a network operator — a subscription became software.

But the more instructive number is the other one. Roughly 2.1 billion people remain offline, overwhelmingly in South Asia and Sub-Saharan Africa, and the gap is no longer mainly about cables. It is about cost, devices, literacy and — persistently — gender: men remain meaningfully more likely to be online than women, a gap several times wider than the population difference.

Meanwhile the physical substrate stays stubbornly, unglamorously material. Something close to 600 submarine cable systems carry the overwhelming majority of intercontinental traffic. The cloud is, in the end, glass on a seabed.

07 — What's next

The layer that hasn't been built yet

2026 —

Every era in this history resolved a specific incompatibility. Packets reconciled bursty data with rigid circuits. TCP/IP reconciled networks that could not speak to each other. The web reconciled documents with the people who needed to read them.

The unresolved incompatibility today is distribution. Mobile networks are national by construction — licensed, regulated and settled country by country. Travel, commerce and software are not. Between the global supply of mobile data and the channels that actually reach travellers sits no wholesale layer worth the name: no clean way for a network's capacity to reach a distributor in another country at scale, in real time, with settlement that works.

That gap is the reason this history is worth reading carefully. Each previous layer looked like plumbing until it existed, and then looked inevitable.

···  ··−  −··  ·−  ·−·  ···−

Ready to launch on Sudarva Connect?

Tell us about your channel and we'll open a line. Partner access starts with a conversation.

Contact us
Contact us

Let's talk about your channel.

Partner access starts with a conversation. Tell us about your business and expected volume — we reply within one business day.

Partnershipspartners@sudarva.io
Supportsupport@sudarva.io
Sudarva.
Message sent

Thanks — we’ve emailed you a confirmation. Our team will reply within one business day.