What is Core Network-as-a-Service (CNaaS)?

Core Network-as-a-Service is a model where a provider delivers the HLR/HSS and packet core functions of a mobile network as a managed cloud service, giving the customer network-level control without owning spectrum or core hardware.

Who is Core Network-as-a-Service for?

It is typically used by MVNOs, travel eSIM providers, IoT connectivity providers, and enterprise data providers that need core-level network control but do not hold a spectrum licence or run their own HLR/HSS.

Do I need to own spectrum to use Core Network-as-a-Service?

No. Core Network-as-a-Service is built for organisations without spectrum. The provider integrates with a partner MNO's network, or with an MNO relationship the customer already holds, so the customer's IMSIs can run on the platform.

Can I keep my existing MNO relationships with Core Network-as-a-Service?

Yes. A customer can bring an existing MNO relationship, and that operator's HLR/HSS is integrated with the platform so its IMSIs continue to run through it.

What charging options does Core Network-as-a-Service support?

Common options include a built-in OCS, integration with an external OCS via Gy, or delegated IP allocation via RADIUS, chosen according to what charging infrastructure the customer already has in place.

Affirmed Networks Migration: A 7-Step Guide to Stacuity Edge

With Microsoft winding down the much-loved Affirmed Networks platform, operators need a clear path off it.

Here is how a network migration to Stacuity Edge works, in seven simple steps.

Step One: Technical discovery call

Book a call with our technical team. We explain how the Stacuity Edge platform works, and you tell us about your network and requirements. From there we agree on the simplest way to get your traffic to us.

Step Two: Connect the PoC (Proof of Concept)

Point your GTP-C at the Stacuity PGW-C. A common route is to create an APN whose DNS resolution returns the Stacuity PGW-C, or alternatively use a GTP proxy if you have one.

The PoC is deliberately scoped to connectivity only, with no charging or AAA integration; that solution design work happens in step 5. Keeping the PoC this narrow is what makes it a day’s work rather than a project.

Step Three: Test the Stacuity Platform

With the PoC live, watch traffic land and break out at any Stacuity edge site. Spin up self-service WireGuard or IPsec tunnels to your own services, and try the built-in OCS to see charging working, without touching your own systems.

Stacuity Edge offers more than just local breakout. We provide a range of advanced, self-serve network capabilities to support IoT, Enterprise Data and Travel eSIM applications.

Step Four: Choose Stacuity

By this point you’ve tested the platform against your real traffic, not a demo or a slide deck. If the PoC has answered your questions, you’re ready to move to production design.

Step Five: Design production

Now we design the production build. Use the Stacuity shared Edge estate (see live and roadmap sites) or design your own dedicated site (optionally your racks, power, connectivity and your own hardware to our spec).

Next comes transit. You can use Stacuity’s IPX and IP transit, or bring your own, which is common with a dedicated site but works on shared too.

Finally, we design the integration itself, covering Diameter Gy/Gx, RADIUS AAA, and how your OCS connects to the PGW-C, whether that’s IPsec, cross-connects, or Equinix Fabric.

The common thread across all three is choice. Nothing is forced into a fixed shape.

Step Six: From Design to Build

We implement the design from step 5. On a shared site, that’s mostly configuration and connectivity. On a dedicated site, it also includes standing up racks and hardware, and landing IPX and IP transit.

Step Seven: The Migration

With the build complete, migrate on your terms. Move live traffic across APN by APN, testing each one before moving to the next, with the option to run Affirmed in parallel throughout. Once every APN is performing as expected, switch Affirmed off.

The common thread across all three is choice. Nothing is forced into a fixed shape.

Why Migrate From Affirmed Networks Now?

Microsoft has confirmed it’s discontinuing support for the Affirmed Networks suite of 4G/5G core applications, including the PGW-C many global operators rely on. Stacuity gives you a proven, no-risk way to replace it. Test it against your live network in a day, then migrate on your own timeline.

Learn More

Frequently Asked Questions (FAQs)

Do I need to buy new hardware to move to Stacuity Edge?

Not necessarily. You can use Stacuity’s existing shared Edge estate with no hardware of your own, or design a dedicated site using your own racks, power and hardware to Stacuity’s spec. Both options are covered in Step 5.

What's the difference between Stacuity's shared Edge estate and a dedicated site?

The shared estate uses Stacuity’s existing live and roadmap edge locations, with no infrastructure investment required. A dedicated site is built to your spec (optionally your own racks and hardware) for cases needing more control. Transit, in either case, can be Stacuity’s own IPX/IP transit or your own.

Can I test Stacuity Edge without committing to a full migration?

Yes. That’s the point of Step 2’s proof of concept. You point your GTP-C at the Stacuity PGW-C (via DNS or a GTP proxy) and can watch real traffic land and break out, test WireGuard/IPsec tunnels, and try the built-in OCS, all before any commercial decision.

Does Stacuity Edge support Diameter Gy/Gx and RADIUS AAA integration?

Yes. This is designed as part of the production build in Step 5, alongside how your OCS connects to the PGW-C (IPsec, cross-connects, or Equinix Fabric).

Core-Network-as-a-Service

Edge-as-a-Service