The reasoning
Renaming a core piece of technology isn't something we do lightly. The decision reflected that the newer generation of the engine represents a meaningful step forward from the original, and continuing to describe it with the older name risked understating that progress, or confusing customers about which generation of the technology was actually managing their account.
What stayed the same
The account-level protections you rely on didn't change with the rename: your pre-set risk and drawdown limits, the independent safety layer that enforces them, and the regular "heartbeat" check-ins that keep your dashboard and our risk systems accurate are all unaffected principles, carried through from one generation to the next.
What you need to do
Nothing — this post is background for anyone curious about the naming history. Day to day, nothing about how your account is managed changes because of the name.
In detail
- The rename reflects a genuine generational step forward in the engine's own development, not a marketing refresh.
- Your account's pre-set risk and drawdown limits, and the independent safety layer that enforces them, carried through the rename unchanged.
- The engine's regular "heartbeat" check-ins, which keep your dashboard and our risk systems accurate, are also unaffected by the name change.
- We're documenting the naming history here mainly so older references don't read as confusing or contradictory.
One more thing
We weighed the rename carefully precisely because a name change to core technology can easily read as bigger or smaller than it actually is; our intent was for it to reflect a real generational step, no more and no less.
The underlying account protections — your own risk and drawdown limits, the independent safety layer, and the regular heartbeat check-ins — were a deliberate constant throughout, specifically so the rename wouldn't coincide with, or be confused with, any change to how your account is actually protected.