Ekalix Research · direction, not a release date

Radar is where we started. It isn't where we stop.

As a product-based company, we're built to grow into new areas, not just add features to one product forever. The directions below aren't shipped and aren't promised on a date - they're genuinely where our attention is going.

Four directions

What we're reading toward.

Artificial intelligence

Ekalix Radar already lets you connect an AI model to explain what it finds, off by default until you turn it on. We want to take that further - not by handing over your estate, but by making the explanation genuinely better where a rule engine reaches its limit.

Data science

Two years of performance history already sits in Radar's own database, for every server it watches. There's real signal in that history we haven't surfaced yet - patterns across an estate, not just a single server's chart.

Data engineering

The pipelines that move data between the systems Radar already watches are a natural next estate - watched with the same read-only, plain-English standard as SQL Server or MongoDB today.

Robotics

The furthest out of the four. The same discipline - reading a system honestly and saying plainly what needs attention - applied to a physical one instead of a database.

Why this order

Each direction builds on the last.

AI needs Radar's data to explain. Data science needs Radar's history to learn from. Data engineering extends what Radar already watches. None of this starts from zero - it starts from what Ekalix Radar already collects, every day, for every customer running it.

Interested in where this is going?

If any of these overlap with what you're working on, we'd like to hear about it.