Veerhelm Trading algorithmic trading interface displayed across monitors
Feature Overview

Every module, built for disciplined execution

A detailed look at how Veerhelm Trading structures signal generation, risk controls, and reporting into a single consistent framework — with no step left to discretion.

Core Framework

One system, four disciplines

Veerhelm Trading is organised around a fixed sequence: market scanning, entry-point calculation, exposure limits, and record-keeping. Each discipline operates independently but reports into the same parameter set, so nothing runs outside the defined rules.

  • Rule-based entry logic with no manual override during live sessions
  • Fixed exposure ceilings applied before any position is opened
  • Every action logged with timestamp and triggering condition
  • Parameters reviewed on a set schedule, not adjusted ad hoc
Veerhelm Trading dashboard showing structured feature modules
Detailed Breakdown

How each feature behaves in practice

The sections below describe what each module does, how it's constrained, and what it is designed to prevent.

Entry-point calculation

The core engine evaluates incoming market data against a fixed set of conditions. It does not predict direction — it identifies whether current conditions match a pre-defined entry profile, and acts only when they do.

Benefit: Removes hesitation and second-guessing from the entry decision, replacing it with a consistent, repeatable check.

Scan frequencyContinuous
Decision basisRule match
Manual overrideDisabled in live mode
Output loggedYes, per event

Exposure and position limits

Before any position is opened, the system checks it against a ceiling for size, concurrent exposure, and daily allocation. If a proposed action would breach a limit, it is not executed — there is no exception path.

Benefit: Keeps total exposure within a known boundary at all times, regardless of market conditions or signal volume.

Position ceilingFixed per account tier
Daily allocation capSet in advance
Breach handlingAction blocked
Review cycleScheduled

Session and schedule controls

Trading activity is restricted to defined windows aligned with market liquidity conditions. Outside those windows, the system remains idle rather than attempting to force activity.

Benefit: Avoids participation during periods the framework was not designed to handle, reducing exposure to irregular conditions.

Active windowDefined per instrument
Idle stateDefault outside window
Schedule changesLogged with reason
Holiday handlingPre-configured

Record-keeping and reporting

Every evaluated condition, triggered action, and parameter change is written to a persistent log. Reports are generated on a fixed schedule rather than compiled retroactively.

Benefit: Provides a complete, unedited account of system behaviour for review, without relying on memory or reconstruction after the fact.

Log retentionContinuous
Report cadenceFixed schedule
Editable after writeNo
Export formatStandard statement
Supporting Capabilities

Additional modules within the framework

These features operate alongside the core discipline sequence to maintain consistency and oversight.

01

Parameter locking

Operating parameters are fixed for a defined review period and cannot be altered mid-cycle, preventing reactive adjustments driven by short-term results.

02

Condition monitoring

The system continuously checks that live market data falls within the ranges it was configured to handle, flagging anything outside normal bounds.

03

Access segregation

Configuration access, execution access, and reporting access are kept separate, so no single function can alter another without a recorded step.

04

Scheduled review points

Performance and parameter reviews occur at set intervals, keeping adjustments structured rather than triggered by individual outcomes.

05

Statement generation

Account activity is compiled into standard statements at fixed intervals, giving a consistent reference point for ongoing review.

06

Fail-safe idling

If a required data input is missing or inconsistent, the system defaults to an idle state rather than proceeding on incomplete information.

Technical Parameters

What governs the system in practice

A summary of the operating constraints that define how Veerhelm Trading behaves once active.

Decision basisPre-defined rule set
Manual interventionNot available during live sessions
Exposure ceilingFixed per account configuration
LoggingContinuous, non-editable
  • Parameters locked for the duration of each review period
  • Configuration and execution functions kept separate
  • Idle default applied whenever input data is incomplete
  • All changes to settings recorded with timestamp and cause

These parameters describe the general structure of the framework. Specific settings, limits, and schedules are configured per account and reviewed on an ongoing basis.

See the full feature set in context

Request access to review configuration options and how each module applies to your account.