Frequently asked questions
Straight answers about what this is — and, just as importantly, what it is not.
No. PropOps Console is a simulated internal-operations console and a source-code starter. It demonstrates how a funded-trader back office is shaped, with seeded fictional data. It is not a live trading platform.
No. Payout actions only update database records and write audit rows. “Paid” sets a timestamp — there are no wires, ACH, cards, crypto, or treasury integrations of any kind.
No. There is no broker or exchange API, no FIX, no order routing, and no live or delayed market data. Account snapshots are seeded end-of-day demo values.
No. There is no identity verification, document checking, sanctions, or PEP screening. Cookie-based sessions are the only authentication flow.
The entire funded-trader domain: traders, accounts, plans, risk evaluations, payouts, and tickets are seeded fictional data, and the external Jira-like integration reads local mock fixtures with no outbound network. The architecture — auth, RBAC, audit, billing foundation — is real and runnable.
Yes — that is the point. It is a server-first Next.js starter: clone it, seed it, read the patterns, and extend the simulated domain with real integrations behind the same Server Actions and audit envelope.
An operations dashboard, trader / account / plan CRUD, a risk-review queue, a simulated payout pipeline, a support desk, a simulated integration with sync history, a global and per-entity audit log, PropOps role management, and a Stripe Free/Pro billing foundation — all i18n/RTL-ready.
Real money movement, broker / exchange / market-data integrations, real risk modeling, KYC/AML, a trader-facing portal, and any real prop-firm branding. These are intentionally out of scope and must not be implied.
No. PropOps Console is not a real prop firm and is not affiliated with, endorsed by, or connected to any real prop firm, broker, or financial institution. All names and identities are generic and fictional.
Next.js App Router with React Server Components, MUI, Prisma and Postgres, Stripe, i18next, and Zod. Server-first by design, with small client islands only where interactivity requires them.
A Stripe Free/Pro foundation: plans are defined in code and mapped to Stripe price IDs via env vars, with checkout, customer portal, webhook verification, and Pro gating. It runs in Stripe test mode and is a starting point, not a hosted subscription service.
Yes. English and Arabic ship out of the box with a runtime language switcher and fully RTL-safe layouts using theme direction and logical CSS — including the public site you are reading now.
Sign in and inspect the workflows
Walk the dashboard, push a payout and a risk item through their pipelines, sync the simulated integration, and read the audit trail — in English or Arabic.