Skip to content

Infrastructure 02 of 06

SieF OS

The customer-controlled environment that implements the shared four-pillar core and runs approved frameworks under the customer’s own authority.

In development

What it enables

  • Framework workloads running on infrastructure the customer owns or controls, rather than on a vendor’s cloud.
  • One trusted core doing security, execution, permissions and model resources, so each framework does not rebuild them differently.
  • Deployment modes that match the obligation: air-gapped, isolated on the customer’s own network, or a dedicated attested host under customer control.

Who it serves

  • Enterprise customers and the administrators they appoint.
  • Technical Sellers who install and support with the customer administrator’s approval.
  • Framework publishers, who target one core instead of many environments.

Scope and boundaries

  • The customer’s administrator approves installation, update and removal. There is no unrestricted remote vendor access and no routine phone-home telemetry.
  • An expired licence stops updates and new installs. It does not delete a customer’s data, and a sealed vault stays sealed.
  • Sovereignty here means control, not isolation. External integrations, regulators and licensed professionals remain part of real operations.
  • These are the controls the design specifies. We call them verified once they are implemented and independently tested, and not before.

In practice

  • An administrator reviews a signed release, approves it, and the framework installs; the approval is recorded.
  • A site runs with no outbound access at all, taking signed updates on offline media.
  • A framework asks for a model workload; the core schedules it inside the resource policy, and the framework cannot reach the hardware directly.

Where we are

In development. Interface previews on this site come from the design work and are labelled as previews wherever they appear.

Questions

Does my data leave the building?
Not for the system to work. A site can run offline after a licence is issued. What leaves is what you authorise through an approved connector.
What happens when a licence expires?
The operating system keeps running. Updates and new installs stop. An expired application stops, and its vault is preserved.