Risk product
ClonePips Risk
Centralised risk across every account and provider. A broker-wide risk layer that evaluates rules across the whole venue and can halt copying platform-wide.
- Tenant-wide risk profiles with inheritance
- Pre-trade and post-trade rule evaluation
- Platform-level kill switches
- Compliance-grade evaluation logs
Demo data — fictional sample content for interface development. Not real ClonePips customer data.
Availability
Announced — release date not set
What the product registry says about this product today, stated without extension.
- Announced in the product registry — release date not set.
- Specifies 2 platform modules, described on this page as a design.
- Declared integrations: rest api, webhooks — none is connected in this build.
Registry facts
- Category: risk
- Status: Announced — release date not set
- Intended for: brokers, institutions
- Delivers modules: 2
- Pricing basis: per broker
Why it exists
Risk controls fail when they live in one place
A control that only guards one strategy or one account is not a venue control. When risk is evaluated somewhere other than the order path, the gap between them is where an overrun happens.
ClonePips Risk packages a venue-wide layer: profiles that inherit from venue to provider to strategy to account, evaluation before and after execution, and kill switches an operator can pull with a recorded reason.
Because the layer is venue-wide, a narrower scope overrides only what it must, and every evaluation is stored whether the outcome was allow, warn or block.
- Tenant-wide profiles with inheritance.
- Pre-trade and post-trade evaluation, both recorded.
- Platform kill switches with a recorded reason.
Product view
The risk console, illustrated
A venue risk view: limit utilisation, active controls and an indicative drawdown, composed from demo data.
Interface preview
- The frame shows venue-wide risk posture: rules active, evaluations and blocked signals.
- Rule and evaluation figures in the frame are fictional demo data.
- The frame is a layout illustration composed from demo data.
- Illustrative product composition built from demo data. Not a live account or venue.
Design
How ClonePips Risk is designed to work
Profiles inherit
A venue-wide profile sets defaults; narrower scopes override only what they must.
Pre- and post-trade
Rules evaluate before an order is routed and again against what came back, with both outcomes stored.
Platform kill switches
A halt is an evaluated control that stops copying across the venue and records who, when and why.
Audience
Who operates it
The risk layer is operated by the broker, but its rules reach every provider, strategy and account on the venue.
- Brokers set the venue-wide posture and the exceptions.
- Providers and strategies inherit defaults and override narrowly.
- Operations teams pull kill switches with an auditable reason.
Declared integration surfaces
- REST API for rule configuration and review.
- Webhooks for risk events and evaluations.
- Kill switches as an operated control, not a background flag.
Deployment
Deployment notes
- 01
Step 1
Evaluates tenant-wide risk profiles with inheritance down to provider, strategy and account.
- 02
Step 2
Runs pre-trade and post-trade evaluation, both recorded with the rule and outcome.
- 03
Step 3
Provides platform-level kill switches as a control the broker operates.
Questions
About ClonePips Risk
What does announced mean for ClonePips Risk?
The registry lists it as announced with no release date set. Rule scope and hosting are confirmed per deployment; availability statements on this site come from that registry.
What is an evaluation log?
The record of a rule run: which rule, against which scope, which action it decided and when — kept whether the outcome was allow, warn or block.
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 it with your venue in mind
Bring the venue, the execution setup and the fee model you run; the walkthrough covers the platform and the commercial basis.