Skip to content
SIAC
ES Sign in
The SIAC Mesh

Your servers, your agents and your AI, in one governed network

Until now, every server was an island: to touch it, someone had to sit at its console or lend a password. The SIAC Mesh joins them into a single network where your agents, Airo, your technical team and your own servers work together, and where anything that can't be undone is decided by a person.

ConnectEvery server, a node with its own identity

Each server gets its own identity, signed by SIAC and renewed every day, and declares what can be done with it and at what risk. It starts switched off: its owner turns it on and chooses what it exposes.

There is one line that is never crossed: servers running a dedicated SIAC instance never join the mesh. It isn't a disabled option; it's the design.

24 h lifetime of each server identity; it renews itself measured on 2026-09-26

12 tools with their declared risk on every server, from the moment it joins measured on 2026-09-26

The SIAC Mesh One door, the whole ecosystem
Who asks The door Your servers
  • Your agents with their toolbox and budget
  • Airo the console assistant
  • Coding assistant of your technical team
  • Another server through a granted route
SIAC
  1. identity
  2. risk
  3. confirmation
  4. ledger
open protocol · MCP
  • ERP accounting and inventory identity · 24 h on
  • Customer portal with your domain and brand identity · 24 h on
  • Data off: its owner decides identity · 24 h off
  • Outside server joined with a code identity · 24 h on
Dedicated SIAC instance outside the mesh, by design
  1. each server receives its signed identity
  2. its owner turns it on and chooses what it exposes
  3. whoever asks comes in through the door, and sees only their own
  4. the dedicated instance never joins
Example names. The rule is real: no identity, no node; not turned on, no tools; and no request skips the door.

OperateOne single door, and the irreversible asks first

The mesh speaks MCP, the open tools protocol. Your agents, Airo, your technical team's coding assistants and other servers all come in through the same door, and each one sees exactly what the person using it would see.

Every tool declares its risk. Reading runs instantly; anything that could reveal a secret arrives redacted; and whatever writes, reaches outside or can't be undone waits for a person to approve those exact arguments.

Everything lands in a ledger that is never deleted: who asked for what, through which channel and what happened, whether it was a person, an agent or a server.

10 min to approve the irreversible; then it expires, and each approval works only once measured on 2026-09-26

The irreversible asks first An agent proposes, a person decides
  1. Support agentoverwrites
    restart the «orders» service on ERP
  2. Waiting for a personexpires in 10:00
    service: orders · reason: not responding since 9:12
  3. approved by Laura, administrator · single use
  4. ledger · support agent · restart · approveddone in 2.1 s
  1. the agent asks
  2. the door stops it and notifies
  3. a person approves those arguments
  4. it runs and lands in the ledger
  • readsruns instantly
  • could revealarrives redacted
  • writes or reaches outwaits for a person
  • can't be undonealways a person
Example names and times. The rule is real: the approval expires after ten minutes, works once, and nobody —not an agent, not an administrator through the door— can skip it.

GrowServers that talk to each other, domains with your brand

  • By default no server sees another. A route lets one ask another for specific tools, with an expiry date and a written reason.

  • A server can publish several domains, each with the brand of whoever uses it: SIAC checks it points where it should and the security padlock is issued automatically.

  • A server SIAC didn't create joins with a single-use code, and only connects outwards: no port needs to be opened.

  • And your published agents accept tasks from other systems through the open agent-to-agent standard, with their own model, budget and ledger.

22 s from activating a new domain to serving it with a padlock, measured in production measured on 2026-09-26

15 min validity of the code that joins an outside server; it burns on use measured on 2026-09-26

How it applies in your company

Four situations solved today with borrowed passwords, tickets or favors, and how they look with the mesh.

  1. Support without borrowed passwords

    BeforeTo check a server, someone shares their access and afterwards nobody knows what was touched.

    With the meshYour agent reads the server's status and logs and proposes the fix; the restart waits for your go-ahead and is written down.

  2. Your technical team, with its AI assistant

    BeforeEvery developer connects their assistant however they can, with access nobody keeps track of.

    With the meshIt connects to the door with a personal key and sees only its organization's servers; anything destructive asks you first.

  3. Your ERP and your portal, talking

    BeforeThe portal pulls data from the ERP through a custom integration nobody dares to touch.

    With the meshA route grants the portal a single ERP tool —check inventory—, with an expiry date and every call in the ledger.

  4. Your brand on your domain

    BeforePublishing a system on your own domain meant a ticket to the vendor and an expired certificate every so often.

    With the meshYou register the domain, SIAC checks it points right and serves it with a padlock; if it's SIAC, it opens with your logo and colors.

Nothing that already runs changes when you turn the mesh on: your organization decides what it connects, server by server and agent by agent.

Does your case look like this?Tell us which servers and systems you want your agents to operateTell us your case

What people ask before deciding

Can an agent delete or restart something on its own?

No. Whatever writes, reaches outside or can't be undone waits for a person to approve those exact arguments; the approval expires after ten minutes and works only once.

Does our dedicated SIAC instance join the mesh?

No, and it can't be enabled: servers running a dedicated instance never receive a mesh identity or appear in any list.

Do we need to open ports on our servers?

No. Servers connect out to SIAC; nobody connects in. Even one SIAC didn't create joins with a single-use code.

Can we use the AI assistant our technical team already uses?

Yes, any that speaks MCP, the open tools protocol. It comes in through the same door and sees only what the person using it would see.

What does one server see of another?

Nothing, except what a route grants: specific tools, with an expiry date and a written reason, and every call in the ledger.

The other verticals

Get started

Tell us a use case. We tell you how it's tackled.

SIAC comes in through the organization, not through personal accounts. If you already work with us, your console is one click away. If not, let's start with the process that hurts most.

Let's talk about your case Sign in to the console
Ask SIAC