Solutions by working context

HOLD OS in your organization’s workflow

The capabilities of HOLD OS are the same for everyone, but each institution uses them along a different path. A gold institution starts from trading, a leasing business from contracts and obligations, and another organization from defining its own asset.

Three working contexts

Choose the context closest to your institution’s work. These are suggested evaluation contexts, not a list of customers.

Choose the workflow to start from

If you are not yet sure which context fits best, start from the everyday task that takes most of your team’s time.

What to evaluateHow HOLD OS approaches it
Recording purchases and sales for customersTrade workflow: request, explicit price, approval and recorded result.
Holding customer assets in separate accountsWallets and records: a wallet per asset and one shared cash wallet.
Placing assets with others in exchange for rentAsset leasing: principal and rent as two separate obligations.
Working with an asset other than gold and silverCustom asset: defined with the institution’s own name, unit and precision.

Questions for decision-makers

Before a walkthrough, review your answers to these questions about your own organization. They make the conversation far more precise.

Which assets does your institution work with?

Gold, Silver, or another asset that needs its own unit and precision. The answer decides which assets are active and which is the default.

How are your customers structured?

Do customers need separate subaccounts? Who creates accounts? In HOLD OS, account creation is a private process controlled by the institution.

Who approves trades?

Define roles and each person’s scope of authority; HOLD OS sets authority by role, account and asset.

Do you run leasing contracts?

If so, each asset needs an approved profile, a rent calculation policy and a calendar.

Tell us about your working context

Email us your organization’s main use case so the walkthrough focuses on the workflow that matters to you.