Obsilient
How it works

From a first conversation to a gate on every change.

You install one small, read-only connector. Everything else is delivered as a service: a map of your agent system as it is actually built, the quiet failures in it, and a pass or fail status your pipeline can call before a change ships.

Request a conversationSee the steps
The journey

Eight steps, one system at a time.

A pilot of about a month proves the value on one of your systems. A subscription keeps it watched after that.

The customer journey: a first conversation, scoping, the connector installed read-only, the first map and findings, a walkthrough, the gate installed on your change path, ongoing readings, then renewal or exit. Steps three to six are the pilot of about a month. Before Pilot, about a month Subscription renew First conversation Scoping Connector installed First map and findings Walkthrough Gate installed Ongoing readings Renew or exit Exit: connector removed, data deleted, you keep every report The customer journey: a first conversation, scoping, the connector installed read-only, the first map and findings, a walkthrough, the gate installed on your change path, ongoing readings, then renewal or exit. Steps three to six are the pilot of about a month. Before Pilot, about a month Subscription First conversationwhat you run, what worries you Scopingone system, your questions answered Connector installedread-only, in your pipeline First map and findingswithin the first week Walkthroughevery finding, with your team Gate installedon your change path Ongoing readingsnew findings, a quarterly review Renew or exityour choice, every year Exit: connector removed, data deleted, you keep every report

  1. First conversation

    You tell us which agent systems you run and what worries you about them. We tell you plainly whether Obsilient fits.

  2. Scoping

    Together we pick one system for the pilot, agree who on your side knows it, and answer your security team’s questions before anything is installed.

  3. Connector installed, read-only

    Your team adds the connector to your build pipeline or runs it as a container. It reads. It never writes, and it never runs your agents.

  4. First map and findings

    Within the first week you receive a map of the system as it is actually built, and the first ranked findings, each with the change that resolves it.

  5. Walkthrough

    We walk your team through every finding, so each one is understood, agreed or set aside before anything else happens.

  6. Gate on your change path

    By the end of the pilot a gate sits in your pipeline: a pass or fail status it calls before a change ships. You decide whether a fail blocks the change or only warns.

  7. Ongoing readings

    On a subscription your system is read on a schedule. New findings arrive as it changes, and we review the whole picture with you every quarter.

  8. Renewal or exit

    Renew for another year, or stop. If you stop, the connector comes out, your data is deleted and you keep every report. What happens at the end

What runs where

A connector on your side. The engine on ours.

The connector is small and read-only. It extracts structural facts and counts, and sends them over an encrypted channel. The engine runs only on Obsilient’s side. What comes back to you is findings, reports and the gate status.

Two boxes. Your environment holds your agents, the read-only connector and your change path. Obsilient holds the engine and the findings. An arrow from the connector to the engine is labelled structural facts, encrypted. An arrow back from Obsilient to your change path is labelled findings and gate status. Your environment Your agentscode, configuration, run logs reads only Read-only connectorstructural facts and counts only Your change pathcalls the gate: pass or fail Obsilient delivered as a servicenothing of it installed with you The engineruns only on our side Findings and reportsfor your team, yours to keep structural facts,encrypted findings andgate status Two boxes. Your environment holds your agents, the read-only connector and your change path. Obsilient holds the engine and the findings. An arrow from the connector to the engine is labelled structural facts, encrypted. An arrow back from Obsilient to your change path is labelled findings and gate status. Your environment Your agentscode, configuration, run logs reads only Read-onlyconnector Your pipelinecalls the gate structural facts,encrypted findings andgate status Obsilient The engineruns only here Findingsand reports Delivered as a service: nothing of theengine is installed in your environment.

In your environment

The read-only connector, in your build pipeline or a container. Nothing else of Obsilient is installed, and you can remove it at any time.

On our side

The engine, delivered as a service. It works out what is wrong and writes up each finding with the change that resolves it.

Back to you

Findings, reports and a walkthrough for your team, and a pass or fail gate status for your pipeline. The reports are yours to keep.

What the connector reads, and what it never sends

Talk to us

Run agents in production?

We are working with a small number of early teams. Tell us about your system and we will tell you plainly whether Obsilient fits.

Request a conversation