Cake Labs

• Name: Cake Labs
• URL: https://cakelabs.com/
• Category: wallet-software company / privacy-wallet operator / partner-rail and distribution boundary
• Tags: bitcoin-ecosystem monero-ecosystem
• Summary: Cake Labs belongs in companies/ because the practical authority is not only a non-custodial wallet exists; it is that a named operator ships Cake Wallet and Monero.com, controls release and documentation workflow, decides which partner rails feel native inside the app, and defines the node, privacy, hardware-wallet, and support defaults users inherit. The project note explains the wallet surface; this entity note is for the company boundary around software distribution, partner packaging, companion-service routing, and the trust pipeline users actually depend on day to day.
• What it does:
  • Builds and distributes Cake Wallet as a non-custodial multi-currency wallet across mobile and desktop platforms
  • Operates the broader Cake Labs product shell around Cake Wallet, Monero.com, and adjacent payment and marketplace surfaces presented through the company site
  • Maintains the official documentation, support path, and public open-source repositories that define setup, recovery, privacy guidance, hardware-wallet workflow, and release provenance expectations
  • Packages built-in exchange, fiat buy/sell, Cake Pay, and Trocador-linked payment and spending rails into the default wallet experience
  • Shapes the privacy and connectivity posture users inherit through Tor guidance, custom-node support, and the surrounding documentation and product defaults
• Key claims:
  • The Cake Labs site says Cake Wallet has operated since January 2018, serves more than 250,000 users, and sits beside Monero.com as part of the same company-run product surface
  • The Cake Wallet docs say the product is open source and highlight intuitive privacy tools, cross-chain swaps, buying and selling crypto, and hardware-wallet support, which makes the company-run distribution and documentation boundary a real part of the trust story
  • The public Cake Wallet repository and docs expose concrete user-inherited control points including custom nodes or servers, Tor-only connectivity, exchange flows, donation links, invoices, and release-signing verification across GitHub, Accrescent, and F-Droid distribution paths
  • The docs and repo also show that hardware-wallet workflow, node customization, support routing, and partner integrations are not incidental extras; they are part of the first-party operating shell Cake Labs maintains
  • The company site frames Monero.com as a Cake Wallet fork and related resource surface, which makes the company boundary analytically useful because distribution, privacy posture, and partner packaging span more than one branded app surface
• Whitepaper: No separate company whitepaper is the point here. The strongest primary materials are the Cake Labs site, Cake Wallet docs, and the public Cake Wallet repository already captured in ../whitepapers/cake-wallet-primary-sources-2026-05-01.md.
• Sources:
  • https://cakelabs.com/
  • https://cakewallet.com/
  • https://docs.cakewallet.com/
  • https://docs.cakewallet.com/home.md?ask=What%20features%20does%20Cake%20Wallet%20documentation%20highlight%20around%20privacy%20tools%2C%20hardware%20wallet%20support%2C%20node%20customization%2C%20and%20supported%20platforms%3F
  • https://docs.cakewallet.com/home.md?ask=Does%20Cake%20Wallet%20documentation%20mention%20Lightning%20support%20or%20other%20payment-related%20features%3F
  • https://github.com/cake-tech/cake_wallet
  • ../whitepapers/cake-wallet-primary-sources-2026-05-01.md

Internal linkages

• Product-layer note: cake-wallet.
• Useful wallet-company contrasts: foundation-devices, ledger, and casa.
• Keep the stronger wallet-ops product comparisons on bluewallet and sparrow-wallet.

Protocol / company boundary

• Keep projects/cake-wallet focused on the wallet product surface: node choice, Tor posture, hardware-wallet support, partner rails, and the broad self-custodial software stack.
• Keep this entity note focused on Cake Labs as the named operator that ships releases, maintains docs and support, packages exchange and spend partners into the default flow, and controls the broader distribution shell around Cake Wallet and Monero.com.
• That split matters because the useful question is not only what can Cake Wallet do? but also which organization controls the release, routing, and trust pipeline around that wallet experience?

Control surface

• Practical authority sits in release and signing workflow, documentation and support routing, node and privacy defaults, hardware-wallet guidance, app-distribution channels, and the exchange / spend / marketplace partners Cake Labs chooses to make feel native.

• Even when the wallet is non-custodial, users still depend on Cake Labs for the software supply path, privacy guidance, packaged integrations, and the operational defaults that shape how self-custody is actually practiced.

• Read the durable risk here as who controls the wallet-operating shell and partner rails around the user's keys?, not only as is the wallet non-custodial?

• Last reviewed: 2026-08-06 UTC