HOLD OS · Unified institutional operations
Manage ownership, trading and leasing in one environment
HOLD OS gives an institution’s accounts, assets and contracts one clear structure: customers and subaccounts, wallets and records, manual trades and leasing contracts. Gold, Silver and Custom assets share one engine, so your team works with all of them in the same way.
- Gold A native asset with its own identity, unit and reference price; a Gold record always stays Gold.
- Silver The same shared core with an entirely separate identity; nothing recorded as Gold is converted into Silver.
- Custom An asset defined by your institution, with its own name, unit and precision.
A structure your team can follow
In HOLD OS every activity belongs somewhere specific. The institution sets the frame and the rules, each customer has a private account, and subaccounts are controlled within the same frame.
When every account has a clear place, everyday questions become easier to answer: who holds this asset, which account an operation was recorded in, and who was authorized to carry it out.
-
Institution
Sets active assets, rules and operational authority.
-
Customer
A private account the institution creates and manages.
- Subaccount A controlled account under a customer, inside the same authority frame.
-
Customer
A private account the institution creates and manages.
From customer account to contract, one continuous path
HOLD OS capabilities were not designed in isolation. Each step builds on the same account, the same asset and the same records as the step before.
-
Open the account
The institution creates the customer account through a private process; an account alone grants no financial authority.
-
Hold the asset
Each asset has its own wallet, and every account has one shared cash wallet.
-
Record the trade
A request carries an explicit quantity and price, and completes only after approval by someone with authority.
-
Lease the asset
A leasing contract keeps the asset principal and the rent as two separate obligations.
-
Follow the record
Every event stays traceable in the asset and unit it was recorded in.
One engine, three asset types
Gold, Silver and Custom are not three copies of the same software. All three use one shared financial core, and each keeps a stable identity, unit and precision of its own; an asset’s display name is not its financial identity.
In a walkthrough you examine this logic in the product itself: how each asset is defined and how it is used across wallets, trades and contracts.
- Gold Its own identity and unit
- Silver Its own identity and unit
- Custom Defined by the institution
Shared financial core One set of rules for quantities, wallets, trades and leasing
Six capabilities, one system
Each capability is tied to everyday institutional work. Open a capability for details and examples.
-
Gold, Silver and Custom assets
Each asset with its own identity, unit and precision on one shared engine.
-
Wallets and records
A wallet for each asset and one shared cash wallet per account.
-
Trade workflows
Manual trades with explicit quantity, price and authority.
-
Asset leasing
Principal and rent kept as two obligations with separate records.
-
Customer accounts
Private onboarding, controlled subaccounts and review of customer bank destinations.
-
Access control
Authority for each operation set by role, account and asset.
HOLD OS pricing
Request a product walkthrough to assess HOLD OS for your institution. You explore the account structure, asset workflows and leasing contracts in the product itself.
See HOLD OS in your own institution’s scenario
Tell us how your organization works today. The walkthrough focuses on the parts of the product that matter to that work.