Solutions · Power and energy

Keep vendor support. Keep the substation topology inside the perimeter.

Power and energy networks run long-lived OEM estates, and a diagnostic bundle from them crosses the boundary between the corporate network and the operational one — carrying control-network and substation addressing, control-centre topology and site names with it. LogVeil is being built so that the utility keeps vendor support without exporting any of that: the values rewritten under your own policy inside your perimeter, with a signed attestation of what left and what did not.

Inside your perimeter, the estate — the control centre, the substations and the corporate network beside them — produces a diagnostic bundle that carries control-network addressing, substation topology, site names and the shape of a long-lived OEM estate; LogVeil, in your own virtual machines under your policy and your key, rewrites every sensitive value and signs the attestation you keep as audit evidence; only the sanitised bundle and the attestation cross the perimeter to the vendor’s technical assistance centre. The release decision stays with you. INSIDE YOUR PERIMETER OUTSIDE Your estate control centre, substationsthe corporate network beside The diagnostic bundle control-network addressingsubstation topologysite names and locationslong-lived OEM estates LogVeil, in your own VMs your policy, your keyevery sensitive valuerewritten; the attestationkept as audit evidence The vendor's TAC the sanitised bundle andthe attestation arrive;the topology never does THE RELEASE DECISION STAYS WITH YOU · NOTHING LEAVES WITHOUT A RECORD Inside your perimeter, the estate — the control centre, the substations and the corporate network beside them — produces a diagnostic bundle that carries control-network addressing, substation topology, site names and the shape of a long-lived OEM estate; LogVeil, in your own virtual machines under your policy and your key, rewrites every sensitive value and signs the attestation you keep as audit evidence; only the sanitised bundle and the attestation cross the perimeter to the vendor’s technical assistance centre. The release decision stays with you. INSIDE YOUR PERIMETER Your estate control centre, substationsthe corporate network beside The diagnostic bundle control-network addressingsubstation topologysite names and locationslong-lived OEM estates LogVeil, in your own VMs your policy, your keyevery sensitive valuerewritten; the attestationkept as audit evidence OUTSIDE The vendor's TAC the sanitised bundle andthe attestation arrive;the topology never does THE RELEASE DECISION STAYS WITH YOU

Drawn by code from the description of the estate; not a screen.

The bundle

What a bundle from this estate carries

  • control-network and substation addressing
  • the boundary between the corporate and the operational network — and the fact that a diagnostic bundle crosses it
  • control-centre topology
  • long-lived OEM estates, with the same devices in place for years
  • site names and locations

Before it leaves

The standing exception, closed without closing the channel

what leaves the perimeter, and to whom

evidence for internal audit

OEM support as the standing exception nobody has closed

What has to be true before anything leaves — in the words of the people who decide.

Vendor support is the standing exception in most perimeters: the one channel through which a copy of the operational network's structure routinely leaves, with no record of what went. LogVeil is designed to keep the channel and remove the exposure. The bundle still goes to the vendor's technical assistance centre; what goes is rewritten under your own policy, and the attestation is the evidence — for internal audit, and for anyone with the standing to ask what left the perimeter — of exactly what was rewritten, what was dropped and what is not asserted.

The fit

How LogVeil is designed to fit

Your policy, your dictionary, your key

in development

The customer writes the rules and holds the key; Zindagi never sees either.

The policy and the key →

Verified — and honest about what isn’t

in development

A separate verification stage re-scans the output with independent scanners, fails closed, and signs an attestation that also says what is not claimed.

The attestation, field by field →

Reversible under control

in development

When the TAC replies about a masked address, your engineer can translate it back — and nobody else can.

How it works, in depth →

Built for the air gap

in development

An offline kit for your own VMs; nothing phones home; AI is optional, off by default, and never touches the result.

The offline kit →

The path

From a proof-of-concept on your own bundles to your own operation

  1. First

    Early access

    Early access is a free, guided proof-of-concept on your own bundles inside your own network: you choose the bundles, you write the policy with our help, and you keep the key; we hand over the offline kit, run the first jobs with your engineers, and leave you with the attestations.

  2. Then

    The offline kit, for your own operation

    in development

    An offline kit for your own VMs; nothing phones home; AI is optional, off by default, and never touches the result.

  3. On the roadmap

    An appliance

    planned

    A server with a local GPU for local AI and TPM-sealed keys. No bill of quantities, no price — it is a roadmap item.

Status, and the next step

LogVeil is in development. An early-access programme opens after our first field trial.

Request early access