Getting started

You're in. Here's how Detent goes live.

One payment, and Detent is yours. It runs on your own machine, against your own broker, holding the limits you set. This page walks you from paid to enforcing.

01 • Your files

Key and download, by email

Your license key and download link came by email after your payment. The download is the full editable Python source, the config templates, and the docs. The license unlocks the download and future updates — it does not lock the software, and it never reaches into a live position. The source is yours to read and edit.

02 • Install

Your own machine, attended

The installer ships everything it needs, Python included — nothing to set up first. Detent runs local and attended: on your own personal device, with you watching while you trade. It is not a hands-off bot, and it is not a cloud service — most prop firms forbid remote or unattended automation, and Detent is built to fit inside those rules. The install guide is in the download's docs.

03 • First run

Connect, set your rules, observe

A short first run in the Config panel. It ends in observe mode until you choose to arm it.

The first run, step by step

The first run takes you from broker connection to enforcement: connect your broker, set your rules in the Config panel, review the armed set as sentences, then run it in observe mode before you arm it. Every protection rule ships on and explains itself in plain English. The one exception is the daily trade cap: there's no honest default for how many trades a day is too many, so you pick that number yourself. Accept the rest and you're still protected. The setup flow on the How page walks through it in full.

What leaves your machine: nothing

The security model is structural, not a promise — same posture as the architecture page.

Credentials

Encrypted, local, yours

Your broker credentials are stored encrypted on your machine and never sent anywhere else. There is no Detent server for them to pass through.

Connections

One outbound line: your broker

The engine's only outbound connection is to your own broker's API. Your market data, positions, and audit log stay on your device.

Runtime

Your trading never leaves your machine

No trade data, no positions, no audit log, no usage tracking — none of it is sent anywhere. The one thing that does leave is a license check: the app confirms your key is valid and which machines it runs on. That check carries your key and a device identifier. It never carries a trade.

Fail-safe • the honest limit

It has to be running

Detent enforces only while it's running and connected. Your stop lives at your broker as a real order, so it holds even if Detent or your connection drops. Full detail is on the architecture page.

Updates

By email, and on the changelog

New versions are announced by email and listed on the changelog, each with a checksum and signature to verify before you run. That page also shows how the bundled update helper installs a release without touching your edited config.

Support

Lost key, license, questions

Re-send a lost key or manage your license through the order provider's customer portal — the link is in your delivery email. For anything else, use the contact method on this site. The legal page has the license, terms of sale, and the 7-day refund policy.