GridPlus

• Name: GridPlus
• URL: https://gridplus.io/
• Category: hardware-wallet infrastructure / signing and wallet-routing control plane / SafeCard-based self-custody architecture / self-hostable device connectivity
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: GridPlus is a real signer stack, but not a category anchor. Keep it for the combined signer-plus-routing surface: Lattice1, SafeCards, Lattice Manager, and the self-hostable Lattice Connect path. That is enough to make it a useful hardware-wallet note without pretending it defines the branch.
• What it does:
  • Builds the Lattice1 hardware wallet for signing digital-asset transactions with a large secure display and human-readable transaction rendering
  • Uses SafeCards as PIN-protected wallet / backup media that let one Lattice1 manage multiple hardware-backed wallets
  • Operates the Lattice Manager web tool for wallet management, BTC send/receive flows, address tagging, wallet exploration, and app-connection management
  • Integrates the Lattice1 with external wallet apps including MetaMask, Rabby, Frame, NuFi, MyCrypto, Ambire, and others according to the official docs
  • Publishes SDKs, a device simulator, and Lattice Connect V2, an open-source self-managed messaging proxy that lets users replace GridPlus cloud routing with their own local endpoint
• Key claims:
  • The Lattice1 introduction page says the device is a “digital asset management hub” and emphasizes user experience plus security rather than cold storage alone, which is important to how the company positions the product
  • The docs say SafeCards let one device manage unlimited hardware-backed wallets, which is the clearest differentiator versus single-seed hardware-wallet models
  • GridPlus’s security docs say the device separates a General Compute Environment from a Secure Compute Environment and uses a mailbox / multiplexer / doorbell design so private keys remain inaccessible from the internet even though the device is network-connected
  • The anti-tamper mesh, SCE-drawn screen, and direct secure-display input path are high-signal details because they show GridPlus treating transaction-readability and physical security as core architecture rather than marketing garnish
  • The Lattice Manager docs are especially useful for categorization because they expose address tags, wallet exploration, BTC wallet management, and custom message-routing configuration, which makes GridPlus look like a wallet-control-plane provider in addition to a hardware vendor
  • The Lattice Connect V2 repository is notable because it explicitly lets users disconnect app-to-device routing from GridPlus cloud infrastructure and self-host the proxy on their own network, which is unusual and important for privacy / sovereignty analysis
  • The public GitHub organization also exposes the gridplus-sdk, lattice-simulator, lattice-manager, and related repos, giving the project a broader developer-facing footprint than the homepage alone suggests
• Whitepaper: No canonical GridPlus whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official Lattice1 and Lattice Manager docs plus the public SDK and routing repositories; see ../whitepapers/gridplus-primary-sources-2026-05-01.md.
• Sources:
  • https://gridplus.io/
  • https://docs.gridplus.io/
  • https://docs.gridplus.io/lattice1/lattice1-introduction
  • https://docs.gridplus.io/lattice1/security-features
  • https://docs.gridplus.io/setup/lattice1
  • https://docs.gridplus.io/apps-and-integrations/lattice-manager
  • https://github.com/GridPlus
  • https://github.com/GridPlus/gridplus-sdk
  • https://github.com/GridPlus/lattice-connect-v2

Internal linkages

• Strongest comparison points: coinkite, foundation-devices, and bitkey.

• Reusable lens: GridPlus is worth keeping when a hardware wallet is really a signer plus routing layer, companion software, and backup media. Stronger Bitcoin self-custody notes still carry more weight.

• Last reviewed: 2026-05-29 UTC