Skip to content

Private preview

The signing layer that refuses to guess.

Signing Fabric gives teams a private control plane for custody, approvals and audit. Threshold cryptography keeps a complete private key out of existence.

The management plane is available by invitation. Wallet creation and signing remain private, supervised ceremony paths while we prove the fabric with our own controlled surfaces.

No complete key · no single trust domain · no silent approval

Control planeNot connected

signing request

Policy-gated value movement

illustrative
  1. 01intent decoded
  2. 02policy evaluated
  3. 03quorum requested
  4. 04partial signatures
  5. 05audit record
complete key materialnever assembled
independent trust domains per signature
2
complete private keys, at any moment
0
chain families: Bitcoin, EVM, Solana
3
decision history, never rewritten
append-only

Trust model

Two domains.
One accountable outcome.

Shares live in deliberately different environments with no shared operator credentials and no shared control plane. Only partial signatures ever leave a domain — compromising one yields a value that is useless without the other.

Neither domain alone can sign. Compromising one yields a share that is useless without the other.

See the lifecycle, boundaries and failure cases

Decision path

A signature is the last event, not the first.

sr_3f8a…9c2alive path

raw calldata

0xa9059cbb0000000000000000000000

71c7656ec7ab88b098defb751b7401b5

f6d8976f00000000000000000000000

00000000000000000000002386f26fc1

method
transfer(address,uint256)
recipient
0x71c7…976f · treasury (allowlisted)
amount
10.000000 USDC
residual
none · value fully accounted

01 / 05

Decode

The exact bytes become a typed, human-readable intent. Nothing is evaluated against a summary.

What you can integrate today

Useful before a signature ever exists.

The surfaces below are live in the invite-only management plane and documented route by route. Each one is generated from the same OpenAPI specification the API is built against.

Policy in the signing path

Versioned value-conservation rules run before either domain may use a share. Decoding is recursive, and an instruction the engine does not understand is a denial — never a default-allow.

/v1/policies · /v1/policies/{id}/versions

Approvals bound to bytes

Quorum approvals carry an Ed25519 stamp over the request itself, so a member signs what they reviewed rather than what a screen rendered. Roles decide who can even be counted.

/v1/signing-requests/{id}/approvals

Append-only audit

Every verdict, actor and committed transition becomes a structural event. Reads are cursor-paginated and are deliberately not themselves audited.

/v1/audit

Signed event delivery

Timestamped HMAC signatures, bounded retries and a stable delivery id so your handler can be idempotent without guessing.

/v1/webhooks

Keys, roles and stamps

Organization-scoped API keys, per-member signing keys and revocation. A credential from another organization cannot even tell your resources exist.

/v1/api-keys · /v1/members

Full platform at launch

One signing layer.
Every critical surface.

Embedded wallets, treasury controls and automation share the same fail-closed policy boundary. Plans change capacity and support — never the custody model or security guarantees.

Create

All plans

Wallet infrastructure

  • Embedded user and business wallets
  • All EVM networks, Solana and Bitcoin at launch
  • Browser, server, React, WalletConnect and native iOS SDKs
  • Passkeys, biometrics, OAuth and enterprise SSO

Control

All plans

Policy and approvals

  • Policy checks before every use of a share
  • Web and Face ID clear-signing approvals
  • Configurable multi-person quorums and roles
  • Scoped sessions, API signers and delegated automation

Operate

All plans

Payments and workflows

  • Batch payments and controlled dApp sessions
  • Qualified gas sponsorship for EVM and Solana
  • Signed webhooks, retries and reconciliation
  • Crypto-only billing in approved assets on supported chains

Prove

All plans

Evidence and recovery

  • Live and historical audit with export
  • Customer-verifiable policy, quorum and finality evidence
  • Independent-domain recovery without reconstructing a key
  • Quorum-approved provider exit to a customer-controlled wallet

Enterprise

Custom only

Private, colocated low-latency execution.

Dedicated topology, customer-specific integration, custom limits, retention, SSO and support belong to Enterprise. The fast path is designed for colocated low latency without bypassing policy, quorum or evidence controls.

Design a deployment

Feature comparison

Everything required.
A stronger custody boundary.

The complete wallet, custody and enterprise platform scope in one readable view. Checks show included capability; an X includes the relevant limitation from reviewed public product material.

FeatureSigning FabricComplete scopePrivyTurnkeyMPCVault
Wallets and money movement
Embedded user walletsWallets provisioned directly inside an application.IncludedIncludedIncludedTeam vaults rather than embedded user wallets.
Business and treasury vaultsShared wallets with roles, approvals and operating controls.IncludedIncludedIncludedIncluded
EVM, Solana and BitcoinThe three primary launch chain families.IncludedIncludedIncludedIncluded
Additional-chain adaptersExtensible signing and policy adapters beyond the launch families.IncludedIncludedIncludedIncluded
WalletConnect and dApp accessControlled connections to external applications and protocols.IncludedIncludedIncludedIncluded
Gas sponsorshipPolicy-controlled fee payment for user transactions.IncludedIncludedIncludedNo native sponsorship product documented.
Batch paymentsValidated multi-recipient payment and approval workflows.IncludedIncludedIncludedIncluded
Funding, swaps, bridges and on/off-rampIntegrated asset movement through qualified providers.IncludedIncludedIncludedIncluded
Cards and controlled spendPolicy-limited card and spending-account integrations.IncludedIncludedNo native card product documented.Included
Earn and DeFi workflowsPolicy-gated access to yield and protocol integrations.IncludedIncludedIncludedIncluded
Security and control
No complete key assembledSigning completes without reconstructing a full private key.IncludedKey use reconstructs inside a provider TEE.Full-key operations run inside a provider TEE.Included
Independent operator domainsA signing quorum spans separately operated infrastructure.IncludedProvider-operated signing infrastructure.Provider-operated signing infrastructure.Server domains are provider-operated.
Proactive share refreshShares rotate while wallet addresses remain unchanged.IncludedNot documented in reviewed public material.Uses a different full-key architecture.Included
Programmable policiesRules constrain signers, assets, destinations, value and sessions.IncludedIncludedIncludedIncluded
Multi-person approvalsRole-aware quorum approval for sensitive actions.IncludedIncludedIncludedIncluded
Customer-verifiable approval evidencePortable proof binds policy, intent, approvers and chain result.IncludedNo portable proof bundle documented.No portable approval-proof bundle documented.No portable proof bundle documented.
Mobile clear signing and biometricsNative transaction review and biometric approval.IncludedIncludedIncludedIncluded
RecoveryGoverned user, member and organisation recovery paths.IncludedIncludedIncludedIncluded
Wallet and custody exportCustomer exit through quorum-controlled resharing or audited migration, without platform lock-in.IncludedIncludedIncludedIncluded
Developer and enterprise platform
Web, server and native SDKsTyped clients and UI kits for browser, backend and mobile apps.IncludedIncludedIncludedIncluded
Passkeys, OAuth and consumer authEmbedded authentication and delegated sessions for end users.IncludedIncludedIncludedBuilt around team-member identity.
Organisations, sub-orgs and rolesTenant isolation and fine-grained administration.IncludedIncludedIncludedIncluded
Audit and signed webhooksSearchable events, delivery history and authenticated callbacks.IncludedIncludedIncludedIncluded
SSO, SCIM and MFAEnterprise identity lifecycle and access enforcement.IncludedIncludedIncludedIncluded
Customer security evidenceVerifiable custody, policy, quorum and execution evidence.IncludedNo portable evidence bundle documented.IncludedNo portable evidence bundle documented.
Dedicated or custom deploymentEnterprise topology, private connectivity and colocated fast paths.IncludedNot documented in reviewed public material.Not documented in reviewed public material.Included

Signing Fabric values show the complete planned platform scope. Competitor entries summarize official public material reviewed 1 September 2026. “Not documented” is not proof of absence.

Crypto-native pricing

Full platform. Lower entry price.

Monthly settlement in USDC. No cards and no security downgrade by tier: every production plan includes the core API, SDKs, policies, approvals and evidence surface.

Developer

$0USDC / month

Build and evaluate on test networks.

  • 500 test wallets
  • 50,000 test signatures
  • 3 signer seats
  • 30-day audit retention

Test only · hard production cap

Launch

$49USDC / month

For an early production integration.

  • 2,000 active wallets
  • 10,000 signatures
  • 5 signer seats
  • $1M outbound volume

Overages from $0.008 / wallet

Growth

$149USDC / month

For growing embedded-wallet products.

  • 5,000 active wallets
  • 100,000 signatures
  • 10 signer seats
  • $4M outbound volume

Overages step down as you scale

Scale

Best value

$249USDC / month

For established platforms with volume.

  • 25,000 active wallets
  • 500,000 signatures
  • 25 signer seats
  • $20M outbound volume

0.02 bps outbound-volume overage

Enterprise

Custom

Pricing, capacity and topology

  • Private colocated fast path
  • Custom deployment topology
  • Custom limits and retention
  • Enterprise SSO and support
Talk to us

Launch pricing · allowances and overages remain subject to final service terms

Developer surface

Read the contract before the pitch.

The public docs describe the management plane that exists today: authentication, endpoints, security invariants and event delivery. Nothing in them implies a signing path you cannot reach.

read-audit.ts
import { FabricClient } from "@signing-fabric/sdk-server";

const fabric = new FabricClient({
  baseUrl: process.env.FABRIC_API_URL,
  apiKey: process.env.FABRIC_API_KEY,
});

// Cursor-following iterator over the append-only trail.
for await (const event of fabric.audit.iterate({
  action: "signing_request.approved",
  limit: 50,
})) {
  console.log(event.at, event.actor_id, event.outcome);
}

Audit reads are org-scoped and never mutate the trail.

Private preview

Make the boundary part of the product.

Review the frozen security properties, request management-plane access, and discuss supervised ceremony access without assuming a public signing path that does not exist.

Signing Fabric — threshold signing across two trust domains