Product

Private APN

Your own private network for IoT devices. Isolate your device traffic from the public Internet and connect them directly to your corporate infrastructure securely.

Key features

Dedicated private network

Your devices on an isolated network with private IP addressing. No public Internet exposure.

Site-to-site VPN

Connect your private APN directly to your datacenter or cloud via dedicated VPN tunnel.

Custom addressing

Define your own private IP range. Compatible with your existing addressing scheme.

Total isolation

Your device traffic never traverses the public Internet. Maximum security.

Private DNS

Configure your own DNS servers for internal name resolution.

Traffic monitoring

Complete visibility of your APN traffic with detailed logs and metrics.

Technical specifications

APN typeDedicated private
AddressingPrivate IPv4 (any range)
VPNIPSec, WireGuard, L2TP, GRE
VPN throughputUp to 1 Gbps
DNSCustomizable
Latency< 10ms additional
RedundancyHigh availability optional
SLA99.9% availability

Use cases

  • Extended corporate networks with mobile devices
  • SCADA systems and critical infrastructure
  • Industry 4.0 and connected factories
  • Financial institutions with compliance requirements
  • Healthcare sector with sensitive data
  • Public administration and government
  • Utilities and infrastructure management
  • Retail with multiple points of sale

Related products

Ready to get started?

Start with a test kit, or tell us about your project.

Buy SIM Test Kit

Test kit · €15 · ships in 48 h

Go to shop

Talk about your project

Custom quote based on your deployment

Tell us about it

Explore also

Frequently asked questions

What is the difference between private APN and VPN?
Private APN tunnels traffic from the mobile network itself to your infrastructure — devices never touch the public Internet. A VPN over public APN does encrypt the data, but traffic still traverses the operator's public network. Detailed comparison at /resources/comparisons/private-apn-vs-vpn.
When do I need it, and when not?
You need it if: (a) your sector requires isolation for compliance (healthcare, finance, critical energy), (b) your devices talk to internal systems on private IPs, or (c) you want to definitively block any outbound traffic that is not towards your backend. If you only expose HTTPS to a public endpoint and that is enough, public APN + static IP may suffice. More at /resources/blog/apn-privado-cuando-lo-necesitas.
Which tunnel types do you support to reach my backend?
Site-to-site IPSec (most common), WireGuard, L2TP and GRE. For SCADA and industrial environments we usually recommend IPSec with active-active redundancy.
Can I use my own private IP ranges?
Yes. We define the APN's CIDR block to fit the addressing plan you already have (e.g. 10.42.0.0/16) so it does not collide with the rest of your corporate network.
How much latency does private APN add?
Less than 10 ms additional in most regions. The overhead comes from the tunnel and routing to the dedicated gateway, not from the APN itself.
Is there a minimum number of SIMs to activate private APN?
No technical minimum, but private APN has a fixed monthly cost. From a few dozen SIMs onwards the per-device cost becomes marginal; below that, public APN + static IP + VPN is often more efficient. We quote each case.
Does it work with multi-operator?
Yes. Multi-operator SIMs can anchor to the private APN regardless of the underlying operator they attach to at any given moment.