Skip to main content

Skylar Compliance: Product Update and What's Next

  • July 10, 2026
  • 0 replies
  • 4 views
Forum|alt.badge.img

This is the first in what will be a regular cadence of product updates here in the community. I'll use these posts to share what we've recently shipped, what's in progress, and where the product is heading.
 

A modernized interface

In an upcoming release, we're shipping a significant update to the Skylar Compliance UI, completing the migration to Material UI, the design system used across the rest of the Skylar suite.

What this means for you:

  • The interface will look and feel consistent with the other Skylar products, which is especially noticeable if you work across multiple products in the suite.

  • Components throughout the product are being modernized, directly addressing feedback we've heard about the interface feeling dated.

  • It sets the foundation for the continued UX work the team is focused on through the rest of the year.



Lua Functions in Device Control

This release also includes a new function type for Device Controls. Available for both ad hoc and scheduled commands, Lua Functions allow scripts to signal errors explicitly, return early using standard Lua syntax, and accept typed variable inputs rather than simple string substitution. This gives you clearer feedback when a command fails and a more reliable foundation for device automation. Note: new Lua Applets can no longer be created. Existing ones continue to work, but we recommend migrating to Lua Functions.
 

Recently released

Two improvements that already landed:

  • Device Control Outputs: A new view that consolidates results when you run commands across multiple devices. Instead of reviewing output device by device, you get a single aggregated view of successes, failures, and timing, with results you can filter and export.

  • Log improvements and tracing: End-to-end tracing and richer contextual fields across Skylar Compliance actions and APIs. When something goes wrong, you can follow the full chain of an action rather than piecing together disconnected log entries.


Further ahead: version 6.0

Later this year we're targeting a 6.0 preview, which brings the compliance capabilities the team has been building toward, along with several other improvements. More detail will follow as it gets closer.

One callout for anyone using the Skylar Compliance API: 6.0 will include breaking API changes. I'll share specifics well ahead of the release so you have time to prepare.


Have questions or something you'd like to discuss? Reply in the thread below, or reach out to your engagement manager or customer success manager. I'll be back with the next update soon.