> For the complete documentation index, see [llms.txt](https://inferra.gitbook.io/inferra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inferra.gitbook.io/inferra-docs/roadmap.md). # Roadmap Inferra is built in a deliberate order: real commerce first, then an open supply network, then a public price for compute, and finally compute as an asset class. Each step stands on its own and sets up the next. ### Real compute commerce Rent real GPUs from verified providers, pay in USDC through an on-chain escrow, and take delivery of a machine over SSH. This is the foundation: a working marketplace where compute actually changes hands and a provider is paid only for what they deliver. ### An open supply network Supply opens up. Anyone can bring hardware and become a provider by bonding stake, without asking permission, while delivery stays provable and anti-sybil controls keep the network honest. Curated supply becomes a network. ### A public price for compute As real volume builds, the GPU-hour index becomes a public price for compute that anyone can read. A provider can price against it, a buyer can plan around it, and it holds value as a benchmark on its own, with no trading required. ### Compute as an asset class With a real, published price, compute becomes something you can hedge and invest in. A liquid index and a forward curve let teams lock in the cost of the GPU time they will need, providers lock in forward revenue, and builders create products on top, from prepaid compute to tools that buy and hedge compute directly. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://inferra.gitbook.io/inferra-docs/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.