SAILIENT GROUPWe have put four interface previews online. They show the surfaces of the three platform agents — Nexus, Sentinel and Atlas — and of the Secure Portal, each with its own entry point rather than as tabs of a single dashboard.
Read them as a sketch, not as a specification. Neither the content nor the interface is settled. The layout, the wording, the structure of each screen and every number shown will change. What is online is a rough impression of what these products could look like, put out early so it can be argued with while changing it is still cheap.
One word, two meanings — worth separating
Elsewhere on this site we use "pilot" to mean a pilot engagement with a customer. No such pilot has started, and that is unchanged. What went online is something else: interface previews, with no customer, no deployment and no backend. We kept the previews at /pilot/ and are naming the difference here rather than letting the two senses of the word blur.
What each surface is for
Each one answers a different question, which is why each gets its own door.
Nexus is the workspace: ask questions of your own material and see which model answered, under which policy, with which sources. The preview makes the path a request takes visible — protection, policy, routing — because that path is the product, not a setting inside it.
Sentinel is the operations view: alerts, incidents, infrastructure and asset coverage. The preview leads with a single incident told as a sequence, because an operator works with an incident, not with a chart.
Atlas is automation: workflows, agents and execution history, with an approval step as an explicit node in the flow. An automation that can act without review is only as trustworthy as its worst input.
The Secure Portal is the customer's own control plane: organisation, people, access, documents and the activity record.
What is not behind them
Nothing. There is no backend, no authentication, no stored state and no customer data. Every figure, name, alert and workflow in the previews is invented for the purpose. Each page says so at the top, and the sign-in form in the Secure Portal preview accepts nothing and sends nothing — deliberately, because a sign-in that looked real would claim something we do not have.
No customer, certification, partnership or performance claim is made anywhere in them.
Why publish something unfinished
Because the alternative is to show the first version only when it is too expensive to change. A product's shape is easiest to argue about while it is still a drawing. If something in these previews looks wrong to you, that is useful to us — and it is the reason they are online at this stage rather than a later one.
They will change. When they do, we will say so here rather than quietly swap them out.