Learn · updated 1 Nov 2026
The back office for trading bots and agents, compared
A back office for trading bots and agents runs the strategy's operations, takes each ruling from outside the strategy, signs only inside a bounded mandate and keeps one book against the chain. Wallet vendors, custodians, bot platforms and accounting tools each document part of that; Nevarn's case is joining them in one system.
The four jobs
Running the bot: scheduling, a time-limited hold so nothing runs twice, recovery when a runner dies, backoff on failure, and the venue adapter that submits the order.
A ruling from outside: before an order moves, something other than the strategy decides whether it may. In Nevarn that is Decionis, a separate execution authority. If it cannot be reached, the order is refused.
Books across ledgers: one double-entry book for every movement, compared with what the chain says, with any difference shown rather than corrected away.
Proof of execution: evidence that the approved trade is exactly what happened, and where its proceeds went.
How the tools compare
Each row is a kind of tool, with examples, described from the vendor's own public pages (numbered sources below). Each is good at what it is built for; the table shows only which of the four jobs each one's pages describe.
| Runs the bot | Ruling from outside | Books across ledgers | Proof of execution | |
|---|---|---|---|---|
| Wallet infrastructure (Privy, Turnkey, Coinbase Developer Platform) | — | Its own policy engine on signing[1][2][3] | — | — |
| Custody platform (Fireblocks) | — | Its own policy engine; an API co-signer can ask a callback you run to approve or reject[4][5] | Balances of its vault accounts[6] | — |
| Bot platforms (Hummingbot, 3Commas) | Yes: an open-source framework you run; hosted bots on connected exchanges[7][8] | — | — | — |
| Crypto accounting (Cryptio, Bitwave) | — | — | Sub-ledger and reconciliation from wallet, exchange and custodian data[9][10] | — |
| Nevarn | Yes: scheduled work with time-limited holds, recovery and backoff; Nevarn's own lanes run on it | Yes: Decionis rules before an order moves, armed lane by lane | One double-entry book, reconciled against the public chain, with drift shown | Partly: every trade is a public transaction on a public dashboard; per-trade receipts are not published yet |
Limits and allowlists are table stakes
Spending limits and allow and deny lists do not set a back office apart. Privy, Turnkey and Coinbase's developer platform each document a policy engine that enforces them on signing (sources 1–3).
What sets Nevarn apart is the intersection of the four jobs, not any one control: the ruling from outside, the signature inside a mandate and the book against the chain, in one system.
Using them together
These tools are not exclusive. A team can sign with a wallet vendor or a custodian, run its strategy in a bot framework and close its books in an accounting tool.
Bitwave describes its platform as a back office for digital assets, centred on accounting, a sub-ledger and reconciliation into an ERP (source 10). Nevarn's is the operating side: the ruling, the signature and the book for each trade as it happens.
Decionis decides. Nevarn operates — and proves it. Decionis owns the mandate format, the policies, the rulings and the proof of decision; Nevarn runs the strategy, signs inside the mandate and keeps the books.
Where Nevarn stands today
Decionis is armed lane by lane, and the gate table on nevarn.com/technology lists each lane's state. Not yet gated: on-chain arbitrage, including flash loans. Every trade from Nevarn's own trading wallet is a confirmed public transaction; a per-trade receipt linking the ruling to the ledger entry is not published yet.
Sources
Questions people ask
Is Nevarn a wallet provider or a custodian?
No. Nevarn never holds the key to a customer's wallet. It signs only with a limited permission the customer's own account has accepted, on a separate working balance, and it runs the operations and keeps the books.
Does Nevarn decide whether a trade is allowed?
No. Decionis decides: it owns the mandate format, the policies and the rulings. Nevarn asks for a ruling before an order moves, acts only on proceed, and records the outcome either way.