MADO Risk: capabilities and coverage boundaries

What does MADO specialize in?

The starting specialty is trading risk-governance software: defining a policy, checking risk around a decision, and retaining an explanation of the result. This is distinct from choosing trades, managing client money, or selling entry and exit signals.

MADO is the company and brand; MADO Risk is the product at the beginning of the access journey. Markets, Intelligence, Capital and Labs have their own disclosed development stages. Those names do not make them automatically available within a Risk subscription.

Who should evaluate MADO Risk?

Individual traders seeking clearer account limits, teams seeking shared policies and reviewable records, and institutions discussing a defined integration and permissions scope. Fit is established before activation, not guaranteed by selecting a plan.

For a funded account, a platform or funding-company name is not enough. Establish the loss definition, treatment of unrealized loss, reset time, static or trailing drawdown, and every order-entry channel. This page does not claim universal broker or prop-firm compatibility.

What can you inspect publicly today?

The MADO Risk page includes an illustrative decision lab running in the browser. It compares a hypothetical request with example limits and remaining budget. It does not connect to a trading account or submit or block real orders.

A calculator, pricing page and application form are not evidence of live execution coverage for your account. Website availability or a successful interface test also does not establish that market losses will remain within a chosen amount.

What must be confirmed before integration?

Identify the covered accounts, instruments and order-entry channels, the balance and position data sources, acceptable data age, and granted permissions. Separate what is calculated or displayed from what the system can actually intervene in.

A pre-trade check requires the order to pass through the checked path. A risk-reducing action after a position opens has a different timing and execution exposure. A rejection record on a screen does not prove that an order from another channel was blocked; trace the request to the intended execution point.

What does MADO Risk not promise?

No trading signals, personal investment advice, discretionary management of client money, profit guarantees, guaranteed funding-challenge completion or prevention of loss. Market outcomes remain distinct from compliance with an operating policy.

Do not infer regulatory approval, security certification or an independent audit from visual design or the word professional. Such claims require a reviewable report with an identified scope and date. This page makes no claim to such approval.

How does evaluation start?

Start with the public example, then describe your needs through the access form or discuss a team or institutional scope. Review compatibility and boundaries before agreement and activation. Applying is not acceptance and does not create an automatic payment.

Do not submit a trading-account password in a contact form. Request a documented connection method and permission scope, and test in a non-live environment before deciding on production use.

Evidence to request before activation

Coverage

Covered and excluded accounts, channels and integrations, with product version and evaluation date.

Limit definitions

Calculation basis, costs, open positions, reset behavior and mapping to any funding-company definitions.

Decision trace

Inputs, policy version, explanation, timestamps and the observed result on the connected execution path.

Failure cases

Test results for stale data, lost connections, concurrent requests, restarts and permission boundaries.

Go-live decision

Reviewable results, disclosed limitations, stop and rollback procedures, and a written scope rather than one successful screenshot.

This is an evaluation checklist, not published test results or a guarantee of capabilities that have not been confirmed in your environment.

A practical evaluation worksheet

Start with eight non-live scenarios and record the product and policy versions, covered channel, observed outcome and evidence reference. Every case in the template is unexecuted: define expectations before testing and do not treat this worksheet as a success report or certification.