No products in the basket.
Teltonika Altos CAP700: What RutOS 7.24 Changes
Teltonika released RutOS 7.24 on 1 July 2026. For most of the router range it is a solid maintenance release. For the Altos CAP700 it is something else entirely. Three features arrive that did not previously exist on the platform: VXLAN, Docker, and NetBird.
Those three additions change what the CAP700 is. It shipped as a 5G Wi-Fi 7 Fixed Wireless Access router. It now doubles as an overlay networking node and a container host. This guide explains what each feature does, why it matters commercially, and where the honest limits sit.
The hardware is unchanged. You can read the full specification on the Teltonika Altos CAP700 product page.
What RutOS 7.24 adds to the Altos CAP700
Teltonika’s announcement covers the whole portfolio. Only part of it lands on the CAP700, because some features depend on hardware the Altos does not carry. The table below separates the two.
| RutOS 7.24 feature | Applies to Altos CAP700 |
|---|---|
| VXLAN | Yes. Altos-specific addition in this release. |
| Docker | Yes. Delivered as a package. Altos-specific addition. |
| NetBird VPN | Yes. Delivered as a package. Altos-specific addition. |
| TR-069 parameter expansion and faster session setup | Yes. Platform-wide. |
| Operator priority list in allowlists | Yes. Applies to any RutOS device with a cellular modem. |
| SSO login for device access | Yes. Platform-wide. [SPEC TO VERIFY: confirm supported identity providers] |
| SFTP and FTPS for Data Sender | Yes. Platform-wide. |
| MQTT topic variables in Data Sender and Event Juggler | Yes. Platform-wide. |
| Third Party Packages tab in Package Manager | Yes. Platform-wide. [SPEC TO VERIFY on CAP700 build] |
| PPSK user import, export and auto-generation | [SPEC TO VERIFY: PPSK availability on CAP700] |
| CANopen Client | No. The CAP700 has no CAN interface. |
| TswOS 1.10 switch features | No. Switch firmware, not router firmware. |
Before you write the CANopen headline into a spec: CANopen Client is a RutOS 7.24 feature, but it needs a physical CAN interface. The Altos does not have one. Teltonika’s press release covers the whole firmware release, not one device.
VXLAN on the Altos: data centre segmentation at the edge
VXLAN stands for Virtual Extensible LAN. It is an encapsulation technology. It carries layer 2 Ethernet frames inside layer 3 UDP packets, which lets a VLAN cross a routed network without losing its identity.
In practice, this means a VLAN at your head office can be extended to a remote Altos over a 5G link. The devices on that remote VLAN behave as though they are plugged into the central switch. Broadcast domains stay intact. Firewall policy and IP addressing stay consistent.
Why this matters on a cellular router
VXLAN is standard equipment on data centre switching. It is unusual on a 5G CPE device. The reason it matters here is that cellular WAN is always routed and almost always behind carrier-grade NAT. Historically, extending layer 2 across that link meant building bridged VPN tunnels and accepting the overhead.
VXLAN gives a cleaner mechanism. Because it is an overlay, it separates the transport network from the tenant network. Therefore the underlay can be 5G today and fibre tomorrow, and the overlay does not change.
Real deployment patterns
- Multi-tenant sites. A serviced office or retail concession where several tenants share one Altos. Each tenant sits on its own VXLAN segment with no visibility of the others.
- Building management extension. A BMS controller network that must remain on a single layer 2 segment across two buildings, where the second building has no fibre.
- Site migration. Moving a rack of devices to a temporary location without re-addressing them. The VXLAN segment travels with them.
- Cloud to edge. Extending a VXLAN segment already running in a cloud VPC out to a physical site.
VXLAN needs a peer. It is not a standalone feature. You need a VXLAN termination point at the other end, typically a switch, a firewall, or a Linux host. Plan the far end before you order the hardware.
Docker on the Altos: running your own software on the router
Docker lets you run containerised applications directly on the device. The container has its own filesystem and libraries. It runs alongside RutOS without touching the router’s own packages.
Until this release, Docker on Teltonika hardware meant the RUTC series. The Altos now joins it. The CAP700 has the resources to make this useful: a Qualcomm processor, 1 GB of LPDDR4 RAM, and 8 GB of eMMC flash. That is more storage than any RUT-series router carries.
Our Docker on Teltonika routers explainer covers the fundamentals. The Altos-specific question is what you would actually run.
Workloads that suit the Altos
- Protocol translation. An MQTT bridge, an OPC UA client, or a small adapter that reshapes JSON before it reaches a cloud endpoint.
- Store and forward buffering. A container that queues telemetry during a 5G outage and replays it once the link recovers.
- Local DNS and ad filtering. A lightweight resolver serving the LAN, useful in small office deployments.
- Monitoring agents. A Prometheus node exporter or a vendor agent that reports device health to an existing observability stack.
- Captive portal logic. Custom authentication or landing page behaviour beyond what the RutOS hotspot provides.
Pro tip: The CAP700 has an operating range of 0 °C to 45 °C and no active cooling. A container that pins the CPU will raise the internal temperature. Test your workload at ambient before you deploy it to a cabinet or a loft. Container images should be built for ARM, not x86.
Storage is the practical constraint
8 GB of eMMC sounds generous next to a 16 MB SPI flash router. However, RutOS occupies part of it, and container images consume the rest quickly. A single Python base image can exceed 100 MB. Use Alpine-based images where possible. Do not plan on running a database with a growing data directory.
NetBird on the Altos: WireGuard mesh without the tunnel matrix
NetBird is an overlay VPN built on WireGuard. It creates a mesh network between enrolled devices. Peers discover each other through a coordination server, then establish direct encrypted tunnels wherever NAT traversal allows it.
The CAP700 already supported OpenVPN, IPsec, WireGuard, ZeroTier, and Tailscale. NetBird adds another option in the same category as ZeroTier and Tailscale. Our VPN on cellular routers explainer compares the protocols in detail.
Where NetBird earns its place
Traditional site-to-site VPN scales badly. Ten sites that all need to reach each other means forty-five tunnels. Each one is configured, monitored, and eventually forgotten by whoever built it. Mesh overlays remove that arithmetic. Each device joins once, and connectivity follows policy rather than topology.
NetBird is self-hostable, which distinguishes it from Tailscale in procurement conversations. Organisations that cannot route control-plane traffic through a third-party SaaS platform can run the management server themselves. As a result, it appears frequently in public sector and regulated environments.
It also removes a common cellular headache. Because peers connect outbound to the coordination server, an Altos behind carrier-grade NAT is reachable without a public IP. That said, a fixed IP SIM remains the cleaner answer where you need deterministic inbound routing or where NAT traversal fails behind a strict carrier.
How the three features combine
Individually these are useful. Together they describe a coherent architecture, and this is where the Altos starts to look like a business device rather than a broadband box.
Consider a chain of twenty small sites with no fibre. NetBird enrols every Altos into one mesh, so engineers reach any device without a jump host. VXLAN extends the corporate VLANs across that mesh, so the POS terminals at each site sit on the same segment as the central payment gateway. Docker runs a local caching container at each site, so a 5G outage does not stop transactions queuing.
One box replaces a router, a VPN concentrator endpoint, and a small edge PC. For a twenty-site rollout, that is a material reduction in hardware, installation time, and failure points.
The Altos CAP700 hardware, briefly
| Specification | Value |
|---|---|
| Cellular | 5G NR SA and NSA, up to 4.0 Gbps DL / 900 Mbps UL |
| LTE fallback | 4G LTE Cat 19, up to 1.6 Gbps DL / 200 Mbps UL |
| 3GPP release | Release 17 |
| SIM | 1 x Nano SIM (4FF) |
| Wi-Fi | Wi-Fi 7 (802.11be), dual band, 2×2 MIMO, up to 128 clients |
| Ethernet | 1 x 2.5 GbE WAN/LAN, 1 x 1 GbE LAN |
| Telephony | 1 x RJ11 port |
| Processor | Qualcomm |
| RAM | 1 GB LPDDR4 |
| Flash | 8 GB eMMC |
| Antennas | 6 x internal mobile, 2 x internal Wi-Fi |
| Power | 12 V DC barrel jack, idle under 8 W, max under 24 W |
| Dimensions | 100 mm diameter x 185 mm |
| Weight | 720 g |
| Operating temperature | 0 °C to 45 °C |
| Ingress protection | IP30 |
| Certifications | CE, UKCA, EAC, UCRF, RCM, CB, WEEE |
| Operating system | RutOS, RMS managed |
What the Altos is not
The CAP700 runs the same operating system as an industrial RUT router. The chassis does not follow. Being clear about this saves returns.
- It is not an industrial router. The operating range is 0 °C to 45 °C. An unheated plant room in January is outside that. The RUT and RUTX ranges run from -40 °C to +75 °C.
- It has one SIM slot. There is no dual-SIM failover and no eSIM. For MNO diversity, look at the Teltonika RUTX50.
- It has internal antennas only. There are no SMA ports. Signal is improved by moving the unit, not by fitting a directional antenna.
- There is no DIN rail mount and no digital I/O. It is a desk or shelf device with a barrel jack.
- It is IP30 and plastic. Indoors only.
Read the Teltonika specification guide if you are weighing the Altos against the industrial range. The right question is rarely which is faster. It is which environment the box has to survive.
Updating to RutOS 7.24
Three routes are available. Firmware over the air is the simplest for a single device: check for firmware on the server from the WebUI and apply it. Keep settings is enabled by default.
For fleets, Teltonika RMS pushes firmware and configuration to many devices at once. RMS consumes credits per managed device per month. You can buy them through our RMS Credits page.
Docker and NetBird arrive as packages rather than as part of the base image. Install them from the Package Manager after the firmware update completes. Our Package Manager explainer covers the process, including the new Third Party Packages tab.
Frequently asked questions
Does the Teltonika Altos CAP700 support Docker?
Yes, from RutOS 7.24 onwards. Docker is installed from the RutOS Package Manager, not included in the base firmware. Prior to 7.24, Docker on Teltonika hardware was limited to the RUTC series. Build container images for ARM and keep them small, because the 8 GB eMMC is shared with the operating system.
What is VXLAN used for on a 5G router?
VXLAN extends a layer 2 VLAN across a routed layer 3 network. On a 5G router it lets you stretch a corporate VLAN to a site that has no fibre, so remote devices keep their original network segment and policy. It requires a VXLAN peer at the far end, typically a data centre switch or a Linux host.
Is NetBird better than WireGuard on RutOS?
NetBird uses WireGuard as its transport. The difference is management. Plain WireGuard requires you to configure each peer, key, and route by hand. NetBird handles peer discovery, key distribution, and NAT traversal through a coordination server. For two sites, plain WireGuard is fine. For twenty, NetBird removes a lot of manual work.
Can the Altos CAP700 be used as a business router?
Yes, in the right environment. It runs full RutOS with the same VPN suite, firewall, RADIUS, VLAN, and RMS support as the industrial range. VXLAN, Docker, and NetBird extend it further. However, it is an indoor device rated 0 °C to 45 °C with a single SIM and internal antennas. Offices, retail units, and small branch sites suit it. Roadside cabinets and plant rooms do not.
Does the Altos support dual SIM failover?
No. The CAP700 has a single Nano SIM slot and no eSIM. Failover is available across WAN types, so the 2.5 GbE port can act as a wired backup to the 5G connection, or the reverse. For failover between two mobile networks, choose a dual-SIM model from our Teltonika 5G router range.
Does CANopen work on the Altos?
No. CANopen Client is part of RutOS 7.24, but it needs a physical CAN interface. The CAP700 has no CAN port. The feature applies to RutOS devices that carry CAN hardware.
Related products and further reading
The Teltonika Altos CAP700 is held in UK stock with next-working-day delivery. For a comparison against the industrial 5G range, see our Teltonika 5G routers and the 5G Fixed Wireless Access explainer. If you are deciding between device classes, our guide to the difference between routers, gateways and modems is a useful starting point. Connectivity is available through our fixed IP SIM cards. For specification advice, call our UK-based technical support team on 0300 124 6181.