Back to blog
Product Updates · February 9, 2026

What Has Changed in Lunixar Since Version 1

If you run IT operations seriously—whether as an MSP or an internal team—you know there are two kinds of tools:

  • The ones that _kind of work_ but force you to adapt to them.
  • And the ones that keep maturing until it feels like the platform is working with you.

Since Lunixar reached version 1.0, the focus has been exactly that: less friction, more control, stronger visibility, and a platform built to scale real-world operations.

Instead of dumping a massive technical changelog on you, let’s talk about the updates that actually change day-to-day work—what improved, why it matters, and how you can take advantage of it.

1) Alerts With Real Context (not just “something happened”)

One of the biggest jumps since 1.0 is how alerts evolved from simple events into a full lifecycle with history.

You can now see:

  • Alert state (active/resolved/ignored),
  • First and last detection,
  • Occurrence count,
  • Resolution date,
  • And a full event timeline showing how the issue progressed.

That sounds small… until a customer says:

“This keeps happening.”

Now you have real data instead of guesswork.

Practical tip: when a client questions recurring problems, open the timeline and use it as evidence to justify fixes—or infrastructure upgrades.

2) Less Email Noise, More Signal

Anyone who runs monitoring knows the danger:

too many alert emails = nobody reads them.

Since 1.x, Lunixar strengthened notification controls so they’re usable at scale:

  • Company-wide configuration,
  • Rules per alert type and category,
  • Recipients per rule (instead of one global list),
  • Cooldown mechanisms to prevent duplicate emails,
  • Templates based on the user’s language (EN/ES).

The result: alerts that get attention instead of being ignored.

Practical tip: start with a tight group of recipients (owner + one lead tech). Expand later—don’t default to “everyone gets everything.”

3) Smarter Rules by Device Type

This is one of the most MSP-friendly upgrades: alert rules can now target multiple device types in a flexible way.

Why that matters:

  • A user laptop that shuts down every night,
  • A 24/7 production server,
  • A critical VM,
  • Or a newly discovered machine…

…should _not_ follow the same rules.

Now you can tune alerts per environment instead of drowning in false positives.

Practical tip: keep _Device Disconnected_ strict for servers and VMs, but far more tolerant—or disabled—for user workstations.

4) True Realtime Visibility

Realtime monitoring was significantly reinforced:

  • Dedicated realtime sessions per company,
  • Session validation with binding + heartbeat,
  • Push events when alerts fire,
  • UI pop-ups for new alerts,
  • And a much more reliable “unseen alerts” badge.

In practice: you see critical issues the moment they happen, without refreshing dashboards or waiting for polls.

Practical tip: this is what lets you fix problems before users even open tickets—huge for service perception.

5) Silent Hardening (the stuff you don’t see—but depend on)

Not flashy, but absolutely essential.

Behind the scenes, Lunixar reinforced:

  • Rate limiting on sensitive endpoints,
  • Server-side sorting for large alert datasets,
  • Backward-compatible flows to avoid breaking customers,
  • Stronger backend ↔ websocket communication.

Translation: fewer surprises, more stability, better uptime as you scale.

Practical tip: when you grow clients, reliability matters more than new features. These upgrades are built exactly for that stage.

6) UX Improvements: Fewer Clicks, Clearer Workflows

Alert configuration and settings got a lot of love:

  • Cleaner Settings layout,
  • Dedicated pages instead of clunky dialogs,
  • Sidebar reorganization,
  • Better filters and search,
  • Improved mobile experience.

You may not notice it at first—but after configuring dozens of rules, you’ll be glad it’s not a fight.

Practical tip: every UX improvement reduces internal mistakes… and cuts down on “why am I not getting alerts?” tickets.

Bonus: What This Tells You About Lunixar’s Direction

If you’re evaluating RMM platforms, these updates send a clear message:

  • Lunixar isn’t just adding features.
  • It’s maturing the platform for real operations.

For MSPs, that matters more than flashy releases.

Closing

Since version 1.0, Lunixar has focused on three things that truly matter in daily IT operations:

  • Alerts with real traceability (less guessing),
  • Email notifications you can actually manage (less noise),
  • A stronger realtime platform (less friction).

If you’re tired of an RMM that feels like “a pile of tools glued together,” Lunixar is moving in the opposite direction: simpler for technicians, more useful for operations, and stable enough to grow with you.

And if you’re curious about what’s coming next—new alert types, deeper security controls, and automation—this direction isn’t changing anytime soon.

Less chaos. More control.