Openfort

• Name: Openfort
• URL: https://www.openfort.io/
• Category: hosted wallet-control plane / embedded wallets / backend signing / account-abstraction middleware
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Openfort is the branded product shell around a company-run wallet and signing stack. OpenSigner is the narrow technical substrate worth isolating; the practical dependency for most teams is the named Openfort operator behind embedded wallets, backend signing, sponsorship, recovery, and session handling. Use openfort when the real question is dashboard authority, policy defaults, credential issuance, or hosted workflow lock-in.
• What it does:
  • Provides embedded-wallet flows with auth, recovery, and user-wallet management
  • Offers backend-wallet and server-signing paths for app-controlled transaction handling
  • Runs bundler, paymaster, sponsorship, and related account-abstraction infrastructure for production use
  • Exposes policy, webhook, and project-configuration surfaces for live wallet operations
  • Supports both EVM and Solana in the current product/docs surface
• Key claims:
  • Openfort sells one stack for embedded wallets, backend wallets, account abstraction, and transaction automation
  • Docs describe OpenSigner as an MIT-licensed, self-hostable signing layer under the managed platform
  • Official materials emphasize lower lock-in and less operational overhead around auth, signing, sponsorship, and wallet lifecycle management
  • The commercial surface is tied to wallet and signing operations, not just generic developer SaaS seats
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Openfort’s official site, docs portal, pricing page, and SDK documentation; see ../whitepapers/openfort-primary-sources-2026-04-23.md.
• Sources:
  • https://www.openfort.io/
  • https://www.openfort.io/docs
  • https://www.openfort.io/docs/llms.txt
  • https://www.openfort.io/docs/overview/why-openfort
  • https://www.openfort.io/docs/products/server
  • https://www.openfort.io/docs/products/infrastructure
  • https://www.openfort.io/pricing.md
  • https://raw.githubusercontent.com/openfort-xyz/openfort-js/main/README.md

Internal linkages

• Primary operator / entity note: openfort.
• Keep the upward reads on the stronger hosted wallet-control planes: turnkey and privy.

Protocol / company boundary

• Keep projects/openfort on the product surface: embedded wallets, backend wallets, sponsorship, and the OpenSigner escape hatch inside the broader stack.
• Use openfort when the practical question is who issues credentials, runs the dashboard and hosted endpoints, defines policy workflow, packages recovery, or chooses which chains and transaction paths are easiest to operate.
• That split matters because Openfort is not just a neutral account-abstraction helper; the sticky dependency is a named company-run wallet-control plane.

Control surface

• The leverage is in backend signing, policy defaults, dashboard and credential workflow, sponsorship rules, telemetry visibility, and recovery or session handling.

• Ignore the non-custodial label for a moment and look at the live dependency path. If the app still needs Openfort for signing policy, sponsorship, recovery, environment management, or session handling, the control surface is still there.

• OpenSigner is the narrow escape hatch. The rest is ordinary hosted wallet operations.

• Read the note as the product shell; read openfort for the named operator boundary underneath it.

• Last reviewed: 2026-08-09 UTC