Tradiator Documentation

Overview

Tradiator is a trading journal and analytics platform for funded futures traders. Log trades, write daily playbook entries, track evaluation costs and payouts, analyze performance, and document strategies — all in one dashboard.

Tech Stack

Roles & Access

Three user roles. All role checks happen server-side via requireRole() on every page and API route — cannot be bypassed from the client.

Plans

Users can be on free, pro, or premium. Free users see a banner. Plan is stored in profiles.plan and the subscriptions table.

Dashboard

Main landing page after login. Route: /dashboard. Shows aggregate performance stats, equity curve, recent trades, and recent journal entries.

Stat Cards

Time Filters

Tabs across the top: Today, 1W, 1M, 3M, 6M, 1Y, All, Custom. Custom allows a date range picker. All stat cards and the equity curve respond to the active filter.

Log Win / Log Loss Buttons

Top-right on desktop (large buttons), floating pill buttons bottom-right on mobile. Log Win pre-fills direction as Long; Log Loss pre-fills as Short.

Recent Journal Feed

Right panel shows the last 3 journal entries with mood badge, title, bias, and notes preview.

Trade Logging

Every trade is stored in the trades table. Trades can be entered manually, created from the Trades page, or imported via CSV.

Trade Entry Form Fields

R-Multiple Auto-Calculation

// Long
R = (exitPrice - entryPrice) / Math.abs(entryPrice - stopPrice)

// Short
R = (entryPrice - exitPrice) / Math.abs(entryPrice - stopPrice)

Trades Page — /trades

Table of all trades. Supports multi-select bulk delete, inline edit via pencil icon, and click-to-detail.

Post-Trade Reflection Popup

If enabled in Preferences, a reflection dialog appears after logging any trade. Can be toggled off in Settings → Preferences.

Playbook Calendar

Route: /journal/calendar. Monthly grid where each day cell shows that day's net P&L and trade count. Green = profit, Red = loss.

Cell Behavior

Journal Day View

Route: /journal/calendar/YYYY-MM-DD. Full-page view for a specific trading day. Only reachable when a day has an existing journal entry.

All Sections Displayed

1. Header Pills — Mood, Bias, Star rating, Rules followed, Net P&L + trade count
2. Pre-Market Plan — Full text, whitespace preserved
3. Post-Session Notes — Notes written after the close
4. Setups Traded — Badge list
5. Sessions Traded — Badge list
6. Improvement Focus — One thing the trader was working on
7. Trades Table — Symbol, Direction, Contracts, Entry, Exit, Net P&L, R, Setup

Insights & Analytics

Route: /insights. All calculations happen server-side from trades and journal_entries tables on every page load.

Computed Metrics

Strategy Library

Route: /strategies. Stored in the strategies Supabase table — not localStorage. Scoped per user via RLS.

Strategy Fields

CRUD Flow

Eval Expenses & Payouts

Route: /eval. Stored in eval_expenses and eval_payouts Supabase tables — not localStorage.

Stats Cards

🏆 Congratulations Banner

When a payout is saved, a gold pill banner drops from the top center. Shows trophy icons, amount, and firm name. Auto-dismisses after 5 seconds.

CSV Import

Route: /import. Supports Tradovate, ProjectX/Rithmic, and Generic CSV formats.

1. 1
   Select Platform

   Choose: Tradovate, ProjectX, or Generic.

2. 2
   Select Account

   Pick which trading account to attribute these trades to.

3. 3
   Paste CSV

   Paste raw CSV text into the textarea.

4. 4
   Preview Parsed Rows

   System shows a preview table of mapped trades before import.

5. 5
   Confirm Import

   Sends to POST /api/import-csv which bulk inserts into trades table.

Account Settings

Route: /settings. All changes save to Supabase in real time.

API Reference

All routes under /api/* as Next.js Route Handlers. Every route verifies auth. Unauthenticated requests return 401.

Trades

Journal Entries

Strategies

Eval Expenses & Payouts

Other

Error Format

// Success
{ data: {...} }

// Error
{ error: "Error message here" }  // HTTP 400, 401, 403, or 500

Database Schema

All tables in public schema of Supabase (PostgreSQL 15). Every table has Row Level Security enabled.

profiles

trades

journal_entries

Other Tables

Auth & Security

Authentication Flow

requireRole() — How It Works

const { user, profile } = await requireRole(["user", "moderator", "admin"]);
// 1. Gets JWT user from Supabase Auth
// 2. Fetches profile row from DB (role, banned, plan)
// 3. Checks role is in allowed array
// 4. Checks banned = false
// 5. Updates last_seen timestamp
// 6. Returns user + profile — or redirects to /login

Security Summary

Test Scenarios & Checklist

Each item should pass without errors on a fresh user account unless noted.

🔐 Authentication

📊 Dashboard

💹 Trade Logging

📅 Playbook Calendar

📝 Journal Day View

🗂️ Strategies

💰 Eval & Payouts

📥 CSV Import

⚙️ Settings

📱 Mobile