Secure wallets.
Zero custody.
Give every user a wallet, set the rules, and let Sigcore sign inside hardware nobody can open. Not attackers, not cloud providers, not us.
- Ethereum
- Solana
- Bitcoin
- Polygon
- Arbitrum
- Optimism
- Base
- Avalanche
Why Sigcore
Keys nobody can open. Rules nobody can skip.
Wallet infrastructure built so you never have to trust the provider.
Hardware-sealed keys
Private keys live inside tamper-proof hardware.
Keys are created and used inside a sealed enclave, and only the signature comes out.
No seed phrases
Users sign in. Nothing to write down.
A passkey or existing login unlocks the wallet on any device.
Non-custodial
Nobody can move your funds, not even us.
There is no key export and no way to sign around your rules.
Rules first
Every transaction is checked before it is signed.
Limits, approvals, destinations and time windows are checked inside the same hardware as the key.
- Under the daily limitPass
- Destination is on the allowlistPass
- Inside signing hoursPass
Integration
Live in an afternoon, not a quarter.
Drop in the SDK and create your first wallet without ever touching a private key.
import { loadSigcore } from "@sigcore/sdk"
const sigcore = await loadSigcore(PUBLISHABLE_KEY)
const { wallet } = await sigcore.client.createWallet({
orgId: "org_acme",
name: "Treasury",
algorithm: "ED25519",
})
How it works
Three steps from sign-up to signed transaction.
Create wallets
Create a wallet per user or purpose with one API call. Its key is generated inside secure hardware and never leaves.
Set the rules
Decide what each wallet may do: daily limits, allowed destinations, who approves large transfers, and when signing is allowed.
Sign safely
Your app requests a signature. Rules are checked, the transaction is signed inside the hardware, and only the signature comes back.
Want the engineering version, with every message between services? Read the technical walkthrough.
Policy controls
Set the rules. Sigcore enforces them.
Write the rules once. They're checked inside the hardware on every request, and nobody at Sigcore can override them.
Spending limits
- Daily limit
- $10,000
- Transactions per day
- 50
- Used today
- $3,420
Approvals
- ACAlexApproved
- MRMayaApproved
- JSJonWaiting
Allowed destinations
- 0x742d35Cc…f2bD18Allowed
- 0xA0b86991…e3606Allowed
- Any other addressBlocked
Time windows
- Mon
- Tue
- Wed
- Thu
- Fri
- Sat
- Sun
Security
Security you can explain to your board.
Five guarantees, in plain words. Each one is enforced by hardware, not by a promise.
Only inside hardware-encrypted memory.
The processor encrypts the enclave's memory with a key that the server, its operating system and the cloud provider never see.
Encrypted at rest, unlockable only by the enclave.
Stored keys are wrapped with a master secret that is split between independent operators. No single person can reassemble it.
The key never travels. Signatures do.
Your transaction goes in, a signature comes out. There is no command to export a signing key, so there is nothing for an attacker to intercept.
Key material is wiped from memory.
Each signing operation cleans up after itself, so keys don't linger between requests.
Nobody at Sigcore. By design, not by policy.
You can verify which software is running in the enclave before you trust it. Our team never has access to key material, and we can prove it.
For the hardware model, the cryptography and the full request flows, read the security deep dive.
Compared
Three ways to handle keys.
Custody is a spectrum between convenience and control. Sigcore is built so you don't have to pick a point on it.
Scroll sideways to compare.
| Sigcore | A custodian holds the keys | Users hold their own keys | |
|---|---|---|---|
| Who can move funds | Only what your rules allow, enforced in hardware | The custodian, and anyone who breaches them | Only the user, as long as they keep their seed phrase |
| If the provider is breached | Nothing to steal. Keys never leave the hardware | Funds are at risk | Not affected |
| If a user loses their device | Recoverable. No seed phrase involved | Recoverable through support | Funds are gone |
| Spending rules and approvals | Built in, per wallet | Depends on the provider | None |
| Your regulatory position | Non-custodial by construction | You may count as a custodian | Clean, but hard to support users |
| Time to integrate | An afternoon with the SDK | Weeks of vendor onboarding | Users bring their own wallet |
Use cases
One signing layer for whatever you're building.
Consumer apps, trading desks, treasuries and games all need the same thing underneath: wallets that can't be stolen and rules that can't be skipped.
Embedded wallets
Give every user a wallet the moment they sign up. No seed phrases, no extensions, nothing to lose.
Trading and DeFi
Let bots and users trade inside limits you set: per-trade caps, approved venues, trading hours.
Company treasury
Hold funds with approvals from the right people, and a record of every decision.
Games and NFTs
Mint and transfer for millions of players without ever handling a key.
Pricing
Start for free. Scale on a flat monthly plan.
No per-wallet or per-user charges. Wallets and users are unlimited on every plan.
Developer
1,000 signatures a month included
Build and test for free
- Unlimited wallets and users
- Hardware-sealed keys
- Spending limits and allowed destinations
- Up to 5 policies
- Community support
Growth
Most popular10,000 signatures included, then $0.02 each
For apps in production
- Unlimited wallets and users
- Unlimited policies
- Approvals and time windows
- 99.9% uptime commitment
- Priority email support
Enterprise
Volume pricing from $0.002 per signature
For organisations at scale
- Everything in Growth
- Dedicated infrastructure
- 99.99% uptime commitment
- Single sign-on (SSO)
- A named engineer
Need the full comparison? See all plans.
FAQ
Common questions.
Straight answers about custody, security and what happens when things go wrong.
Start signing in minutes.
Create your account, create your first wallet, and sign your first transaction. Free to start.