Turn your fiber into the on-ramp every GPU cloud is reached through.
The AI on-ramp for your market, run as your marketplace. Every GPU and neocloud provider in the region is listed on it and reachable in minutes. You own the on-ramp, the relationship and both sides of the bill. The scope is the access layer alone, on your network, live within 90 days.
ONE ON-RAMPEVERY PROVIDER ON ITBOTH SIDES BILLABLE
On your fiber. Inside your borders. Under your name.
THEIR COMPUTE, THEIR PRICE
THEIR COMPUTE, THEIR PRICE
THEIR COMPUTE, THEIR PRICE
The compute is landing.
The road to it is not built.
Capital is going into AI compute faster than any operator has seen it move, and every build lands as its own island. Nobody can reach it privately, so every request becomes a one-off networking project quoted per account, and the capacity sits there waiting.
The distance between 5 and 70 is 65 points of utilization nobody can reach, and it is not a networking problem the GPU providers are going to solve. Their build focus is compute, power and contracts, and rightly so. The on-ramp has to come from the network side, and you are the network side — and the layer above the fiber already earns $0.70 of advanced services per $1 of connectivity at a major US operator, up from $0.20.
Every build is an island. The on-ramp is what turns them into a market.
A GPU cloud in your market
Reached over your on-ramp: a GPU cloud in your market, a neocloud region, an enterprise data center, a colo cage, a branch site, a public cloud region, whatever lands next.
- 5% Average GPU utilization today
- 70% What a 1,024 GPU H100 cluster needs to break even
- $330K Lost every month it runs 15 points below that
- Weeks Of lead time per private path. On an on-ramp, minutes.
- 111 to 114% Net revenue retention at the platform layer above your pipe
WHAT MAKES THIS DIFFERENT FOR AN OPERATOR
One on-ramp you own. Every provider in your market on it, live in a quarter.
You become the on-ramp every GPU and neocloud provider in your market is reached through, and the marketplace where enterprises find them. It runs on your fiber, inside your borders and under your name, and both sides are billable. Three things make that a quarter of work rather than a roadmap item.
One on-ramp. Every provider in your market listed on it.
You stand the on-ramp up once and run it as your marketplace. Every GPU and neocloud provider in the region is listed on it under its own logo, with its own capacity and its own price. Any enterprise that lands on your on-ramp reaches any of them in minutes, over your fiber, under your name.
Your name is on the access contract with the enterprise and on the listing agreement with the provider. Both sides are billable. Adding the second provider is a listing on a platform that is already up.
The path stays on fiber you own, inside your borders.
Every enterprise path to every provider on your marketplace runs on fiber you own, hands off inside your borders and answers to the license you already hold. The telemetry proves it flow by flow. A marketplace sitting above your pipe carries the same enterprise off-net, and can only promise best effort.
Sovereignty is the one thing a player above your pipe cannot rent from you. On your own fiber it is yours by construction.
Start with a few sites. Grow when a provider asks.
A high availability on-ramp edge node pair, in facilities you already run, handed off over a standard NNI, and live within 90 days.
The footprint follows provider demand, so every site you add is one a provider has already asked for. The scope stays the access layer, which is what keeps the number a quarter.
THE TWO SIDES OF YOUR MARKETPLACE
One side brings the compute. The other side brings the workloads.
A marketplace only works if both sides turn up, and both sides have to be better off on yours than anywhere else. Here is what each one gets, and how fast it gets it.
One on-ramp · two sides · both of them billable
SUPPLYGPU and neocloud providers, listed under their own logosONBOARDED IN DAYS
DEMANDEnterprise customers, each one in its own gVPCTURNED UP IN MINUTES
Every GPU and neocloud provider in your market sits above one on-ramp, and every enterprise customer sits below it. The on-ramp is yours: your marketplace, your name, and a bill on each side, the listing and access on the provider side and the access and capacity on the enterprise side.
Reach that arrives already built
A provider has a few campuses. You have metros, buildings and meet-me rooms. Listing on your on-ramp is the only way they reach an enterprise where it already is, and it costs them no capital to do it.
Enterprise access, fully operated
Their engineers stay on GPUs, power and contracts, which is where they want to be. The private path, the policy, the telemetry and the routing are yours, and they never hire a single person for any of it.
Turned up in minutes
Today every enterprise that wants a private path into them is an LOA, a cross-connect order and weeks of lead time. On your on-ramp it is a turn-up in minutes, at any hour, with no order form.
Neutral by construction
You never rent compute to the enterprises they are chasing, and you never will. For a provider deciding where its private on-ramp lives, that neutrality is the whole decision, and it gets more valuable every quarter.
What the market already prices
Compute discounts. The on-ramp does not — and on your marketplace, the on-ramp is yours.
Published neocloud price lists, September 2026.
A gVPC per enterprise customer
Where a cloud VPC is private to one region of one cloud, a gVPC is private to one enterprise customer and reaches everywhere that customer works: any cloud, any data center, any site and the internet.
Security Groups that follow the workload
Policy-driven groups replace per-site VPNs and firewalls. Every workload reaches only what it needs, with full encryption and zero added hops. One endpoint can sit in several overlapping groups while blast radius stays per group.
Live rate, loss and completion
Telemetry on every link, at flow level. Anything moving where it should not is flagged in real time, which is the evidence an enterprise security team asks for before it moves a regulated workload.
One routing layer across every cloud
Direct Connect, ExpressRoute, cluster BGP and the wavelength beneath, spoken as one language across every cloud and carrier. The path is yours to set, and to prove.
Elastic capacity, billed by the window
Provisioned in minutes, gone at teardown. Hundreds of TB at 100G and 40G bursts, with cheap persistent links in between. The customer pays for the window, not the year.
NEO, so an agent can order it
An enterprise describes two endpoints in plain language and NEO discovers, prices and turns up the path. Everything the portal does is also an API, aligned to MEF LSO Sonata and Cantata and TM Forum TMF622 and TMF641.
Neither side waits on a build. A listing is configuration rather than construction, and for the enterprise the path is already there.
Every screen, every API response and every invoice on the on-ramp carries your name. The provider's brand stays on its compute, where it belongs. Yours is the only name on the on-ramp.
SCOPE
The whole product, in one table.
Most platform conversations with an operator start with a catalog and end with a program. This one is one service. Here is everything you stand up, and everything that stays exactly as it is.
- A high availability on-ramp edge node on your network
- A marketplace where enterprises find providers and reach them in minutes
- A gVPC per enterprise customer, per provider
- Zero-trust Security Groups
- Live rate, loss and completion on every link
- One routing layer across clouds and carriers
- Elastic bandwidth, billed by the window
- Your branded portal and API, with a listing and billing records per provider
- Dedicated internet access
- Data center interconnect
- Wavelengths and dark fiber
- A full platform service catalog
- A network build or a new footprint
- A capex program
- GPU capacity, power or contracts
- A white label of your platform for someone else to resell
The right column is the reason this is a quarter. Every line on it is either a product you already sell under your own name, or a program this keeps off your roadmap. The access layer is the one piece the market is short of, so it is the one piece here.
HOW IT RUNS
An installation, a listing and a license.
Three questions decide whether this is a quarter or a program: what goes in the ground, who runs it, and how it is paid for.
An edge node in a facility you already run
A high availability on-ramp edge node pair, handed off over a standard NNI or a cross-connect. White-box service nodes, commodity hardware, lightweight demarcation at the customer, and no forklift anywhere in your network.
It sits on your network, not over the top of it. Start with the sites your first provider needs, and add sites as providers ask for them.
Yours to run, or ours on your behalf
Run it with your own NOC and your own processes, the way you run the rest of your wholesale book. Or InsidePacket operates it for you end to end: routing, security, observability, provider onboarding, billing records and day-2 support.
Either way, your engineers stay on the network you already run and no new operating model lands on them.
It lands inside the systems you have. The portal, the APIs and the billing records speak MEF LSO Sonata and Cantata and TM Forum TMF622 and TMF641, so your OSS and BSS integrate against standards rather than against us, and nothing here is a proprietary hook you have to unpick later.
Usage-aligned, with the margin on your side
A per site or unlimited platform license on commodity hardware, with operator margin in the range of 50 to 70 percent. Costs scale with the access revenue you bill on both sides, so the on-ramp pays for itself as the marketplace fills.
It is a license, so you keep every dollar you bill on both sides of your marketplace. It runs as operating spend and stays off your capital plan.
Both sides sell through motions you already run. The provider side is wholesale access sold to a new class of customer. On the enterprise side the marketplace does the finding and NEO does the ordering, so demand arrives without a rep in front of it. Scoped to your network in a working session.
You already sell access to competitors, price it, provision it and support it. A wholesale book is already a two-sided one. A marketplace is that same muscle, pointed at both sides of a new market.
TIME TO MARKET
Five years, three years, or this quarter.
Building a comparable access layer internally means standing up multi-cloud interconnects, policy-based segmentation, encryption, telemetry and intelligent routing, and then keeping a standing engineering commitment behind all of it. Assembling one from vendors trades the build for an integration program. Neither finishes inside the window.
TIME TO A COMPARABLE SERVICE IN MARKET
THE WINDOW · THE NEXT 4 TO 8 QUARTERS · AI ON-RAMPS BEING CLAIMED
What the 90 days actually contains
The edge node, the handoffs, your branding on the on-ramp and the marketplace, and the listing of your first provider, whose portal and APIs speak the same MEF LSO and TM Forum standards yours do.
The number is days because the deployment is an installation and a listing. The platform beneath it has been in production since September 2025 in the US and EU, with quarterly releases.
And what the second provider costs
A listing. Their logo, their capacity, their price and their billing records, configured in days on an on-ramp that is already carrying traffic for the first. No engineering, and no second 90 days.
The expensive one is the first, and it is the one priced in the 90 days. Every provider listed after it is margin.
Bar length is time to a comparable service in market for those building it. Your deployment is an edge node in a facility you already run, not a build. Build and assemble durations are planning assumptions, not measured outcomes.
WHY THIS LANDS WITH YOU
You already own the two things an over-the-top player has to rent.
The fiber and the metros are the first, and they are the obvious one. The second matters more: a wholesale motion that already sells access to competitors, prices it, provisions it, bills it and supports it. A wholesale book is already a two-sided book, which is exactly what a marketplace is, and almost nobody outside a carrier has one.
| THE ACCESS LAYER | AN OVER-THE-TOP PLAYER | YOU, ON THE ON-RAMP |
|---|---|---|
| Whose fiber the path runs on | Yours, rented from you | Yours |
| Whose brand the enterprise sees | Theirs | Yours, on the on-ramp |
| Where the access margin lands | With them | With you, on both sides |
| In-country and regulated routing | Best effort, off-net | On-net, and provable |
| Who owns the customer relationship | They do, and they keep it | You own the access, they own the compute |
| Time to a service in market | Theirs is already live | 90 days, on your network |
Scroll the table sideways on a narrow screen.
The two ways this goes wrong
Building a comparable access layer internally is a standing engineering commitment in a category that is not your core business, and it does not finish inside the window.
Reselling a labeled over-the-top service trades that build cost for something worse. Your brand disappears from the relationship, the margin follows it, and you lose control of the one layer that increasingly decides whether an enterprise workload lands on your network or on someone else's.
The AI Access Platform gives you the outcome of building it yourself without the build: your network, your providers, your margin, and your name on the on-ramp while theirs stays on the compute. InsidePacket's technology underneath, and your name on top of it.
THE WINDOW
Every market gets one on-ramp. The second one sells what is left.
The GPU and neocloud providers in your market will choose where their private on-ramp lives once, and then they will not choose again. What they are picking is the place their enterprise customers arrive, and the operator who owns that place owns access to everything the market becomes.
THE MARKET YOUR ON-RAMP WOULD SIT IN FRONT OF
1 Synergy Research, April 2026: neocloud revenue above $25B in 2025, heading toward roughly $400B by 2031 at a 58% compound annual growth rate. The curve is that published rate plotted between those two published endpoints, not a forecast of ours. The window is a judgement about how these providers buy, not a projection.
A provider integrates its access once
Getting listed costs a provider engineering time, a contract and a security review. Once it has paid that, it has no reason to pay it again for a second on-ramp in the same market. The first operator to ask is usually the last one who gets to.
Enterprises go where the providers already are
A marketplace carrying every provider in the region is worth arriving at. One carrying two is not. Each side pulls the other, so the on-ramp that fills first keeps filling, and the gap widens without anyone having to work at it.
The second on-ramp inherits the rest
It gets the providers the first one did not want and the enterprises that could not get what they needed. That is a real business and somebody will run it. It is not the one on this page.
2 Gartner, June 2026. 3 Gartner, enterprises on a multicloud networking platform by 2027, up from 10% in early 2024. 4 The Business Research Company, July 2026. Three separate populations, shown together only to size the same opportunity from three directions.
The operator that owns the on-ramp in its market in the next year or two has access to all of this. The one that does not will carry it anyway, underneath somebody else's marketplace, on fiber it paid for.
That choice is made once, by providers who are not waiting for anyone.
Whoever packages distributed infrastructure into an on-ramp owns the customer relationship and the margin. For an operator the risk was never losing one GPU deal. It is carrying the traffic beneath someone else's marketplace, on fiber you paid for.
The compute is being built now, and the providers behind it are choosing their on-ramp in the next four to eight quarters. Standing one up is a quarter of work on a network you already own. Watching someone else get chosen is permanent.
Scope a deployment for your network in one working session.
Bring the providers in your market you would list first, the sites you would start with, and your wholesale pricing. You leave with a footprint, a 90 day timeline and a commercial shape for both sides that you can take to a board.