Frequently asked questions.

The development platform end to end: data, features, experiments, backtesting with provenance, a registry, deployment to monitored paper sessions on real market data, and workspaces. Evaluation records and discovery on the marketplace. In-app courses.

Every dataset declares keys and a timestamp; every read is as-of a moment; training frames are assembled from what was knowable at each row's decision time; joins are as-of; label windows are explicit. These are properties of the read path.

Yes. Per-organization isolation at the data layer; you control what is listed.

Yes. The browser workspace is a convenience; the SDK is the interface.

Evaluated under the platform's methodology (point-in-time data, out-of-sample discipline, order-book-fidelity backtesting, live observation) with a reproducible record. It is a mechanical property of the record. It is not an endorsement.

Economics for builders are being designed within the appropriate regulatory framework and are not yet offered.

Live sessions are paper today: real data, simulated fills. Real-money execution comes after the regulatory and venue work it requires.

No. Promethean is a technology platform. It does not run strategies for capital, manage assets, or offer investment products.

No. The marketplace lists strategies with standardized, reproducible evaluation records, and access, when offered, will be through the appropriate regulated structures.

No.

Infrastructure for composing many specialized strategies against objectives and constraints, and the direction of the company. Any product built on it for investors would be offered through an appropriately registered structure.

Live data today is digital assets. The platform is asset-class-agnostic, and expansion follows venue and regulatory work.

We intend to open specific components (the SDK, agent interfaces, possibly parts of the feature store) as their surfaces stabilize. The value is in the integrated platform and the evidence it produces.

One source of truth. Every service has a Rust core; Python is a thin binding; the web application is Rust compiled to WebAssembly, so the SDK and the interface share real code.

Yes. An organization can run Promethean as its internal research platform with its own identity provider and isolated namespaces. Mention it when you request access.

Request access and say what you are building or what you represent. We onboard by cohort.