Where the product is today

Straight answers about the current state. A product that names its own edges is worth more than one that does not.

In private pilot

Nexyron is running with design partners. Names, numbers and case studies will appear when partners agree to stand behind them publicly, and not before. If you are evaluating and want references, ask, and we will tell you honestly what we can and cannot arrange.

Mac first, servers anywhere

The desktop application is built for the Mac. The server runs on ordinary infrastructure of your choosing and is not tied to Apple hardware. If your team works on Windows or Linux and wants the local experience specifically, tell us, because it affects what we build next.

Its own query language

Nexyron speaks its own dialect of Cypher. Queries written for another graph database will generally not run unchanged.

This is a real cost if you have an existing body of queries, and worth weighing. In exchange, failures are specific: an error explains what is wrong, names the closest valid construct, points at its reference page, and gives a working example. Teams generally find the dialect quick to pick up, but you should plan for a short learning period rather than a lift and shift.

The assistant uses an AI provider you choose

Understanding your data happens on your machine. The reasoning layer of the assistant currently uses an external AI provider that you select and supply credentials for.

Everything else, including the query language, the analytics, the Lenses and the reports, works without it.

Scale

A single machine handles a great deal, and most businesses evaluating Nexyron will not approach its limits. If you are working at a scale where that is a real question, ask us with your numbers in hand and we will give you a straight answer rather than a reassuring one.