Straight answers about how this works.

A trading operating system that takes a signal from your strategy and executes it across many broker accounts at once, with risk rules applied per account. It handles the whole path: signal intake, identity and validation checks, risk enforcement, routing, execution, and logging. You supply the strategy and the broker accounts. The OS is the infrastructure between them.

GhostTrader is the company. GhostTraderOS is the product, the trading operating system. GhostFund is the company's own private fund, run on that OS with the company's own capital. GhostTraders are independent operators running their own funds on the same infrastructure.

Traders who already have a working strategy and want to run it across more than one account without managing each one by hand. That means multi-account traders, prop firm account holders, and small fund operators. If you are looking for a strategy to trade, this is not that. The OS executes your edge, it does not supply one.

No. Strategies sit outside the OS, the same way your broker does. GhostTraderOS defines a standard signal payload so any strategy you write, on TradingView or elsewhere, can talk to it correctly. GhostFund runs its own private strategies on the system and those are not distributed.

No, and the distinction matters. A trade copier is one component inside the OS, used to mirror one strategy across your own accounts with each account's own risk applied before the order goes out. You are not following someone else's trades, you are distributing your own signal.

The signal enters at the source layer, then hits the gate, which checks identity, catches duplicates, and validates the payload. It then passes the risk engine, which applies system-level and account-level rules. The router maps it to the accounts registered to that strategy, and a receiver running on your own machine places the order at your broker.

Five source types are in the v0.003 design: TradingView alerts, Telegram signals, API or script calls, manual signals entered by the operator, and an account connector. Each source carries its own auth token and can be revoked on its own. Every source is normalized into one internal format before anything downstream sees it.

The piece that runs on your machine and talks to your broker terminal. It holds three things only: a consumer ID, the server URL, and a token. Everything else, the strategy it follows, its risk profile, its limits, lives server side and gets pushed down to it, so there is one source of truth and nothing to keep in sync by hand.

MetaTrader 5 is live and is what GhostFund runs on today. A NinjaTrader 8 receiver for futures is built. Crypto exchanges, cTrader, and Interactive Brokers are on the roadmap and not built yet.

Yes. An account carries a market tag (crypto, forex and CFDs, futures, stock) and a platform as two separate fields, so you are not locked into one platform per market. The only constraint is that the platform has to support the market you tagged, which is why NinjaTrader 8 cannot be tagged crypto. Tagging also groups accounts, so you can pause or report on every crypto account in one action.

The current live build polls, so a receiver picks up a signal within roughly half a second. v0.003 replaces polling with push, where signals go out the instant they are ready and receivers push events and equity back immediately. That rebuild is in development, so the push path is not something you can use today.

No. GhostTraderOS never holds funds and never holds broker credentials. You log into your own broker terminal yourself and attach the receiver to it. The system sends execution instructions to a terminal you are already authenticated on, so your capital never leaves your account and never passes through us.

No, and there is nowhere to enter one. You log into your broker terminal on your own machine, and the receiver attaches to a session that is already authenticated. That is the whole reason the OS can execute without ever storing a credential.

Open positions stay where they are, at your broker. The receiver keeps managing them from cached risk limits if the connection drops, and every trade carries a broker-side stop loss that holds whether or not the OS, your machine, or your internet is reachable. New signals stop until the connection is back.

At the account level: daily drawdown, total account drawdown, max open trades, margin protection, and a manual pause. At the system level: news windows, market-closed and weekend blocks, and a global drawdown default for accounts that set none. There is also a strategy health gate that pauses a strategy when its win rate or other thresholds degrade.

From the account's own sizing mode: a percentage of balance, balance divided by ten, or a fixed cash amount. The stop loss is corrected for broker constraints first, then the lot is calculated against that corrected stop, so the risk you set is the risk you actually take. Optional equity auto-scaling grows size above a base floor as the account grows.

Yes, and there are two levels. Blackout mode blocks new signals while leaving open positions alone, which is the maintenance setting. The kill switch is the emergency one: it closes every open position and turns blackout on. A separate weekend auto-close flattens enabled accounts at the Friday cutoff.

A broker account you already hold, a strategy that can fire an alert, and a machine that stays on. The receiver runs on Windows alongside your broker terminal. Most operators run it on a VPS rather than a home PC, because a machine that sleeps, drops Wi-Fi, or loses power is a machine that misses trades.

The installer places the receiver, connector, and watchdog on your machine once, and registers the machine. After that, creating an account in the dashboard spawns an instance with its connection details already filled in, so there is no ID or token for you to type. You log into your broker, attach the preconfigured connector to a chart, and it fetches its full profile from the server.

Yes. Self-hosting is what the OS installer exists for, and it sets up the runtime, services, reverse proxy, and config on your machine. It is for licensed operators rather than open download. A hosted option, where the OS is already installed and there is nothing for you to set up, is planned.

To run the OS, no. To have something worth running, yes, at least enough to write a strategy that fires an alert carrying the standard payload: bot name, symbol, direction, entry, stop, target, and action. A Pine Script library that handles that formatting for you is planned and not published yet.

Yes, that is the normal case, and it is what the multi-account design exists for. Each account gets its own instance with its own identity, its own risk profile, and its own limits. How many a given machine can carry depends on its specs, so the installer reports capacity when it registers the machine and gates new instances against it.

No pricing is published yet. GhostTraderOS v0.003 is in development and access is by waitlist, not purchase. Any GhostTraderOS price you see quoted somewhere else did not come from us.

Join the waitlist. That is the only route right now, and it is for early access to v0.003 when it is ready. There is no self-serve signup and no trial.

No. GhostFund is the company's own private fund running the company's own capital, and it is not open to outside money. It exists as proof the system runs live on real capital, not as a product you can buy into.

A set of trading tools is planned as free with no account needed: the indicators run on the company's own charts, a position risk calculator, and a trade journal. All three are listed as coming soon. None of them are downloadable yet.

That is what the Signal Feed and AutoTrader layers are for, and both are licensed rather than open. Signal Feed publishes a chosen strategy's signals to subscribers who view them and act for themselves. AutoTrader executes on external users' accounts inside an isolated box that receives signal copies and can never write back into your own fund's trading. Both are specified in the v0.003 blueprint and neither is shipping.

An earlier build, v0.002, runs live every trading day on real capital in the company's own fund. v0.003 is a ground-up rebuild and is in development, not released. Where the site says v0.003, it is describing what is being built, not what you can use today.

No date is set and none is published. The build runs component by component with no shipping deadline attached to it. The waitlist is how release gets announced.

The architecture is specified component by component, and that blueprint is complete apart from the Optimizer, which is deferred on purpose. Specification is not code. Individual components sit at different stages of implementation, and the honest summary is that v0.003 is a design being built out, not a finished system in testing.

v0.002 polls, which puts a fixed delay on every signal, and its structure grew over time rather than being designed. v0.003 is built around push, so signals reach receivers the moment they are ready and receivers push events back with no polling interval. It also splits the system into components with clear ownership, so one part failing cannot quietly take another down with it.

Receivers for crypto exchanges, cTrader, and Interactive Brokers. The Optimizer, which studies collected strategy telemetry against real wins and losses to find what conditions a strategy actually performs in, is deferred until there is enough data to make it trustworthy. The free community tools and the receiver setup guides are also queued.