Learn
The ideas behind the platform, explained once.
Short explainers on how ProjectX works and why: the decisions behind the products, in plain language, with links to where each idea is put to work.
Explainers
A provider-blind cloud
You order a machine class and a region in the platform’s own vocabulary. Which capacity serves it is decided at provision time, so nothing you write names a provider.
Residency before placement
Where something may run is decided before where it will run. Residency rules filter the candidates first, so placement can only ever choose a compliant one.
An open lakehouse
Tables in the open Iceberg format, behind a standard catalog, on object storage you choose. Any engine that speaks Iceberg can read them, and every write is a snapshot you can return to.
One decision point for every permission
Every service asks the same policy decision point whether an action is allowed, and every answer carries its reason. There is no second, quieter path to the data.
A tamper-evident audit
Every allow and every deny, from every pillar, lands in one hash-chained record that can be verified, exported and kept under legal hold.
Searching video in plain language
A sentence is read into objects, attributes, places and times. Only what the parser is sure of becomes a filter; the rest ranks results, and every result says why it matched.
Questions that cross systems
A question is split into one request per system that holds part of the answer, each authorized as the person asking, and the parts are joined on people, resources, time and place.
Agents that stay accountable
An agent is a principal of its own with scopes and a budget. It acts only within the narrower of its own and its user’s permissions, destructive steps wait for a person, and every step is traced.
How Platform Credits work
Every product is priced in one unit, Platform Credits, at a published rate per meter. Usage draws from one balance, and one invoice covers everything.