> For the complete documentation index, see [llms.txt](https://docs.beamable.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beamable.network/project-documentation/readme.md).
# Whitepaper
Gaming is a $200B+ per year global market with billions of end-users worldwide. One of the most complex aspects of this business is that games are no longer simply software—they are “Live Services,” in which games are maintained online and often generate revenue as people continue to consume them. Game companies spend billions of dollars on cloud-based infrastructure, backend technology, and siloed development efforts to support this business model. Yet these initiatives often come with massive amounts of risk, technical debt, and dependencies on centralized providers who can disrupt the operations of games.
Game development has a unique set of technical requirements—statefulness, high concurrency, latency optimization, development workflow integration, and interoperability between core components (accounts, inventory, social systems, etc.)
Beamable is creating the first decentralized physical infrastructure network (DePIN) to support the backend and Live Services requirements of game developers. Our network is built around several principles:
* Sustainability of the network through decentralized ownership of physical infrastructure—de-risking the network for all of the games on it.
* Composability of software built on top of the network, enabling an ecosystem of third-party plugins with built-in scalability. These modules add value to all games on the network—while providing revenue incentives for independent backend developers.
* Enterprise-grade infrastructure nodes to ensure that the network delivers the high quality of service and performance necessary for the most demanding games.
* Superior unit economics results from the network's ability to pair gaming workloads with appropriate and cost-optimized compute providers and absorb burst-traffic by aggregating across large network capacity.
* Standardization of workflows, deployment processes, and data objects to help accelerate game development velocity, predictability, and reliability.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.beamable.network/project-documentation/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.