Exposure
Stablecoin balances across wallets and treasury venues, in one operating view.
On-chain treasury
Policy and risk controls for on‑chain treasury.
Monitor stablecoin exposure, set limits by asset, chain, issuer, protocol, and counterparty, and surface treasury risk before it becomes a loss.
For treasury, risk, and operations teams. No custody. No automatic execution.
Sample book
Treasury exposure
Sample data
Exposure
$28.5m
Gross cap
$40.0m
USDT cap
34%
Gross cap used
71%
Inside the gross cap. The USDT issuer cap is the binding rule.
-
Issuer · USDT
Near
-
Chain · Tron
Inside
-
Protocol · Lending
Inside
Alert · needs approval
USDT is one point under its issuer limit. Additional USDT exposure needs approval before it lands.
Illustrative only. These numbers are invented for the demo.
What LimitOps is for
Limits
Thresholds by asset, chain, issuer, protocol, and counterparty.
Alerts
A signal while a position is approaching the limit, not after the review.
Record
Who was asked to approve a movement, and which rule it sat against.
The gap
The balances are on‑chain. The policy is not.
A wallet balance is not a risk position. Capital sits across chains, issuers, and venues, while the limits live in a document, a slide, or someone’s memory.
-
01
No single view of exposure
Stablecoins are split across operating wallets, multisigs, exchanges, and protocols. Issuer, chain, and counterparty risk get rebuilt in spreadsheets.
-
02
Limits are outside the workflow
A concentration cap in a policy memo does not stop the next transfer. The rule and the movement never meet.
-
03
The warning comes late
Breaches show up in a weekly review, or after a depeg, a freeze, or a venue issue. By then the position is already on.
-
04
The audit trail is a chat log
When someone asks who approved a movement, and against which rule, the answer is scattered across messages and memory.
How it works
From the venues you use to a decision you can audit.
LimitOps is the control layer between a treasury policy and the capital that policy is supposed to govern.
-
01
Connect
Bring in the wallets and venues that already hold treasury capital. Designed to start read-only, without taking custody.
-
02
Map
Group exposure by asset, chain, protocol, issuer, and counterparty. A blended total is not the risk.
-
03
Set limits
Turn the thresholds the team already uses into rules: gross caps, issuer mix, chain concentration, venue and counterparty limits.
-
04
Alert and approve
When a position approaches a limit, the people who should decide see it before capital moves. The decision stays on record.
This is the workflow we are building with early design partners. Not every connection is available today.
Product
A book, a policy, and a record.
Six controls for the people who run on-chain capital during the week, not for a product tour.
-
01
Exposure monitoring
A current view of stablecoin and treasury balances across the wallets and venues you connect.
-
02
Limit policies
Rules by asset, chain, protocol, issuer, and counterparty, using the thresholds your team already agreed to.
-
03
Treasury alerts
A signal when concentration or venue exposure approaches a limit, while there is still time to act.
-
04
Approval workflows
Exceptions go to the people who should sign off, before capital moves.
-
05
Audit trail
Limits, alerts, and decisions in one record, so a later review does not start from a chat log.
-
06
Multi-chain visibility
One operating view across the chains where the treasury actually sits.
Teams
For people who already hold the capital.
LimitOps is for operators of on-chain treasury: the teams that hold, move, and account for the capital.
-
Crypto startups
Operating cash in stablecoins, usually across a few wallets, without a treasury system underneath.
-
DAO treasury teams
Multisig balances and outgoing payments, with a need to show how capital is governed.
-
OTC and trading desks
Inventory, venue balances, and counterparties that need hard limits, not a weekly spreadsheet.
-
Small funds
Concentrated books, where issuer and chain exposure matter as much as the position itself.
-
Fintech teams
Stablecoin balances beside fiat operations, and no shared control framework between them.
Principles
How the product is meant to behave.
There is no customer wall here. These are the constraints we are building against.
-
01
Policy first
Limits are the product. A screen that cannot say whether the book is inside policy is only a balance check.
-
02
Visibility before action
Exposure should be obvious before anyone is asked to approve a movement.
-
03
Operator-grade controls
Built for the people who run the book on a Tuesday: clear status, a named rule, and a next decision.
-
04
On-chain treasury, specifically
Stablecoins, wallets, issuers, protocols, and counterparties. The objects these teams already manage.
Early access
Tell us how your treasury is held.
We are opening LimitOps to a small number of treasury, risk, and operations teams. A few details are enough to start.
Request received
We will reply to about early access.
Send this request by email
Your details are ready. Email them to hello@limitops.io. We reply to the work address in the message.
FAQ
Questions
Is this a wallet?
No. LimitOps is a visibility and control layer. Assets stay in the wallets and venues you already use.
Is this a custody provider?
No. LimitOps does not take custody of assets and does not hold private keys.
Does it execute transactions automatically?
No. It is built to surface limits, alerts, and approvals. It does not move funds on its own.
Who is this for?
Treasury, risk, and operations teams at crypto startups, DAOs, OTC and market-making desks, small funds, and fintech companies that hold stablecoins.
When is the product launching?
LimitOps is in early development. Leave your details and we will reply with timing for design partners. There is no public launch date on this page.