Aller au contenu principal

Zeq Edge · Pricing

Phase 2.1 pricing follows the existing tallyEconomy.OPERATION_COSTS 80/20 burn/foundation split. The per-tier limits are gated in the routes; pay-as-you-go ZEQ charges for cf-specific actions land in Phase 2.2 (cf_request_billable, cf_bandwidth_kb_egress).

Free tier (Phase 2.1 decision lock)​

  • 1 protected site
  • 100,000 requests / day shared across all routes of that site
  • No custom rules (built-in WAF gate only)
  • Cache TTL fixed at 300 Zeqonds
  • Site lives at the customer's CNAME → <edge_id>.zeqedge.zeq.dev

Pro tier (existing framework subscription)​

  • Up to 10 sites
  • 10 M requests / day per site
  • Up to 50 custom rules per site
  • Configurable cache TTL (60 – 86400 Zeqonds)
  • Custom origin TLS verification (opt-out per site via insecure_origin_allowed)

Business tier (existing framework subscription)​

  • Unlimited sites
  • 100 M requests / day per site
  • Unlimited rules

Threat-blocked rebate​

For every 1,000 requests blocked at the WAF (across a customer's sites), the owner machine receives 5 ZEQ credited from the foundation pot.

Cap: 100 ZEQ per Zeqond per machine — anti-farm-rebate per Zeq's 2026-05-19 decision lock. A site under sustained attack receives the rebate at the maximum cap rate (~ 100 ZEQ / 0.777 s).

Math (verbatim from lib/cfCore.ts computeRebate):

raw          = floor(blockedInWindow / 1000) * 5
headroom     = max(0, 100 - alreadyPaidThisZeqond)
rebatePayout = min(raw, headroom)
capped       = raw > headroom

Phase 2.2 — what's coming​

  • cf_request_billable (0.0001 ZEQ / request above tier free quota)
  • cf_bandwidth_kb_egress (0.0001 ZEQ / KB)
  • cf_cert_upload (25 ZEQ / upload — anti-spam)
  • cf_cache_purge (5 ZEQ / call, max 20/day rate-limited)

The macro 80/20 burn/foundation split is preserved across every new charge.