tmgt.

Deployment and operations

From plan selection to deployment

Compare plans and estimate usage, then prepare your process, trust model, integrations and test criteria. Online signup is currently unavailable.

Choose a planThe security model

Deployment steps

  1. Plan and use case

    Compare included usage and choose the product scope, assets, networks and control requirements.

  2. Trust model

    Authority distribution, MPC/HSM, policies and recovery conditions.

  3. Specification

    Integrations, status formats, risk data and operation records.

  4. Environment preparation

    Infrastructure, access, accounts and test data.

  5. Pilot

    Permitted and rejected operations, publication and agreed failure scenarios.

  6. Acceptance and operation

    Test results, procedures and the agreed configuration.

Prepare your configuration

  1. A short description of the operation and intended result.

  2. Networks, assets and operation types.

  3. Business and technical owners of the process.

  4. Existing applications, accounting systems and signers.

  5. Requirements for deployment, access, control and records.

What determines the configuration

Deployment and trust model

Agree trust boundaries, participant independence, MPC/HSM and infrastructure responsibilities.

Integrations and data

Define exchange methods, statuses, retries, risk sources and record exports.

Operations and load

Specify operation profiles and performance measurement conditions.

Operations management

Define updates, monitoring, stops, recovery and responsibilities.

Clear plans and usage-based pricing

Developer is $0, Build is $199, Scale is $999 and Enterprise is $3,999 per month in USD. Paid plans include wallet and operation allowances, with optional additional usage. Network fees, external services and applicable taxes are separate.

Compare plans and calculate costs

Timelines and operating terms are agreed

Implementation timelines, support arrangements, service levels and recovery parameters are agreed for each configuration. They become commitments only when agreed.

The basis for acceptance

Test agreed permissions and rejections, statuses, records and behaviour under selected failures. Measure load and operation duration using a fixed configuration and an agreed methodology.

Further reading

Choose the plan for your next step

Compare monthly plans, included usage and additional costs. Online signup is currently unavailable.

Choose a planExplore the platform