FAQ

Questions, answered.

Common questions about how Promethean works, and how the money and safety pieces fit together.

The full stack: the developer platform — feature store, pipelines, registry, remote execution — plus the investor marketplace, backtesting engine, and paper trading. It's built infrastructure-first, because a marketplace on top of flaky infra publishes garbage strategies. We open access in waves as we onboard developers and investors.

When a developer publishes a strategy and an investor subscribes, the developer earns a share of both the monthly subscription and the performance fee. The performance fee is 25% of annual profit, split 70/30 in the developer's favor. Promethean handles billing, payouts, and tax reporting.

You browse strategies, filter by risk and performance, and subscribe for a monthly fee plus a performance fee on realized profit. You set risk limits (max drawdown, stop-loss, position size) per subscription. Cancel anytime.

Regulatory compliance is a first-class concern. Promethean is an infrastructure platform — we do not provide investment advice, broker-dealer services, or custody. Every strategy carries its own specific regulatory disclosures, and investor funds are custodied through appropriate partners, not by us.

Crypto-first. Cryptex is the first adapter, with Binance close behind. Equities, derivatives, and forex are on the longer-term roadmap behind execution infrastructure and regulatory work.

Yes. Enterprise clients — hedge funds, prop shops, fintechs — can run Promethean as their internal ML trading platform. Your own OIDC identity provider, isolated namespaces, audit trails, no vendor lock-in on identity. If that's you, mention it in the waitlist form and we'll reach out directly.

Not yet, and likely not in full — but we intend to open-source specific components (SDK, MCP servers, possibly pieces of Ember) once the platform is stable enough that we're confident in the surface area. The proprietary value is in the integrated platform and marketplace, not any single crate.

One source of truth. Every service has a Rust core; Python is a thin PyO3 binding for SDK ergonomics. The web app is Dioxus/Rust compiled to WASM so the SDK and the app share real code — no bifurcation between "how the platform works" and "how the UI talks to it." Performance, memory safety, and maintainability compound in our favor over years of build.

Join the waitlist on the landing page or via the developer / investor pages. We onboard in waves and prioritize by fit — if you're an active quant or an experienced investor, mention it in the message box.