Keep Your Funds
Safe From Here On
Safeheron offers enterprise-grade digital asset self-custody services and MPC privatization solutions, ensuring the highest level of security for your assets.
Secure, Efficient, Scalable
Top-tier, battle-tested security solutions for 260+ institutions since 2021.
RAISED
PEAK AUC
SECURELY TRANSFERRED
Committed to the highest standards of security and compliance.
Certified and Insured
Partner with Top Security and Compliance Partners
Compliance in Action
Explore Our Trust Center
MPC Self-Custody
Enterprise-grade digital asset self-custody services
Eliminate single-point failures to manage digital assets
- MPC and TEE technologies protect your digital assets with the highest level of security.
- Manage wallets and transfer funds on multiple terminals, including the mobile App and Web Console.
- Policy Engine flexibly controls access authorization.
- Off-chain multisignature enhances approval privacy and significantly reduces on-chain transaction fees.
Interact with dApps under multi-party control
- Supports all public EVM-compatible blockchains and DeFi protocols.
- Policy Engine meticulously delegates transaction permissions.
- Real-time contract monitoring and phishing detection safeguard every transaction.
- Customize RPC nodes for diverse business scenarios.
- Collaboratively manage smart contract owner’s permissions to reduce single-point risk in critical operations.
Enterprise-grade digital asset self-custody services
- Seamlessly create and manage millions of MPC wallets with APIs.
- Automatic gas fuelling and sweeping significantly improve integration efficiency and accelerate your business success.
- Web3 API securely controls the entire lifecycle of smart contracts.
- API Co-Signer automates transaction approval and signing.
- MPC and TEE technologies provide multi-layer security to eliminate single-point-of-failure risk for private keys.
MPC Node Suite
White-label MPC privatization solutions
Flexibly build MPC wallets for seamless integration into your applications
- Fully privatized, with hardware-level data security and privacy protection under your control.
- A secure, universal, and cross-platform MPC-TSS key management solution.
- Support diverse business scenarios to accelerate your success.
Safest software is
open source
Safeheron independently developed MPC algorithms and is now the world's first company to open-source the mainstream MPC-TSS algorithm in C++.
Why choose us?
100% control over assets
3-of-3 MPC-TSS key management eliminates the single-point failures with full asset control.
Open-source algorithms
Safeheron open-sourced the world's first MPC-TSS algorithm library implemented in C++.
Maximum security
Safeheron’s multi-layer security defenses against state-level attacks.
Certified and insured
Safeheron is certified with ISO/IEC 27001:2022 and SOC 2 and is insured by Lockton.
Extensive features
Safeheron offers one-stop management for Web3, DeFi, NFTs, and smart contracts.
Governance and policy
TEE Policy Engine customizes multi-dimensional policies and approval workflows.
Technical support
Robust technical support encompasses use cases, solutions, technologies, and security expertise.
Diversified solutions
Battle-tested SaaS services and MPC privatization solutions.
Hear from our customers
Our partnership with Safeheron has unlocked new possibilities in digital payment through advanced MPC and TEE technology. This collaboration strengthens our security, scalability, and compliance, enabling us to meet the highest standards. With Safeheron’s powerful MPC self-custody solution, dtcpay continues to provide our users with institutional-grade security, seamless transactions, and an intuitive user experience, reinforcing our commitment to advancing the future of digital payments.
As a trusted financial service provider, we have strict standards when choosing our security infrastructure provider. Safeheron turns out to be a great match. Its MPC self-custody solution eliminates private key risks while providing enterprise-grade security with ease of use. With Safeheron’s sophisticated technology, we are confident to provide our customers with a reliable and secure digital payment experience.
The Safeheron team has in-depth expertise and extensive practical experience in blockchain security. With a highly robust security mechanism, a comprehensive permission management system, and an excellent user experience, Safeheron has provided strong support for our institutional trading services in the Asia region. We look forward to further deepening our collaboration.
UXUY has developed a highly secure key management service powered by Safeheron's MPC technology. In today's challenging cyber environment where digital assets face numerous security threats, Safeheron's mature solution provides us with robust technical assurance. Through this innovative MPC solution, we have effectively reduced the risks of private key leakage and asset theft, delivering users a seamless experience that combines both security and convenience.
With Safeheron’s hardcore MPC technology, we ensure the highest level of security for our clients' crypto funds within our crypto-to-fiat feature. In addition, Safeheron's customer support exemplifies excellence, promptly resolving issues to maintain our uninterrupted operations.
Partnering with Safeheron has been transformative for AlphaYield. Their MPC + TEE platform delivers the enterprise-grade security and operational efficiency we need to execute large institutional trades with complete confidence, while their exceptional team consistently goes above and beyond to support our evolving needs.
Security, flexibility, and compliance — all solved on one platform. Since integrating Safeheron, our business volume has tripled.
Latest Updates from Safeheron
How to Move Funds Safely Between Hot and Cold Wallets
How do you move funds safely between hot and cold wallets? The key is to treat the two directions differently. Moving funds from a hot wallet to a cold wallet is low risk and can run automatically under rules, while topping up a hot wallet from a cold wallet should require multi-party approval and capped amounts. In both directions, destinations must be the business’s own wallets, locked by an address whitelist, and every movement should be fully recorded for reconciliation. When Do Funds Need to Move Between Hot and Cold Wallets? The most common trigger is the balance. Based on how they split funds between hot and cold wallets, businesses set upper and lower limits for the hot wallet: when it goes above the upper limit, the excess moves to the cold wallet, and when it falls below the lower limit, the cold wallet tops it up. For exchanges, funds swept from deposit addresses keep pushing the hot wallet balance up and need to be moved to cold storage regularly. The other trigger is events: before expected large withdrawals, sharp market moves, or settlement dates, the hot wallet is topped up in advance; when a security incident is detected, funds in the hot wallet are moved to cold storage as quickly as possible to reduce exposure. Do Transfers From a […]
How Should Businesses Split Funds Between Hot and Cold Wallets?
How should businesses split funds between hot and cold wallets? There is no fixed ratio that suits every business. The principle is that a hot wallet should only hold enough to cover withdrawals and payments for a short period, while most assets stay in cold wallets or more tightly controlled wallets. Businesses should set upper and lower limits for the hot wallet based on daily outflows, peak demand, and how quickly it can be refilled: anything above the upper limit moves to cold storage, and when the balance drops below the lower limit, it is topped up from the cold wallet with approval. Why Shouldn’t All Funds Sit in a Hot Wallet? A hot wallet has to stay online and sign automatically at any time, which is why it carries the highest risk in any comparison of crypto wallet security. Keeping most assets in cold wallets puts a ceiling on losses: even if hot wallet security risks such as a compromised server or stolen credentials materialize, the most you can lose is the small amount it holds. How Much Should a Hot Wallet Hold? A practical approach is to look at outflows and refill speed. Track the average and peak daily outflows for each chain and asset, then see how long it takes to top up from the cold wallet. […]
How Can Businesses Secure Their Hot Wallets?
How can businesses secure their hot wallets? Focus on three areas: use MPC to eliminate the complete private key, so compromising one server does not yield the key; use a policy engine to check every outbound transfer before signing, restricting amounts and destinations; and continuously monitor transfers and API calls so outflows can be paused immediately when something looks wrong. The security risks of a hot wallet can never be fully eliminated, but it can be set up so that even if one link is compromised, losses are capped. How Should a Hot Wallet’s Private Key Be Protected? The biggest problem with a traditional hot wallet is that the complete private key sits on one online server, so compromising the server means losing the funds. An MPC wallet keeps the private key split into shares across different servers and parties from the moment it is generated, with signing done jointly so the complete key never appears. Each share can also be placed inside a trusted execution environment or an HSM for an extra layer of protection. Signing servers should be isolated from business servers, expose only the interfaces they need, and limit access to as few people as possible. How Do You Control Outbound Transfers From a Hot Wallet? Even if a signing credential is compromised, funds should not be […]
HSM vs KMS: What’s the Difference?
HSM vs KMS: what’s the difference? An HSM (hardware security module) is a dedicated tamper-resistant device in which keys are generated, stored, and used, never leaving the device in plain text. A KMS (key management service) is a service that manages the key lifecycle, handling creation, rotation, authorization, and auditing, and it is often backed by HSMs underneath. Put simply, an HSM answers “where is the safest place to keep a key,” while a KMS answers “how do we manage large numbers of keys.” What Are an HSM and a KMS? An HSM is a physical device. It can be a dedicated server in a data center or a cryptographic card installed in a server. It is built to resist tampering, and signing and encryption happen inside the device, so the outside world only ever sees the results, never the key itself. Many products are also certified to security standards such as FIPS 140. A KMS is a software service, most commonly a managed KMS offered by a cloud provider. It helps businesses manage large numbers of keys centrally: who can use which key, when keys are rotated, and a log of every use. When it comes to storing application credentials such as API keys and database passwords, KMS is what businesses use most. How Do HSM and KMS Differ […]
API Key vs Private Key: What’s the Difference?
API key vs private key: what’s the difference? A private key is the ultimate control over on-chain assets. It signs transactions, and once it is lost or leaked, the damage cannot be undone. An API key is the credential a business’s systems use to prove their identity when calling a wallet service, and it can be revoked and reissued at any time. But both can trigger transfers: in Wallet-as-a-Service, someone holding an API key may get the system to sign a transfer on their behalf without ever touching the private key, so both need strict protection. What Do API Keys and Private Keys Each Do? A private key lives at the blockchain level. It corresponds to a wallet address, and the blockchain only accepts transactions signed with it. Whoever controls the private key owns the assets at that address, and a private key cannot be changed; if it leaks, the only option is to move the assets to a new address. An API key lives at the application level. It is not on-chain at all. It is simply the credential a business’s backend uses to prove “who I am” when calling a WaaS API, and the provider uses it to decide what each request is allowed to do. It is issued by the provider, can be scoped to specific permissions, […]