Skip to main content
New UniFi OS Server Hosting now available: Learn More »
Home
Partners Get a Quote

Tangent › Roadmap & release notes

Tangent roadmap and release notes

This page is where we say what Tangent does today, which routers it runs on, and what we’re working on. We only list a feature as shipped when it has been tested on real hardware, and we only list a router as supported when a build exists for it. Anything beyond “Now” is direction, not a promise. Dates move, and we’d rather tell you that than invent them. If your router or the service you need isn’t here, tell us. Requests are how we decide what comes next.

Current version: 0.6.0 Last updated: 16 October 2026

Supported Hardware

Supported routers

Tangent runs on Teltonika routers with RutOS 7.24 or later and the Bondix client installed. Teltonika builds one firmware image per router family, so support is by family; every model in a supported family runs the same build. We publish a build for each RutOS point release.

  • TestedFull end-to-end test run on this hardware
  • Firmware-verifiedEvery dependency verified against the family firmware image; build installs; not yet run on a physical unit
  • PlannedOn the list, not yet verified
  • Not supportedThe platform cannot run Tangent
FamilyModelsStatusNotes
RUTX RUTX50, RUTX12, RUTX14 Tested Tested on hardware; the RUTX50 is our development platform.
RUTX RUTX08, RUTX09, RUTX10, RUTX11, RUTXR1 Firmware-verified Runs the same firmware image as the tested RUTX50.
RUTC RUTC50 Tested Tested on hardware.
RUTC RUTC40, RUTC41, RUTC42 Firmware-verified Runs the same firmware image as the tested RUTC50.
RUTM RUTM52 Tested Tested on hardware.
RUTM RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM54, RUTM55, RUTM56, RUTM59 Firmware-verified Runs the same firmware image as the tested RUTM52.
RUT2M RUT200, RUT241, RUT260 Tested Tested on hardware (RUT200). RUT241 and RUT260 run the same firmware; other RUT2xx models to be confirmed.
RUT9M RUT901, RUT906, RUT951, RUT956 Tested Tested on hardware (RUT956, dual-SIM). RUT901, RUT906 and RUT951 run the same firmware. Small overlay on this family (2.9 MB, ~320 KB free with Tangent installed): install nothing else alongside.
RUTE RUT202, RUT204, RUT206, RUT261, RUT271, RUT276, RUT281, RUT286 Tested Tested on hardware (RUT271, 5G RedCap, eSIM). RUT202, RUT204, RUT206, RUT261, RUT276, RUT281 and RUT286 run the same firmware line; the RUT261 is end of life and the RUT271 is its replacement.
OTD5 OTD500 Planned Planned, subject to a Bondix client for this family.
ATRM ATRM50 Planned Planned, subject to a Bondix client for this family.
Non-Teltonika GL.iNet Flint 2, MikroTik RB5009, Universal Client hardware Not supported Under consideration; see the roadmap.
Other Teltonika RUT140, RUT142, RUT145, RUT301, RUT361, RUT950, RUT955, TRB Not supported No Bondix client available for these models, so Tangent cannot run on them.

RutOS versions: 07.24.3.x, 07.24.4.x, 07.24.5.x, 07.24.6.x: supported. Earlier than 07.24: not supported.

Roadmap

Where Tangent is going

Tangent ships a release roughly every two weeks, and every release is tested on real Teltonika hardware before it goes out. The dates below are our targets. When testing tells us a release isn't ready, it moves and we say so here: we'd rather show you a plan that changes than promise one that doesn't. Each item joins the release notes below the moment it has shipped.

Shipped

October 2026 (0.6.0)

  • Managed rule sets: build a rule set in your SimpliWiFi portal, assign it to a router or to every router on a customer, and each router picks it up on its next check-in and shows it as managed beside its own rules
  • Routers report back whether each managed rule applied; a rule naming a WAN a router does not have is skipped on that router with the reason shown
  • Every rule set is signed by SimpliWiFi and verified by the router before it is read; a router that cannot reach the platform keeps working on what it already has, through a reboot
  • Name your routers in your SimpliWiFi portal and see the name on the router itself; one-line notices from SimpliWiFi on the Tangent page when there is something you should know about your firmware or build
  • Partner (MSP) accounts: buy licence keys in bulk, redeem a key on a router and it appears in your portal under your account
  • Your routers in the portal: one table with filters by state, firmware and licence, and a page per router with its rules, exits, WANs, health and history
  • Every Tangent router reports its status to the SimpliWiFi platform: firmware, version, each rule and the exit it is using right now, WAN state, DNS and health. Nothing is pushed to the router
  • Rules by IP address, network or domain name, with a chosen exit WAN and ordered fallbacks
  • Licensing and 7-day trial through the SimpliWiFi platform; buy with your serial or redeem a key
  • Survives router firmware upgrades; reinstalls itself with your rules and licence intact
  • Update from the Tangent page when a new version is published for your firmware
  • Beta builds for the latest RutOS, a report form and a one-click support bundle
  • A Test button on every rule: the router checks its own exit and shows you the public address the rule's traffic leaves from, next to the address the tunnel would give
  • Export and import your rules as a file: clone a proven set across sites
  • Domain rules fill their address list the moment they are applied, so a device that had already looked the name up is still caught on its next connection
  • Dual-stack clients are kept on IPv4 for breakout domains so a rule can't be sidestepped over IPv6
  • Supported on the RUTX, RUTC, RUTM, RUT2, RUT9 and RUTE series (the RUTE family joined with 0.6.0, tested on a RUT271 5G RedCap router)
0.5 Shipped

Fleet, in your hands: the portal follow-ups

Shipped 26 September 2026

The router half shipped on 29 September as 0.5.0 (see Shipped above), two weeks early, with beta builds for RutOS 07.25.3

  • Request a support bundle from the portal, sites, CSV export and the engineer's key helper arrive as portal updates during October and November; no router update needed
0.6 Shipped

Remote management: the portal follow-ups

Shipped 16 October 2026

The router half shipped on 16 October as 0.6.0 (see Shipped above), ten days early, with the RUTE family and builds for RutOS 07.24.6

  • Assign a rule set to a site once sites arrive in the portal (23 October); serial and customer scope shipped with 0.6.0
  • Live demo on the Teltonika and Bondix MSP webinar, 6 November
0.7 Planned

Where traffic comes from

mid November 2026

  • Rules for a VLAN, an interface, or particular devices: "everything from the card terminal goes down the shop broadband", with no destinations to maintain
  • Discovery mode: watch one device for a few minutes and see every domain it uses, then turn the ones you want into a rule
  • Alerts by email when a rule has been on fallback too long, a WAN is down, a router stops checking in, or a licence is about to expire; thresholds and a daily digest per account. Portal update, early December
0.8 Moved

Presets

December 2026

Moved so the fleet and remote-management releases could come first; the router side ships in late November and the signed catalogue follows in December

  • Ready-made destination lists for common services (BBC iPlayer, UK banks, card terminal providers, Microsoft 365 sign-in), maintained and signed by us; your router shows you what changed and you choose when to apply it
  • Strict DNS mode to stop browsers bypassing domain rules with their own DNS-over-HTTPS
1.0 Moved

Stable

January 2027

Three months of MSP field use from the October fleet release before we call it stable

  • No new features: three months of field feedback folded in, documentation completed, and the MSP tier (fleet view and managed rules) generally available

Being considered

tell us if you need it

  • IPv6 destination rules (waiting for a customer with an IPv6-capable bond)
  • Tangent for OpenWrt-based routers running the Bondix Universal Client; MikroTik
  • Time-based rules and per-rule bandwidth history

Targets, not promises: a release moves when testing says it should. Last updated 16 October 2026.

Changelog

Release notes

Newest first. Each entry lists the RutOS builds it was published for. Your router shows its installed version under Network → Tangent → About.

0.6.0

16 October 2026 RutOS 07.24.3, 07.24.4, 07.24.5, 07.24.6 RUT2M, RUT9M, RUTC, RUTE, RUTM, RUTX GitHub release v0.6.0

Beta: 07.25.1, 07.25.2, 07.25.3

  • Managed rule sets: a rule set assigned to this router from your SimpliWiFi portal is picked up on the router's next check-in, applied beside your own rules, and shown read-only on the Tangent page in a Managed rules card. Change or remove it in the portal and the router follows. Your own rules are never touched, and a router with nothing assigned works exactly as before.
  • Every rule set is signed by SimpliWiFi. The router checks the signature against a key built into the plugin before it reads a single byte of the document, refuses anything that does not verify, and reports what it applied (or why it could not) in its next status report. The key set refreshes daily from the platform so a key rotation never needs a plugin update, and a router that cannot reach the platform still verifies against the built-in key.
  • A rule set assigned to many routers fits each one: a managed rule whose exit WAN this router does not have uses the first of its listed WANs that it does have, and a rule naming only WANs this router lacks is skipped with the reason shown on the page and reported to the portal, while the other rules still apply. Managed rules can also say whether they cover the router's own traffic.
  • Rules are matched top to bottom, first match wins, exactly: an address listed in two rules now goes to the rule listed first (it previously went to the later one).
  • Managed rules no longer appear in the editable Breakout rules table, only in the Managed rules card, and if one is edited or removed on the router it is put back from the signed rule set on the next apply.
  • The status report names the exact build (`plugin_build`, the package version with its release number) beside the version, so the portal can tell an upgrade between two builds of the same version and answer which routers are still on the older one. The About card shows the build when it is not the release build.
  • `tangentctl rules` shows the managed rule set's state and the signing keys the router trusts; `tangentctl rules verify` re-checks the last signed document the router accepted (`--baked` against the built-in key alone, which is what a router cut off from the platform has); `tangentctl rules keys refresh` fetches the key set now. The support bundle includes the state and the trusted keys.
  • The RUTE family (RUT271 and the models on the same firmware: RUT202, RUT204, RUT206, RUT261, RUT276, RUT281, RUT286) moves from firmware-verified to supported: a RUT271 (5G RedCap, eSIM) passed the full hardware bench including a wired-to-eSIM failover and failback and a fourteen-day run, and carried a full column of the 0.6 bench.
  • Builds for RutOS 07.24.6, which Teltonika released on 12 October for the RUTX, RUTC, RUTM, RUT2M and RUTE families. No change to Tangent itself; routers upgraded to 07.24.6 reinstall themselves from this release.
  • Tested on six routers across five families (RUTX14, RUTX50, RUTC50, RUT200, RUT956, RUT271) against the live platform, 13 to 16 October: in-place upgrades from 0.5.0, the rule-set lifecycle from the portal at serial and customer scope, fleet fitting, tampered documents refused, a reboot with the platform unreachable, failover with a managed rule live, and a soak on the RUT200 and RUT956. The bench record is in `docs/tests/0.6-bench-results.md`.
  • Worth knowing: a WAN that drops and recovers inside the status sender's one-minute check, or inside the five-minute minimum between change reports, is recorded in the router's log but produces no change report; the next report carries the current state. Managed rules at site scope wait for sites to arrive in the portal (23 October); serial and customer scope are available now.

0.5.0

26 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUT9M, RUTC, RUTM, RUTX GitHub release v0.5.0

Beta: 07.25.1, 07.25.2, 07.25.3

  • The status report now says which WANs Bondix is bonding (`bondix_channel` on each WAN entry), so the portal can tell a bonded channel from a WAN that only exists for breakout.
  • `tangentctl status --json` prints the status object exactly as it is encoded for the platform, on one line, including the fields that are null (the previous output dropped them). `tangentctl status --body` prints the whole report request around it: serial, the licence token masked, and the notice ids the router has acknowledged.
  • The relay interface RutOS creates on the RUT2 series is no longer counted as a WAN. It never carries traffic and was showing every RUT200 with one WAN permanently down.
  • The DNS forwarder no longer lists the same upstream resolver twice when RutOS writes it once per mobile interface.
  • Every licence check-in now records in the log what asked for it (start-up, the schedule, or Check licence now).
  • The name you give a router in your SimpliWiFi portal now shows on the router's own Tangent page, at the top of the Status card. It arrives with the next status report or licence check-in, follows any change made in the portal, and clears when the name is removed there.

0.4.0

23 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUT9M, RUTC, RUTM, RUTX GitHub release v0.4.0

Beta: 07.25.1, 07.25.2

  • Fleet foundation: the router reports its status to the SimpliWiFi platform, on change (at most once every five minutes) and at least every six hours, and with every licence check-in. The report contains the router's identity and firmware, each rule with its current state and exit, WAN state, DNS forwarder health, the firewall self-check and the daemon's memory figures. It never contains the devices behind the router, only counts. `tangentctl status --json` prints exactly what is sent.
  • The router now understands instructions from the platform: a one-line notice shown on the Tangent page (dismissed once, never shown twice, and the dismissal reported back with the next status) and a request for the support bundle (uploaded once, at most two megabytes). The platform starts sending notices with the October portal update and bundle requests later in the year; until then the router receives an empty instruction set. Managed rule sets and presets arrive in later releases; this release ignores them.
  • A status report is never used to decide the licence: the router only ever reads the licence state from a licence check-in.
  • The support bundle now records flash and memory headroom (the RUT9 series has about 3 MB of writable flash) and the fleet status snapshot.
  • Fixed: the About card's last self-heal attempt could show nothing even when the bootstrap had recorded one.
  • The Release licence button has moved to its own row on the Licence card, is red, and asks for confirmation that names the router serial and the key before anything happens. It sat next to Check licence now and was one click from taking a licence off a router.
  • Fixed: the status report said the Bondix tunnel was down whenever a WAN default route sat in the main table, which is always (Bondix routes through two half routes and leaves the WAN defaults underneath). The report now reads the half routes.
  • Fixed: a WAN that RutOS reports as up but that holds no IPv4 address (a wired port whose link never drops at the switch, a lapsed DHCP lease, a modem mid-reconnect) is no longer chosen as a rule's exit; the rule falls back exactly as it does when the WAN is down, and the status report shows the WAN as up without an address. Found on an RUTC50 during the 0.4 bench.
  • Fixed: on 64-bit routers (RUTC and RUTM series) releases 0.3.11 to 0.3.13 lost the WebUI API files at start-up, so the Tangent page reported "Service not running", the licence check could not run and rules were not applied, while the daemon itself kept running. Installing this release over the top restores them; no settings are lost. 32-bit routers (RUTX, RUT2, RUT9 series) were never affected.

0.3.13

19 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUT9M, RUTC, RUTM, RUTX GitHub release v0.3.13

Beta: 07.25.1, 07.25.2

  • The RUT9M family (RUT901, RUT906, RUT951, RUT956) moves from beta to supported: the RUT956 passed the full hardware bench including wired-to-SIM failover and failback, and a 22-hour soak. No change to Tangent itself.

0.3.12

18 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUT9M, RUTC, RUTM, RUTX GitHub release v0.3.12

Beta: 07.24.3, 07.25.1, 07.25.2

  • Builds for RutOS 07.25.2, which Teltonika published as the Latest release for RUTX and RUTM on 17 September. No change to Tangent itself.

0.3.11

18 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUT9M, RUTC, RUTM, RUTX GitHub release v0.3.11

Beta: 07.24.3, 07.25.1

  • The RUT2M family (RUT200, RUT241, RUT260) moves from beta to supported: the RUT200 passed the full hardware bench and a 24-hour soak of this release's daemon.
  • First beta build for the RUT9M family (RUT901, RUT906, RUT951, RUT956): verified against the firmware; hardware bench to follow.
  • The daemon's periodic self-check spawns one process instead of five or six (one interface dump instead of a status call per WAN, one combined firewall check) and runs every 30 seconds instead of 15; the garbage collector is tuned for small-memory routers.
  • The daemon no longer spawns a shell and `ubus` every five seconds to read the DNS forwarder's counters; the forwarder writes a small status file instead. Noticeably lighter on small routers.

0.3.10

16 September 2026 RutOS 07.24.3, 07.24.4, 07.24.5 RUT2M, RUTC, RUTM, RUTX GitHub release v0.3.10

Beta: 07.24.3, 07.24.5, 07.25.1

  • Builds for RutOS 07.24.5, which Teltonika has made the Stable release for the RUTX, RUTC and RUTM families. No change to Tangent itself; routers upgraded to 07.24.5 reinstall themselves from this release.
  • Bundles for 32-bit-only router families (RUT2M, RUT9M) ship only the 32-bit runtime, about 90 KB smaller on the router's small flash.
  • First beta build for the RUT2M family (RUT200, RUT241, RUT260): the firmware was verified against every Tangent dependency and the build passed the full hardware bench on a RUT200 on 16 September (install, rules, Test, failover and failback, support bundle). It has not yet had the weeks of field use the other families have, so it ships on the beta channel; use at your own risk and please report.

0.3.9

16 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.3.9

Beta: 07.25.1

  • Self-heal after a firmware upgrade no longer depends on the router holding a licence token. A router that had installed Tangent but never activated (for example, no internet at install time) could be left without Tangent after a RutOS upgrade, retrying silently every six hours. The platform now serves the stable build to any router that identifies itself by serial; the router logs the case clearly.
  • The About card shows the last self-heal or update attempt (when, what happened, and why if it failed), and the support bundle includes it.

0.3.8

13 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.3.8

Beta: 07.25.1

  • The About card shows the page version and warns when the browser is showing a cached page after an upgrade. The Licence card no longer repeats "Tangent is licensed on this router" under a healthy licence.
  • Test button on every rule (Live status): the router fetches a public echo page via the rule's exit WAN and via the bonded tunnel and shows you both public addresses, so "is it working?" is answered from the router itself.
  • Export and import rules as a JSON file (Settings card, "Rules file") - copy a proven rule set to other routers. The file carries rules only, never the licence or settings.
  • Domain rules now fill their address set the moment they are applied: the router resolves each listed domain itself instead of waiting for a device to look it up, so a device that already cached the address is caught by its next connection.
  • Dual-stack devices are kept on IPv4 for breakout domains (IPv6 lookups for those names return no address), closing a path that could bypass a rule. New setting "Keep breakout domains on IPv4", on by default.
  • Live status shows "New connections" per rule instead of packets and bytes (the counter only ever saw the first packet of each flow), and the DNS forwarder line updates more promptly.

0.2.12

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.12

Beta: 07.25.1

  • Fixes in-place upgrades through the Package Manager on RutOS 07.25: uploading a newer Tangent bundle over an older one only replaced the WebUI package and left the old service and API running (the Status card kept showing the old version). All three packages now upgrade together. Upgrades on 07.24 and the Update now button were not affected.

0.2.11

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.11

Beta: 07.25.1

  • Beta programme: the Update available row shows a "beta" badge when the build offered is for a firmware Teltonika has not yet marked stable, and says so.
  • Report an issue: a link in the About card opens the SimpliWiFi report form with your router model, firmware, Tangent version and serial already filled in.
  • Download support bundle: one button in the About card produces a small archive of Tangent's logs, rules and status to attach to a report. It never contains your licence token or any passwords. Also available over SSH as `tangentctl support-bundle`.

0.2.10

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.10

Beta: 07.25.1

  • Update from the Tangent page: when a newer version is published for your router's firmware, the Status card shows "Update available" with a What's new link and an Update now button. The update downloads, verifies and installs in place; rules re-apply within a few seconds.
  • If a newer version needs a newer router firmware, the page says so instead of offering the button.

0.2.9

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.9

Beta: 07.25.1

  • Fixes upgrading from 0.2.7 or earlier through the Package Manager: 0.2.8 could fail to start after an in-place upgrade ("Service not running") because of files left from the previous version.

0.2.8

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.8

Beta: 07.25.1

  • Hardened release build: the plugin now ships as compiled code with a signed integrity manifest, and refuses to run if its files have been modified.
  • Licence agreement and "What's new" links in the About card.

0.2.7

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.7

Beta: 07.25.1

  • RutOS 07.25: Package Manager install now completes (07.25's package tool verifies MD5 checksums, which 0.2.6's index did not carry).

0.2.6

11 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.6

Beta: 07.25.1

  • Installs on RutOS 07.25 through the Package Manager: 07.25 changed how uploaded bundles are installed (from a local package index) and renamed some system packages; 0.2.5 could not be installed on 07.25.1.
  • After a firmware upgrade the router no longer shows a leftover "Tangent" entry in the Package Manager that could not be installed or removed.

0.2.5

10 September 2026 RutOS 07.24.3, 07.24.4 RUTC, RUTM, RUTX GitHub release v0.2.5

Beta: 07.25.1

  • Reinstalls itself after a router firmware upgrade: with "keep settings" ticked, Tangent comes back on the new firmware within a couple of minutes of the first boot, with the same rules and licence, fetched from SimpliWiFi for the exact firmware version. (Needs the SimpliWiFi download service, which is being built; until it is live the router simply retries.)

Not seeing your router or the service you need? Tell us, or download Tangent for a supported router today.

Beta Programme

Beta programme

Beta builds are for RutOS versions Teltonika lists as "Latest" but has not yet marked "Stable". They pass the same tests as our stable builds but have spent less time in the field and on fewer router models. Use them at your own risk: they are supplied as-is under the Tangent licence agreement, and support for beta builds is best-effort via the feedback form. When Teltonika marks the firmware stable, the same build is promoted and your router carries on as normal.

Found a problem in a beta build? Report an issue and attach the support bundle from your router's Tangent page.