Launchnodes / KMS Driver for Canton
Launchnodes / Canton key management

Canton Network KMS driver

Our externally audited KMS driver securely connects your Canton validator node to your KMS, enabling secure key management without exposing private keys.

Get KMS Speak to us
Runs on Azure and Google Cloud
Audited by Nullreturn
DevNet / TestNet Free
Canton guidance

To improve key security, participants should be configured to use an external Key Management System (KMS) to generate and store keys.

Canton documentation
01 / Key custody

Your keys belong outside the node.

Your Canton participant’s private keys are critical to its identity and network operations. An external KMS reduces the risk of key exposure.

Launchnodes’ externally audited KMS driver lets you manage those keys the way Canton’s documented deployment pattern recommends: created and used inside your cloud key manager, never handled directly by the node.

Launchnodes KMS driver Azure or Google Cloud
01Key created inside your cloud›
02Node asks for a signature›
03Key manager signs and returns it›
04Operation written to cloud logs›
02 / Why it matters

An auditable control.

/ 01

The pattern Canton recommends

External key management is the guidance for participants handling anything of value. This is the shortest route to meeting it on either cloud.

/ 02

Controls you already run

Your existing access model, network restrictions, retention rules and logging now cover your Canton keys too.

/ 03

Nothing to leak

The node authenticates with the identity your cloud already gives it. No secrets, certificates or connection strings sit anywhere in your node deployment.

/ 04

An audit trail your security team owns

Every key operation is recorded by your cloud provider, independent of the node. Evidence for auditors and regulators that does not rely on our software.

/ 05

Resilience

Rebuild a cluster, replace a node pool, restore from backup. Our KMS driver makes all of this easier.

03 / Licensing

Free to test. Licensed in production.

DevNet and TestNet
Free

Run the driver on DevNet and TestNet with no licence and no time limit. Same driver, same integrity checks, same support material.

  • Deploy into the cluster you already run
  • Full deployment guide from day one
  • Prove the control before you commit to it
MainNet
Commercial licence

Production use is licensed, with support from the team that built and maintains the driver. Talk to us about a licence for your deployment.

  • Supported production releases
  • Direct line to the engineers behind it
  • Help with your first MainNet rollout
04 / Speak to us

Move your keys off the node.

Tell us where you are with Canton and we will walk you through the deployment on your own cluster. Most teams have the driver running on TestNet the same day.

Corporate email required / Response within 2 working days
Read, Learn, Participate

Blog

Docs (Gitbook)

Canton Webinar

Cookie Policy

Privacy Policy

71-75 Shelton Street, Covent Garden, London, England WC2H 9JQ

Copyright © 2026 Launchnodes Limited – All rights reserved.

Validator Node End to End Set up and Support

Launchnodes’ Concierge Service provides end-to-end set up for an Ethereum validator node. This is ideal if you want to Solo Stake and have at least 32 Ethereum or multiples of 32 Ethereum in a Metamask wallet, or a wallet compatible with depositing ETH through the ETH launchpad.

The validator nodes can connect to a Launchnodes Beacon node or your own Beacon nodes. You can use this service to build your own customised staking architecture as a solo Ethereum stakers. On AWS or your own infrastructure.

  • A fully managed set up for Ethereum Nodes in your own infrastructure
  • Non-technical users can run an Ethereum node as Solo Stakers
  • Scope for engineers and more technical users to review and optimise Validator node set up
Run Nodes
Etherum
Validator

RPC Nodes

When performing mission critical or financially significant activity on the Ethereum blockchain, having your own RPC nodes ensures you can trust the data. Third party APIs are powerful tools making development at scale easy, but Blockchain-building requires data you can trust, where you own the source, and this is what RPC nodes provide.

Run Nodes
Etherum
Validator

Teku Beacon Node with Geth

A pre-synced Beacon node (using the Teku or Prysmatic client), with the Geth Client for Ethereum that allows you to connect to the beacon chain quickly and connect to Validator nodes. Beacon nodes can take 4-5 days to synchronise. Geth nodes can take 1 or 2 days.

  • Launchnodes Pre-synced Ethereum Beacon node with Geth is synchronised within 3-5 hours, saving 5+ days of synchronisation time
  • Solo Stake Ethereum
  • Run RPC nodes faster and more resiliently
  • Build effective backup infrastructure for staking at scale
Run Nodes
Etherum
Validator

Pre-synced Geth Node

Launchnodes provides a pre-synced Geth Node on AWS for staking ETH, native RPC nodes and other Layer 2 solutions. For the purposes of ETH staking Geth is an execution layer client.

A pre-synced Geth node is useful for any business or person staking ETH and can be used by all consensus layer clients. These consensus layer clients can run on public cloud or private data centre infrastructure. Making it easier and cheaper to stake ETH

All ETH Layer 2 solutions also require an Ethereum Geth node. This easy to run Geth node is pre-synced and can be deployed on public cloud or bare metal. By making Geth easy Launchnodes supports building in the Layer 2 eco-system.

  • A pre-synchronised Geth node to make staking ETH easier, faster and cheaper.
  • Suitable for those staking ETH using all consensus layer clients
  • Makes ETH staking easier on cloud or private data centre infrastructure
Run Nodes
Etherum
Geth

Teku Validator Node

Launchnodes provides an Always ON Teku Validator Node for Ethereum staking on mainnet or testnets

  • Use the power of public cloud or bare metal to build your Solo Staking infrastructure
  • Always running the latest version of the Prysmatic or Teku Validator client software for Solo Staking
  • Your Validator node is easy to set up and private. It is entirely managed in your own infrastructure and connected to a Launchnodes Beacon node with a Geth execution layer client as default.
  • Or connect to your own Prysmatic or Teku Beacon node with your own execution layer client on public cloud or bare metal.
Run Nodes
Etherum
Validator

Nodes for other PoS blockchains

We provide customers with white labelled nodes that can run on public cloud, our infrastructure or data centre infrastructure owned by you. Create your own independent staking infrastructure with your own nodes in your own AWS, GCP or Azure account, or running on your own infrastructure.

Launchnodes offers all the staking building blocks to allow any level of customisation for ETH staking and for alternative blockchains.

Run Nodes
Geth
Beacon
Validator

Prysm Validator Node

Run Validator nodes on your own infrastructure public cloud or bare metal and stake 32ETH per node.

Launchnodes allows you to choose between Prysm or Teku software to be a Solo Staker and run Validator nodes and stake ETH. The Ethereum nodes run on infrastructure you own, while mnemonics, passwords, or public or private keys are never shared with Launchnodes.

Run Nodes
Etherum
Validator

Pre-synced Prysm Beacon Node with Geth

Launchnodes provides a pre-configured Geth client (execution layer) running alongside a Teku client (consensus layer). This allows you to run Beacon nodes that can connect to validator nodes to start earning staking rewards or access blockchain data directly.

Participate and stake Ethereum as a Solo Staker. Use Launchnodes container based product to run Beacon nodes that have a connected Geth node to connect to the beacon chain. The Beacon Chain coordinates the network, and manages Proof of Stake for Ethereum.

Run Nodes
Etherum
Beacon

Registration

Blockchains of most interest:(Required)
Contact Us

Contact us to learn more

Do you currently own Ethereum to stake?

Find out

Find out

Contact Us