Custom Indicators
Build your own market lens, then carry it into a governed strategy
Research teams can define organisation-specific indicator groups through a guided workflow covering the data source, schema, validation, field selection, computation, review and activation. An activated version exposes reusable indicator codes in charts and strategy configuration, subject to organisation access and data availability.
Software infrastructure only. No investment advice, no brokerage services, no guaranteed returns.
01 · Client experience
Broker digital channels
02 · The governed layer
Stretus AI Strategy Infrastructure
03 · Execution authority
Broker execution environment
Why does a broker need its own indicators?
Because a platform where every client computes the same twelve standard indicators offers nothing a competitor cannot offer. Proprietary research is the differentiator, and it is worth nothing if it cannot reach the place where strategies are actually built.
The usual outcome is that research lives in a spreadsheet or a notebook, gets discussed in a meeting, and never becomes an input to anything a client can act on. The gap is not analytical capability; it is the absence of a governed path from a computed series to a strategy rule.
What makes an indicator pipeline trustworthy?
Validation before activation, and versioning after it. An indicator that silently changes definition invalidates every backtest that used it, and an indicator whose data source degrades without anyone noticing produces confident nonsense.
So the workflow checks shape, history, field type, missing data and quality before a definition can be activated, and it treats each activation as a version rather than an edit. A strategy references a version, which means the strategy's evidence remains interpretable after the indicator moves on.
The four stages of a definition
| Stage | What is established |
|---|---|
| Source contract | Approved feed or organisation data, expected schema, and refresh policy |
| Validation | Shape, history, field type, missing-data and quality checks |
| Indicator definition | Raw fields, computed series, version, and reusable codes |
| Activation | Organisation entitlement, review state, and availability controls |
How does an activated indicator get used?
Through reusable indicator codes available in charts, scanner conditions, strategy rules and backtest context, without bypassing strategy validation or execution policy.
That last clause is the point. An indicator being available does not create a route around the gates: a strategy using a custom indicator passes the same deterministic validation and the same policy checks as any other. Research gains reach without gaining exemption.
What do dynamic scanners do, and what do they not do?
Scanners compose liquidity, momentum, data-quality and ranking conditions over an eligible universe to find and rank assets. They do not decide entries, exits or position sizes.
Stating the boundary explicitly matters because scanners are the feature most likely to be mistaken for advice. A ranked list is a research output; the decision about what to do with it stays with the person building the strategy, and the platform does not blur the two.
How does research stay connected to execution?
Four surfaces share one context: discover, construct, observe and investigate. Custom research feeds the builder; the builder feeds monitoring; monitoring feeds an investigation of why a specific order was allowed, blocked, filled, rejected or paused.
Keeping those connected is what makes a research asset accountable. An indicator that contributed to a strategy that produced an order is traceable in both directions, which is the property a review needs and the one a disconnected toolchain cannot provide.
What does a worked example look like?
A desk wants a liquidity-adjusted momentum measure of its own. It declares the source and expected schema, the platform validates shape, history, field types and missing data, the desk defines the raw fields and the computed series, and an activated version exposes a reusable code usable in charts, scanners and strategy rules.
The step that earns its keep is validation. A definition that assumes twenty periods of history and receives twelve is caught before a strategy is built on it, rather than producing a series with a silent gap that turns into a backtest nobody can explain.
The step that earns its keep second is versioning. When the desk revises the measure, the previous version continues to exist, so the strategies referencing it keep producing interpretable evidence until they are deliberately moved forward.
Where an activated indicator can be used
| Surface | What it does there | Still subject to |
|---|---|---|
| Charts | Plotted as a reusable series alongside price | Organisation entitlement and data availability |
| Dynamic scanners | A condition in a liquidity, momentum, quality or ranking filter | The scanner boundary. It ranks assets, it does not decide trades |
| Strategy rules | An input to entry, exit, filter, target or stop conditions | Deterministic validation and execution policy, unchanged |
| Backtest context | Evaluated historically alongside the strategy referencing it | The version the strategy was built against |
Availability on any surface depends on organisation access and data availability for the deployment.
What does this deliberately not do?
It does not let a research output bypass a gate. An indicator being activated grants reach, not exemption, a strategy using it passes the same deterministic validation, the same risk checks and the same policy gates as any other.
It also does not turn a scanner into a recommendation engine. A ranked list of instruments is a research artefact, and the platform keeps the decision about what to do with it firmly on the person building the strategy.
Surfaces
What each surface does
The product surfaces this page covers, named as they appear in the application.
- Indicators
- The client-side view of activated indicator versions and their reusable codes, available in charts, scanner conditions and strategy rules. A user sees the indicators their organisation has entitled them to, at the version those were activated at.
- Custom Indicators
- The administrative surface, present in both the broker console and the platform control plane, where a definition is created and governed: source contract, validation, computed series, version, and activation against organisation entitlement. Definitions are versioned rather than edited in place, so a strategy referencing one keeps producing interpretable evidence after the definition moves on.
Ownership boundaries
Where Stretus sits in the stack
Benefits
Business benefits
Differentiated research reaches clients
Proprietary indicator work becomes usable inside charts, scanners and strategies rather than staying in a notebook.
Versioned, so evidence survives
Strategies reference an indicator version, so a backtest remains interpretable after the definition evolves.
Validated before it can be used
Shape, history, field type, missing-data and quality checks run before activation, not after a strategy has relied on the output.
Entitlement-controlled
Availability is governed by organisation entitlement and review state, so a definition reaches only the users it should.
Use cases
Enterprise operating situations
Illustrative operating situations. Availability varies by broker, exchange, account, connector and tenant.
- Challenge
- Turn in-house analytics into something clients can build strategies with.
- Stretus role
- Define, validate, version and activate indicator groups, exposing reusable codes across the platform.
- Outcome
- Research that differentiates the platform instead of circulating internally.
- Challenge
- Use a proprietary computed series without exposing its construction to every user.
- Stretus role
- Scope activation by organisation entitlement and review state.
- Outcome
- Controlled reuse, with the definition visible only where it should be.
Security posture
Security considerations
- Source contracts are explicit
- An indicator is bound to an approved feed or organisation data source with a declared schema and refresh policy, so a silent upstream change surfaces as a validation failure.
- No exemption from strategy gates
- A strategy using a custom indicator passes the same deterministic validation and execution policy as any other.
- Freshness observable
- Indicator freshness is monitored alongside strategy state and events, so a stale series is visible rather than silently in use.
Answers
Frequently asked questions
Can indicators be edited after activation?
Definitions are versioned rather than edited in place. A new version goes through validation and activation, and strategies continue to reference the version they were built against until they are deliberately moved.
Do scanners generate trade signals?
No. Scanners find and rank assets over an eligible universe. They do not decide entries, exits or position sizes, that boundary is explicit in the product.
What data can an indicator be built on?
An approved feed or organisation data, with an expected schema and a declared refresh policy. Availability depends on organisation access and data availability for the deployment.
Ecosystem
Related capabilities
AI Strategy Builder
Natural-language strategy creation with deterministic validation: intent becomes a structured, reviewable rule set your client can read before testing.
Monitoring & Observability
Strategy health, order monitoring, latency, exceptions and connected audit evidence, retained for at least five years and identifying the actual user.
Backtesting Engine
Backtesting that applies brokerage, STT and slippage, then reports drawdown, risk-adjusted metrics and trade quality alongside return.
Arrange a working demonstration
Review strategy creation, F&O contract handling, backtesting, broker controls and integration boundaries with the team. If you would rather talk to an engineer than a salesperson, say so and we will arrange that instead.
Risk and disclosure
Trading and derivatives involve risk of loss. AI output requires review. Backtests and simulations do not predict future results; live outcomes can differ because of costs, latency, slippage, liquidity, rejections, broker rules and market conditions. Availability varies by broker, exchange, account, connector and tenant. Product information only; not investment advice.