Daulat Join the pilot

The platform contract

Govern the work without taking over the boundary.

PLATFORM / 01

Daulat separates what is owned, what is authorized, where it executes, and how the result is verified—across an open-ended set of independently controlled environments.

Four assets, four control surfaces

Governed separately. Joined only for an approved run.

A workflow can reference each asset without collapsing their owners, policies, or version histories into one opaque package.

01

Data

Node-resident datasets, versions, custodian ownership, policy labels, and permitted use.

Owned by the data custodian
02

Algorithms

Versioned methods with independent ownership, licenses, approved uses, and confidential execution needs.

Owned by its algorithm custodian
03

Runtimes

Platform-approved signed images, pinned dependencies, resource boundaries, and execution policy.

Approved by platform governance
04

Models

Signed outputs with lineage back to input versions, runtime identity, policy decisions, and the run.

Governed as a versioned result

The governed journey

Declare → Authorize → Execute → Verify

Execution starts only after the participating identities, assets, purpose, approvals, and runtime satisfy policy.

  1. 01

    Declare

    Register governed assets, owners, policy labels, versions, and intended use.

  2. 02

    Authorize

    Evaluate identity, consent, licensing, custodian approval, and consortium policy.

  3. 03

    Execute

    Run platform-approved signed workloads where protected data is controlled.

  4. 04

    Verify

    Record outputs, signatures, lineage, policy decisions, logs, and reproducible versions.

Governed separately
  • Data
  • Algorithms
  • Runtimes
  • Models

Deployment boundary

Your environment stays yours.

The control plane coordinates governed work. Customer appliances execute approved work where each participant controls infrastructure and protected data.

Control plane
Identity, governed registries, policy, workflow coordination, approvals, and auditable state.
Customer environment
Node-resident data, approved runtime execution, environment-specific controls, and local operational authority.
Open topology
Customer cloud, on-premises, hybrid, or mixed infrastructure—without a fixed customer count.
The Federated Loom Any number of independent customer cloud, on-premises, hybrid, or mixed environments can connect through a shared trust layer while remaining independently controlled. CUSTOMER CLOUD customer-controlled ON-PREMISES customer-controlled HYBRID customer-controlled MIXED + MORE open edge SHARED TRUST LAYER
Compute moves through policy. Protected data stays within each governed boundary.

Execution engine, not platform core

Flower runs federated workloads behind Daulat’s governance boundary.

Daulat owns the lifecycle, policy, approvals, trusted runtime contract, audit, and governed asset model. Flower is one execution engine the platform coordinates; it is not the source of platform identity or authority.