VSlice

What is a VSlice?

A VSlice (Virtual Slice) is an isolated private network within the Stacuity platform. It defines the fundamental network parameters for everything that runs inside it: IP addressing, DNS resolution, and the APN pattern used by endpoints.

Think of it like this.

A VSlice is the container, it defines the boundary of a logical network segment. The container alone does nothing. Everything else, Endpoint Groups, Routing Targets, Routing Policies, Operator Policies, Regional Policies are the rules, mappings, and configurations associated with that container that collectively determine how traffic entering and leaving the VSlice is handled.

You can think of it in layers:

VSlice : the container itself; establishes the logical network boundary
Endpoint Groups : defines which endpoints (SIMs) belong to this container
Routing Targets : defines where traffic can be sent (the available destinations)
Routing Policies : defines how traffic is routed (which target, under what conditions)
Operator/Regional Policies : defines the rules governing behaviour within the container (data limits, restrictions, event responses)

The VSlice is the what, and everything associated to it answers the who, where, how, and under what rules questions. Together, those associations are what make the VSlice functional.

These objects can be created independently of a VSlice, but they have no operational effect until associated with one. This allows operators to build out their configuration in stages before activating it.

Creating a VSlice is always the first step before building any other configuration.

When to Create a New VSlice

Create a separate VSlice when you need network isolation, separate IP addressing, different APNs, or regulatory separation.

You do not need a new VSlice just to apply different routing rules to different device groups — use separate Endpoint Groups with different Routing Policies within the same VSlice for that.

Key Settings

IP Allocation Type

Type	Behaviour	Recommended for
Auto/Static	Each endpoint keeps the same IP across sessions.	Most IoT and telematics deployments.
Pooled	IPs are allocated per-session and returned to the pool when the session ends.	High-churn consumer deployments.
RADIUS	IP allocation is delegated to an external RADIUS server.	Enterprises with existing RADIUS infrastructure.

DNS Mode

Mode	Behaviour
Auto	Stacuity provides DNS resolution. Standard choice.
Custom	You specify your own DNS server(s).

APN Pattern

The VSlice defines the APN pattern that all endpoints within it must use. The standard pattern is *.flex — any APN ending in .flex is valid.

IP Subnets

After creating a VSlice, add at least one IP subnet before creating Endpoint Groups. Go to the VSlice's Edit → Subnets tab to add subnets.

Create a VSlice

Steps:

Go to Configuration → VSlices.
Click Add.
Fill in the fields and click Create.
Immediately go to Edit → Subnets to add at least one IP subnet. The VSlice is not usable until it has a subnet.

Field	Required	Notes
Name	Yes	Can be changed later.
Moniker	Yes	Used in the API. Auto-generated from the name, but can be overwritten.
PDN Type	Yes	IPv4 is the standard choice.
DNS Mode	Yes	Auto or Custom.
IP Allocation Type	Yes	Auto/Static recommended for most deployments.
IPv4 Subnet Address	No	Can be added here or via Edit → Subnets after creation.
Event Map	No	Applies an Event Map at VSlice level.

When adding subnets, you will need to provide a Name and Moniker (the moniker is auto-generated from the name, but can be overwritten) for each subnet, in addition to the CIDR range and type (Static or Pooled).

Edit a VSlice

Editable fields: Name, Moniker, DNS Mode, Event Map.

PDN Type and IP Allocation Type cannot be changed after creation.

Removing a subnet while endpoints have IPs allocated from it will cause those endpoints to lose their IP addresses on their next session.

Updating the active APN will reprovision and reset all Endpoints in this VSlice. Proceed with caution!

Delete a VSlice

Before a vSlice can be deleted, all Endpoint Groups associated with it must first be removed. Once all associations have been cleared, the VSlice itself can be deleted. Deleting a VSlice removes the container entirely, which means the logical network segment it defined no longer exists.