# Revenue Model

FliteGrid's value to token holders is directly tied to real-world revenue from data sales. This page explains how revenue is generated, how it flows back to the network, and how it's reported.

## How Revenue Is Generated

FliteGrid sensors collect drone tracking data. That data feeds into SkySafe's cloud platform, where it becomes part of the airspace intelligence product that SkySafe sells to government and enterprise customers.

These customers pay SkySafe for access to real-time and historical drone tracking data, airspace monitoring capabilities, alerting, analytics, and compliance tools. The customer base includes military, law enforcement, border security agencies, airport operators, critical infrastructure managers, stadiums, universities, and other organizations with airspace security and awareness needs.

This isn't theoretical future revenue. SkySafe already generates millions in annual revenue from these customers. FliteGrid data expands the coverage and value of the product they're already buying. More sensors deployed across more locations means more comprehensive data, which means more value to customers, which means more revenue.

## Buyback Mechanism

Revenue generated from FliteGrid data sales is allocated to buying $FLITE tokens.

Here's how the mechanism works:

1. SkySafe sells FliteGrid drone tracking data to customers.
2. Revenue is tracked and attributed to the FliteGrid network.
3. Revenue is used to purchase $FLITE tokens on the open market.

This creates a direct link between network revenue and token value. As more data is sold, more tokens are bought. The more coverage the network provides, the more data it generates, the more revenue it earns, and the more buy pressure is applied to the token.

The buyback ratio is consistent with the model adopted by other leading DePIN projects. It balances returning value to the network with maintaining SkySafe's ability to operate, invest in growth, and serve customers.

## Phase 1 Revenue Tracking

Revenue tracking begins when the network goes live, even though the token won't launch until 2027. All revenue generated during this pre-token period is recorded and accounted for. When the token launches, the accumulated revenue obligation is included in the initial buyback, ensuring that early network operation generates value for participants from day one.

## Quarterly Reporting

FliteGrid will publish quarterly reports on revenue generated by FliteGrid data sales. These reports will include:

* Total FliteGrid data revenue for the quarter
* Amount allocated to buyback mechanism
* Network growth metrics (sensors deployed, coverage area, data volume)

Transparency is a core commitment. The community should be able to verify that the revenue flywheel is working and that the buyback mechanism is being executed as described.

## Why This Matters

The DePIN projects that perform best over time are the ones with real, growing revenue that benefits token holders. Token emissions without revenue backing eventually dilute to zero. Revenue-backed token buybacks create sustainable value.

FliteGrid's advantage is that it doesn't need to build a customer base from scratch. SkySafe's existing customers are already paying for drone tracking data. FliteGrid expands the supply of that data, making the product more valuable and driving more revenue. The buyback mechanism ensures that revenue flows back to the people who built the network.


---

# Agent Instructions: 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:

```
GET https://docs.flitegrid.io/rewards-and-token/revenue-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.