RMS VPN - RMS Credits

What RMS VPN does

RMS VPN creates encrypted peer-to-peer or hub-and-spoke VPN tunnels between Teltonika devices and designated management servers, using the RMS platform as the control plane. No dedicated VPN server infrastructure is required. Configuration is done through the RMS dashboard.

RMS VPN topology options

Hub-and-spoke – multiple Teltonika devices (spokes) connect back to a central server or management host (hub). Traffic from remote devices flows back to the hub for processing or management.
Peer-to-peer – direct encrypted tunnels between two Teltonika devices, useful for site-to-site connectivity.
Remote access – a single remote management machine connects to multiple Teltonika devices via RMS-brokered tunnels.

RMS VPN vs self-managed OpenVPN

Aspect	RMS VPN	Self-managed OpenVPN
Server infrastructure	Not required – RMS brokers connections	Requires VPN server with public IP
Configuration	Dashboard-based, no certificate management	Manual certificate and config file management
Scalability	Add devices in dashboard	Requires server capacity planning
Data routing	Via RMS platform (Teltonika hosted)	Via your own infrastructure
Credit requirement	Yes – one credit per device	No RMS credit needed
Suitable for	Quick deployment, MSP use cases	Data sovereignty, high-throughput needs

When to use RMS VPN

RMS VPN is best suited to deployments where simplicity and speed of setup are priorities – managed service provider deployments, small-to-medium fleets where setting up dedicated VPN infrastructure is disproportionate, and situations where devices are behind restrictive NATs or firewalls that make inbound VPN connections difficult. For deployments with strict data sovereignty requirements or very high throughput needs, self-hosted OpenVPN or WireGuard on the Teltonika devices is typically a better fit.