Hold funds in hot, warm and cold vaults where no single key exists: two of three MPC key shards sign, transfers follow vault policies (limits, hours), need two different approvers above a threshold, go only to approved screened addresses, can be frozen by a kill switch, and every action lands in a hash-chained audit log.
Hold funds in hot, warm and cold vaults where no single key exists: two of three MPC key shards sign, transfers follow vault policies (limits, hours), need two different approvers above a threshold, go only to approved screened addresses, can be frozen by a kill switch, and every action lands in a hash-chained audit log. This is a full prototype: every role has its own screens and the business rules are enforced on the server. It runs on sample data and shows how this kind of product works. It is not a client project.
It is built for exchanges, funds and fintechs that hold customer crypto and need approvals and policy controls. Use the demo to agree the scope with your team: which flows you need on day one, which roles log in, and what can wait for a later release.
An institution wants to hold client assets without a single point of key failure, with approvals that match its internal policy.
We compare chains supported, signing latency, audit needs and vendor risk before choosing the signing scheme.
Limits, allow-lists, time locks and multi-party approval are code, enforced before anything is signed.
Shares live with different operators and infrastructure, so one breach cannot move funds.
Backup and disaster recovery are tested in drills, not only documented.
Illustrative example, not a client case study. Custody licences, insurance and legal structure are yours; we build the technical controls.
Pricing starts at USD 15–40 per hour, scopes are milestone-based, and you own the full source code. We reply to every enquiry within 10 minutes, set up a meeting, share a demo within 24 hours of it and then send a proposal as per your budget. Work runs 24/7 in three shifts, remotely from India, in your time zone.
Hold funds in hot, warm and cold vaults where no single key exists: two of three MPC key shards sign, transfers follow vault policies (limits, hours), need two different approvers above a threshold, go only to approved screened addresses, can be frozen by a kill switch, and every action lands in a hash-chained audit log. It is a clickable prototype built by Hurain Technologies to show how this kind of product works before you commit to a build. It runs on sample data and is not a client project.
Open the demo above, pick a role on the sign-in screen and click through the tabs. Switch role to see the same data from another side: Operator, Approver, Security officer, Admin. You can change the language, turn on dark mode and use the 2026 add-ons tab. Rules such as limits, prices and approvals run on our server, so the results are checked, not scripted.
No. Everything is sample data created for the demo. Nothing you do is stored: the current state is sent to the server for each action, the rules are applied and the result comes back. Do not enter real personal or payment details.
It is built for exchanges, funds and fintechs that hold customer crypto and need approvals and policy controls. The demo shows the flows those teams ask for first, so you can decide what to keep, change or add for your own business.
Yes. We reply to every enquiry within 10 minutes, set up a meeting to understand your requirements and share a demo within 24 hours of that meeting, followed by a proposal as per your budget. Pricing starts at USD 15–40 per hour, scopes are milestone-based, and you own the full source code.
Yes. Real builds are adapted to your market: local payment methods, tax, data-protection rules, languages and your own branding and workflows. We work remotely from India for clients worldwide, in your time zone.
MPC versus multi-signature: We compare chains supported, signing latency, audit needs and vendor risk before choosing the signing scheme. Policy engine for transfers: Limits, allow-lists, time locks and multi-party approval are code, enforced before anything is signed. Key shares in separate trust domains: Shares live with different operators and infrastructure, so one breach cannot move funds. Recovery rehearsed: Backup and disaster recovery are tested in drills, not only documented.
Tell us what you would change after trying it. You get a reply within 10 minutes, a demo within 24 hours of our meeting and a proposal as per your budget.
Last updated: 2026-10-07. Sample data only; not a client project.