DeFlow Docs
Private betaVerified 2026-08-18

Product Availability

Check the release status, operating environment, and assurance boundary for every DeFlow capability.

DeFlow documentation describes the complete product model and separates it from the release state of each capability. Use this matrix to determine what can be used now, what has restricted behaviour, and what remains part of the product roadmap.

Account and identity verification

Private beta

Third-party verification runs in sandbox mode.

Bilateral OTC settlement

Private beta

Uses Sepolia contracts and test assets.

Syndicate raises

Private beta

Invited validation flow; implemented with FIFO allocation and one Sepolia escrow per approved investor. End-to-end validation is pending.

Team desks and invitations

Private beta

Default desks, members, roles, invitations and activity records are implemented for beta coordination.

Dashboard and deal analytics

Limited beta

Beta deal, volume and activity summaries are available; some telemetry remains simplified and is not a financial statement.

VIP progression and referrals

Private beta

Cash withdrawal flows use TestUSDC.

Partner programme

Limited beta

Access and benefits are subject to onboarding and product readiness.

Pro-rata syndicate allocation

Planned

The beta uses FIFO; proportional oversubscription is not implemented.

Pooled syndicate escrow

Planned

The beta deploys one escrow per approved allocation; the pooled contract and on-chain SyndicateController are not implemented.

Institutional KYB tiers

Planned

Individual sandbox verification is available; L2/L3 institutional onboarding is not launched.

Portfolio and risk analytics

Planned

Read-only analytics are roadmap functionality.

Public API and SDK

Planned

No supported public developer interface is published.

Current operating environment

AreaCurrent configurationProduct direction
NetworkEthereum Sepolia, chain ID 11155111Production networks require a separately approved deployment
Gas assetSepolia ETH with no monetary valueNetwork-specific native gas asset
Settlement assetAllowlisted TestUSDC with no monetary valueGoverned asset allowlist
Identity verificationThird-party sandbox workflowApproved production provider and reviewed policy configuration
Smart contractsDeployed on SepoliaRelease-specific verified deployments
External contract auditNot engagedIndependent audit required before a production-readiness claim
Legal reviewAwaiting qualified counselJurisdiction and service-specific approval required

How availability labels work

  • Private beta means the capability is available to invited participants in the current environment.
  • Limited beta means the capability exists, but access, integration coverage, or behaviour is restricted.
  • Planned means the capability belongs to the product model but is not an available workflow.
  • Pending review or pending audit means implementation evidence must not be presented as independent assurance.

Syndicates, for example, support FIFO allocation and one escrow per approved investor in the current release. Pro-rata allocation, pooled escrow, and an on-chain SyndicateController remain planned. Availability labels and page-level notes carry this distinction without reducing the rest of the documentation to a temporary test manual.

Change control

Every product claim is derived from the canonical product-facts ledger and has an owner and verification date. A capability changes status only when implementation, deployment, operational, and assurance evidence support the new label. Marketing plans or a visible interface alone are not sufficient.