---
title: "Nosflare Pricing and Cost Model"
description: "What running a Nosflare relay costs: one-time 21,420 sats for one-click deploy, then Cloudflare usage-based billing - typically 75-90% less than traditional relay hosting."
canonical: "https://nosflare.com/docs/pricing.md"
---

# Pricing and Cost Model

## One-click deploy

**21,420 sats, one time.** [Nosflare Deploy](https://deploy.nosflare.com) sets up a fully customized relay on your own Cloudflare account. There is no subscription and no per-update charge - you can keep changing your relay's configuration afterwards at no extra cost.

## Self-hosting

Nosflare is MIT-licensed and free to deploy yourself from https://github.com/Spl0itable/nosflare. Your only cost is Cloudflare usage.

## Running cost

Nosflare typically costs **75-90% less than traditional relay hosting**, while delivering better performance, global scale, and zero maintenance. The reason is structural: you pay for what the relay actually does rather than for a server sized for peak load.

Cost components, all usage-billed by Cloudflare:

| Component | What it bills for | Cloudflare pricing |
| --- | --- | --- |
| Workers | Requests and CPU time | [Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/) |
| Durable Objects | Requests and active Duration (GB-s) | [Durable Objects pricing](https://developers.cloudflare.com/durable-objects/platform/pricing/) |
| D1 | Rows read/written and storage (10 GB limit) | [D1 pricing](https://developers.cloudflare.com/d1/platform/pricing/) |

The Workers **paid plan is recommended**, though a free tier is available.

### Why it is cheaper

- **No idle cost.** Workers scale to zero. A VPS bills the same at 3am as at peak.
- **WebSocket hibernation.** Durable Objects using the Hibernation API do not accrue Duration charges while connected clients are idle - normally the dominant cost of a Durable-Objects relay.
- **No ops overhead.** No patching, monitoring, or on-call time, which is the real cost of self-hosted infrastructure.
- **Caching.** A "cache everything" page rule with a long edge TTL keeps a high share of traffic off the Worker entirely.

## Earning it back

With [pay-to-relay](https://nosflare.com/docs/pay-to-relay.md), a relay can charge for write access in sats over Lightning, letting operators offset or exceed their Cloudflare bill.
