HELIX NMS+

What changed, and when.

Generated from the repository’s own changelog at build time, so this page cannot describe a release that did not happen.

HELIX NMS+ is pre-GA and in live production use. Releases before 1.5.0 were not consistently tagged, so this record begins there rather than reconstructing a history it cannot verify.

1.9.1

  • A router's page keeps showing exactly the actions your role allows, from the moment it opens, including the control for marking a link as internal or a client.
  • The email template editor opens with the template already in it.
  • After a payment at the counter, the amount box clears and stays clear for the next customer.

1.9.0

  • A live wall for the operations room, and a traffic graph for every router and port at four time ranges, searchable from one place. The traffic view shows the busiest links and their peaks. Alerts fire when a watched port goes down or flaps, and when an uplink saturates or goes quiet.
  • Cards at the top of each organisation's dashboard show money owed, overdue and collected this month, subscriptions, routers, open incidents, backups, routing and failed sign-ins. A card that cannot be read says so instead of showing zero.
  • See each network as it is configured: addresses, firewall rules, queues, VLANs, bridges and spanning tree are read from the routers and shown with who manages each entry. You also see the public address blocks in use, and who announces and holds them.
  • Bring the subscribers you already run into billing without changing your routers, including business VLAN and static address clients. A business VLAN import can bill its first part-period up to the date you choose.
  • Each organisation gets a daily briefing of what needs attention. Once you switch it on, an assistant answers questions about your network and billing on the web and in Telegram. The assistant only reads: it never changes a router or a bill.
  • When a router is added a second time, it is recognised as the same router and the older entry is retired, or the pair is marked for you to decide when retiring it is not safe. A router's name and model stay in step with what the router reports.

1.7.0

  • Manual billing works end to end: raise a one-off invoice, take part payments at the counter, carry credit to the next bill, and print a customer's statement of account.
  • Each organisation's billing page shows who owes money, oldest first, and a customer can be billed their own negotiated price.
  • Moving from Splynx is done in checked batches, each customer's billing is handed over when you are ready, and anyone at risk of being billed by both systems is listed.
  • Business customers on a static public address or their own VLAN can be set up, moved and re-addressed, and the console says when a suspension would not actually cut a client off.
  • See which routers accept management from anywhere, and be told when a router gains a user or script nobody created through Helix.
  • Routing health (BGP, OSPF and LDP) on the monitoring board, a Ctrl-K search for any router or subscriber, and a light theme.

1.6.0

  • Bills, reminders and disconnection notices now respect whichever system is in charge during a migration, so nobody is cut off by one and restored by another.
  • Alerts group themselves. One upstream failure that takes out many sites arrives as a single message, and a problem that is still going on reminds you once a day instead of every few minutes.
  • A router that answers a ping but refuses management is now reported as such, instead of appearing perfectly healthy on every screen.
  • Payments taken at the counter settle the right invoice and reconnect the customer immediately.
  • Firmware upgrades check that the device has room before they start, and say what to do instead when it has not.
  • The people who handle money and the people who handle the network can now be given access separately.

1.5.0-beta.1

  • Alerting works end to end: rules, destinations, and a record of what was actually delivered.
  • Every action taken on a router is recorded with who asked for it, including the ones that were refused.
  • Backups run on a schedule, and you can see whether they worked rather than assuming.
  • Customer records, plans and invoices are usable as a day-to-day billing system rather than a data store.

1.5.0

  • First release with network management and billing in one product, so the system that knows a router is down is the same one that knows who is on it.
  • Routers can be reached whether or not they have a public address.
  • Traffic and system graphs show gaps where data is genuinely missing, rather than drawing a confident zero.