Trezor Bridge

The Secure Gateway to Your Hardware Wallet® — connect apps, dApps, and services while keeping keys on-device.

One bridge. Many apps. Zero key exposure.

Trezor Bridge is a lightweight, privacy-first connector that places your hardware wallet at the heart of secure Web3 interactions. Sign transactions, authenticate to services, and manage sessions without exposing secrets to browsers or servers.

Hardware‑first signing
Private keys remain inside the Trezor device; Bridge handles transport and session management.
Privacy by design
Minimal telemetry, encrypted session metadata, and explicit consent for every connection.
Multi‑chain support
EVM, Solana, Cosmos and custom chains via plugin architecture.

How Trezor Bridge works — simple flow

Bridge acts as an intermediary between your Trezor hardware and client applications. It exposes a secure local API (WebSocket/REST/WalletConnect) and performs transport negotiations while enforcing attestation, user prompts, and scoped sessions.

  1. Pair — Connect your Trezor device over USB or Bluetooth and pair it with the Bridge app.
  2. Authorize — Applications request a scoped session; you approve the request on-device and in Bridge.
  3. Sign — Signing occurs inside the secure element; Bridge returns only signed payloads to the requesting app.

Quick setup (Windows / macOS / Linux)

1. Download and install the Trezor Bridge app
2. Connect your Trezor device via USB (or pair via BLE)
3. Open the Bridge app and follow the pairing instructions
4. Authorize a dApp when it requests a session

User-focused features

  • Session manager: View active sessions, set expiry times, and revoke permissions instantly.
  • Per‑dApp policies: Define transaction limits, permitted chains, and metadata visibility for each origin.
  • On‑device prompts: Every sensitive action requires physical confirmation on your Trezor device.

Security — hardware‑backed, auditable, transparent

Security is the core of Bridge. It ensures private keys are never exported and that every signing request is explicit, auditable, and verifiable through attestation and on‑device confirmation.

Secure element storage
Private keys live in the device's secure element — non-exportable and tamper‑resistant.
Mutual attestation
Bridge and the Trezor device verify each other's identity to prevent forged clients or man‑in‑the‑middle attacks.
Audit logs
Encrypted, local logs for session audits — exportable for enterprise compliance.

Privacy controls

Bridge minimizes telemetry and stores only the metadata necessary for UX and auditing. Users control diagnostic sharing and can opt out of all non‑essential telemetry.

Attestation & verification

Developers and power users can verify device and Bridge attestation tokens to ensure they're talking to genuine hardware and Bridge instances before trusting signed payloads.

Developer notes — integrate securely

Bridge simplifies integration while enforcing security. Use the SDK to request scoped sessions, present clear human‑readable prompts to users, and validate attestation tokens on your server when high‑assurance is required.

Example (JavaScript)

import { BridgeClient } from 'trezor-bridge-sdk'

const bridge = new BridgeClient()
await bridge.connect()
const session = await bridge.requestSession({ appName: 'MyDApp', scopes: ['sign:eth','accounts'] })
// open the Ethereum app on device
const signed = await session.signTransaction({ chain: 'ethereum', rawTx })
console.log('Signed tx:', signed)

Best practices for developers

Enterprise & deployment

Businesses can deploy Bridge with BYOK policies, HSM bridging, and on‑prem installations for maximum control. Integration with SSO, role‑based admin controls, and compliance exports make Bridge suitable for regulated environments.

On‑prem & cloud options

Choose cloud‑hosted Bridge for low friction or on‑prem for strict data residency and compliance requirements. Enterprise plans include SLAs, dedicated support, and training.

Pricing & plans

Starter: Free for personal use — basic session management and device pairing. Pro: Monthly subscription for teams, advanced policies, and analytics. Enterprise: Custom — on‑prem deployment, SLAs, and training.
Contact sales for volume discounts, integration packages, and professional services for migration and onboarding.

FAQ

Which devices are supported?

Most Trezor models are supported — check the compatibility matrix in the docs for per‑model limitations and special instructions.

Can I export private keys?

No — Bridge never allows private keys to leave the hardware device. You can export public keys and signed payloads only.

Is Bridge open-source?

Bridge components and SDKs are open-source where possible; consult the repository for licenses and contribution guidelines.

Trezor Bridge — The Secure Gateway to Your Hardware Wallet®

Trezor Bridge

The Secure Gateway to Your Hardware Wallet® — connect apps, dApps, and services while keeping keys on-device.

One bridge. Many apps. Zero key exposure.

Trezor Bridge is a lightweight, privacy-first connector that places your hardware wallet at the heart of secure Web3 interactions. Sign transactions, authenticate to services, and manage sessions without exposing secrets to browsers or servers.

Hardware‑first signing
Private keys remain inside the Trezor device; Bridge handles transport and session management.
Privacy by design
Minimal telemetry, encrypted session metadata, and explicit consent for every connection.
Multi‑chain support
EVM, Solana, Cosmos and custom chains via plugin architecture.

How Trezor Bridge works — simple flow

Bridge acts as an intermediary between your Trezor hardware and client applications. It exposes a secure local API (WebSocket/REST/WalletConnect) and performs transport negotiations while enforcing attestation, user prompts, and scoped sessions.

  1. Pair — Connect your Trezor device over USB or Bluetooth and pair it with the Bridge app.
  2. Authorize — Applications request a scoped session; you approve the request on-device and in Bridge.
  3. Sign — Signing occurs inside the secure element; Bridge returns only signed payloads to the requesting app.

Quick setup (Windows / macOS / Linux)

1. Download and install the Trezor Bridge app
2. Connect your Trezor device via USB (or pair via BLE)
3. Open the Bridge app and follow the pairing instructions
4. Authorize a dApp when it requests a session

User-focused features

  • Session manager: View active sessions, set expiry times, and revoke permissions instantly.
  • Per‑dApp policies: Define transaction limits, permitted chains, and metadata visibility for each origin.
  • On‑device prompts: Every sensitive action requires physical confirmation on your Trezor device.

Security — hardware‑backed, auditable, transparent

Security is the core of Bridge. It ensures private keys are never exported and that every signing request is explicit, auditable, and verifiable through attestation and on‑device confirmation.

Secure element storage
Private keys live in the device's secure element — non-exportable and tamper‑resistant.
Mutual attestation
Bridge and the Trezor device verify each other's identity to prevent forged clients or man‑in‑the‑middle attacks.
Audit logs
Encrypted, local logs for session audits — exportable for enterprise compliance.

Privacy controls

Bridge minimizes telemetry and stores only the metadata necessary for UX and auditing. Users control diagnostic sharing and can opt out of all non‑essential telemetry.

Attestation & verification

Developers and power users can verify device and Bridge attestation tokens to ensure they're talking to genuine hardware and Bridge instances before trusting signed payloads.

Developer notes — integrate securely

Bridge simplifies integration while enforcing security. Use the SDK to request scoped sessions, present clear human‑readable prompts to users, and validate attestation tokens on your server when high‑assurance is required.

Example (JavaScript)

import { BridgeClient } from 'trezor-bridge-sdk'

const bridge = new BridgeClient()
await bridge.connect()
const session = await bridge.requestSession({ appName: 'MyDApp', scopes: ['sign:eth','accounts'] })
// open the Ethereum app on device
const signed = await session.signTransaction({ chain: 'ethereum', rawTx })
console.log('Signed tx:', signed)

Best practices for developers

Enterprise & deployment

Businesses can deploy Bridge with BYOK policies, HSM bridging, and on‑prem installations for maximum control. Integration with SSO, role‑based admin controls, and compliance exports make Bridge suitable for regulated environments.

On‑prem & cloud options

Choose cloud‑hosted Bridge for low friction or on‑prem for strict data residency and compliance requirements. Enterprise plans include SLAs, dedicated support, and training.

Pricing & plans

Starter: Free for personal use — basic session management and device pairing. Pro: Monthly subscription for teams, advanced policies, and analytics. Enterprise: Custom — on‑prem deployment, SLAs, and training.
Contact sales for volume discounts, integration packages, and professional services for migration and onboarding.

FAQ

Which devices are supported?

Most Trezor models are supported — check the compatibility matrix in the docs for per‑model limitations and special instructions.

Can I export private keys?

No — Bridge never allows private keys to leave the hardware device. You can export public keys and signed payloads only.

Is Bridge open-source?

Bridge components and SDKs are open-source where possible; consult the repository for licenses and contribution guidelines.

Trezor Bridge — The Secure Gateway to Your Hardware Wallet®

Trezor Bridge

The Secure Gateway to Your Hardware Wallet® — connect apps, dApps, and services while keeping keys on-device.

One bridge. Many apps. Zero key exposure.

Trezor Bridge is a lightweight, privacy-first connector that places your hardware wallet at the heart of secure Web3 interactions. Sign transactions, authenticate to services, and manage sessions without exposing secrets to browsers or servers.

Hardware‑first signing
Private keys remain inside the Trezor device; Bridge handles transport and session management.
Privacy by design
Minimal telemetry, encrypted session metadata, and explicit consent for every connection.
Multi‑chain support
EVM, Solana, Cosmos and custom chains via plugin architecture.

How Trezor Bridge works — simple flow

Bridge acts as an intermediary between your Trezor hardware and client applications. It exposes a secure local API (WebSocket/REST/WalletConnect) and performs transport negotiations while enforcing attestation, user prompts, and scoped sessions.

  1. Pair — Connect your Trezor device over USB or Bluetooth and pair it with the Bridge app.
  2. Authorize — Applications request a scoped session; you approve the request on-device and in Bridge.
  3. Sign — Signing occurs inside the secure element; Bridge returns only signed payloads to the requesting app.

Quick setup (Windows / macOS / Linux)

1. Download and install the Trezor Bridge app
2. Connect your Trezor device via USB (or pair via BLE)
3. Open the Bridge app and follow the pairing instructions
4. Authorize a dApp when it requests a session

User-focused features

  • Session manager: View active sessions, set expiry times, and revoke permissions instantly.
  • Per‑dApp policies: Define transaction limits, permitted chains, and metadata visibility for each origin.
  • On‑device prompts: Every sensitive action requires physical confirmation on your Trezor device.

Security — hardware‑backed, auditable, transparent

Security is the core of Bridge. It ensures private keys are never exported and that every signing request is explicit, auditable, and verifiable through attestation and on‑device confirmation.

Secure element storage
Private keys live in the device's secure element — non-exportable and tamper‑resistant.
Mutual attestation
Bridge and the Trezor device verify each other's identity to prevent forged clients or man‑in‑the‑middle attacks.
Audit logs
Encrypted, local logs for session audits — exportable for enterprise compliance.

Privacy controls

Bridge minimizes telemetry and stores only the metadata necessary for UX and auditing. Users control diagnostic sharing and can opt out of all non‑essential telemetry.

Attestation & verification

Developers and power users can verify device and Bridge attestation tokens to ensure they're talking to genuine hardware and Bridge instances before trusting signed payloads.

Developer notes — integrate securely

Bridge simplifies integration while enforcing security. Use the SDK to request scoped sessions, present clear human‑readable prompts to users, and validate attestation tokens on your server when high‑assurance is required.

Example (JavaScript)

import { BridgeClient } from 'trezor-bridge-sdk'

const bridge = new BridgeClient()
await bridge.connect()
const session = await bridge.requestSession({ appName: 'MyDApp', scopes: ['sign:eth','accounts'] })
// open the Ethereum app on device
const signed = await session.signTransaction({ chain: 'ethereum', rawTx })
console.log('Signed tx:', signed)

Best practices for developers

Enterprise & deployment

Businesses can deploy Bridge with BYOK policies, HSM bridging, and on‑prem installations for maximum control. Integration with SSO, role‑based admin controls, and compliance exports make Bridge suitable for regulated environments.

On‑prem & cloud options

Choose cloud‑hosted Bridge for low friction or on‑prem for strict data residency and compliance requirements. Enterprise plans include SLAs, dedicated support, and training.

Pricing & plans

Starter: Free for personal use — basic session management and device pairing. Pro: Monthly subscription for teams, advanced policies, and analytics. Enterprise: Custom — on‑prem deployment, SLAs, and training.
Contact sales for volume discounts, integration packages, and professional services for migration and onboarding.

FAQ

Which devices are supported?

Most Trezor models are supported — check the compatibility matrix in the docs for per‑model limitations and special instructions.

Can I export private keys?

No — Bridge never allows private keys to leave the hardware device. You can export public keys and signed payloads only.

Is Bridge open-source?

Bridge components and SDKs are open-source where possible; consult the repository for licenses and contribution guidelines.