Skip to content
ClonePips

Platform module

Risk Management

Broker and provider risk controls applied before and during execution. Part of the platform's core domain: brokers, providers and investors read the same records through it.

  • Rule engine with warn, block and close actions
  • Broker-wide kill switches
  • Exposure, drawdown and margin limits
  • Every rule evaluation recorded for review

Demo data — fictional sample content for interface development. Not real ClonePips customer data.

Product view

The surface, illustrated

A composed product view over fictional demo data. It shows the shape of the interface this module feeds, not a live venue.

Illustrative product composition showing the Risk Management module. The illustrated surface is a venue risk console built from demo data. Utilisation figures are illustrative, not measured from a live venue. The kill switch shown as off reflects an unreleased build, not a venue.

Interface preview

  • The illustrated surface is a venue risk console built from demo data.
  • Utilisation figures are illustrative, not measured from a live venue.
  • The kill switch shown as off reflects an unreleased build, not a venue.
  • Illustrative product composition built from demo data. Not a live account or venue.

How it works

How Risk Management works on the platform

Stage 1

The risk engine evaluates tenant, strategy and account rules before and during execution.

Stage 2

A rule can warn, block, or close — and every evaluation is recorded, so a decision is reviewable even when nothing happens.

Stage 3

Kill switches give a broker a platform-wide stop that is a real control, not a dashboard indicator.

Placement

Where risk is evaluated

Where this module acts in the platform's one-domain model, and which other modules it depends on.

  • Evaluates exposure, drawdown and margin limits across the venue.
  • Applies broker- and provider-scoped profiles with inheritance.
  • Records every warn, block and close for review.

Sits behind

  • Copy Trading — every replicated order passes these rules.
  • PAMM / MAM — allocation limits are evaluated in the same engine.
  • Analytics — risk figures in reports are snapshots, not recomputations.

Questions

About Risk Management

What happens when a rule fails?

The action the rule defines runs — warn, block, or close — and the evaluation is recorded. A blocked instruction never becomes an order.

Can rules differ across the venue?

Yes. Profiles inherit from tenant-wide defaults and are overridden per provider, strategy or account, so a broker can tune without duplicating config.

Notices

Risk warning

Trading foreign exchange, CFDs and leveraged instruments on margin carries a high level of risk and may not be suitable for all investors.

No advice

Information on this site is provided for general information only and does not constitute investment advice or a recommendation.

Demo data

Demo data — fictional sample content for interface development. Not real ClonePips customer data.

Next

See Risk Management against your deployment

The demo walks the module, the shared model it sits on, and the commercial basis for the venue.