Learn. Invest. Trade. Automate. Analyse. Evolve.

Open-source self-hosted trading software for local research, sample-data testing, manual orders, automation, and AI-assisted workflows. It runs in the browser from your own machine. A desktop shell comes after a checksummed Electron release.

v0.0.1 is not production ready. Use Practice and example data first; Live mode remains your own risk.

Five native adapters with evidence-gated availability
Practice, Connected (read), and Live
Option chain, Greeks, order flow, and depth
Strategy lab, SIP tracking, and AI context

Install the self-hosted web app. Nothing else needs to be installed first.

macOS / Linuxterminal
curl -fsSL https://flinttrade.vercel.app/web-install.sh | bash
Windows 10/11terminal
irm https://flinttrade.vercel.app/web-install.ps1 | iex

Electron installer pending. Desktop guide

FlintTrade cinematic welcome screen
FlintTrade trade canvas
Strategy lab
GatewayBroker connections use the native gateway. Native broker HTTP is frozen until Task 9D and Task 7C.2; adapters stay evidence-gated behind credential, ACL, and SDK checks.
18Package surfaces across Python, React, shared UI, Rust/PyO3, and the Electron desktop shell.
71Terminal widgets described by the public contributor documentation.
AGPLNetwork-use source sharing keeps the self-hosted stack accountable.

Built for people who read the source.

The public site stays close to the repository. Root docs, package READMEs, screenshots, and contribution commands are generated into the site rather than rewritten in a second place.

A self-hosted workflow workspace

React, FlexLayout, Python services, Rust tick processing, and the native broker gateway in one inspectable workspace. Native broker HTTP is evidence-gated and frozen until Task 9D and Task 7C.2.

Safety before automation

Practice, Connected (read), and Live keep simulated fills, broker reads, and live orders apart. Example data is not a Mode.

Agent-ready contribution docs

Generated docs indexes, llms files, and read-only MCP tools help contributors understand the repo before editing.

Docs, API, and contribution paths in one flow.

Start with product usage, move into architecture and endpoint contracts, then use the MCP tools to orient local development work.

Contributor MCPread-only
{
  "mcpServers": {
    "flinttrade-docs": {
      "url": "https://flinttrade.vercel.app/api/mcp"
    },
    "flinttrade-local": {
      "command": "npm",
      "args": ["run", "mcp:stdio"],
      "cwd": "packages/apps/site"
    }
  }
}

MCP for development, not trading.

The site exposes docs search, package maps, path explanations, test recommendations, and contribution prompts. Broker credentials, account state, funds, order IDs, and order placement stay outside this MCP surface.

MCP setup

Package map at contributor speed.

Each package README becomes a docs page and MCP resource, so agent-assisted development starts from the same public source a human contributor reads.