The capabilities of the HOLD OS platform
Capabilities that work together
In HOLD OS, accounts, assets, trades and contracts speak one shared language. The result is a system your team can follow, knowing for every operation what was recorded, in which account and under whose authority.
Six core capabilities
Each capability has its own page with an explanation, an example and its connection to the rest of the system.
-
Gold, Silver and Custom assets
A distinct identity, unit and precision for each asset, with a separate reference price.
-
Wallets and records
Asset wallets beside one shared cash wallet, with records tied to account and asset.
-
Trade workflows
Requests with explicit quantity and price, approval by someone with authority, and a recorded result.
-
Asset leasing
Contracts based on an approved asset profile; principal and rent as two separate obligations.
-
Customer accounts
Institution-managed private onboarding, controlled subaccounts and bank destination review.
-
Access control
Authority by role, account and asset; password sign-in with optional additional factors.
Three kinds of everyday work
HOLD OS capabilities can be grouped by the question they answer. Grouping them this way lets you start an evaluation from your own needs.
- Ownership and holding
- Which asset, in which unit, held in which account? (multi-asset management, wallets, customer accounts)
- Trading
- Who requested which quantity at what price, and who approved it? (trade workflows)
- Contracts and obligations
- What has to come back, and what is settled separately? (asset leasing)
- Authority
- Who is allowed to do each operation, and how do people sign in? (access control)
One shared architecture, not separate modules
Wallets, trading, ledger records and leasing for Gold, Silver and Custom assets are implemented on one shared financial core. The Gold logic was not copied for Silver or Custom; each asset has validation suited to it.
For an operations team, that means one way of working: once you know how a Gold trade is requested and approved, you know the same path for every other active asset.
- Gold Validation suited to Gold
- Silver Validation suited to Silver
- Custom Validation suited to the institution’s definition
Shared financial core Versioned contracts for quantity, wallets, trades and leasing
Compare your needs with the HOLD OS approach
This is not a comparison with another product. It is a list of questions an institution should ask when choosing an asset operations system.
| What to evaluate | How HOLD OS approaches it |
|---|---|
| Which asset does each quantity belong to? | Every asset has a stable identity, unit and precision; a display name never replaces identity. |
| Are asset balances kept apart from cash? | Each asset has its own wallet, and each account has one shared cash wallet in whole toman. |
| What does a trade request do before approval? | A request does not change balances until it is approved and recorded. |
| How do principal and rent stay separate? | Two obligations with separate records; rent never reduces principal. |
| Who can create accounts? | Accounts are created through the institution’s private process; there is no public signup. |
| What is operational authority based on? | The user’s role, the current account and the asset concerned, together. |
See the capabilities in the product
In a walkthrough we go through the capabilities that matter to your institution in the product itself.