AEX OPEN ACCESS NETWORKS 

AEX - Built for Open Access from Day 1.

AEX is the wholesale operations software for open access networks, connecting every ISP to your network through a single interface.

Request a demo How AEX Open Access works

 
Open access on AEX

Built for open access from day one

100+retail ISPs selling across AEX-run networks
40+retail ISPs on a single network
300K+network devices managed
Why open access breaks

The fiber is open. The operation often isn't.

Open access is easy to describe and hard to run. The industry said so itself in February 2026, when ATIS stood up the Open Access Network Forum to work on exactly these problems.

The answer: AEX was built for open access operators and has run that way for more than a decade. Adding a retailer is a configuration against a standing interface, not an integration project on both sides.

Two-sided catalogs

Wholesale and retail products have to stay in step.

A third party in every order

Each order belongs to an ISP as well as a subscriber.

Per-ISP provisioning

Provisioning has to know who the subscriber bought from.

Money moving both ways

Billing runs to subscribers and back to ISPs.

What that means in practice

How AEX runs open access

01

Wholesale and retail catalogs in one place

Your ISPs build their retail products against your wholesale catalog, in one system.

02

Orders that know which ISP they belong to

Addresses resolve to a key before an order proceeds, and the work order routes to the ISP the subscriber chose.

03

One contract, every ISP

The AEX ISP API covers selling, ordering, provisioning and support, and every ISP works to the same contract.

04

A portal your ISPs run themselves

ISPs manage their own products, coverage, orders and services. Fewer tickets into your team.

05

Billing in both directions

Recurring, prepaid, postpaid and wholesale in one engine, with per-ISP billing files and split billing.

06

Provisioning on any hardware

Zero-touch detect, configure, activate and roll back at layer 2 and layer 3, with per-ISP VLANs held against each service.

What makes AEX different

Open, closed or both

Network models

Open and closed on the same software

A closed network is the same setup with a single retail brand. Run open access in some markets and closed in others from one system.

Change later

Open your network when you are ready

Opening a closed network means changing configuration and commercial terms, not moving systems. We'll plan the real work with you.

Standards

Built on standards, not a connector catalog

The data model follows the TM Forum SID, and we track the ATIS Open Access Network Forum work directly.

How AEX handles OSS/BSS →

Use what you need

Better with the rest of AEX

Each works on its own alongside the vendors you already have.

Subscriber booking on the AEX self-service app

Run the business

AEX Software

Runs the open access operation end to end: catalogs, ISP orders, provisioning and two-way billing.

Explore AEX Software →

AEX Field Service schedule board and mobile apps

Get crews there

AEX Field Service

The install that connects a subscriber to their chosen ISP closes straight into provisioning and billing.

Explore AEX Field Service →

Technician working on a fiber line

Run the network

AEX Network Services

Backbone, NOC and white-label helpdesk underneath the network.

Explore AEX Network Services →

Where you are

Starting somewhere else?

New network

Launching a network

Get to your first invoice without assembling a stack first.

Launching a network →

Growing fast

Scaling a network

Close the gaps between systems without a rip-and-replace.

Scaling a network →

Bought a network

Integrating acquisitions

Onboard an acquired base without replatforming it.

Integrating acquisitions →

Grant funded

BEAD-funded builds

Fill the operational gaps behind a BEAD build.

BEAD-funded builds →

Open the network. Keep operations simple

FAQs

Do I have to run open access to use AEX?

No. Closed access is the same platform with one retail brand configured, and plenty of operators run it that way. The point is that you are not choosing a system that forecloses the other model, in either direction.

We’re closed access today but may open later. What does converting actually involve?

It’s a configuration and commercial exercise rather than a replatform, but it isn’t nothing. It touches three areas: how subscriber sessions are handed off on the network, how wholesale and retail billing split, and how your product catalog is restructured so ISPs can build against it. We’d work through all three with your team before quoting a timeline.

How long does it take to bring on a new ISP?

It depends far more on your commercial process than on ours. On the platform side, an ISP needs an entity, a catalog relationship, portal and API credentials, and VLAN assignment on the network. Our role is to make sure none of that is bespoke.

Does BEAD require open access?

No. It never required retail open access, and the narrower middle-mile interconnection and wholesale requirement in the original NOFO was removed in June 2025 under the Benefit of the Bargain restructuring. Where public money does favor open access, it’s at the state level, New York’s ConnectALL municipal program being the clearest current example.

Do our ISPs get their own portal and their own API?

Both. ISPs work in their own view of the platform for products, coverage, customers, services, and work orders, and integrate to the AEX ISP API for the same functions. Smaller retailers tend to live in the portal; larger ones integrate.

Can we run open and closed access at the same time?

Yes. The model is set per network, so an operator running closed access in one market and open access in another runs both from one system, with the rules for each applied automatically.

Learn more about open access