The short version: your coins don't depend on the company that sold you the device — provided the device followed the open standards. Most do. Some quietly don't, and the difference only becomes visible on the day the company is gone and you need to restore somewhere else.
I built the shelter out of timber, insulation board and a bag of straw. Two chambers, a divider, a roof.
If the shop I bought the timber from closes tomorrow, the shelter keeps working. If I need to rebuild it, I buy timber somewhere else. Nothing about the design depends on that particular shop continuing to exist, because the thing I built from was materials, not a proprietary kit.
If I'd bought a flat-pack shelter with custom fittings, a missing panel in 2029 would be a different conversation entirely.
That's the question nobody asks before buying a hardware wallet, and it's the one that decides whether you own bitcoin or own a relationship with a company.
1. The reassuring part, which is true
For a standards-compliant wallet, the company's survival is irrelevant to your coins.
Your seed is generated from a published word list (BIP39). The keys are derived in a published way (BIP32). The paths used to find your addresses are published conventions (BIP44/49/84/86, depending on address type). None of this is owned by anybody.
Which means: take your twelve or twenty-four words to a different manufacturer's device, or to open-source software on an offline machine, and the same wallet appears — same addresses, same balance. The device that generated it is a convenience, not a dependency.
Your bitcoin was never in the device. It's on the chain. The device holds keys derived from words you wrote down, and those words work anywhere.
That's the single most important thing to understand in this article, and it is genuinely reassuring.
2. Where the dependency sneaks back in
Four ways a setup becomes less portable than it looks:
Non-standard derivation paths. A handful of wallets have historically used paths that don't match the common conventions. Your seed restores fine, the balance shows zero, and you conclude you've lost everything — when actually the new wallet is looking in the wrong place. Recoverable, but only if you know the original path. Write the derivation path down with your seed. It costs one line.
Proprietary backup schemes. Some devices offer share-based backups that split your secret into several parts. These are often excellent engineering and they are usually not a BIP39 seed. If the scheme is specific to one manufacturer, your recovery depends on that manufacturer's implementation existing. Where such a device also offers a standard seed, taking it is the portable choice.
Multisig without the descriptor. A multisig wallet needs more than the seeds — it needs to know the quorum, the participating public keys and the script type. That's what a descriptor records. Lose it and you have all the keys and no idea how to assemble them. This is the quietest total loss in self-custody and it has nothing to do with the vendor at all.
Companion-app lock-in. The app that talks to your device is the company's. If it stops being maintained or dropped from an app store, you may need another route to your own device. Not fatal where the underlying standards hold, but it's the part people haven't thought through, and it's where the inconvenience lands first.
3. The test that settles it
Don't take anyone's word, including mine. Verify portability yourself, once:
Restore your seed into different software, offline. Take your words to an air-gapped machine running open-source wallet software from a different author, derive the addresses, and check that the first few match what your hardware wallet shows. If they do, you've proven your coins are reachable without that company.
Do it with a trivial amount first, and understand you're typing your seed into a computer — so do it on a machine that's offline and that you'll wipe afterwards, or on a spare device. If that makes you uncomfortable, generate a fresh test seed on the device and verify portability with that instead. Same proof, nothing at risk.
Record what you learn: the derivation path, the address type, the script type, and for multisig the full descriptor. That record is the difference between a seed and a recoverable wallet.
4. The uncomfortable half
Open standards don't make a company irrelevant — only its survival irrelevant. While it exists, it's still shipping the firmware your device runs, and a compromised or coerced update is a live risk that portability does nothing about. "I can restore elsewhere" protects you from the company vanishing. It doesn't protect you from the company being compromised while you're using it.
I've been reassuring, and the actual failure mode is more mundane than bankruptcy. Companies rarely vanish overnight. They get acquired, deprioritise a product line, drop support for older hardware, stop signing firmware for an old model. Your five-year-old device still works until the day an operating system update breaks the app and nobody's going to fix it. That's the realistic scenario, and the answer is the same: have you proven you can restore without them?
And the portability argument gets used to dismiss real differences. "It's all just BIP39 anyway" is true about recovery and false about everything else — secure element quality, screen trustworthiness, supply-chain practices, how the company behaved when it had a breach. Portability means you can leave. It doesn't mean the choice didn't matter while you were there.
One caution against over-correcting: none of this is an argument for avoiding hardware wallets in favour of paper or memory. The device is still the best available protection for the thing it protects. The point is to be able to walk away from the brand, not from the category.
Timber, insulation and a bag of straw. Build from materials you can buy anywhere, and the shop closing is somebody else's problem. 🐾⚡