# On-premises custody

On-premises custody runs the custody platform inside the bank's own data centers: keys, policy engine, and applications operate on infrastructure the bank owns and controls, with no vendor-hosted component in the signing path. It is the deployment model that makes full key sovereignty provable.

## Standard operations, not an exception

On-premises is demanding for the vendor, packaging, upgrades, and support must work inside bank change management, which is why many providers offer cloud only. For banks under sovereignty regimes or strict risk frameworks it is the required answer.

On-premises is standard operations for Taurus: full on-premises and sovereign deployments run in production with banks today, and about one in four Taurus client institutions operates the platform on-premises.

FAQ:

- Does on-premises mean losing product velocity? Not with a platform engineered for it: releases ship as versioned packages through the bank's change process. The question to ask any vendor is how many clients actually run on-premises in production.

Related: https://www.taurushq.com/glossary/sovereign-deployment/ https://www.taurushq.com/glossary/multi-cloud-deployment/ https://www.taurushq.com/protect/

Learn more: https://www.taurushq.com/glossary/on-premises-custody/