Skip to content

The Anoryx EcoSystem

Four products that share one event bus and one rule: they run inside your infrastructure. Know who owns every key, approve risky actions in private, keep AI spend in check, and let agents work as a team.

Diagram: Sentinel, Rendly, Delta and your existing systems connect through the Orchestration Layer event bus, all inside your own infrastructure. The connection to third parties outside the boundary is blocked.
Your infrastructure · VPC / data centre
SentinelIdentity ownership
RendlyPrivate approvals
DeltaAI spend control
Your systemsIdP · cloud · ERP · Git
Orchestration Layer
Third partiesno egress

Illustrative architecture · products in development, see status below

How they work together

One orphaned key. Four products. Zero guesswork.

Here is the kind of problem no single tool closes on its own, followed end to end. Names and numbers are sample data.

orchestration · trace 0x9c41
  • spend.anomaly02:14:07
    key …7f2a · +340% vs baseline · no use case
1 event · stays in your VPC0 bytes egress

Principles

Architecture, not adjectives.

Trust is designed in, not promised. These rules hold for every product in the EcoSystem.

Self-hosted by default

Every product runs inside your VPC or data centre. No outbound telemetry, no shared tenancy, no copy of your data on our side.

Read-only first

We start by looking, not touching. Discovery connectors ask for the narrowest read scopes, and write access is opt-in, per action.

Humans approve high-risk actions

Revoking a key, retiring an agent or lifting a budget cap waits for a named owner. Automation proposes; people decide.

Audit-ready evidence

Every finding, decision and action is logged with who, what and when, and is built to export as evidence that maps to the frameworks your auditor uses.

Works with your tools

Plugs into the identity provider, cloud and Git you already run. Nobody wants a tech stack on top of a tech stack.

Deployment

Start on one machine. Grow into your cluster.

Pick the shape that matches your risk posture. Phases are labelled plainly: the pilot path comes first.

Pilot · MVP

Docker Compose

One virtual machine you control.

  • Designed to install in a day (target)
  • Read-only connectors to start
  • Ideal for a design-partner pilot
Production · Next

Kubernetes with Helm

Your cluster, your rules.

  • High-availability Postgres
  • Role-based access control
  • Signed images and SBOM
Regulated · Roadmap

Air-gapped

No internet. No exceptions.

  • Offline install bundle
  • Local models only
  • Zero egress by design

Deployment targets are design goals for products still in development. We will confirm sizing and timelines with each design partner before anything is installed.

See the platform on your own infrastructure. Become a design partner.

We are recruiting a small number of design partners to shape Sentinel and the wider EcoSystem. You get early access and a direct line to the founder; we get honest feedback.