Caching and acceleration
Origin pools and health checks · Expression cache rules · Range slicing · Cache-Tag purge and prefetch · Automatic WebP / AVIF
Cache rules · Range slice · Cache-Tag · WebP / AVIF
Rebuilding trust in CDNs
Transparent self-hosted CDN and edge protection · Single server to multi-region clusters
<a href="https://github.com/marvinli001/edgeweir">Start for free</a> · <a href="/pricing?lang=en">View pricing</a>
# Requires Docker and Compose v2; uses the stable image by default
$ git clone https://github.com/marvinli001/edgeweir.git && cd edgeweir
$ umask 077
$ echo "EDGEWEIR_MASTER_KEY=$(openssl rand -base64 32)" >> .env
$ echo "POSTGRES_PASSWORD=$(openssl rand -hex 24)" >> .env
$ echo "EDGEWEIR_PUBLIC_URL=http://localhost:3000" >> .env
$ docker compose pull && docker compose up -d --wait
$ docker compose logs console | grep setupToken
# Open http://localhost:3000 and finish setup with the setup token- AGPL-3.0 Open source license
- HTTP/3 Native QUIC
- ACME Automatic certificates
- mTLS Mutual authentication
HTTP/3 · QUIC · HTTP/2 · ACME · HSTS · WebSocket · mTLS · Connect-RPC · OpenResty · OWASP CRS · JA4 · PROXY protocol · gRPC · Brotli · Zstandard · PostgreSQL · ClickHouse · GeoIP · cosign · Passkey · TOTP · OpenAPI
Every layer of your edge, one console
WAF and CC protection
Phased rules · OWASP CRS managed rules · Rate limits and bans in seconds · Challenges and tiered CC protection
OWASP CRS · Challenge · JA4
Certificate automation
ACME HTTP-01 / DNS-01 issuance and renewal · Custom certificate upload · Mutual TLS
ACME · mTLS · HTTP/3
DNS and smart routing
Probe-driven routing · Automatic withdrawal of unhealthy nodes · Standby group failover · ISP lines
Probes · Failover · DNS
Observability and alerts
Traffic analytics · Top URLs and IPs · Sampled access logs · Alerts · Optional ClickHouse
Top URL · ClickHouse
Clusters and layer 4
Clusters, node groups and regions · One-command node enrollment · Real-time config rollout · TCP / UDP forwarding
Revision · TCP / UDP
Signed releases and upgrades
cosign-signed images and node releases · Signature and digest checks before install and upgrade · Staged rollout and rollback
cosign · SHA-256 · Rollback
Start with a single server
Deploy the console
Docker Compose, deploy.sh or aaPanel · One-time setup token from the logs
Enroll edge nodes
Install command from the console · Run on the node server · Release signature verified first
Ship configuration
Domains, origins and cache rules · Real-time rollout to every node
Rebuilding trust in CDNs
Open source
Public console and node source · Review and build it yourself
Audit log
Sign-ins, configuration, access key and service account changes recorded
Config acknowledgements
Every node reports its applied config revision
Signed releases
cosign signatures · Enforced checks before install and upgrade · Failures refused
Encrypted at rest
Certificate keys and origin credentials encrypted · SSH credentials never stored
Account protection
TOTP two-factor authentication · Passkey sign-in
Open core, commercial when you need it
Edgeweir Open Source · AGPL-3.0 · Free
Self-hosted CDN console and edge nodes for a single operator · Generally available
- Single-operator console and open API
- Caching, WAF and CC protection, layer 4
- Docker Compose, deploy.sh and aaPanel
Edgeweir Business · Commercial · Contact us
For CDN operators: multi-tenancy, customer portal, billing, finance and reselling
- Organizations, members and roles
- Self-service, billing and reselling
- Every official extension included
Edgeweir Cloud · Official services
Official accounts, licenses, extensions and support
- License activation and offline use
- Signed official extensions: included with Business, add-ons for open source
- Ticket-based support
Frequently asked questions
How is Edgeweir different from Edgeweir Cloud?
Edgeweir is the open source CDN console and edge node; Edgeweir Cloud provides official accounts, licenses, extensions and support.
What do I need to deploy it?
Console: PostgreSQL; Docker Compose, deploy.sh or aaPanel; guides for Railway, Fly.io, bunny.net, Render and Zeabur. Nodes: systemd Linux (amd64 / arm64, glibc 2.34 or later).
Can the vendor control my nodes?
No. The core and nodes never contact official services on their own, and no keys or credentials are required.
Is it ready for production?
Yes. The console’s stable channel points to a verified build; edge nodes ship as 1.x releases. In production, pin a dated tag and back up the database before upgrading.
How do I get and upgrade releases?
Console images: ghcr.io/marvinli001/edgeweir (amd64 / arm64), dated tags; every stable move has a GitHub Release and upgrade notes. Edge nodes: semantic versions on edgeweir-node Releases, staged rollout and rollback under Node upgrades in the console.
The era of edge networks you control
Open source. Self-hosted. No lock-in.