> For the complete documentation index, see [llms.txt](https://documentation.dbforest.org/r/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.dbforest.org/r/d/architecture.md).
# Technical Architecture
DB Forest is a decentralized cloud aggregator. The decentralization is important to ensure that at no future time if the company goes public and replace the founders, it could change the results of the system. Validators define requirements for each product line. Providers register on a smart contract how much inventory they have of a product type. Each time a provider registers the validators will automatically test them by impersonating a new customer once at the point of registration and then again at random throughout time. Validators perform a series of feature completeness checks as well as compute performance benchmarks and egress speed tests but the details of this vary between product lines.
Detailed steps of a purchase.
1. Customer sees list of inventory per product and provider as well as their performance score via the web DAPP
2. Customer makes a purchase order on-chain. With a stable coin deposit worth of 2 months of this service.
3. Service Provider listens to on-chain event and triggers a new deployment with their Infrastructure provider (In many cases the Service Provider and Infrastructure Provider can be the same entity but there are also Service Providers that resell deployments hosted on public clouds).
4. Service Provider sends status update to Customer about deployment process being started over XMTP
5. Once deployed the Service Provider sends the credentials to the Customer end to end encrypted over XMTP
6. Customer is listening for new messages from the provider on XMTP and can display the returned credentials in the web DAPP . (XMTP is important here to ensure that DB Forest does not become a communication intermediary).
---
# 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://documentation.dbforest.org/r/d/architecture.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.