Fystack

• Name: Fystack
• URL: https://fystack.io/
• Category: self-hosted custody-and-payments operator / wallet-governance workflow company / stablecoin treasury backend
• Summary: Fystack belongs in companies/ because the useful question is not only what MPC wallet or stablecoin wallet API exists? but which named operator ships the self-hosted stack, defines the split between Hyper wallets and MPC wallets, maintains the signing / indexing / deployment components, and packages sweep, approval, audit, and treasury workflow that payment processors, fintechs, and digital-asset platforms inherit inside their own cloud or compliance boundary? The old project note had already drifted into describing a company-run operating shell rather than a neutral protocol primitive.
• What it does:
  • Packages a self-hosted wallet-and-custody backend for stablecoin businesses that want the stack inside their own infrastructure rather than in vendor custody
  • Exposes MPC wallets for higher-security operational custody and Hyper wallets for high-volume deterministic user-wallet generation
  • Provides multi-chain deposit detection, address issuance, rescanning, and webhook-style transaction visibility across the supported wallet stack
  • Automates treasury sweeps and operator workflow through configurable thresholds, internal-wallet routing, approval groups, transaction policies, RBAC, and audit trails
  • Maintains the deployable backend components described in the public self-hosted materials, including Apex services, MPCIUM signing nodes, multichain indexers, rescanners, and local-portal workflow
  • Publishes the API, docs, deployment scripts, and open-source component map that customers will treat as the canonical starting point for operating the stack
• Key claims:
  • The homepage calls Fystack the wallet layer for stablecoin businesses, which is already company-shell language rather than a narrow protocol description
  • The same homepage says teams can deploy on their own infrastructure, keep keys in their own cloud, and avoid vendor custody or transaction-based revenue sharing, which makes the operator boundary analytically interesting because company dependence persists even without hosted key custody
  • The homepage also claims 20+ self-hosted instances are already running in production for payment processors, fintechs, and digital-asset platforms, which frames Fystack as a real operating shell rather than a lab demo
  • The docs homepage says developers can create and manage secure MPC wallets, authorize transactions, and integrate transaction policies and multi-approval flows through Fystack’s API, showing that approval workflow and policy authoring live inside the company-packaged stack
  • The wallet docs split the product into Hyper wallets for high-volume derived-wallet issuance and MPC wallets for institutional-grade hot-wallet and custody use cases, with automatic sweep-task parameters built into wallet creation; that packaging choice is part of the real control surface
  • The self-hosted scripts repository describes Fystack as a self-hosted custody stack for crypto and stablecoin payments with threshold signing, multichain deposit detection across 10+ chains, automated sweeps, approval controls, audit trails, RBAC, and a developer-first SDK
  • The same public deployment materials expose concrete backend components such as Apex, MPCIUM nodes, multichain indexing, rescanners, audit logging, and a local UI, reinforcing that the practical dependency is a company-authored operations stack rather than a single signing library
• Whitepaper: No separate company whitepaper is the point here. The strongest primary materials are the official homepage, docs, wallet docs, GitHub organization, and self-hosted deployment repository already captured in ../whitepapers/fystack-primary-sources-2026-05-03.md.
• Sources:
  • https://fystack.io/
  • https://docs.fystack.io/
  • https://docs.fystack.io/wallets
  • https://github.com/fystack
  • https://github.com/fystack/fystack-selfhost-scripts
  • ../whitepapers/fystack-primary-sources-2026-05-03.md

Internal linkages

• Product-layer alias: fystack.
• Useful adjacent custody-and-wallet-ops operator reads: liminal, dfns, and safeheron.
• Useful stablecoin-workflow contrast: dakota and chain.

Protocol / company boundary

• Keep fystack only as the alias preserved for legacy links.
• Keep this note on Fystack as the named operator that packages the self-hosted stack, defines wallet-model choices, ships deployment materials, and publishes the approval / sweep / audit workflow customers inherit.
• That split matters because there is no especially useful standalone Fystack protocol layer doing separate analytical work from the company-run custody-and-payments shell.

Control surface

• Practical authority sits in the company-authored deployment path: which components are canonical, how Hyper wallets and MPC wallets are framed, how sweeps and approvals are normalized, what multichain indexing and rescanning path customers inherit, and which APIs or scripts remain the supported way to operate the stack.

• Self-hosted does not dissolve the entity boundary here. Customers may hold infrastructure and keys, but they still inherit Fystack’s docs, repo stewardship, backend decomposition, wallet semantics, and upgrade / integration path.

• Read the durable risk as who packages and defines the custody-and-payments operating shell?, not only as who directly holds the keys?

• Last reviewed: 2026-08-13 UTC