> For the complete documentation index, see [llms.txt](https://docs.gevulot.com/gevulot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gevulot.com/gevulot-docs/firestarter/overview.md).
# Overview
Firestarter is a high-performance compute network optimized for ZK. It is designed to scale to thousands of prover nodes handling both CPU and GPU workloads, as well as incorporate new hardware as that becomes available. Users can generate proofs using one of the pre-deployed provers, such as Risc0, SP1, Nexus, Aztec, ZKsync, Starkware, Linea & Polygon, or by deploying their own.
Under the hood, Firestarter is an end-to-end implementation of Gevulot’s ZkCloud, just running in a permissioned fashion. The full system is made up of a blazingly fast CometBFT-based chain, which handles Credits, workload allocation and monitoring, and a network of prover nodes that provide compute for generating and verifying zk proofs.
---
# 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://docs.gevulot.com/gevulot-docs/firestarter/overview.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.