Xavinet · CryptoRail

Your business operations, settled on chain.

CryptoRail sits between your systems and EVM blockchains. Your teams keep calling an API; CryptoRail signs, sends, follows every transaction to finality and reports back, so the chain becomes one more system your back office can trust.

Ask for a pilot Read the deep dives

Public and permissioned EVM networksSelf-hosted or run for youKeys stay on your side

The problem

Blockchains settle in seconds. Connecting a back office to them safely takes months.

Sending one transaction is easy. Sending thousands, from systems that retry, under approvals, with keys that must never leak, and knowing for certain which ones landed, is a project every company rebuilds from scratch. CryptoRail is that project, done once.

What it buys you

Three things your teams stop worrying about.

Everything else on this site is detail behind these three outcomes. See the product.

Transactions that land

An operation CryptoRail has acknowledged is never lost: not across crashes and restarts, not through a node outage of up to ten minutes.

Keys that stay where they belong

Keys never enter CryptoRail: signing happens in your HSM, your cloud KMS or your own signer, and only the development signer ever touches a key.

Events your systems can trust

At-least-once delivery through a transactional outbox, with a deterministic id on every event so your systems can drop duplicates.

How it works

From a business call to a final, reconciled result.

Your systems describe what should happen. CryptoRail takes care of everything between that intent and a transaction the network has finalised, and tells your systems what happened.

STEP 1

Describe the operation

Call a contract function or send a transfer through the API, in business terms. Sent twice by mistake, it still runs once.

STEP 2

CryptoRail carries it

Approvals, signing with your own keys, network fees, ordering and retries, until the network makes it final.

STEP 3

Your systems are told

Signed events to your back office, a full history for audit, and a failure report that says what to do when something goes wrong.

Composability

Your back office, plugged into the protocols that already exist.

Lending pools, tokenised funds and bonds, stablecoins, identity registries: thousands of contracts are already deployed. Import the description of the ones you need and call them from your own systems, under your policies, approvals and keys. How it works and its limits.

Bring the ABI of any deployed contract, yours or a third party's, as JSON or in readable form, even with only the functions and events you use, and check it against the deployed code.
Call a function by the contract's name in your registry: arguments checked against the ABI before anything is signed, and the contract's own errors decoded when it refuses.
Policies per protocol: which contracts and functions may be called, with what value, and how much per period.

flowchart TD
    B[Your ERP, treasury or customer systems] --> C[CryptoRail: policies, approvals, signing, events back]
    C --> L[Lending and liquidity pools]
    C --> F[Tokenised funds and bonds]
    C --> S[Stablecoins]
    C --> I[Identity registries]

Where it runs

In your infrastructure, on your networks.

Self-hosted, run for you, or a pilot sandbox; public networks or a consortium's own. Compare the deployment options.

Runs in your infrastructure, as a container image over your PostgreSQL, with schema migrations applied by an explicit command.
Run for you in production without ever holding a key of its own: signing stays on your side or in your own cloud account. Available for pilots
Permissioned consortium networks with free gas (Hyperledger Besu with QBFT): no fee market, no gas balance to keep topped up.
Tested on every change to the code against Anvil and a Hyperledger Besu QBFT network, and run on public test networks by recorded manual procedures.

What it guarantees

Built for the operations team, not only for the developers.

Every statement below is backed by tests run on every change. See the evidence.

Submitting the same intent twice with the same idempotency key returns the same transaction: a retry never becomes a second payment.
Your own signer keeps the key: CryptoRail prepares the exact bytes, your system signs them, CryptoRail verifies and broadcasts.
Operations above a threshold wait for a quorum of approvers, who sign an EIP-712 digest that names neither nonce nor fee.
Several node endpoints per network: calls go to the first healthy one, an operation stays on the endpoint it started on, and a dead or lagging node is left aside without losing anything.

The company

Xavinet builds the infrastructure between business and blockchain.

Xavinet connects the back offices of banks and companies to blockchain networks, with the controls they already expect from their own systems. CryptoRail is its first product.Discover CryptoRail.

Your business operations, settled on chain.

Blockchains settle in seconds. Connecting a back office to them safely takes months.

Three things your teams stop worrying about.

Transactions that land

Keys that stay where they belong

Events your systems can trust

From a business call to a final, reconciled result.

Describe the operation

CryptoRail carries it

Your systems are told

Your back office, plugged into the protocols that already exist.

Five pilots, running today.

Stablecoin payouts

Treasury on Aave

Supplier accreditations

Your own asset

Loyalty programme

In your infrastructure, on your networks.

Built for the operations team, not only for the developers.

Xavinet builds the infrastructure between business and blockchain.

See it on your own use case.