The whole system. Clearly answered.

PRAETIR is a connected trading operating system for evidence-led performance review. It brings trading days, multi-account analytics, journals, plans, market context, community activity and AI-supported review into one continuous record instead of leaving them in separate tools.

PRAETIR is built for traders who want to examine how a result was produced, preserve the evidence behind each session and improve a repeatable process. It is especially useful when trades, accounts, notes, screenshots and plan rules currently live in disconnected places.

No. The journal is one evidence layer. PRAETIR also connects execution records, account and market contribution, risk and drawdown analytics, trading-plan compliance, setup behavior, market context, community surfaces and SENTINEL AI reviews.

A result alone shows what reached the account, not why it happened. The connected record keeps trades, timing, size, risk, plan rules, journal context and screenshots together so a review can separate repeatable process from luck, noise or hidden rule drift.

No. PRAETIR is designed for context, evidence and review. It does not provide trade signals, copy-trading instructions or a substitute for the trader's own plan and decision authority.

No. PRAETIR can make evidence easier to inspect and development priorities easier to measure, but it cannot remove market risk, guarantee profits or promise a particular trading outcome.

PRAETIR Systems is the performance-intelligence layer. It covers the trading cockpit, multi-account analytics, trading-day records, journal, trading plan, PRAETIR Sync imports, community access and personalized SENTINEL AI reviews.

PRAETIR Command includes Systems and adds the PRAETIR Trader chart workspace, ES and NQ GEX heatmaps, futures order-flow views, Market Intelligence, ATAS connectivity, delayed charts without ATAS and the active connectivity roadmap.

PRAETIR Guidance is the planned guided-development path. It is intended to connect PRAETIR Command, The Vault and direct coaching support to the same performance record. It is not part of the first Systems and Command release.

Exact launch pricing for PRAETIR Systems and PRAETIR Command will be announced before launch. PRAETIR Guidance pricing will follow later because that product is planned for a later phase.

Submit your name and email through the Early Access form. The request is reviewed manually and access is assigned in a controlled sequence. The form is a request for consideration, not a purchase or a promise of immediate access.

No. The public website does not collect payment for an Early Access request. Product status and pricing are communicated before any paid access step.

The product supports connected import paths such as PRAETIR Sync and ATAS transfer, CSV import and manual entry. The available path depends on the workspace and access level being used.

Yes. Multi-account analysis is a core Systems capability. Combined results remain traceable to individual accounts, markets and trading days so totals do not hide concentration, inconsistent sizing or account-specific behavior.

PRAETIR Sync is the Windows connection layer used to move execution data into the platform. The app includes a secure connection token, account matching, upload history and controls to renew or revoke that connection.

No. ATAS is one direct data path for compatible execution and order-flow workflows, but PRAETIR also supports other import methods. PRAETIR Command is designed to provide delayed chart access when ATAS is not connected.

No. Direct Rithmic connectivity is identified as roadmap work. It should not be treated as an active launch capability until its status is explicitly updated.

Not as a current product capability. Integrated order routing belongs to the roadmap. PRAETIR's present role is to connect context, execution evidence, analytics and review rather than take over trade authority.

P&L describes the account result, but it does not show whether the setup was valid, risk was controlled, timing matched the plan or a rule break happened to work. PRAETIR keeps the result connected to the evidence that produced it.

The analysis surfaces include net performance, account and market contribution, equity development, win rate, expectancy, drawdown and recovery behavior, risk efficiency and advanced ratios such as Profit Factor, Sharpe, Sortino and Calmar where sufficient data exists.

Yes. Setup and weekday heatmaps, entry-time analysis, sample size and execution-quality context help show when a pattern is actually supported by evidence instead of relying on a setup name or one memorable result.

Transfers and payouts can be recorded separately from trading performance. That keeps account cash movements from distorting the equity and performance record used for review.

Yes. Trading-day records and journals can preserve notes, screenshots and contextual evidence alongside executions. This helps compare what the trader saw and intended with what was actually executed.

The plan stores concrete rules such as session windows, approved setups, entry requirements, invalidation, risk limits and no-go conditions. Reviews can then compare the recorded execution with that declared standard instead of judging it from the outcome alone.

SENTINEL AI can work with the trader profile, current trading plan, recent trading days and executions, journals, prior reviews, rule violations, development tasks and trader memory. The goal is a connected review rather than a generic answer from one metric.

Trader memory preserves recurring behavior, previous review findings and active development priorities across sessions. It helps the AI recognize continuity instead of treating every conversation and trading day as an isolated event.

No. SENTINEL AI is designed for education, reflection, planning support and performance review. Its output is not financial advice and should not be treated as an instruction to enter, exit or size a trade.

No. SENTINEL AI does not execute orders, control an account or issue trade signals. Trading authority remains with the individual trader and the trader's own plan.

Personalization comes from the trader's own profile, goals, preferred markets, plan, evidence and development history. The same result can therefore be reviewed differently when the intended rules and recurring behavior are different.

The app interface supports adding context through attachments and voice input where those controls are available. Submitted material becomes supporting review context; it does not change the AI into an execution or signal service.

Market Intelligence organizes charts, news, volatility, VIX references and AI-supported summaries into preparation context. It is built to reduce scattered research, not to declare which trade a user should take.

The current product surfaces reference ES, NQ, CL, GC, SI and 6E for market screening and context. Availability can differ by view, data connection and release status.

The defined GEX heatmap scope is ES and NQ. Other markets may appear in broader chart or screening contexts, but they should not be assumed to have the same GEX coverage.

No. Market data can be delayed depending on the selected connection and access state. PRAETIR Command is designed to expose delayed charts without ATAS, while connected data paths can provide different depth and timing.

No. These surfaces provide context that a trader may compare with an existing plan. A level, heatmap, headline or AI summary is not presented as a guaranteed setup or an instruction to trade.

PRAETIR Trader is the Command chart environment. Its defined scope includes chart workspaces, GEX and futures order-flow views, market screening, ATAS connectivity and multi-chart workflows, with additional connections separated as roadmap items.

The community combines structured market channels, announcements, activity, performance context, coach resources and a live Trading Floor. Its purpose is accountable development around shared evidence, not high-volume chat for its own sake.

The Trading Floor is a focused live voice room where members can share market context and visible presence. Conversation can be shared, but every member remains governed by an individual plan and retains personal trade authority.

No. Shared observations, coach briefings and member discussion are context. They are not copy-trade calls, and the room is explicitly structured to keep shared information separate from individual execution authority.

Community surfaces can show verified participation, session activity, setup statistics, equity context and leaderboard-style records. These views are intended to make process and participation visible, not to promise future results.

PRAETIR Guidance is planned for a later phase after Systems and Command. The intended path includes direct coach support connected to the same evidence and performance record, but it should not be treated as currently available until its status changes.

The Vault structure is planned and its course framework is defined, but lesson videos and final delivery are still in production. It is therefore presented as coming soon rather than as a complete live course library.

The form collects first name, last name and email address. It may also record limited attribution details such as the page path, referrer or campaign parameters, plus technical request information needed to deliver and protect the service.

Waitlist records are stored in a protected Supabase database. The public website is built and delivered with Base44 and supporting infrastructure providers that process information as needed to operate and secure the service.

No. Waitlist information is not sold. It is disclosed only to service providers needed to operate the site, when required by law or when necessary to protect users, the service and its integrity.

Yes. You can contact PRAETIR to request access, correction, deletion, restriction or other applicable privacy action. The team may need enough information to verify and locate the relevant record.

Connection surfaces use account access controls and, for PRAETIR Sync, a dedicated token that can be renewed or revoked. Never send passwords, broker credentials or other sensitive access details through public forms or ordinary support messages.

Use the Contact page for product questions, Early Access, partnerships, support or privacy requests. Include the relevant workspace or issue context, but do not include passwords, broker credentials or other secrets.