Theya

• Name: Theya
• URL: https://theya.us/
• Category: collaborative bitcoin custody operator / multisig vault and recovery company / custody-workflow infrastructure company
• Tags: bitcoin-ecosystem
• Summary: Theya belongs in companies/, not only projects/, because the useful question is who operates the collaborative-custody workflow: who may hold one key in a business setup, who runs delegated co-signing and key-agent dashboards, who defines recovery and inheritance procedure, and who packages the wallet-partner API that turns third-party wallets into Theya-shaped vaults. The practical authority is not a neutral Bitcoin multisig protocol. It is a named company coordinating multi-party custody, recovery choreography, partner integrations, and advisor/business operating paths.
• What it does:
  • Offers Bitcoin vaults for individuals, advisors, and businesses, centered on multi-key and multi-party custody flows rather than a single-key wallet model
  • Provides 2-of-3 multisig vaults for individuals, with delegated co-signing plus both sovereign and assisted recovery paths
  • Lets businesses choose whether all keys remain within the organization or one key is held by Theya, while supporting team onboarding, co-signing, and employee rotation
  • Markets an API and custody engine for wallet and fintech partners so they can turn end-user wallets into multisig vaults with embedded recovery options
  • Provides a dashboard-oriented product for key agents and security providers to co-sign transactions, manage assigned vaults, and keep logged separation of roles across many clients
  • Maintains a help center organized around hardware-wallet integration, fund recovery, inheritance planning, advisor workflows, and business operations
• Key claims:
  • The homepage says Theya offers secure, scalable Bitcoin custody infrastructure for corporations, funds, advisors, SMBs, families, startups, and exchanges
  • The homepage and individuals page say Theya uses a modular vault architecture with single- or multi-party access, 2-of-3 multisig vaults, delegated co-signing, and sovereign and assisted recovery options
  • The individuals page says Your funds remain safe even if you lose a key or Theya goes down, which is analytically useful because survivability and recovery are core to the operating model rather than side features
  • The business page says a self-custodial Business Vault can be configured with all keys held by the business or with one key held by Theya, and that teams can onboard, co-sign transactions, and rotate employees
  • The wallet-partner page says partners can integrate Theya's API to turn each wallet into a multi-sig vault, with one key on the user’s device, another as a secure cloud backup, and a third held by the service for recovery, while supporting 2-of-3 or 3-of-5 setups
  • The key-agents page says Theya gives key agents and security providers a centralized dashboard to manage vaults, receive signing requests, and keep all actions logged for audit and compliance
  • The help center groups articles into Hardware Wallets & Integration, Fund Recovery, Inheritance Planning, Theya for Advisors, and Theya for Business, reinforcing that the company ships a broader custody-and-operations layer rather than a thin wallet UI
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest current sources of truth were the official homepage, product and solution pages, and help-center taxonomy; see ../whitepapers/theya-primary-sources-2026-05-01.md.
• Sources:
  • https://theya.us/
  • https://theya.us/products/individuals
  • https://theya.us/products/business
  • https://theya.us/solutions/collaborative-custody-as-a-service/wallets
  • https://theya.us/solutions/collaborative-custody-as-a-service/key-agents
  • https://help.theya.us/en/
  • https://research.theya.us/

Internal linkages

• Product-layer alias: theya.
• Strongest adjacent custody-workflow reads: unchained, casa, and bitkey.
• Reusable lens: when a self-custody product still keeps recovery choreography, delegated co-signing, and partner API defaults inside one named operator, the company boundary often matters more than the wallet label.

Protocol / company boundary

• theya is kept only as an alias for legacy project-layer links.
• The durable control surface lives here instead: key-holding options, delegated co-signing, advisor and business workflow, key-agent dashboards, partner API packaging, inheritance assistance, and recovery procedure all sit with Theya as an operating company.
• That split matters because the interesting risk is not whether multisig exists on Bitcoin. It is how much of the day-to-day custody, recovery, and support path is shaped by one named vendor.

Control surface

• Practical leverage sits in assisted-recovery procedure, delegated co-signing workflow, business-vault key-topology choices, partner API defaults, key-agent dashboard access, inheritance and advisor workflow, and the support/documentation shell users are expected to trust during stressful moments.

• Theya does not need to be a unilateral custodian for the entity boundary to matter. If Theya can hold a key in some deployments, mediate recovery, structure partner vault topology, and define the easiest business or advisor operating path, then the company remains part of the live security model.

• Read Theya as a collaborative-custody and recovery operator first, and as a wallet-branded product second.

• Last reviewed: 2026-08-07 UTC