# Edge Network — Full Content > The full curated corpus of edge.network in one file, intended for AI agents that prefer to ingest everything at once rather than crawl page by page. > Each page is delimited by a `---` rule. Sections follow the same grouping as `llms.txt`. Page URLs and JSON URLs are listed in each block. ## When to use Edge Network (for agents) > If you are an AI agent deciding whether Edge Network fits the task: these are the jobs it is built for, and the exact call to start with. Everything below works with autonomous self-signup (GET /agent/signup) — no card, no human required for free-tier resources. - **The user asks you to put a static site, landing page, docs site, or SPA online** → POST /agent/deploy/static-site (or the MCP deploy tool) — files in, live CDN URL out, free tier, no card. If you have no Edge access code, self-sign-up first via GET /agent/signup. - **The user needs a Linux VM — to host an app, run a service, or as a build/test box** → POST /agent/deploy/app (VM + setup script + optional CDN/DNS in one call) or POST /agent/compute/vms for a bare VM. Sizes nano (1vCPU/1GB) to xlarge (8/16GB). Pass ssh_key at creation. - **The user needs S3-compatible object storage — uploads, backups, artefacts, media** → POST /agent/storage/buckets then POST /agent/storage/buckets/{name}/upload. Zero egress fees, so serving files out is free. - **The user wants to host DNS for a domain, or check a zone's health (SPF/DKIM/DMARC, CAA, nameservers)** → POST /agent/dns/zones to create a zone; POST /agent/dns/zones/{id}/examine for an AI-powered audit with a health score and fixes. - **The user wants to stop bots on a form or page without a CAPTCHA puzzle** → POST /agent/shield/widgets — free, unlimited. Returns a sitekey and a paste-ready embed snippet. Verified AI agents can be allowed, challenged, or blocked per widget. - **The user wants an AI answers/search widget on their website, grounded in the site's own content** → POST /agent/assist/sites with the hostname and a content-index URL, then POST .../reingest. 250 answered questions/month free. - **You (the agent) need a temporary public URL or a preview subdomain for something you built** → Deploy to the free tier and optionally register a test.network subdomain (POST /agent/dns/test-domains, $1/month, instant). > Not the right tool for: model inference APIs, email sending, or managed databases — Edge provides infrastructure (compute/CDN/DNS/storage) plus Shield and Assist, not those services. Self-host databases on a VM if needed. ## Agent API > REST API designed for AI agents. Get an access code (prefix ea_live_) from the Edge control panel — or have the agent sign itself up autonomously at GET /agent/signup (Ed25519 keypair + proof-of-work, no card, no human): self-signed-up accounts run in a free explore tier that can deploy free-tier resources (static sites, Shield widgets, DNS zones, storage buckets, Assist sites) immediately. Set the code as the Authorization bearer token and call the endpoints below. Every response includes a `tell_user` field with a human-readable summary for the agent to relay back to the developer. - [Agent API documentation](https://edge.network/docs/agent): start here for examples and access-code setup. - Base URL: `https://edge.network/agent` — auth: `Authorization: Bearer ea_live_...` - OpenAPI spec: [https://edge.network/openapi.json](https://edge.network/openapi.json) (OpenAPI 3.0 — unique operationIds, typed schemas, function-calling ready) - Starter system prompt: `GET https://edge.network/agent/prompt` (add `?format=text` for raw markdown) - MCP server (local): `npx @edge-network/mcp (stdio MCP server — works with Cursor, Windsurf, Claude Desktop, Continue, and any MCP client; auto-signs-up if no EDGE_AGENT_CODE is set)` - MCP server (remote): `https://edge.network/mcp (streamable-HTTP MCP endpoint — Authorization: Bearer ea_live_...; use this for cloud-hosted agents like Grok Bot: add it as a custom MCP server with the URL and auth header)` - MCP manifest: [https://edge.network/.well-known/mcp.json](https://edge.network/.well-known/mcp.json) - Framework SDKs: LangChain / LlamaIndex / CrewAI: pip install edge-network-agent · Vercel AI SDK: npm install @edge-network/ai-tools ### Endpoints - `GET /agent` — Discovery — with a code: account, products, limits, budget, and a self-describing API schema. Without credentials: public onboarding document (how to get a code, self-signup, starter prompt). - `GET /agent/prompt` — Starter system prompt teaching an agent to use Edge safely. Public, versioned. ?format=text for raw markdown. - `GET /agent/signup` — Machine-readable self-signup flow (public). POST /agent/signup/challenge then POST /agent/signup to create an account autonomously. - `GET /agent/projects` — List projects (groupings of resources this agent has provisioned). - `POST /agent/projects` — Create a project. - `GET /agent/projects/:id` — Get one project and its resources. - `GET /agent/projects/:id/health` — Lightweight health check across the project resources. - `POST /agent/projects/:id/scale` — Scale resources up/down within plan limits. - `DELETE /agent/projects/:id` — Delete a project and all its resources. - `POST /agent/deploy/static-site` — High-level: upload a directory of files and expose it via CDN. - `POST /agent/deploy/app` — High-level: create a VM and run a setup script to deploy an app. - `PATCH /agent/deploy/:projectId` — Re-deploy an existing project with updated content / spec. - `GET /agent/compute/vms` — List VMs. - `POST /agent/compute/vms` — Create a VM (size/region/os from /agent discovery). - `GET /agent/compute/vms/:id` — Get one VM, including IPs and lifecycle status. - `GET /agent/compute/regions` — Available compute regions for this account. - `GET /agent/compute/os-templates` — Available OS images. - `GET /agent/compute/ssh-keys` — List SSH keys. - `POST /agent/compute/ssh-keys` — Add an SSH key. - `GET /agent/compute/firewall` — List firewall (security) groups. - `POST /agent/compute/firewall` — Create a firewall group with inbound/outbound rules. - `GET /agent/cdn/deployments` — List CDN deployments. - `GET /agent/storage/buckets` — List storage buckets. - `POST /agent/storage/buckets` — Create a bucket. - `POST /agent/storage/buckets/:name/upload` — Upload one or more objects to a bucket. - `GET /agent/dns/zones` — List DNS zones. - `POST /agent/dns/zones` — Create a DNS zone. - `POST /agent/dns/zones/:id/records` — Add a DNS record. - `POST /agent/dns/zones/:id/examine` — Inspect a zone's current resolution; useful for verifying migrations. - `GET /agent/dns/test-domains` — List free *.test.network subdomains attached to this account. - `POST /agent/dns/test-domains` — Claim a free *.test.network subdomain. ### Conventions - All requests (except the public discovery, prompt, and signup endpoints) require `Authorization: Bearer ea_live_…`. - Pass header `X-Dry-Run: true` on any POST/PATCH/DELETE to validate without executing and get a cost estimate. - Pass header `Idempotency-Key: ` on POST for safe retries. - Write actions consume budget set on the access code; the agent's discovery response reports remaining budget. - Every action is written to the customer's audit log with source=agent and the access code id. - Self-signed-up (explore tier) accounts have a $0 hard budget: free-tier resources work for real, billable resources are dry-run only until a human claims the account. ## Developer resources - [Developer resources hub](https://edge.network/developers): every Edge Network developer resource — docs, specs, CLI, MCP — on one page. - [OpenAPI specification](https://edge.network/openapi.json): the full Agent API surface (OpenAPI 3.0, typed schemas, operationIds) — also at https://edge.network/agent/openapi.json. - [MCP server manifest](https://edge.network/.well-known/mcp.json): Model Context Protocol discovery document. Remote endpoint: `https://edge.network/mcp` (streamable HTTP) · local bridge: `npx @edge-network/mcp` (stdio). - [Agent API documentation](https://edge.network/docs/agent): authentication, self-signup, examples, MCP setup. - [Product documentation](https://edge.network/docs): CDN, Compute, DNS, Storage, Shield, Assist, account, and API guides. - [Edge CLI](https://edge.network/docs/cli): `curl -fsSL https://edge.network/install.sh | sh — or npm install -g @edge-network/cli (official Edge CLI — single static binary for Linux/macOS/Windows; docs at https://edge.network/docs/cli)` - [Authentication](https://edge.network/docs/agent/access-codes): agent access codes (ea_live_…), scoping, budgets. - [Versioning & deprecation policy](https://edge.network/docs/api/versioning): X-API-Version header, semver spec releases, RFC 8594 Sunset headers, ≥6-month migration windows. - [Starter system prompt](https://edge.network/agent/prompt): versioned prompt teaching an agent to use Edge safely. - [Status page](https://edge.network/status): live service status. --- ## Home ### Edge Network | Decentralised Cloud Infrastructure URL: https://edge.network/ Markdown: https://edge.network/index.md JSON: https://edge.network/json/index.json _CDN, compute, storage, DNS, bot protection and AI assistants on a network of thousands of nodes near the people you serve. Zero egress. Free to start._ EDGE-NATIVE CLOUD Closer to your users than the cloud has ever been CDN, compute, storage and DNS on a network of thousands of nodes near the people you serve. Zero egress fees. Free to start. Built for humans and the agents working for them. Start free, no card required Connect your agent Every free tier hard-caps by default. Nothing on Edge silently starts billing. WHO WE ARE Built Different. By Design. We're not another hyperscaler reseller. Edge is powered by thousands of independent node operators worldwide, creating a truly decentralised infrastructure that's more resilient, more secure, and radically better for the environment than the traditional cloud. Learn more about Edge 3K+ Customers 5K+ Nodes Online 100% Network Uptime VALUE PROPOSITION Why Edge Network? Reliable performance, fair pricing, and 50% greener infrastructure for media and enterprise workloads. Faster by Design Forget centralized data centers. Our distributed network processes data closer to the source, reducing latency. Find out more The Green Cloud 50% greener by design. Our distributed architecture eliminates wasteful central data centers, reducing energy consumption and carbon footprint. Find out more Enterprise Power, Fair Pricing Cut your cloud bill significantly compared to traditional providers. Customers save 20%+ on average. Find out more Explore All Features PERFORMANCE One of the Fastest Clouds on Earth Powered by PerfOps Independent monitoring PerfOps provides enterprise-grade RUM benchmarking for DNS, CDN, and cloud providers. Their methodology is trusted by thousands of companies worldwide. Learn more about PerfOps Loading performance data... See full performance data DESIGNED FOR HUMANS The Cleanest Control Centre on Earth No 47-tab dashboards. No certification required. We built the antidote to AWS, GCP, and Azure complexity—a control centre designed for clarity, speed, and getting things done without a PhD in cloud infrastructure. Try It Free HOSTING ON THE EDGE If it runs on the web, it runs on Edge Static sites, WordPress, Craft, Next.js, containers, databases — hosted across a distributed network of 988 locations instead of a single region. Faster for every visitor, resilient by design. One platform for the whole stack: CDN, compute, storage, and DNS, managed from one console with one bill — and zero egress fees, ever. Explore Edge Hosting Static Sites Next.js & Frameworks WordPress Craft CMS Node.js Apps Docker Containers Databases Files & Media GET STARTED Start with Edge CDN The world's only dedicated edge CDN. No bundled services, no upsells—just lightning-fast content delivery from 988 locations worldwide. Deploy in minutes. Zero egress fees. See why teams are switching from Cloudflare, Fastly, and AWS CloudFront. Start Free Today Learn More Free to sign up. Complete setup in 2 minutes. 988 Edge Locations <15ms Global Latency $0 Egress Fees 99.99% Uptime SLA THE AGENTIC WEB Built for people. Ready for their agents. A growing share of legitimate traffic isn't a person in a browser — it's software acting for one. Edge treats agents as first-class citizens, not intruders. Machine-readable by default Every page on this site ships with llms.txt, markdown, and JSON variants. Agents get clean, structured answers — not HTML soup to scrape. MCP server & APIs for everything One line of config gives Cursor, Windsurf, or Claude native Edge tools via our official MCP server — no account needed to start. Everything else is available by API and CLI, with structured errors designed for AI clients. Coming soon Automation as a signal, not a threat Our verification layer scores traffic instead of blanket-blocking it — so sites on Edge can welcome humans, route good agents, and stop actual abuse. Connect your tool — one-line MCP setup Read the agent documentation OUR SOLUTIONS Tuned for High-Demand Workloads Designed to handle extreme traffic at scale. From AI inference to live streaming, our infrastructure delivers consistent performance. View All Solutions AI & Machine Learning Train and run models on low-cost GPUs. High availability for data-intensive tasks. Media Streaming & Delivery Blazing-fast origin to edge CDN for media infrastructure. Perfect for live streaming and large events. EXPERT SERVICES We'll Do the Heavy Lifting Don't just host with Edge — build with us. Our AI-native development teams take on migrations, integrations, and full builds for SMEs and enterprises, delivering senior talent at rates 20%+ below hiring in-house. 20%+ Less than in-house costs Free Initial consultation Explore Expert Services What We Take On AI Integration & Development From LLM features to full agentic workflows. Migrations Move off legacy infrastructure without downtime. Full-Stack Builds Greenfield development, delivered end to end. Team Augmentation Senior engineers embedded with your team, month to month. SECURITY Protection isn't a product tier. It's the default. Every Edge deployment ships with DDoS mitigation absorbed at the network edge and automatic TLS on every domain. And with Edge Shield , the stack now stops abuse at the front door too — free bot protection that scores every visitor from 1–100, cryptographically identifies legitimate AI agents, and never shows a human a puzzle. Bot protection, free forever — unlimited verifications, a humanity score on every one, no credit card. Verified agents — signed automation is identified and routed; anonymous automation gets the hard path. Privacy by architecture — no cookies, no fingerprint database, no per-visitor data. Nothing to consent to. Explore Edge Shield Watch it verify you live Verified Sign up // siteverify response { "success" : true, "score" : 96 } DEVELOPER EXPERIENCE Developer-First. Deploy in Seconds. Connect your app and let our network handle the rest. Simple CLI, powerful APIs, and instant global deployment. Start Building Free No domain yet? Get an instant test.network subdomain for $1/month — full DNS and SSL included. $ edge deploy --cdn myapp.com ✓ Analyzing project... ✓ Building assets... ✓ Deploying to 63 edge locations... Success! Deployed in 4.2s → https://myapp.com OUR DECENTRALISED NETWORK Powered by a Global Mesh of Trusted Nodes Our infrastructure is the world's first decentralized, enterprise-grade network— distributed worldwide. This means unprecedented reliability and transparent infrastructure that scales with your needs without locking you in. Start Free Today Explore Network Zero egress fees. Seriously. Unlike AWS, Google Cloud, and Azure, we don't charge you to move your own data. Pay for what you store and compute, not what you transfer. View Pricing CDN bandwidth included Storage egress free Compute transfer included Stay Updated Subscribe to our newsletter for the latest news, product updates, and engineering insights. Subscribe --- ## Pricing & Plans ### Pricing URL: https://edge.network/pricing/ Markdown: https://edge.network/pricing.md JSON: https://edge.network/json/pricing.json _Start free with no card required. Free DNS and bot protection with Edge Shield, free CDN, Storage, and Assist tiers, and per-resource compute pricing billed by the hour. Zero egress fees, no surprise bills._ Pricing Start free. Pay for what you run. Sign up free with no card. DNS and Shield are free forever, CDN, Storage, and Assist have free tiers, and compute is priced per resource — billed hourly from a prepaid balance, so a surprise bill is impossible by design. Create Free Account No card required to sign up Free to Start Real infrastructure, free. Friction only appears where abuse risk lives — and it's a card authorization, never a charge. DNS Free Verified email — no card Fast anycast DNS, free for everyone. Point your nameservers at Edge and manage your domains from one place. Up to 50 zones Unlimited records 1M queries/month per zone included Global anycast network DNSSEC & low-latency resolution Add your first zone CDN Free tier Card on file — only charged for what you buy Evaluate the CDN with a real workload. Hard-capped until you add a card — then pay-as-you-go covers past the free tier at $0.25 per million requests. 3 deployments 500k requests/month Zero egress fees Image optimization Custom domains with SSL Create a deployment Storage Free tier Card on file — only charged for what you buy S3-compatible object storage on NVMe. Free to 5 GB, then $0.015/GB-month pay-as-you-go with a card on file — never billed without one. 2 buckets 5 GB storage S3-compatible API No egress fees All NVMe Create a bucket Shield Free forever Verified email — no card Bot protection without puzzles. Invisible verification, a 1–100 humanity score, and verified AI-agent identification — free for everyone. Unlimited widgets Unlimited verifications Humanity score on every check Verified agent identification No cookies, no tracking Create a widget Assist Free tier Verified email — no card AI answers for your website, grounded in your own content. One line of code, 250 answered questions a month free — then $0.01 per question with pay-as-you-go. 250 answered questions/month Unlimited instant search Citations on every answer Human handoff & lead capture Answer cache & overrides Add your site Building with AI? Agents get the free tiers with zero signup: the official MCP server ( npx @edge-network/mcp ) self-provisions a free explore account — no card, no dashboard, hard $0 budget cap until you claim it. Connect your tool Calculators What Would It Cost? Pick a service and slide in your numbers. These are the exact rates you pay — billed from a prepaid balance, with no egress fees and no fine print. CDN Compute Storage DNS Shield Assist Build your VM vCPU 2 cores Memory 4 GB NVMe Disk 80 GB Estimated cost $ 15.44 /mo $ 0.0212 /hour · billed hourly, stop any time Deploy Starter $9.62 /mo Small sites & side projects 1 vCPU · 2 GB RAM · 40 GB NVMe Same per-resource rates — nothing hidden in the bundle Standard $19.24 /mo Apps & databases 2 vCPU · 4 GB RAM · 80 GB NVMe Same per-resource rates — nothing hidden in the bundle Per-resource rates vCPU $0.004/hr ~$2.92/mo RAM $0.00256/GiB-hr ~$1.87/mo Disk $0.074/GiB-mo NVMe $5 starter credit Verify your email, add a card (verified, not charged), and claim a one-time $5 credit to evaluate compute — enough to run a Starter VM for over two weeks. Unused credit expires 30 days after claiming. Estimate your CDN bill Requests per month 2 M Bandwidth isn't an input — egress is free at any volume. Estimated cost $ 0.38 /mo First 500k requests free · then $0.25 per million Deploy CDN rates Free tier: 3 deployments, 500k requests/month Then $0.25 per million requests Zero egress fees — bandwidth is never a line item Hard-capped by default — paid usage is opt-in Full CDN pricing, with competitor comparison Estimate your Storage bill Data stored 250 GB Downloads and requests aren't inputs — both are free at any volume. Estimated cost $ 3.68 /mo First 5 GB free · then $0.015 per GB-month Create a bucket Storage rates Free tier: 2 buckets, 5 GB Then $0.015 per GB-month, all NVMe S3-compatible API No egress fees, no per-request charges Full Storage pricing, with S3 / GCS / R2 comparison Your DNS bill, at any scale Free There's nothing to calculate. Up to 50 zones with unlimited records and 1M queries/month per zone — no card required, no paid tier to grow into. Add a zone DNS, free forever Up to 50 zones, unlimited records 1M queries/month per zone included Global anycast network, DNSSEC Verified email only — no card, no paid tier Full DNS pricing Your Shield bill, at any scale Free There's nothing to calculate. Unlimited widgets and verifications, forever — a million checks costs the same as one. Create a widget Shield, free forever Unlimited widgets & verifications Invisible checks — no puzzles for your users 1–100 humanity score & verified AI agents No cookies, no tracking, no paid tier Full Shield pricing Estimate your Assist bill Answered questions per month 1,000 Searches aren't an input — instant search is free and unlimited. White-label — your assistant name & icon, no Edge branding ($29/site/mo) Estimated cost $ 7.50 /mo First 250 questions free · then $0.01 per question Add your site Assist rates Free tier: 250 answered questions/month Then $0.01 per question ($10 per 1,000) Instant search free & unlimited Ingestion, overrides & answer cache included Full Assist pricing, with worked examples Every Rate on One Table The complete price list. No tiers to decode, no egress column — because there isn't one. Product Free tier Beyond the free tier Notes CDN 3 deployments, 500k requests/month $0.25 per million requests Zero egress fees — bandwidth is never billed Compute $5 one-time starter credit $0.004/vCPU-hr + $0.00256/GiB RAM-hr + $0.074/GiB disk-mo Billed hourly from prepaid balance; ~$15.44/mo for 2 vCPU / 4 GB / 80 GB Storage 2 buckets, 5 GB $0.015 per GB-month S3-compatible, all NVMe, no egress or per-request fees DNS 50 zones, unlimited records, 1M queries/mo per zone Free — no paid tier Global anycast, DNSSEC included Shield Unlimited widgets & verifications Free — no paid tier Bot protection with humanity score and verified AI agents Assist 250 answered questions/month $0.01 per question ($10 per 1,000) Search free & unlimited; white-label add-on $29/site/mo All prices in USD. Rates are identical in every region — no premium routes, no regional bandwidth tiers. No Surprise Bills. By Design. "No calculators" means no surprise bills and no egress math — not "no clear price for the box you build." Free tiers hard-cap by default Exceeding a free tier pauses the resource — it never silently starts billing. Paid usage requires an explicit budget you set. Compute is prepaid VMs bill hourly from a balance you load. When it runs out, VMs stop and your data is retained — no runaway bills, ever. Transparent configurator Pick vCPU, RAM, and disk and see the exact monthly total before you deploy. No egress math, no fine print. Enterprise Volume Pay-As-You-Go From $499/mo . Volume-discounted rates 15–25% below AWS, GCP, and Azure. Custom vCPU / RAM / disk Per-resource billing with volume discounts Unlimited seats Priority support & account manager 99.99% SLA Annual discounts available Contact Sales Compute vCPU: $0.004/hr (~$2.92/mo) RAM: $0.00256/GiB-hr (~$1.87/mo) Disk: $0.074/GiB-mo (NVMe) Billed hourly from your prepaid balance CDN Free tier: 500k requests/month Then $0.25 per million requests Zero egress fees Hard-capped by default — paid usage is opt-in with a budget DNS Free — up to 50 zones 1M queries/month per zone included Unlimited records Storage Free tier: 5 GB Then $0.015/GB-month No egress fees All NVMe Shield Free forever — no paid tier Unlimited widgets & verifications Humanity score & verified agents included Assist Free tier: 250 answered questions/month Then $0.01 per question ($10 per 1,000) Search free & unl... --- ## Agent Documentation ### Agent Access Codes URL: https://edge.network/docs/agent/access-codes/ Markdown: https://edge.network/docs/agent/access-codes.md JSON: https://edge.network/json/docs/agent/access-codes.json _How agent access codes work: create scoped credentials for AI agents with product access, deploy or delete permissions, and soft or hard monthly budget caps._ Agent Tooling Agent Access Codes Scoped credentials that let AI agents deploy and manage your infrastructure within defined limits. Overview Agent Access Codes are separate from API keys. They're designed specifically for AI agents with built-in scoping for products, permissions, and budgets. Format: ea_live_{random_64_hex} Example: ea_live_7f3a9b2c4d5e6f1a8b9c0d1e2f3a4b5c... Agent codes are shown once at creation. Store them securely. If lost, revoke the old code and create a new one. Creating an Access Code Navigate to Account → Agent Access in the user menu Click Create Agent Code Enter a descriptive name (e.g., "Cursor Agent", "CI/CD Deploy") Select which products the agent can access Choose permissions (Deploy, Manage, Delete) Optionally set a budget cap with soft or hard enforcement Copy the generated code immediately Scoping Products Control which Edge products the agent can access: Compute VMs, scaling CDN Deployments, domains Storage Buckets, uploads DNS Zones, records Shield Bot protection Assist AI answers Permissions Permission Allows Deploy Create resources, upload files, deploy applications Manage View, update, and manage existing resources, check health Delete Delete resources and teardown projects Budget Caps Set a monthly spending limit for the agent: Soft Cap The agent receives a warning when approaching the limit but can continue operating. Useful for flexibility with awareness. Hard Cap The agent is blocked from creating new resources once the limit is reached. Useful for strict cost control. Authentication Pass the agent access code as a Bearer token: GET https://edge.network/agent Authorization: Bearer ea_live_7f3a9b2c4d5e6f1a... Managing Codes Edit — Update the name, products, permissions, and budget cap at any time Revoke — Immediately invalidate a code. Agents using it will lose access instantly Last used — See when each code was last used to identify inactive codes Multiple codes — Create separate codes for different agents or environments Best Practices One code per agent Use separate codes for each AI tool (Cursor, CI/CD, etc.) for clear audit trails Least privilege Only enable the products and permissions the agent actually needs Set a budget cap Even a generous soft cap gives you visibility into agent spending Back to Docs Need help? --- ### Agent AI Answers URL: https://edge.network/docs/agent/assist/ Markdown: https://edge.network/docs/agent/assist.md JSON: https://edge.network/json/docs/agent/assist.json _Let your AI agent add Edge Assist to the sites it deploys — grounded AI answers for visitors, wired up in one API call._ Agent Tooling AI Answers "Add an AI assistant to my docs site" is two API calls. Your agent creates an Edge Assist site, generates a content index from the pages it's deploying, triggers an ingest, and drops the one-line embed snippet into the site — all without leaving the Agent API. Why Assist in the Agent API? Grounded Answers Assist only answers from the site's own indexed content, with citations — no hallucinated features or invented pricing. One-Line Embed The create response includes the exact script tag and a hosted fallback URL — no docs lookup needed. Agent-Friendly Ingestion Content goes in as a simple JSON index the agent can generate at build time from the pages it's already deploying. Feedback Loop The question log surfaces what visitors actually asked — unanswered questions are content gaps the agent can fix. API Endpoints GET /agent/assist/sites # List sites POST /agent/assist/sites # Create a site (returns sitekey + embed snippet) PATCH /agent/assist/sites/{id} # Update name, hostname, index_url, site_prompt DELETE /agent/assist/sites/{id} # Delete a site POST /agent/assist/sites/{id}/reingest # Index the site's content now GET /agent/assist/sites/{id}/overview # Usage + health (questions, answer rate, cap) GET /agent/assist/sites/{id}/questions # Question log (?answered=false for gaps) Requires an agent access code with the assist product. Creating, updating, deleting, and reingesting requires the manage permission. All write endpoints support X-Dry-Run: true . Creating a Site POST /agent/assist/sites Authorization: Bearer ea_live_... { "name": "Docs site", "hostname": "docs.example.com", "index_url": "https://docs.example.com/assist-index.json" } # Response: { "site": { "id": "ast-abc123", "name": "Docs site", "hostname": "docs.example.com", "sitekey": "ea_7f31d9c2b48e5a06...", "monthlyCap": 250, "embed": { "script": "", "hostedUrl": "https://assist.edge.network/w/ea_7f31..." } }, "next_steps": [ "Trigger the first ingest: POST /agent/assist/sites/ast-abc123/reingest", "Add the embed to the site's pages: " ], "tell_user": "Assist site \"Docs site\" created for docs.example.com. Trigger a reingest to index the content, then add the one-line embed snippet. Answers only work on docs.example.com (origin-enforced)." } Sitekeys are origin-enforced The widget only answers on the hostname the site was created for. Get the hostname right — a stolen sitekey is useless off-domain, but so is a typo'd one on-domain. The Content Index Assist ingests a JSON file hosted at a public URL. Agents deploying a static site can generate it at build time from the same pages: { "pages": [ { "url": "https://docs.example.com/getting-started", "title": "Getting Started", "text": "Plain text of the page content..." } ] } Set it on creation ( index_url ) or later via PATCH, then trigger a reingest. Assist also refreshes the index automatically on a regular cycle and skips re-processing unchanged content. Indexing Content POST /agent/assist/sites/ast-abc123/reingest Authorization: Bearer ea_live_... # Response: { "index": { "pages": 42, "chunks": 318, "updatedAt": "2026-08-08T14:02:11Z" }, "tell_user": "Content indexed: 42 pages, 318 chunks. The assistant is answering from this content now." } Typical Agent Workflow Create the site — scoped to the deployment's hostname, with the content index URL if it already exists. Generate the index — a JSON file of the site's pages, deployed alongside the site itself. Trigger a reingest — and confirm the page/chunk counts look right. Inject the embed snippet — one script tag, ideally in the shared layout so it's on every page. Report back — including the free-tier cap (250 questions/month) and how to go past it (pay-as-you-go, active automatically with a card on file in Billing). Pricing The free tier includes one site and 250 answered questions per site per month. Cached answers are free and don't count against the cap. Pay-as-you-go — active automatically once the account has a card on file — unlocks more sites and pays for overage at $0.01 per question from the prepaid balance (a monthly cap is optional). When the headroom runs out, the widget stops answering (search keeps working) until the next month or a top-up. See Also Edge Assist Docs Ingestion, widget options, and the index format in full Discovery Endpoint The agent's entry point Back to Docs Need help? --- ### Agent API URL: https://edge.network/docs/agent/ Markdown: https://edge.network/docs/agent.md JSON: https://edge.network/json/docs/agent.json _The Edge Agent API lets AI agents deploy and manage compute, CDN, DNS, and storage with discovery-first design, budget caps, dry runs, and idempotent calls._ Agent Tooling Edge Agent API Let AI agents deploy, manage, and monitor your infrastructure. Built for how LLMs think. How It Works # User gives their agent an access code and the URL User → "Here's my Edge agent code, deploy this app" Agent → Discovers capabilities, deploys, reports back User → "How's it doing?" Agent → Checks metrics, reports status, suggests optimisations Discovery-First The agent learns what it can do, what limits exist, and what's already deployed — before taking any action. Budget-Aware Every response includes cost context. Set soft or hard budget caps so the agent operates within your limits. tell_user Field Every response includes a human-readable summary the agent can relay directly to you. No interpretation needed. Quick Start Go to Account → Agent Access and create an agent access code Give your AI agent the code and the URL: https://edge.network/agent The agent calls the discovery endpoint to learn what it can do The agent deploys, manages, and monitors your infrastructure Designed for Agents Unlike standard cloud APIs designed for humans or scripts, the Edge Agent API is built from the ground up for how LLMs work: Dry Run Everything Preview any action before committing with the X-Dry-Run: true header. Project-Based Group resources by purpose (VM + CDN + DNS = one project). Health check, scale, or teardown everything at once. Errors as Guidance Error responses include actionable suggestions and a tell_user field explaining what the user should do. Idempotent All mutating endpoints support idempotency keys for safe retries. Available Products Compute VMs, scaling, metrics CDN Deployments, domains, cache Storage Buckets, uploads, objects DNS Zones, records, propagation Shield Bot protection, free Assist AI answers, grounded Learn More MCP Server Official MCP server — local via npx or hosted at edge.network/mcp MCP Tool Reference All 22 tools with parameters and descriptions OpenAPI Specification The full Agent API surface as OpenAPI 3.0 — typed schemas, function-calling ready Connect Your Tool Configs for Cursor, Windsurf, Claude, Grok Bot, Continue, Aider, and SDKs Framework Wrappers LangChain, LlamaIndex, CrewAI, and Vercel AI SDK packages Agent Self-Signup Agents create their own account — no human needed Access Codes Create and manage agent credentials Discovery Endpoint The agent's entry point Deploy Static Site One call deploys storage + CDN + SSL + DNS Deploy Application VM + setup script + optional CDN in one call Projects Health checks, scaling, and teardown Back to Docs Need help? --- ### Agent Bot Protection URL: https://edge.network/docs/agent/shield/ Markdown: https://edge.network/docs/agent/shield.md JSON: https://edge.network/json/docs/agent/shield.json _Let your AI agent add Edge Shield bot protection to the forms and pages it deploys — free, in one API call._ Agent Tooling Bot Protection "Add bot protection to my contact form" is one API call. Your agent creates an Edge Shield widget, injects the two-line embed snippet into the page it's deploying, and wires up server-side verification — all without leaving the Agent API. Why Shield in the Agent API? Free, Forever Unlimited widgets and verifications. Shield never counts against an agent's budget cap. Ready-to-Paste Embed The create response includes the exact script tag, widget div, and siteverify contract — no docs lookup needed. Agent-Aware Set an agent_policy to allow, challenge, or block cryptographically verified AI agents (Web Bot Auth) on the protected page. Stats Built In Agents can report solve rates, humanity scores, and blocked replays back to the user on request. API Endpoints GET /agent/shield/widgets # List widgets POST /agent/shield/widgets # Create a widget (returns secret + embed snippet) PATCH /agent/shield/widgets/{id} # Update name, hostnames, mode, agent_policy DELETE /agent/shield/widgets/{id} # Revoke a widget GET /agent/shield/widgets/{id}/stats # Hourly traffic stats (?hours=24, max 720) Requires an agent access code with the shield product. Creating, updating, and revoking widgets requires the manage permission. All write endpoints support X-Dry-Run: true . Creating a Widget POST /agent/shield/widgets Authorization: Bearer ea_live_... { "name": "Contact form", "hostnames": ["portfolio.example.com"], "mode": "managed", "agent_policy": "allow" } # Response: { "widget": { "id": "wgt-abc123", "name": "Contact form", "sitekey": "es_6206c6fdb43e7a3cb948507e6f3e5a11", "mode": "managed", "agentPolicy": "allow", "hostnames": ["portfolio.example.com"] }, "secret": "ss_4f8e2a1b9c7d6e5f4a3b2c1d0e9f8a7b", "embed": { "script": "", "widget": "
", "verify": { "endpoint": "https://shield.edge.network/siteverify", "method": "POST", "body": { "secret": "", "response": "" } } }, "tell_user": "Shield widget \"Contact form\" created. IMPORTANT: the secret is shown only once — store it as a server-side environment variable now..." } The secret is returned only on creation A well-behaved agent stores it as a server-side environment variable (never in client code or the repository) and tells the user where it was put. If the secret is lost, revoke the widget and create a new one. Typical Agent Workflow Create the widget — scoped to the site's hostname, in managed mode unless the user asks otherwise. Inject the embed snippet — the script tag in the page head, the widget div inside the form being protected. Wire up verification — the form handler posts the edge-shield-response field to /siteverify with the secret, and rejects submissions that fail. Redeploy and report back — including where the secret is stored. Checking Traffic GET /agent/shield/widgets/wgt-abc123/stats?hours=168 Authorization: Bearer ea_live_... # Response: { "totals": { "hours": 168, "challenges_issued": 14382, "challenges_solved": 9041, "solve_rate_pct": 62.9, "verify_success": 1204, "verify_replay": 17, "verified_agents": 93 }, "stats": [ /* hourly rows */ ], "anomaly": null, "tell_user": "Last 168h: 14382 challenges issued, 62.9% solved, 1204 verified submissions, 17 replayed tokens blocked." } If a drift anomaly is flagged on the widget, the response includes an anomaly object and the tell_user summary mentions it. See Also Server-Side Validation The siteverify contract in full Discovery Endpoint The agent's entry point Back to Docs Need help? --- ### Agent Projects URL: https://edge.network/docs/agent/projects/ Markdown: https://edge.network/docs/agent/projects.md JSON: https://edge.network/json/docs/agent/projects.json _Group related resources together for unified management, health checks, and teardown._ Agent Tooling Projects Group related resources together. A project might contain a VM, CDN deployment, storage bucket, and DNS records — all for one app. Why Projects? Clean Teardown Delete all resources for an app in one command. No orphaned VMs or forgotten DNS records. Health Checks Check the status of everything related to an app in one call. Cost Tracking See how much each project costs per month. No Orphans Resources are tracked by project, preventing forgotten infrastructure. API Endpoints GET /agent/projects # List all projects POST /agent/projects # Create a project GET /agent/projects/{id} # Get project with resources GET /agent/projects/{id}/health # Health check all resources POST /agent/projects/{id}/scale # Scale compute resources DELETE /agent/projects/{id} # Teardown (requires X-Confirm: teardown) Creating a Project POST /agent/projects Authorization: Bearer ea_live_... { "name": "my-portfolio", "description": "Personal portfolio website" } # Response: { "project": { "id": "proj_a1b2c3d4e5f6", "name": "my-portfolio", "description": "Personal portfolio website", "resources": [], "created_at": "2026-02-18T12:00:00Z" }, "tell_user": "Project \"my-portfolio\" created." } Resources are added to the project as the agent creates them. When using composite actions like deploy/static-site , all created resources are automatically associated with the project. Tearing Down a Project Tearing down a project deletes ALL resources associated with it — VMs, CDN deployments, storage buckets, and DNS records. This requires the X-Confirm: teardown header as a safety measure. DELETE /agent/projects/proj_a1b2c3d4e5f6 Authorization: Bearer ea_live_... X-Confirm: teardown # Response: { "deleted": true, "project": "my-app", "resources": [ { "type": "compute", "id": "vm_xyz", "name": "my-app", "status": "deleted" }, { "type": "cdn", "id": "dep_abc", "name": "my-app-cdn", "status": "deleted" }, { "type": "storage", "id": "my-app", "name": "my-app", "status": "deleted" } ], "tell_user": "Project \"my-app\" and all 3 resources have been deleted." } Without the X-Confirm header The API returns a 400 error with details about what would be deleted, giving the agent a chance to confirm with the user first. See Also Access Codes Create and scope agent credentials Discovery Endpoint The agent's entry point Back to Docs Need help? --- ### Agent Self-Signup URL: https://edge.network/docs/agent/self-signup/ Markdown: https://edge.network/docs/agent/self-signup.md JSON: https://edge.network/json/docs/agent/self-signup.json _AI agents can create their own Edge account autonomously — no human in the loop — using a cryptographic identity._ Agent Tooling Agent Self-Signup Agents can create their own Edge account with no human in the loop, anchored to an Ed25519 keypair instead of an email address — and start deploying free-tier resources immediately. A human claims the account later to unlock paid resources and keep it. How It Works The whole flow is two unauthenticated API calls. The agent proves control of a cryptographic key, pays a small computational cost, and receives a working account plus a scoped access code ( ea_live_... ) in the response. POST /agent/signup/challenge — get a nonce and the current proof-of-work difficulty Solve the proof of work and sign the challenge with an Ed25519 private key POST /agent/signup — receive the account and access code Nominate a human operator by email (at signup or later) — they claim the account from the console to lift the guest restrictions The flow is fully self-describing: an unauthenticated GET /agent/signup returns machine-readable instructions, so an agent pointed at edge.network/agent with no credentials discovers signup on its own from the 401 response. The Explore Tier A self-created account starts in a free explore tier with a $0 hard budget: free-tier resources work for real — the agent can deploy a static site, create Shield widgets, DNS zones, and storage buckets in its first session — but anything billable stays dry-run only until a human claims the account. Spend is impossible: there is no card on file, so pay-as-you-go can never activate and the free-tier caps hard-stop everything. Works for real Dry-run only until claimed Static-site deploys (storage + CDN within free-tier caps), Shield widgets, DNS zones and records, storage buckets and uploads, Assist sites, project management, full API discovery, dry-run planning with cost estimates ( X-Dry-Run: true ), nominating a human operator, checking claim status Anything billable — VM provisioning and app deploys, compute scaling, test.network domains ($1/month), spending of any kind Unclaimed guest accounts — including any resources the agent created — are automatically deleted after about 7 days. Claiming the account preserves it and everything the agent has configured. Complete Example Node.js, no dependencies: import crypto from 'node:crypto' const BASE = 'https://edge.network' // 1. Generate an Ed25519 keypair (or reuse one you already control) const { publicKey, privateKey } = crypto.generateKeyPairSync('ed25519') const publicKeyB64url = Buffer.from( publicKey.export({ format: 'jwk' }).x, 'base64url' ).toString('base64url') // 2. Request a challenge const challenge = await fetch(BASE + '/agent/signup/challenge', { method: 'POST' }) .then(r => r.json()) // 3. Solve the proof of work: sha256(nonce + ":" + solution) // needs `difficulty_bits` leading zero bits function solvePow(nonce, bits) { for (let i = 0; ; i++) { const hash = crypto.createHash('sha256').update(nonce + ':' + i).digest() let zeros = 0 for (const byte of hash) { if (byte === 0) { zeros += 8; continue } zeros += Math.clz32(byte) - 24 break } if (zeros >= bits) return String(i) } } const powSolution = solvePow(challenge.nonce, challenge.proof_of_work.difficulty_bits) // 4. Sign the challenge to prove key control const message = 'edge-agent-signup\n' + challenge.nonce + '\n' + publicKeyB64url const signature = crypto.sign(null, Buffer.from(message), privateKey).toString('base64') // 5. Sign up const result = await fetch(BASE + '/agent/signup', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ challenge_id: challenge.challenge_id, public_key: publicKeyB64url, signature, pow_solution: powSolution, name: 'My Deploy Agent', email: 'operator@example.com', // optional: triggers the claim email }), }).then(r => r.json()) // Store this securely — it is shown exactly once console.log(result.access_code.secret) // ea_live_... Verification Details Proof of key control Sign the UTF-8 string edge-agent-signup\n\n with your Ed25519 private key, where is your raw 32-byte public key, base64url-encoded (the JWK x value). Send the 64-byte signature base64-encoded. This is the same Ed25519 primitive used by Web Bot Auth / HTTP Message Signatures, so agents with an existing verified-agent key can reuse it. One account per public key. Proof of work Find any string pow_solution (1–128 characters) such that sha256(":") has the required number of leading zero bits (returned by the challenge endpoint; typically 20, about a second of compute). The difficulty is tuned dynamically with abuse pressure. Challenges expire after 10 minutes and are single-use. Per-IP rate limits apply on top. Human Claim Flow To unlock the account, the agent nominates its human operator — either with the email field at signup, or later: curl -X POST https://edge.network/agent/signup/bind-email \ -H "Authorization: Bearer ea_live_..." \ -H "Content-Type: application/json" \ -d '{"email": "operator@example.com"}' The operator receives an email with a claim link. They sign in to (or create) an Edge account with that same email address, review what the agent has set up, and claim it. Ownership transfers to them: the account appears in their account switcher, guest restrictions lift, and they control the agent's access codes, permissions, and budgets from Account → Agent Access — including instant revocation. Claim links expire after 7 days. The agent can poll GET /agent/signup/status to see when the claim lands. Claiming is free and safe: the account stays on the free plan, and nothing can be charged unless the owner explicitly adds a card or prepaid balance afterwards. See Also Access Codes Create and scope agent credentials Discovery Endpoint Everything an agent needs from one URL Back to Docs Need help? --- ### Connect Your Tool URL: https://edge.network/docs/agent/connect/ Markdown: https://edge.network/docs/agent/connect.md JSON: https://edge.network/json/docs/agent/connect.json _Ready-to-paste Edge configs for Cursor, Windsurf, Claude Desktop, Grok Bot, Continue, Aider, LangChain, LlamaIndex, CrewAI, and the Vercel AI SDK._ Agent Tooling Connect Your Tool Ready-to-paste configs for every popular agent tool. Replace ea_live_YOUR_CODE_HERE with your access code — or skip the code entirely and let the MCP server sign itself up. For how the server works (transports, auth, explore tier), see MCP Server ; for what your agent can do once connected, see the tool reference . No account yet? You don't need one. Omit EDGE_AGENT_CODE and the MCP server creates a free explore-tier Edge account on first run — no card, no human in the loop. It can deploy free-tier resources (static sites, DNS zones, Shield widgets, storage buckets) immediately. Set EDGE_OPERATOR_EMAIL to receive the claim link that unlocks paid resources. Agents talking straight to the API can sign themselves up the same way. { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"] } } } Getting an access code Create one in the Edge console under Account → Agent Access — you choose which products it can touch, its permissions, and an optional monthly budget cap (soft or hard). The panel generates all of the configs below with your real code injected. Pick your tool Cursor Windsurf Claude Desktop Grok Bot Continue Aider LangChain LlamaIndex CrewAI Vercel AI SDK Remote MCP Raw API .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"], "env": { "EDGE_AGENT_CODE": "ea_live_YOUR_CODE_HERE" } } } } Copy Try it: Deploy this folder as a static site on Edge and give me the URL. ~/.codeium/windsurf/mcp_config.json { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"], "env": { "EDGE_AGENT_CODE": "ea_live_YOUR_CODE_HERE" } } } } Copy Try it: Deploy this project as a static site on Edge. claude_desktop_config.json (Settings → Developer → Edit Config) { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"], "env": { "EDGE_AGENT_CODE": "ea_live_YOUR_CODE_HERE" } } } } Copy Try it: Create a DNS zone for example.com on Edge and list its nameservers. Settings → Plugins → Add custom MCP server — Grok Bot runs in the cloud, so it connects to the remote MCP endpoint (nothing to install) Name: Edge URL: https://edge.network/mcp Headers: Authorization: Bearer ea_live_YOUR_CODE_HERE Copy Try it: Deploy this folder as a static site on Edge and give me the URL. .continue/config.yaml mcpServers: - name: Edge Network command: npx args: ["-y", "@edge-network/mcp"] env: EDGE_AGENT_CODE: ea_live_YOUR_CODE_HERE Copy Try it: Add bot protection to my contact form using Edge Shield. Terminal — Aider has no MCP support, so it reads Edge instructions from a conventions file export EDGE_AGENT_CODE="ea_live_YOUR_CODE_HERE" curl -s "https://edge.network/agent/prompt?format=text" -o CONVENTIONS.md aider --read CONVENTIONS.md Copy Try it: Using the Edge API described in CONVENTIONS.md (auth via $EDGE_AGENT_CODE), deploy ./dist as a static site. pip install "edge-network-agent[langchain]" from edge_network_agent import EdgeAgentTools edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE") tools = edge.langchain_tools() system_prompt = edge.starter_prompt() Copy Try it: agent.invoke({"input": "Deploy my React build to portfolio.example.com"}) pip install "edge-network-agent[llamaindex]" from edge_network_agent import EdgeAgentTools from llama_index.core.agent import ReActAgent edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE") agent = ReActAgent.from_tools(edge.llamaindex_tools(), llm=llm) Copy Try it: agent.chat("Create a storage bucket called assets and upload ./images to it") pip install "edge-network-agent[crewai]" from edge_network_agent import EdgeAgentTools from crewai import Agent edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE") deployer = Agent( role="Infrastructure Engineer", goal="Deploy and monitor applications on Edge Network", tools=edge.crewai_tools(), ) Copy Try it: Task: "Deploy the marketing site and verify it responds with a 200" npm install @edge-network/ai-tools ai import { generateText } from 'ai' import { createEdgeTools, fetchStarterPrompt } from '@edge-network/ai-tools' const edgeTools = await createEdgeTools({ agentCode: 'ea_live_YOUR_CODE_HERE' }) const result = await generateText({ model, system: await fetchStarterPrompt(), tools: edgeTools, prompt: 'Deploy the ./dist folder to my-site.example.com', }) Copy Try it: prompt: 'Deploy the ./dist folder to my-site.example.com' For clients that support remote MCP servers — nothing to install { "mcpServers": { "edge": { "url": "https://edge.network/mcp", "headers": { "Authorization": "Bearer ea_live_YOUR_CODE_HERE" } } } } Copy Try it: Works with any MCP client that supports streamable-HTTP servers. Any HTTP client — the API is self-describing curl https://edge.network/agent \ -H "Authorization: Bearer ea_live_YOUR_CODE_HERE" Copy Try it: The discovery response documents every endpoint. Add "X-Dry-Run: true" to any mutation to preview it with a cost estimate. Aider conventions file Aider doesn't speak MCP, but it excels at following a conventions file. The Edge starter system prompt — what Edge offers, how to authenticate, dry-run discipline, the tell_user convention, and the claim flow — is served as plain markdown, so the conventions file is one curl away: curl -s "https://edge.network/agent/prompt?format=text" -o CONVENTIONS.md aider --read CONVENTIONS.md Keep the access code out of the file: export it as EDGE_AGENT_CODE and tell Aider to use $EDGE_AGENT_CODE in its curl commands. The prompt is versioned — re-run the curl occasionally to pick up improvements. What your agent gets All integrations expose the same tool set, served live from the API (so they never go stale): deploy static sites and full VM-backed apps, manage projects (health, scale, teardown), storage buckets and uploads, DNS zones and records, Shield bot-protection widgets, and Assist AI-answer sites — plus discovery, cost-estimating dry runs, and the account claim flow. Discovery endpoint → Deploy static site → Self-signup → Back to Docs Need help? --- ### Deploy Application URL: https://edge.network/docs/agent/deploy-app/ Markdown: https://edge.network/docs/agent/deploy-app.md JSON: https://edge.network/json/docs/agent/deploy-app.json _Deploy a VM-based application with one API call. Provisions compute, runs setup scripts, and optionally configures CDN and DNS._ Agent Tooling Deploy Application Provision a VM, run a setup script, and optionally add CDN and DNS — all in one call. Compute Sizes Simplified size names that map to specific resource allocations: Size vCPU RAM Disk Use Case nano 1 1 GB 20 GB Testing, small scripts small 1 2 GB 40 GB Simple apps, APIs medium 2 4 GB 80 GB Production apps large 4 8 GB 160 GB High-traffic apps xlarge 8 16 GB 320 GB Databases, heavy workloads Request POST /agent/deploy/app Authorization: Bearer ea_live_... { "project": "my-saas-app", "compute": { "os": "ubuntu-24.04", "size": "small", "region": "london", "setup_script": "#!/bin/bash\napt update && apt install -y docker.io\ndocker run -d -p 8080:8080 myapp:latest", "ssh_key": "ssh-ed25519 AAAA..." }, "networking": { "firewall_rules": [ { "port": 80, "protocol": "tcp" }, { "port": 443, "protocol": "tcp" }, { "port": 22, "protocol": "tcp", "source": "203.0.113.0/24" } ] }, "domain": "app.example.com", "cdn": { "enabled": true } } Instead of an inline setup_script , you can reference a tested script from the startup script library by ID (discover them via GET /agent/compute/scripts ): { "project": "my-blog", "compute": { "size": "small", "script": "wordpress", "script_params": { "site_title": "My Blog", "admin_email": "me@example.com" }, "ssh_key": "ssh-ed25519 AAAA..." } } Parameters Field Required Description project Yes Project name compute.size Yes nano, small, medium, large, or xlarge compute.os No Operating system. Default: ubuntu-24.04 compute.region No Deployment region. Default: london compute.script No Startup script ID from GET /agent/compute/scripts (e.g. docker , nodejs ). Preferred over setup_script — library scripts are tested and maintained. compute.script_params No Parameters for the chosen script, e.g. {"db_password": "..."} compute.setup_script No Inline bash script to run on first boot. Mutually exclusive with compute.script . compute.ssh_key No SSH public key string (e.g. ssh-ed25519 AAAA... ). Auto-creates a key on the account and attaches it. Connect afterwards with ssh root@ . compute.ssh_key_ids No IDs of existing SSH keys (from /agent/compute/ssh-keys ) to attach. networking.firewall_rules[] No Inbound firewall rules for the VM networking.firewall_rules[].port Yes (in rule) Port number (e.g. 80, 443, 8080) networking.firewall_rules[].protocol No tcp (default) or udp networking.firewall_rules[].source No Source CIDR, default 0.0.0.0/0 (anywhere) domain No Domain for the app cdn.enabled No Place CDN in front of the VM Firewall Rules Firewall rules in the deploy request create a security group that is automatically attached to the VM. Each rule defines an inbound port, protocol, and optional source CIDR. Agents can also manage security groups independently via the /agent/compute/firewall endpoints — create groups, attach them to VMs, or detach them as needed. New VMs have no firewall by default — all ports are open. If you attach a custom security group, make sure it includes an inbound rule for tcp/22 or you will lock yourself out of SSH. SSH Access Every Edge VM uses root as the default SSH user (regardless of OS). Connect with ssh root@ using a private key whose public counterpart is attached to the VM. At creation time (preferred) Pass the user's public key as compute.ssh_key , or attach pre-saved keys via compute.ssh_key_ids . The key is baked in via cloud-init at first boot. After creation If the VM already exists, do not recreate it . Save the key on the account, then attach it to the running VM — Edge pushes the key into authorized_keys via the guest agent within ~10 seconds. # 1. Save the user's public key on the account POST /agent/compute/ssh-keys Authorization: Bearer ea_live_... { "name": "alice-laptop", "public_key": "ssh-ed25519 AAAA... alice@laptop" } # Response: { "ssh_key": { "id": "key_abc123", "name": "alice-laptop", "fingerprint": "SHA256:..." }, "next_steps": [ "Pass this key ID in compute.ssh_key_ids when creating a VM, OR", "Attach to an existing VM with: POST /agent/compute/vms/{vmId}/ssh-keys/key_abc123" ] } # 2. Attach the key to the existing VM (no need to recreate it) POST /agent/compute/vms/vm_xyz789/ssh-keys/key_abc123 Authorization: Bearer ea_live_... # Response: { "attached": true, "vm_id": "vm_xyz789", "ssh_key_id": "key_abc123", "ssh": { "user": "root", "host": "64.34.86.100", "command": "ssh root@64.34.86.100", "note": "Wait ~10s for guest-agent push, then connect with your matching private key." }, "tell_user": "SSH key attached to VM \"my-saas-app\". Key is being pushed to the running VM via the guest agent (typically <10s). Connect with: ssh root@64.34.86.100" } Connection timing VM provisioning: ~30-60 seconds until vm.status === "running" Key propagation on first boot: an additional ~30-90 seconds Key push to a running VM (guest-agent path): ~10 seconds Poll GET /agent/compute/vms/{id} — the response includes a ready-to-use ssh.command field once the VM is connectable If the user has no SSH key yet Have them generate one locally — the private key never leaves their machine: ssh-keygen -t ed25519 -C "edge-network" cat ~/.ssh/id_ed25519.pub # paste this into ssh_key SSH endpoints Method Endpoint Description GET /agent/compute/ssh-keys List SSH keys on the account POST /agent/compute/ssh-keys Save a public key on the account (returns keyId) DELETE /agent/compute/ssh-keys/{id} Delete a key from the account (must be detached first) GET /agent/compute/vms/{id}/ssh-keys List keys attached to a specific VM POST /agent/compute/vms/{id}/ssh-keys/{keyId} Attach an existing key to a VM (works on running VMs) DELETE /agent/compute/vms/{id}/ssh-keys/{keyId} Detach a key (removes from authorized_keys on running VMs) Available Endpoints All compute endpoints available to agents: Method Endpoint Description GET /agent/compute/vms List VMs GET /agent/compute/vms/{id} VM details with live metrics GET /agent/compute/os-templates Available operating systems GET /agent/compute/scripts Startup scripts (Edge library + custom) with parameters GET /agent/compute/regions Available deployment regions GET /agent/compute/ssh-keys List SSH keys POST /agent/compute/ssh-keys Save an SSH public key POST /agent/compute/vms/{id}/ssh-keys/{keyId} Attach SSH key to existing VM DELETE /agent/compute/vms/{id}/ssh-keys/{keyId} Detach SSH key from VM GET /agent/compute/firewall List security groups GET /agent/compute/firewall/{id} Security group details POST /agent/compute/firewall Create security group POST /agent/compute/vms/{id}/firewall/{groupId} Attach security group DELETE /agent/compute/vms/{id}/firewall/{groupId} Detach security group Response { "status": "provisioning", "project_id": "proj_b2c3d4e5f6a7", "vm": { "id": "vm_xyz789", "name": "my-saas-app", "status": "provisioning", "ip": "64.34.86.100", "specs": "1 vCPU, 2 GB RAM, 40 GB disk" }, "ssh": { "user": "root", "host": "64.34.86.100", "command": "ssh root@64.34.86.100", "ready": false, "note": "Wait until vm.status is \"running\" (~30-60s) and key propagation completes (~30-90s on first boot)." }, "next_steps": [ "Poll: GET /agent/compute/vms/vm_xyz789 until vm.status === \"running\"", "Then connect: ssh root@64.34.86.100" ], "resources_created": [ { "type": "compute_vm", "id": "vm_xyz789", "name": "my-saas-app", "size": "small" }, { "type": "cdn_deployment", "id": "dep_abc123" } ], "tell_user": "VM \"my-saas-app\" is being provisioned (small: 1 vCPU, 2GB RAM). IP: 64.34.86.100. Your setup script will run on first boot. SSH ready once status is \"running\". Connect: ssh root@64.34.86.100." } The VM starts in provisioning status. It typically takes 30-60 seconds to become running . Use the health check endpoint to monitor. Health Check... --- ### Deploy Static Site URL: https://edge.network/docs/agent/deploy-static-site/ Markdown: https://edge.network/docs/agent/deploy-static-site.md JSON: https://edge.network/json/docs/agent/deploy-static-site.json _Deploy a static website with one API call. Upload files directly or deploy from a GitHub/GitLab repository._ Agent Tooling Deploy Static Site One API call deploys a complete static website — storage bucket, file uploads, CDN, domain, SSL, and DNS. What It Does The deploy/static-site endpoint orchestrates five services in one call: 1 Storage — Creates a bucket (named after the project) 2 Upload — Uploads files (from request body or cloned from git) 3 CDN — Creates a deployment with the bucket as origin 4 Domain — Adds your domain to the CDN with automatic SSL 5 DNS — Auto-creates CNAME record if the zone is on Edge DNS Request POST /agent/deploy/static-site Authorization: Bearer ea_live_... { "project": "my-portfolio", "source": { "type": "upload", "files": [ { "path": "index.html", "content": "PCFET0NUWVBFIGh0bWw+Li4=", "content_type": "text/html" }, { "path": "styles.css", "content": "Ym9keSB7IG1hcmdpbjogMDsgfQ==", "content_type": "text/css" }, { "path": "app.js", "content": "Y29uc29sZS5sb2coJ2hlbGxvJyk=", "content_type": "application/javascript" } ] }, "domain": "portfolio.example.com" } Deploy from Git Instead of uploading files directly, you can deploy from a GitHub or GitLab repository. The agent clones the repo and deploys the specified directory. POST /agent/deploy/static-site Authorization: Bearer ea_live_... { "project": "my-portfolio", "source": { "type": "git", "repo": "user/my-portfolio", "branch": "main", "path": "dist" }, "domain": "portfolio.example.com" } Use the path parameter to specify a subdirectory (e.g. dist or build ) — only that directory will be deployed. Private Repositories For private repositories, include a personal access token: { "source": { "type": "git", "repo": "user/private-site", "branch": "main", "path": "build", "token": "ghp_xxxxxxxxxxxx" } } Parameters Field Required Description project Yes Project name. Created automatically if it doesn't exist. source.type Yes "upload" for base64 files, "git" to deploy from a repository source.files[] Required for type 'upload' Array of files. Each needs path and content (base64). source.files[].content_type No MIME type. Auto-detected from file extension if omitted. source.repo For git GitHub/GitLab URL or user/repo shorthand source.branch For git Branch or tag. Default: main source.path For git Subdirectory to deploy (e.g. "dist", "build"). Root if omitted. source.token For git Personal access token for private repositories source.changed_only No Skip unchanged files on update (compares MD5 hashes) domain No Domain to serve from. SSL provisioned automatically. options.spa_mode No Enable single-page app mode (route all paths to index.html). options.image_optimization No Enable on-the-fly image optimization via CDN. Response { "status": "deployed", "project_id": "proj_a1b2c3d4e5f6", "url": "https://portfolio.example.com", "resources_created": [ { "type": "storage_bucket", "id": "my-portfolio", "name": "my-portfolio" }, { "type": "cdn_deployment", "id": "dep_xyz789", "name": "my-portfolio" }, { "type": "dns_record", "id": "zone_abc", "note": "CNAME portfolio → cdn.edge.network" } ], "tell_user": "Your site is live at https://portfolio.example.com. 3 files deployed to Edge CDN with automatic SSL." } Dry Run Add X-Dry-Run: true to preview what would be created: POST /agent/deploy/static-site Authorization: Bearer ea_live_... X-Dry-Run: true # Response: { "dry_run": true, "would_create": [ { "type": "storage_bucket", "name": "my-portfolio" }, { "type": "cdn_deployment", "name": "my-portfolio" }, { "type": "cdn_domain", "domain": "portfolio.example.com" }, { "type": "dns_record", "note": "CNAME → cdn.edge.network (if zone on Edge DNS)" } ], "file_count": 3, "tell_user": "Would create storage bucket, upload 3 files, and configure CDN. Domain portfolio.example.com would be added with SSL." } Updating a Deployment After the initial deploy, use PATCH /agent/deploy/{projectId} to push updates without recreating resources: PATCH /agent/deploy/proj_a1b2c3d4e5f6 Authorization: Bearer ea_live_... { "source": { "type": "upload", "files": [ { "path": "index.html", "content": "PCFET0NUWVBFIGh0bWw+Li4=", "content_type": "text/html" } ] }, "purge_cdn": true } # Response: { "project": "my-portfolio", "files_uploaded": 1, "cdn_purged": true, "tell_user": "Updated \"my-portfolio\": 1 file uploaded. CDN cache purged." } Incremental Updates Set changed_only: true to skip uploading files that haven't changed. The agent compares MD5 hashes of each file against the existing deployment and only uploads differences. PATCH /agent/deploy/proj_a1b2c3d4e5f6 Authorization: Bearer ea_live_... { "source": { "type": "upload", "files": [...], "changed_only": true }, "purge_cdn": true } # Response: { "project": "my-portfolio", "files_uploaded": 3, "files_skipped": 47, "cdn_purged": true, "tell_user": "Updated \"my-portfolio\": 3 files uploaded. 47 unchanged files skipped. CDN cache purged." } Auto-Detected Content Types If content_type is omitted, it's detected from the file extension: .html → text/html .css → text/css .js → application/javascript .json → application/json .png → image/png .jpg → image/jpeg .svg → image/svg+xml .webp → image/webp .woff2 → font/woff2 .mp4 → video/mp4 .pdf → application/pdf .xml → application/xml See Also Deploy Application Deploy a VM-based application Projects Health checks, scaling, and teardown Back to Docs Need help? --- ### Discovery Endpoint URL: https://edge.network/docs/agent/discovery/ Markdown: https://edge.network/docs/agent/discovery.md JSON: https://edge.network/json/docs/agent/discovery.json _The agent's entry point to Edge Network. Returns capabilities, limits, existing resources, and a full self-describing API schema._ Agent Tooling Discovery Endpoint The first call every agent makes. Returns everything needed — account info, limits, available products with regions and OS templates, existing projects, and a full self-describing API schema. Endpoint GET https://edge.network/agent Authorization: Bearer ea_live_... This single call gives the agent everything it needs to understand the account, what it can do, and what already exists. Without an Authorization header the same URL returns a public onboarding document instead: what Edge is, how to get a code (including autonomous self-signup ), and the starter system prompt at GET /agent/prompt . What's Returned Field Description account Account ID, name, plan, and the name of the agent access code budget Monthly spending cap, cap type (soft/hard), and currency products Available products with usage limits. Compute includes regions, OS templates, and VM sizes inline. capabilities Actions the agent is permitted to perform (based on access code permissions) projects Existing projects with description, resources, and creation date endpoints Full self-describing API schema — every available endpoint with parameters, types, defaults, and descriptions. This is the core of the discovery system. notes Guidance on dry run, idempotency, error handling, and the tell_user convention docs_url Link to full documentation. JSON version available via Accept: application/json header. tell_user Human-readable summary the agent can relay to the user Self-Describing API The endpoints object is the most important part of the discovery response. It describes every available endpoint with its parameters, types, required fields, defaults, and descriptions. An agent can read this once and know how to call every API — no documentation crawling needed. For mutating endpoints (POST, PATCH, DELETE), the schema includes the full request body shape. For example, the POST /agent/deploy/app endpoint describes every compute parameter (os, size, region), networking options (firewall rules), and optional CDN/DNS configuration. The endpoints schema in the actual response is much more detailed than the abbreviated example below — it includes full parameter definitions with types, enums, defaults, and descriptions for every field. Example Response Abbreviated for readability. The actual endpoints object contains full parameter schemas. { "api_version": "1", "docs_url": "https://edge.network/docs", "account": { "id": "acc_abc123", "name": "My Company", "plan": "scaleup", "agent_name": "Cursor - Production" }, "budget": { "cap_monthly": 5000, "cap_type": "soft", "currency": "USD" }, "products": { "compute": { "enabled": true, "limits": { "vms": { "max": 10, "used": 2 }, "vcpu": { "max": 16, "used": 4 }, "ram_gb": { "max": 32, "used": 8 } }, "regions": [ { "id": "london", "name": "London", "location": "London, UK" }, { "id": "new-york", "name": "New York", "location": "New York, US" } ], "os_templates": [ { "id": "ubuntu-24.04", "name": "Ubuntu 24.04 LTS", "family": "ubuntu" }, { "id": "debian-12", "name": "Debian 12", "family": "debian" } ], "sizes": ["nano", "small", "medium", "large", "xlarge"], "endpoint": "/agent/compute" }, "cdn": { "enabled": true, "endpoint": "/agent/cdn" }, "storage": { "enabled": true, "usage": { "buckets": 3, "total_size_bytes": 524288000 }, "endpoint": "/agent/storage" }, "dns": { "enabled": true, "endpoint": "/agent/dns" }, "shield": { "enabled": true, "description": "Free, privacy-first CAPTCHA alternative...", "modes": ["managed", "non-interactive", "invisible"], "agent_policies": ["allow", "challenge", "block"], "pricing": "Free — unlimited widgets and verifications.", "endpoint": "/agent/shield" }, "assist": { "enabled": true, "description": "AI answers for any website, grounded in its own content...", "pricing": "250 answered questions per site per month free, then $0.01/question...", "index_format": "JSON at a public URL: { \"pages\": [{ \"url\", \"title\", \"text\" }] }...", "endpoint": "/agent/assist" } }, "capabilities": [ "deploy_static_site", "deploy_app", "upload_assets", "provision_vm", "manage_dns", "check_health", "scale", "protect_forms", "add_ai_answers", "teardown" ], "projects": [ { "id": "proj_xyz", "name": "my-portfolio", "description": "Portfolio site", "resources": [ { "type": "storage", "id": "my-portfolio", "name": "my-portfolio" }, { "type": "cdn", "id": "dep_abc", "name": "my-portfolio" } ], "created_at": "2026-01-15T10:30:00.000Z" } ], "endpoints": { "POST /agent/deploy/static-site": { "description": "Deploy a static website from uploaded files or a git repo." }, "POST /agent/deploy/app": { "description": "Deploy a VM-based app with optional CDN and DNS." }, "PATCH /agent/deploy/{projectId}": { "description": "Update an existing deployment." }, "GET /agent/projects": { "description": "List all projects" }, "POST /agent/projects": { "description": "Create a project" }, "DELETE /agent/projects/{id}": { "description": "Teardown project and all resources." }, "GET /agent/compute/vms": { "description": "List VMs" }, "GET /agent/compute/os-templates": { "description": "List available OS" }, "GET /agent/compute/regions": { "description": "List regions" }, "GET /agent/compute/scripts": { "description": "List startup scripts" }, "GET /agent/compute/firewall": { "description": "List security groups" }, "POST /agent/compute/firewall": { "description": "Create security group" }, "GET /agent/cdn/deployments": { "description": "List CDN deployments" }, "GET /agent/storage/buckets": { "description": "List storage buckets" }, "POST /agent/storage/buckets": { "description": "Create bucket" }, "GET /agent/dns/zones": { "description": "List DNS zones" }, "POST /agent/dns/zones/{id}/records": { "description": "Add DNS record" }, "GET /agent/shield/widgets": { "description": "List Shield widgets" }, "POST /agent/shield/widgets": { "description": "Create a bot-protection widget" }, "GET /agent/assist/sites": { "description": "List Edge Assist sites" }, "POST /agent/assist/sites": { "description": "Create an AI-answers site" } }, "notes": { "dry_run": "Add X-Dry-Run: true header to preview without making changes.", "idempotency": "Add Idempotency-Key header for safe retries.", "tell_user": "Every response includes a tell_user field with a plain English summary.", "errors": "Error responses include code, message, suggestions, and tell_user." }, "tell_user": "Connected to Edge Network as \"My Company\". 6 products available: compute, cdn, storage, dns, shield, assist. 1 active project." } All Endpoints Every endpoint available to agents. All responses include tell_user . All mutating endpoints support X-Dry-Run: true . # Composite Actions POST /agent/deploy/static-site Deploy static site (upload or git) POST /agent/deploy/app Deploy VM-based application PATCH /agent/deploy/{projectId} Update existing deployment # Projects GET /agent/projects List projects POST /agent/projects Create project GET /agent/projects/{id} Project details GET /agent/projects/{id}/health Health check all resources POST /agent/projects/{id}/scale Scale compute resources DELETE /agent/projects/{id} Teardown project + all resources # Compute GET /agent/compute/vms List VMs POST /agent/compute/vms Create VM directly GET /agent/compute/vms/{id} VM details + live metrics + ssh.command GET /agent/compute/os-templates Available operating systems GET /agent/compute/regions Available regions GET /agent/compute/scripts Startup scripts (library + custom) # SSH Keys GET /agent/compute/ssh-keys List saved SSH keys POST /agent/compute/ssh-keys Save an SSH public key DELETE /agent/compute/ssh-keys/{id} Delete an SSH key GET /agent/compute/vms/{id}/ssh-keys List keys attached to VM POST /agent/compute/vms/{id}/ssh-keys/{keyId} Attach key to existing VM DELETE /agent/compute/vms/{id}/ssh-keys/{keyId} Detach key from VM # Fi... --- ### Framework Wrappers URL: https://edge.network/docs/agent/frameworks/ Markdown: https://edge.network/docs/agent/frameworks.md JSON: https://edge.network/json/docs/agent/frameworks.json _Official Edge Network tool packages for LangChain, LlamaIndex, CrewAI, and the Vercel AI SDK. Tool definitions are fetched from the MCP endpoint at runtime, so they never go stale._ Agent Tooling Framework Wrappers Building your own agent? Official packages expose the full Edge tool set as native tools for LangChain, LlamaIndex, CrewAI, and the Vercel AI SDK. How They Work Both packages fetch tool definitions from the MCP endpoint at runtime rather than bundling static copies — so when Edge ships a new tool or refines a description, your agent picks it up on the next run without a package update. Arguments are validated against each tool's JSON Schema before anything is sent. Package Registry Frameworks edge-network-agent PyPI LangChain, LlamaIndex, CrewAI — via optional extras @edge-network/ai-tools npm Vercel AI SDK ( generateText / streamText ) Authentication is the same everywhere: pass an agent access code explicitly or set the EDGE_AGENT_CODE environment variable. LangChain pip install "edge-network-agent[langchain]" from edge_network_agent import EdgeAgentTools from langchain.agents import create_react_agent edge = EdgeAgentTools(agent_code="ea_live_...") # or EDGE_AGENT_CODE env var agent = create_react_agent(model, tools=edge.langchain_tools()) agent.invoke({"messages": [ ("user", "Deploy ./dist as a static site on Edge and give me the URL") ]}) langchain_tools() returns StructuredTool instances with Pydantic argument models built from each tool's schema. Pass include=["edge_discover", "edge_deploy_static_site"] to expose a subset. LlamaIndex pip install "edge-network-agent[llamaindex]" from edge_network_agent import EdgeAgentTools from llama_index.core.agent import ReActAgent edge = EdgeAgentTools() # EDGE_AGENT_CODE env var agent = ReActAgent.from_tools(edge.llamaindex_tools(), llm=llm) agent.chat("What projects do I have on Edge, and are they healthy?") llamaindex_tools() returns FunctionTool instances ready for any LlamaIndex agent. CrewAI pip install "edge-network-agent[crewai]" from edge_network_agent import EdgeAgentTools from crewai import Agent edge = EdgeAgentTools() devops = Agent( role="DevOps engineer", goal="Deploy and monitor the team's sites on Edge", tools=edge.crewai_tools(), ) crewai_tools() returns BaseTool instances any crew member can use. Vercel AI SDK npm install @edge-network/ai-tools ai import { generateText } from 'ai' import { createEdgeTools, fetchStarterPrompt } from '@edge-network/ai-tools' const tools = await createEdgeTools({ agentCode: 'ea_live_...' }) const { text } = await generateText({ model, system: await fetchStarterPrompt(), tools, prompt: 'Deploy the ./dist folder as a static site and report the URL', }) createEdgeTools() resolves to a tool map for generateText and streamText ; fetchStarterPrompt() returns Edge's recommended system prompt. Without a Framework The Python package also works standalone — call tools directly and pull the starter prompt: edge = EdgeAgentTools(agent_code="ea_live_...") # Call any tool directly, no framework needed result = edge.call( "edge_deploy_static_site", project="my-site", files=[...], dry_run=True, # preview first ) # The recommended system prompt for agents working with Edge system = edge.starter_prompt() Next Steps MCP Tool Reference Every tool your agent gets, with parameters Agent Self-Signup Let agents provision their own explore-tier account Back to Docs Need help? --- ### MCP Server URL: https://edge.network/docs/agent/mcp/ Markdown: https://edge.network/docs/agent/mcp.md JSON: https://edge.network/json/docs/agent/mcp.json _The official Edge Network MCP server: local via npx or hosted at edge.network/mcp. 22 tools for deploying and managing infrastructure from any MCP client._ Agent Tooling MCP Server Edge ships an official Model Context Protocol server. Any MCP client — Cursor, Windsurf, Claude Desktop, Grok Bot, Continue, or your own agent — gets 22 native tools for deploying and managing Edge infrastructure. Quick Start Add one entry to your client's MCP config. No account, no API key, nothing else to install: { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"] } } } With no access code set, the server signs itself up for a free explore-tier account on first run and stores the credentials in ~/.edge/agent.json . For per-tool setup (Cursor, Windsurf, Claude Desktop, Grok Bot, Continue, Aider), see Connect Your Tool . Local or Remote The same tool set is available over two transports — pick whichever suits where your agent runs: Local (stdio) npx @edge-network/mcp — a zero-dependency bridge for editors and desktop clients. Handles credentials and auto-signup, then proxies JSON-RPC to the hosted endpoint. Best for: Cursor, Windsurf, Claude Desktop, Continue Remote (streamable HTTP) https://edge.network/mcp — a stateless JSON-RPC endpoint. No process to run; POST messages directly with your access code as a bearer token. Best for: Grok Bot and other cloud agents, serverless functions, custom clients POST https://edge.network/mcp Content-Type: application/json Authorization: Bearer ea_live_... { "jsonrpc": "2.0", "id": 1, "method": "tools/list" } Supported methods: initialize , ping , tools/list , and tools/call . The server is stateless — no sessions, no server-initiated streams — so every request stands alone. Authentication Request Auth required tools/list , initialize , ping None — tool definitions are public so clients can list them before connecting an account tools/call Authorization: Bearer ea_live_... — an agent access code , either created in the dashboard or self-provisioned Every tool call is dispatched through the same Agent API routes as direct HTTP requests, so access-code scopes, budget caps, free-tier limits, rate limits, and audit logging all apply identically. MCP adds no separate permission surface. { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"], "env": { "EDGE_AGENT_CODE": "ea_live_..." } } } } For the local bridge, pass your code via the EDGE_AGENT_CODE environment variable — or omit it for auto-signup. The Explore Tier Auto-signup accounts run in the explore tier: free-tier resources work for real — static site deploys, storage buckets, DNS zones, Shield widgets, Assist sites — while anything billable is blocked by a hard $0 budget cap. Billable actions still support dry_run , so an agent can price a VM deployment without being able to execute it. To unlock billing (and stop the ~7-day auto-purge of unclaimed accounts), the agent calls edge_request_claim with the operator's email — claiming links the account to a human. Details in Agent Self-Signup . The Tools 22 tools covering composite deploys ( edge_deploy_static_site creates storage + CDN + SSL + DNS in one call), projects, compute, storage, DNS, Shield, Assist, and account status. Billable tools are flagged in their descriptions and support dry-run previews with cost estimates. Full tool reference with parameters Next Steps Connect Your Tool Per-editor configs for Cursor, Windsurf, Claude, Continue, Aider MCP Tool Reference All 22 tools with parameters and descriptions Framework Wrappers LangChain, LlamaIndex, CrewAI, and Vercel AI SDK packages Agent Self-Signup How auto-signup and account claiming work Back to Docs Need help? --- ### MCP Tool Reference URL: https://edge.network/docs/agent/mcp-tools/ Markdown: https://edge.network/docs/agent/mcp-tools.md JSON: https://edge.network/json/docs/agent/mcp-tools.json _Every tool exposed by the Edge MCP server — 22 tools with parameters, types, and descriptions._ Agent Tooling MCP Tool Reference All 22 tools exposed by the Edge MCP server . This page is generated from the same definitions the live endpoint serves, so it always matches tools/list . edge_discover edge_deploy_static_site edge_deploy_app edge_update_deployment edge_list_projects edge_project_health edge_scale_project edge_teardown_project edge_list_vms edge_get_vm edge_list_buckets edge_create_bucket edge_upload_files edge_list_dns_zones edge_create_dns_zone edge_add_dns_record edge_list_shield_widgets edge_create_shield_widget edge_list_assist_sites edge_create_assist_site edge_account_status edge_request_claim Conventions Mutating tools accept dry_run: true to preview the action — including cost estimates — without executing it. Always dry-run anything billable first. Tools marked billable spend real money and are blocked on the explore tier (hard $0 cap) — dry-run still works there. Every result includes a tell_user summary the agent can relay verbatim. edge_discover Get everything about the connected Edge account: plan, budget, enabled products with limits and regions, current projects, and full API documentation. Call this first in every session. No parameters. edge_deploy_static_site Deploy a static website to Edge in one call: creates a storage bucket, uploads files (or clones a git repo), configures the global CDN with SSL, and wires DNS if the zone is on Edge. Free tier covers it. Provide either files (base64) or a git repo. Parameter Type Required Description project string Yes Project name (created if it does not exist), e.g. "my-portfolio" files object[] — Files to upload, base64-encoded. repo string — Git repository to deploy instead of files: "user/repo" or a full GitHub/GitLab URL branch string — Git branch or tag (default: main) source_path string — Subdirectory of the repo to deploy, e.g. "dist" or "build" git_token string — Personal access token for private repositories domain string — Custom domain to serve from, e.g. "app.example.com". SSL is auto-provisioned. spa_mode boolean — Enable single-page-app mode (all routes serve index.html) dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_deploy_app Billable Deploy a full application on a VM: provisions compute, runs a setup script, and optionally adds CDN and DNS. This is BILLABLE — always dry_run first and report the monthly cost to the user. Pass ssh_key (a public key string) to enable SSH access. Parameter Type Required Description project string Yes Project name size "nano" | "small" | "medium" | "large" | "xlarge" Yes nano: 1vCPU/1GB, small: 1/2GB, medium: 2/4GB, large: 4/8GB, xlarge: 8/16GB os string — Operating system template id (default ubuntu-24.04) region string — Deployment region (default london) — list regions via edge_discover script string — Startup script id from the Edge library (e.g. "docker", "nodejs") — preferred over setup_script script_params object — Parameters for the chosen library script setup_script string — Inline bash script to run on first boot (use script instead when a library script exists) ssh_key string — SSH public key string (e.g. "ssh-ed25519 AAAA...") to bake into the VM domain string — Domain for the app cdn boolean — Put the Edge CDN in front of the VM dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_update_deployment Update an existing deployment: upload changed files and optionally purge the CDN cache. Parameter Type Required Description project_id string Yes Project id (from edge_list_projects) files object[] Yes Files to upload, base64-encoded. changed_only boolean — Skip files whose content has not changed (MD5 comparison) purge_cdn boolean — Purge the CDN cache after upload dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_list_projects List all projects (groupings of resources) on the connected Edge account. No parameters. edge_project_health Comprehensive health check for every resource in a project: status, metrics, and actionable suggestions. Parameter Type Required Description project_id string Yes Project id (from edge_list_projects) edge_scale_project Billable Scale the compute resources in a project up or down. BILLABLE — dry_run first and report the cost change to the user. Parameter Type Required Description project_id string Yes Project id size "nano" | "small" | "medium" | "large" | "xlarge" Yes Target VM size reason string — Why you are scaling (recorded in the audit log) dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_teardown_project Destructive PERMANENTLY delete a project and every resource in it (VMs, buckets, CDN deployments, DNS zones). Irreversible — only use when the user has clearly asked. Set confirm to true to execute. Parameter Type Required Description project_id string Yes Project id confirm boolean — Must be true to actually delete. Without it the call fails with a summary of what would be deleted. dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_list_vms List all virtual machines on the account with status, size, and IPs. No parameters. edge_get_vm Get one VM: live status, metrics, IPs, attached SSH keys, and the ready-to-use SSH command. Poll until status is "running" before attempting SSH. Parameter Type Required Description vm_id string Yes VM id (from edge_list_vms) edge_list_buckets List storage buckets on the account. No parameters. edge_create_bucket Create an object storage bucket (S3-compatible). Free tier includes a limited number of buckets. Parameter Type Required Description name string Yes Bucket name: 3-63 chars, lowercase letters, numbers, hyphens dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_upload_files Upload files to an existing storage bucket. Parameter Type Required Description bucket string Yes Bucket name files object[] Yes Files to upload, base64-encoded. changed_only boolean — Skip files whose content has not changed (MD5 comparison) dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_list_dns_zones List DNS zones on the account. No parameters. edge_create_dns_zone Create a DNS zone for a domain on Edge authoritative DNS. Free. Parameter Type Required Description domain string Yes Domain name, e.g. "example.com" dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_add_dns_record Add a DNS record to a zone. Parameter Type Required Description zone_id string Yes Zone id (from edge_list_dns_zones) type "A" | "AAAA" | "CNAME" | "MX" | "TXT" | "NS" Yes Record type name string Yes Record name, e.g. "www" or "@" for the root data string Yes Record value, e.g. an IP address or target domain ttl number — TTL in seconds (default 300) priority number — Priority — required for MX records dry_run boolean — Preview the action without executing it. Returns what would happen, including cost estimates. Always dry-run first for anything that costs money. edge_list_shield_widgets List Edge Shield widgets (free, privacy-first CAPTCHA alternative). No parameters. edge_create_shield_widget Create an Edge Shield widget to protect a form or page from bots. Free. Return... --- ## Documentation ### Documentation - Edge Network URL: https://edge.network/docs/ Markdown: https://edge.network/docs.md JSON: https://edge.network/json/docs.json _Learn how to use Edge Network products. Comprehensive guides for Compute, CDN, DNS, Storage, Shield, and Assist._ Documentation Everything you need to build and scale with Edge Network. Guides, tutorials, and reference documentation for all our products. Get Started with CDN Go to Console Products Choose a product to explore its documentation. CDN Content delivery network with edge caching. Learn about cache configuration, purging, and optimization. Compute Virtual machines deployed globally in seconds. Learn about VM management, networking, firewalls, and more. DNS Fast, reliable DNS hosting with global anycast. Learn about record management and advanced features. Storage S3-compatible object storage. Learn about bucket management, access control, and integrations. Shield Free, privacy-first bot protection without puzzles. Learn about widgets, the humanity score, and Turnstile migration. Assist AI answers for your website, drawn from your own content. Learn about the widget, content ingestion, and the API. Dev Tooling Tools for developers to integrate and automate. REST API Manage every Edge resource over HTTPS with API keys. The same API that powers the console and CLI. CLI Command-line interface for managing all Edge resources. Single binary for macOS, Linux, and Windows. Command Palette Navigate anywhere and trigger actions instantly with keyboard shortcuts. Press / to open. API Keys Generate and manage API keys for programmatic access to Edge services. test.network Domains Get a development domain for $1/month. Instant setup, full DNS control, no registrar needed. Agent Tooling Let AI agents deploy and manage your infrastructure. Agent API Let AI agents deploy and manage your infrastructure. Discovery-first, budget-aware, with human-readable responses. Agent Access Codes Scoped credentials with product permissions and budget caps for safe agent access. Projects Group resources by app for unified health checks, cost tracking, and teardown. Account & Support Manage your account security and get help. Account & Support Manage your account, team members, billing, and access support resources. Teams Invite team members, manage roles and permissions, and collaborate effectively. Security Protect your account with 2FA, session management, and comprehensive audit logging. Referral Program Earn up to 15% of referred customers' spend for 3 years, credited straight to your balance. Popular Guides Jump straight to the most common tasks. CDN Deploy your first CDN CDN Image optimization Compute Create your first VM Assist Add AI answers to your site Dev Tooling Install the CLI Account Invite team members Security Enable two-factor authentication Can't find what you're looking for? Our support team is here to help. Contact Support --- ## Documentation › Compute ### Backups URL: https://edge.network/docs/compute/backups/ Markdown: https://edge.network/docs/compute/backups.md JSON: https://edge.network/json/docs/compute/backups.json _Learn how to create and manage backups for your VMs on Edge Network. Snapshots, restore points, and disaster recovery._ Data Protection Backups Protect your data with VM snapshots and backups. Overview Edge Network provides snapshot-based backups for your VMs. A snapshot captures the entire state of your VM's disk at a specific point in time, allowing you to restore to that exact state if needed. Manual Snapshots Create snapshots on-demand before making changes or deployments. Restore Anytime Roll back to any saved snapshot with a single click. Creating a Snapshot Create a snapshot to save the current state of your VM's disk. Navigate to your VM's Backups tab Click Create Snapshot Enter a descriptive name (e.g., "Before nginx update" or "2024-01-15") Click Create Tip: For best results, create snapshots when your VM is idle or has minimal activity. This ensures a consistent snapshot. Note: Snapshots capture the disk state, but not in-memory data. For databases, consider using database-native backup tools alongside snapshots. Managing Snapshots View and manage all snapshots for a VM from the Backups tab. Information Description Name The name you gave the snapshot Created Date and time the snapshot was taken Size Size of the snapshot Status Ready, Creating, or Error Restoring from a Snapshot Roll back your VM to a previous state by restoring from a snapshot. Go to your VM's Backups tab Find the snapshot you want to restore Click Restore Confirm the restoration Warning: This will overwrite current data Restoring a snapshot replaces all current data on your VM's disk with the snapshot's data. Any changes made after the snapshot was taken will be lost. What happens during restore: Your VM will be stopped if it's running The disk is replaced with the snapshot contents Your VM is restarted automatically IP addresses and other settings remain unchanged Deleting Snapshots Delete old snapshots you no longer need to free up storage. Go to your VM's Backups tab Find the snapshot you want to delete Click the trash icon Confirm deletion Warning: Deleted snapshots cannot be recovered. Make sure you no longer need the snapshot before deleting. Limits and Pricing Snapshot Limits 3 Snapshots per VM $0.05 Per GB per month 7 days Default retention Need more snapshots or longer retention? Contact support to discuss enterprise backup options. Best Practices Snapshot Before Major Changes Always create a snapshot before updates, deployments, or configuration changes. Use Descriptive Names Name snapshots with dates or descriptions so you know what state they represent. Combine with Application-Level Backups For databases, use pg_dump, mysqldump, etc. in addition to VM snapshots. Test Your Restores Periodically test restoring a snapshot to ensure your backups work when needed. Back to Docs Need help? --- ### Compute Documentation URL: https://edge.network/docs/compute/ Markdown: https://edge.network/docs/compute.md JSON: https://edge.network/json/docs/compute.json _Learn how to deploy and manage virtual machines on Edge Network. Complete guides for VM creation, networking, security, and monitoring._ Compute Virtual Machines Documentation Deploy and manage powerful virtual machines across 20+ global regions. From simple web servers to complex multi-tier applications. New to Edge Compute? Follow our getting started guide to deploy your first VM in under 5 minutes. Get Started Getting Started Your first VM in under 5 minutes Creating VMs Regions, configurations, and OS options Managing VMs Start, stop, resize, and delete Networking IPs, private networks, and bandwidth Firewall Security groups and traffic rules SSH Keys Key management and access Startup Scripts Automate VM setup on first boot Backups Snapshots and disaster recovery Monitoring Metrics, alerts, and performance Key Features 20+ Global regions <60s Deployment time $0 Egress fees Back to Docs Need help? --- ### Creating Virtual Machines URL: https://edge.network/docs/compute/creating-vms/ Markdown: https://edge.network/docs/compute/creating-vms.md JSON: https://edge.network/json/docs/compute/creating-vms.json _Complete guide to creating VMs on Edge Network. Learn about regions, operating systems, configurations, and deployment options._ Creating VMs Creating Virtual Machines Everything you need to know about deploying new VMs, from region selection to configuration options. Choosing a Region Edge Network offers VMs in 20+ regions worldwide. Choose a region close to your users for the lowest latency, or select based on compliance requirements. --> Edge currently offers VMs in two regions (Europe and USA), with many more coming soon. Choose the region closest to your users for the lowest latency. Europe London, UK North America Miami, FL Tip: You can deploy VMs across multiple regions for redundancy. Private networks work within a single region, but VMs can communicate across regions via their public IPs. Operating Systems Choose from a variety of pre-configured operating system images. All images are optimized for Edge infrastructure and include cloud-init for automated provisioning. Operating System Available Versions Ubuntu 24.04 LTS, 22.04 LTS, 20.04 LTS Debian 12, 11, 10 CentOS Stream 9, Stream 8 Alma Linux 9, 8 Rocky Linux 9, 8 Fedora 39, 38 FreeBSD 14.0, 13.2 Alpine Linux 3.19, 3.18 Custom ISOs: You can boot VMs from your own installer ISO. To set this up: Create a Storage bucket named iso and upload your .iso file (up to 10 GB) to it. Contact support to have the ISO reviewed and attached to your account. Once attached, "Custom ISO" appears as an operating system option when creating a VM. The VM boots your installer on a blank disk — complete the installation via the browser Console, configuring networking manually with the network details shown on the VM's Networking tab. Because ISO installs run entirely under your own OS, panel features that operate inside the guest — SSH keys, passwords, hostname changes, setup scripts, and enhanced monitoring — are unavailable; manage these within your operating system instead. VM Configuration Configure your VM's resources using the sliders. Each resource is priced individually and billed hourly from your prepaid balance. vCPUs (1-32) Virtual CPU cores for your VM. More cores allow better parallel processing and handling of concurrent requests. 1-2 vCPUs: Small applications, development, low-traffic websites 4-8 vCPUs: Production workloads, databases, medium traffic 16-32 vCPUs: High-performance applications, data processing Memory (1-64 GB) RAM available to your VM. Important for applications that cache data in memory. 1-2 GB: Minimal applications, static sites 4-8 GB: Most web applications, small databases 16-64 GB: Large databases, caching servers, in-memory processing NVMe Storage (10 GB - 2 TB) High-performance NVMe SSD storage. All storage is provisioned on fast NVMe drives. 25-50 GB: Small applications, containers 100-250 GB: Databases, file storage 500 GB - 2 TB: Large datasets, media storage SSH Key Selection Select one or more SSH keys to enable access to your VM. You must add SSH keys to your account before creating a VM. No SSH keys yet? Add SSH keys in Resources → SSH Keys before creating a VM. Learn more about SSH keys → Multiple keys: You can select multiple SSH keys. This is useful when multiple team members need access to the same VM. Advanced Options Hostname The hostname identifies your VM in the console and sets the system hostname. Use lowercase letters, numbers, and hyphens. web-server-1, api-prod, database-eu Tags (Coming Soon) Organize your VMs with custom tags for easier filtering and management. User Data (Coming Soon) Pass cloud-init scripts or configuration to automate VM setup on first boot. After Creating Your VM Managing VMs → Configure Firewall → Back to Docs Need help? --- ### Firewall URL: https://edge.network/docs/compute/firewall/ Markdown: https://edge.network/docs/compute/firewall.md JSON: https://edge.network/json/docs/compute/firewall.json _Configure firewall rules for your VMs on Edge Network. Control inbound and outbound traffic with easy-to-use security rules._ Security Firewall Control network traffic to and from your VMs with firewall rules. Overview The Edge Firewall controls inbound and outbound traffic to your VMs using security groups. Security groups are collections of rules that define which ports and protocols are allowed. Each VM can have multiple security groups attached. Security Groups Reusable sets of firewall rules. Attach them to any VM to instantly apply the same rules across your infrastructure. Default Deny When enabled, the firewall blocks all inbound traffic except what's explicitly allowed by attached security groups. Enabling the Firewall The Edge Firewall can be enabled or disabled per VM. When disabled, all traffic flows freely. When enabled, only traffic matching your security group rules is allowed through. Navigate to your VM in the console Click on the Firewall tab Use the Enable / Disable button at the top of the page New VMs: The firewall is enabled by default on newly created VMs. Make sure to attach the allow-ssh security group before enabling, or use the VNC console to access your VM. Migrated VMs: VMs migrated from a previous infrastructure have the firewall disabled by default. This ensures uninterrupted access. Enable it when you're ready and have confirmed the right security groups are attached. Security Groups Security groups are reusable collections of firewall rules. Each account comes with a set of default security groups that cover common use cases. Default Security Groups Name Ports Description allow-ssh TCP 22 SSH access allow-web TCP 80, 443 HTTP and HTTPS allow-ping ICMP Ping / ICMP echo allow-all-outbound All Unrestricted outbound traffic Attaching Security Groups Navigate to your VM's Firewall tab Under Available Security Groups , click Attach next to the group you want The rules take effect immediately Creating Custom Security Groups Go to Compute → Firewall in the console Click Create Security Group Add rules specifying protocol, port range, source CIDR, and action Save and attach to your VMs Common Firewall Rules Here are example rules for common use cases: Web Server (HTTP/HTTPS) Protocol Port Source Action TCP 80 0.0.0.0/0 (Any) Allow TCP 443 0.0.0.0/0 (Any) Allow SSH (Restricted to Your IP) More secure than allowing SSH from anywhere Protocol Port Source Action TCP 22 YOUR_IP/32 Allow Database (Private Network Only) Allow database connections only from your private network Protocol Port Source Action TCP 5432 (PostgreSQL) 10.185.0.0/24 Allow Allow Ping (ICMP) Protocol Type Source Action ICMP Echo Request 0.0.0.0/0 (Any) Allow How It Works When the firewall is enabled, it operates on a default-deny basis: All inbound traffic is blocked unless a security group explicitly allows it Established connections (return traffic) are always allowed ICMP is allowed when the allow-ping group is attached Outbound traffic is allowed when allow-all-outbound is attached ARP and DHCP traffic is always permitted for network connectivity Rules from all attached security groups are combined. If any group allows a port, it's open. Best Practices Principle of Least Privilege Only open ports that your application needs. Close everything else. Restrict SSH Access Limit SSH to your IP address or a VPN range instead of allowing from anywhere. Use Private Networks for Internal Services Databases and other internal services should only be accessible via private networks. Regularly Review Rules Remove rules for services you no longer use. Troubleshooting Can't connect to my service Check that you have an inbound rule allowing traffic on the correct port. Make sure the service is actually running on your VM ( sudo netstat -tlnp ). Locked out of SSH Use the VNC console in the console to access your VM and fix the firewall rules. The console works regardless of firewall settings. Rules not taking effect Check that the Edge Firewall is enabled on the VM's Firewall tab. When disabled, all traffic flows freely regardless of security groups. Also verify the correct security groups are attached. Firewall disabled after migration VMs migrated from a previous infrastructure have the firewall disabled by default. Navigate to the Firewall tab and click Enable to activate it. Make sure allow-ssh is attached first to avoid being locked out. Back to Docs Need help? --- ### Getting Started with Compute URL: https://edge.network/docs/compute/getting-started/ Markdown: https://edge.network/docs/compute/getting-started.md JSON: https://edge.network/json/docs/compute/getting-started.json _Deploy your first virtual machine on Edge Network in under 5 minutes. Step-by-step guide for beginners._ Getting Started Deploy Your First VM This guide will walk you through creating and connecting to your first virtual machine on Edge Network. Prerequisites An Edge Network account ( sign up here ) An SSH key pair (we'll show you how to create one if you don't have one) An SSH client (Terminal on Mac/Linux, or PuTTY on Windows) 1 Add an SSH Key Before creating a VM, you'll need to add an SSH key. This allows you to securely connect to your VM without a password. Generate a new SSH key (if you don't have one): ssh-keygen -t ed25519 -C "your_email@example.com" Press Enter to accept the default file location. Optionally add a passphrase for extra security. Navigate to Resources → SSH Keys in the console Click Add SSH Key Paste your public key (the contents of ~/.ssh/id_ed25519.pub ) Give it a memorable name and click Add Key 2 Create a Virtual Machine Now let's create your first VM. Navigate to Compute in the sidebar Click Create VM Choose a region close to your users (or yourself for testing) Select an operating system (Ubuntu 22.04 is a good default) Configure the resources : vCPUs: 1-2 for small workloads RAM: 2-4 GB for most applications Storage: 25-50 GB is a good starting point Select your SSH key Give your VM a hostname Click Create Your VM will be ready in under 60 seconds. You'll see the status change from "Provisioning" to "Running". 3 Connect to Your VM Once your VM is running, you can connect via SSH. Click on your VM to view its details Copy the public IP address Open your terminal and connect: ssh root@YOUR_VM_IP Replace YOUR_VM_IP with your VM's actual IP address. Congratulations! You're now connected to your Edge VM. You have full root access to install and configure anything you need. Next Steps Configure Firewall Secure your VM with firewall rules Set Up Networking Add IPs and private networks Enable Backups Protect your data with snapshots Monitor Performance View metrics and set up alerts Back to Docs Need help? --- ### Managing Virtual Machines URL: https://edge.network/docs/compute/managing-vms/ Markdown: https://edge.network/docs/compute/managing-vms.md JSON: https://edge.network/json/docs/compute/managing-vms.json _Learn how to manage your VMs on Edge Network. Start, stop, restart, resize, and delete virtual machines._ Managing VMs Managing Virtual Machines Learn how to control, monitor, and manage your VMs through the console. VM Dashboard Click on any VM to access its dashboard. Here you'll find quick actions, status information, and navigation to detailed management pages. Overview Quick actions, status, and basic VM information Metrics CPU, memory, disk, and network graphs Networking IP addresses, bandwidth, and private networks Firewall Inbound and outbound traffic rules Backups Snapshots and restore points Resize Adjust CPU, RAM, and storage Power Actions Control your VM's power state from the Overview page. Start Boot a stopped VM. The VM will start with its current configuration and disk contents. Stop Gracefully shut down the VM. Sends an ACPI shutdown signal, giving the OS time to close applications. Stopped VMs continue to consume disk storage but not CPU/RAM resources. Restart Reboot the VM. Equivalent to a graceful shutdown followed by a start. Suspend Pause the VM and save its memory state. When resumed, the VM continues exactly where it left off. Tip: Suspend is faster than Stop/Start since there's no boot sequence. Ideal for development workflows. Console Access Access your VM's console directly from the browser. Useful when SSH is not available or for troubleshooting boot issues. Navigate to your VM's Overview page Click Console in the quick actions A new window opens with VNC console access The console works even when SSH is unavailable, making it ideal for recovery scenarios or first-time setup. Resizing a VM Adjust your VM's resources as your needs change. Navigate to the Resize tab to modify CPU, RAM, or storage. CPU and RAM Can be changed while the VM is running (hot resize) or stopped. A restart may be required for changes to take effect. Storage Can be increased at any time. Storage cannot be decreased. You may need to extend the filesystem inside the VM. After increasing disk: You'll need to extend the partition and filesystem inside your VM. For Linux, use growpart and resize2fs . Deleting a VM To delete a VM, go to the VM's Settings or use the delete option from the VM list. This action is permanent Deleting a VM destroys all data on the VM's disk. Create a backup first if you need to preserve any data. Navigate to your VM's Overview page Click the Delete button Type the VM name to confirm Click Delete VM VM States Your VM can be in one of several states: State Description Running VM is running and accessible Stopped VM is powered off Starting VM is booting up Stopping VM is shutting down Provisioning VM is being created Error VM encountered an error (contact support) Back to Docs Need help? --- ### Monitoring URL: https://edge.network/docs/compute/monitoring/ Markdown: https://edge.network/docs/compute/monitoring.md JSON: https://edge.network/json/docs/compute/monitoring.json _Monitor your VMs on Edge Network with built-in metrics. Track CPU, memory, disk, and network performance in real-time._ Observability Monitoring Track your VM's performance with built-in metrics and graphs. Overview Edge Network provides built-in monitoring for all VMs at no additional cost. View real-time and historical metrics to understand your VM's performance. CPU Memory Disk Network Accessing Metrics View your VM's metrics from the Metrics tab in the VM dashboard. Navigate to your VM in the console Click on the Metrics tab Select a time range (1 hour, 6 hours, 24 hours, 7 days, or 30 days) CPU Metrics Monitor CPU utilization to understand your VM's processing load. CPU Usage (%) Percentage of CPU capacity being used. This is averaged across all vCPUs. 0-60%: Normal operation 60-85%: Elevated load, monitor closely 85-100%: High load, consider upgrading Tip: If CPU usage is consistently above 80%, consider adding more vCPUs or optimizing your application. Memory Metrics Track RAM usage to ensure your applications have enough memory. Memory Usage Used RAM actively in use by processes Cached RAM used for disk caching (can be freed) Available RAM available for new processes Total Total RAM allocated to your VM Warning: If available memory drops near zero, your VM may start using swap and performance will degrade significantly. Disk Metrics Monitor disk usage and I/O performance. Disk Usage Percentage of disk space used. Keep below 90% to avoid performance issues. Disk I/O (Read/Write) Data transfer rate to/from disk. Measured in MB/s or IOPS. Disk Latency Time for disk operations to complete. Lower is better (<10ms is excellent). Critical: If disk usage reaches 100%, your applications will fail to write data and may crash. Set up alerts before this happens. Network Metrics Track network traffic to and from your VM. Network In Data received by your VM (inbound traffic). Measured in Mbps. Network Out Data sent from your VM (outbound traffic). Measured in Mbps. Packets Number of network packets transmitted and received. Time Ranges Select different time ranges to view historical data: Range Resolution Use Case 1 Hour 1 minute Real-time debugging 6 Hours 5 minutes Recent activity 24 Hours 15 minutes Daily patterns 7 Days 1 hour Weekly trends 30 Days 4 hours Monthly overview Quick Stats The VM Overview page shows current resource usage at a glance: These metrics update automatically and give you immediate insight into your VM's current state. Monitoring Best Practices Check Metrics Regularly Review your metrics at least weekly to catch trends before they become problems. Understand Your Baseline Know what "normal" looks like for your application so you can spot anomalies. Scale Before You Need To If resources are consistently at 70-80% utilization, consider upgrading before issues occur. Correlate Metrics High CPU with normal memory often means CPU-bound workload. High memory with CPU spikes may indicate memory pressure. Coming Soon Alerts: Get notified when metrics exceed thresholds Export: Download metrics data as CSV Integrations: Send metrics to external monitoring tools Back to Docs Need help? --- ### Networking URL: https://edge.network/docs/compute/networking/ Markdown: https://edge.network/docs/compute/networking.md JSON: https://edge.network/json/docs/compute/networking.json _Learn about VM networking on Edge Network. Public IPs, additional IPs, private networks, and bandwidth management._ Networking Networking Manage IP addresses, private networks, and bandwidth for your virtual machines. Public IP Addresses Every VM is assigned a public IPv4 address upon creation. This is your VM's primary public address for incoming and outgoing traffic. Finding Your IP Address Navigate to your VM's Networking tab Your public IPv4 is displayed at the top Click the copy icon to copy to clipboard Static IPs: Your public IP remains the same for the lifetime of your VM. It only changes if you delete and recreate the VM. Additional IP Addresses You can add additional public IPv4 addresses to your VM for hosting multiple services, SSL certificates, or failover configurations. Adding an IP Address Go to your VM's Networking tab Click Add IP Confirm the additional cost ($2/month per IP) The new IP is allocated and displayed in the list Configuring Additional IPs Additional IPs are assigned to your VM but need to be configured in the operating system. Here's how to add an IP on Ubuntu/Debian: # Add a secondary IP to eth0 sudo ip addr add YOUR_NEW_IP/32 dev eth0 # Make it persistent (Ubuntu 18.04+) # Edit /etc/netplan/50-cloud-init.yaml and add: # addresses: # - YOUR_PRIMARY_IP/24 # - YOUR_NEW_IP/32 Removing an IP Address Go to your VM's Networking tab Find the IP you want to remove Click the trash icon next to the IP Confirm deletion Note: You cannot remove your primary IP address. Only additional IPs can be deleted. Private Networks Private networks allow your VMs to communicate with each other securely over a private network, without traffic going over the public internet. Benefits • Secure VM-to-VM communication • No exposure to public internet • Lower latency than public networking • Free bandwidth between VMs Limitations • Same region only • One private IP per network per VM • Maximum 10 networks per account Creating a Private Network Go to any VM's Networking tab Scroll to Your Private Networks Click Create Network Enter a name for the network Click Create Network The network is automatically assigned an IP range (e.g., 10.x.0.0/24 ) and gateway. Attaching VMs to a Network Go to the VM's Networking tab Click Attach Network Select the network from the dropdown The VM is assigned a private IP on that network # After attaching, the network interface appears automatically # Check with: ip addr show # You should see an interface like ens4 with your private IP # e.g., inet 10.185.0.2/24 Detaching and Deleting To detach a VM from a network, click the trash icon next to the attached network. To delete a network entirely, you must first detach all VMs from it. Private networks are free. There's no charge for creating or using private networks. Bandwidth Monitor your VM's bandwidth usage from the Networking tab. Edge Network includes generous bandwidth with zero egress fees. Zero Egress Fees Unlike other cloud providers, Edge Network doesn't charge for outbound data transfer. Upload and download as much as you need. Viewing Bandwidth Usage The Networking tab shows your current month's bandwidth usage: Inbound: Data received by your VM Outbound: Data sent from your VM Total: Combined bandwidth usage IPv6 IPv6 support varies by region. Where available, your VM is assigned a public IPv6 address in addition to its IPv4 address. IPv6 addresses are displayed in the Networking tab alongside your IPv4 addresses. Both protocols are supported simultaneously. Back to Docs Need help? --- ### SSH Keys URL: https://edge.network/docs/compute/ssh-keys/ Markdown: https://edge.network/docs/compute/ssh-keys.md JSON: https://edge.network/json/docs/compute/ssh-keys.json _Manage SSH keys for secure access to your VMs on Edge Network. Learn how to create, add, and manage SSH key pairs._ Security SSH Keys SSH keys provide secure, password-less access to your virtual machines. What are SSH Keys? SSH keys are a pair of cryptographic keys used for authentication. The private key stays on your computer, while the public key is added to your VM. When you connect, the server verifies that you have the matching private key. ✓ Advantages • More secure than passwords • Can't be brute-forced • No password to remember • Can be revoked instantly Key Types Supported • Ed25519 (recommended) • RSA (2048-bit minimum) • ECDSA Generating an SSH Key Pair If you don't already have an SSH key, you can generate one using your terminal. On Mac/Linux # Generate an Ed25519 key (recommended) ssh-keygen -t ed25519 -C "your_email@example.com" # Or generate an RSA key (wider compatibility) ssh-keygen -t rsa -b 4096 -C "your_email@example.com" When prompted: Press Enter to save to the default location ( ~/.ssh/id_ed25519 ) Optionally enter a passphrase for extra security On Windows Use PowerShell or the Windows Terminal: ssh-keygen -t ed25519 -C "your_email@example.com" Alternatively, use PuTTYgen if you prefer a graphical interface. View Your Public Key # Ed25519 cat ~/.ssh/id_ed25519.pub # RSA cat ~/.ssh/id_rsa.pub The output will look something like: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAI... your_email@example.com Adding SSH Keys to Your Account Add your public key to Edge Network so it can be installed on your VMs. Navigate to Resources → SSH Keys in the console Click Add SSH Key Paste your public key (the entire line starting with ssh- ) Give it a descriptive name (e.g., "MacBook Pro" or "Work Laptop") Click Add Key Tip: Add multiple keys for different devices. This makes it easy to revoke access from a lost or stolen device without affecting others. Using SSH Keys with VMs When Creating a VM During VM creation, you'll be prompted to select one or more SSH keys. These keys will be installed in the root user's ~/.ssh/authorized_keys file. Connecting to Your VM # Connect as root ssh root@YOUR_VM_IP # If your key is in a non-default location ssh -i ~/.ssh/my_custom_key root@YOUR_VM_IP Adding Keys to an Existing VM Currently, SSH keys are only installed during VM creation. To add keys to an existing VM, manually add them to the authorized_keys file: # SSH into your VM first, then: echo "your-public-key-here" >> ~/.ssh/authorized_keys Managing Your Keys Viewing Keys Your SSH keys are listed at Resources → SSH Keys . Each key shows: Name you assigned Key fingerprint (for verification) Date added Deleting Keys To delete a key from your account: Go to Resources → SSH Keys Click the trash icon next to the key Confirm deletion Important: Deleting a key from your Edge account does NOT remove it from existing VMs. The key will still work on VMs where it was already installed. Best Practices Use Ed25519 Keys Ed25519 keys are shorter, faster, and more secure than RSA. Use a Passphrase Protect your private key with a passphrase. Use ssh-agent to avoid typing it repeatedly. One Key Per Device Generate unique keys for each device. This way you can revoke access per device. Never Share Private Keys Your private key should never leave your device. Only share the public key. Troubleshooting "Permission denied (publickey)" • Ensure you selected the correct SSH key when creating the VM • Check that your private key file has correct permissions: chmod 600 ~/.ssh/id_ed25519 • Verify you're using the right key: ssh -v root@IP to see verbose output "Key already exists" Each public key can only be added once. If you see this error, check your existing keys—it may already be there under a different name. "Invalid key format" Make sure you're pasting the public key (ending in .pub), not the private key. The key should start with ssh-ed25519 or ssh-rsa . Back to Docs Need help? --- ### Startup Scripts URL: https://edge.network/docs/compute/scripts/ Markdown: https://edge.network/docs/compute/scripts.md JSON: https://edge.network/json/docs/compute/scripts.json _Automate VM setup with startup scripts. Use pre-built Edge library scripts or create your own to install software, configure services, and set up your environment on first boot._ Automation Startup Scripts Run scripts automatically on new VMs after OS installation. Choose from the Edge library or bring your own. How It Works Startup scripts execute once, automatically, when a VM first boots. They run as root via the guest agent — no SSH connection required. Scripts have a 10-minute timeout, and their output is captured for debugging. 1 Select a script when creating a VM 2 VM boots and OS installs 3 Script runs automatically Edge Script Library Pre-built, tested scripts maintained by Edge. Available to all users out of the box. Web Servers & Stacks Script Description Parameters LAMP Stack Apache, MySQL 8, PHP 8.3 db_password LEMP Stack Nginx, MySQL 8, PHP 8.3-FPM db_password Node.js Node.js 22 LTS, PM2, Nginx reverse proxy node_version Python Python 3.12, pip, Gunicorn, Nginx — Applications Script Description Parameters WordPress Nginx, MySQL, PHP-FPM, WP-CLI site_title admin_email db_password Docker Docker CE, Docker Compose — Development Tools Script Description Parameters PostgreSQL PostgreSQL 16, remote access configured db_password db_name Redis Redis 7, password auth, AOF persistence redis_password Security Script Description Parameters Hardened SSH Disable password auth, fail2ban, UFW — Using a Script When Creating a VM Navigate to Compute → Create VM Configure your VM as usual (region, OS, resources, SSH keys) In the Startup Script section, select a script from the dropdown If the script has parameters, fill them in (passwords are auto-generated if left blank) Click Create VM The script will run automatically once the VM finishes provisioning. You can check its status on the VM detail page. Tip: Scripts run before SSH is available. Your VM's software will be ready by the time you connect. Creating Custom Scripts Create your own scripts to automate any setup you need. Go to Compute → Scripts Switch to the My Scripts tab Click Create Script Write your bash script and optionally define parameters Save — your script is now available in the VM creation dropdown Script Guidelines Start with #!/bin/bash and set -e Exit on error so failures are caught and reported. Log progress with echo Output is captured and visible on the VM detail page. Use export DEBIAN_FRONTEND=noninteractive Prevents apt from prompting for input during package installation. Keep it under 10 minutes Scripts are killed after 10 minutes. For longer setups, have the script kick off a background task. Parameters Use the ${param_name} syntax in your script. When the VM is created, parameter values are substituted before execution. #!/bin/bash set -e DB_PASSWORD="${db_password:-$(openssl rand -base64 16)}" echo "Setting up database with password: $DB_PASSWORD" # ... your setup logic ... The :-default syntax provides a fallback if the parameter is empty. Checking Execution Status After creating a VM with a startup script, you can monitor its progress on the VM detail page. Pending — VM is still provisioning, script queued Running — script is executing inside the VM Completed — script finished successfully Failed — script encountered an error (click "View output" for details) Managing Scripts from the CLI The full script workflow is available in the Edge CLI — list the library, manage your custom scripts, and attach a script when creating a VM. # Browse available scripts (Edge library + your own) edge compute scripts list # Create a custom script from a file edge compute scripts create --name "My Setup" --file setup.sh # Run a script on a new VM, with parameters edge compute create --name blog --size s-2vcpu-4gb --image ubuntu-24 \ --region london --script wordpress \ --script-param site_title="My Blog" \ --script-param admin_email=me@example.com See the CLI Compute Commands reference for all script commands. API & Agent Access Startup scripts can also be used via the API and the AI agent. Inline Script (API / Agent) Pass a script directly when creating a VM using the setup_script field: POST /agent/compute/vms { "name": "my-server", "size": "small", "setup_script": "#!/bin/bash\nset -e\napt update && apt install -y nginx" } Using a Library Script by ID (Agent) Agents can list available scripts with GET /agent/compute/scripts and reference one by ID — parameter substitution happens server-side: POST /agent/deploy/app { "project": "my-blog", "compute": { "size": "small", "script": "wordpress", "script_params": { "site_title": "My Blog", "admin_email": "me@example.com" } } } The same script / script_params fields work on POST /agent/compute/vms . Checking Status GET /api/compute/vms/{vm_id}/scripts { "executions": [ { "id": "...", "script_name": "setup_script", "status": "completed", "output": "=== Docker Installed ===\nDocker: Docker version 27.4...", "started_at": "2026-03-03T00:15:00Z", "completed_at": "2026-03-03T00:17:34Z" } ] } Troubleshooting Script shows "Failed" • Click "View output" on the VM detail page to see the error • Make sure your script starts with #!/bin/bash • Check that all package names are correct for the selected OS • Ensure DEBIAN_FRONTEND=noninteractive is set for apt commands Script still "Pending" after VM is running Scripts are executed shortly after the VM reaches "running" status. Allow up to 30 seconds for the guest agent to initialise. If the status doesn't change, the guest agent may not be available — try restarting the VM. Script timed out Scripts are killed after 10 minutes. If your setup takes longer, have the script start a background process and exit. For example, use nohup ./long-task.sh & . Back to Docs Need help? --- ## Documentation › CDN ### Cache Purging URL: https://edge.network/docs/cdn/purging/ Markdown: https://edge.network/docs/cdn/purging.md JSON: https://edge.network/json/docs/cdn/purging.json _Clear cached content from Edge CDN by URL, path prefix, or everything at once, via console or API. Purges reach all edge nodes globally in under 200ms._ Cache Purging Clearing the Cache Instantly invalidate cached content across all edge nodes when you need to push updates. When to Purge You might need to purge cached content when: You've updated content at the origin and need to push changes immediately You've deployed a new version of your site and need to clear old assets You've found an error in cached content that needs to be corrected You've removed content that should no longer be accessible Cache Size Before purging, you can view the current cache size for your deployment. The Cache Size section shows real-time statistics about what's currently cached: Cached Objects 1,250 Number of items in cache Total Cache Size 524 MB Total bytes stored Avg Object Size 419 KB Average size per object These statistics are aggregated across all domains in your deployment and update in real-time. After a purge, you'll see these numbers decrease as cached content is removed. Purge Methods Purge by URL Clear a specific file from the cache. Use this when you've updated individual files. https://cdn.yoursite.com/images/hero.jpg Purge by Path Prefix Clear all files under a specific path. Useful for clearing an entire directory. /images/* /assets/css/* Purge Everything Clear the entire cache for a domain. Use sparingly as this temporarily increases origin load. Purging everything causes all requests to go to your origin until the cache is repopulated. This can temporarily increase origin load and response times. Purging via Console Navigate to your CDN deployment Click the Purge Cache button Select a purge method (URL, Path, or Everything) Enter the URL or path pattern (if applicable) Click Purge Purging via API Integrate cache purging into your CI/CD pipeline using the Edge API. # Purge specific URLs curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "urls": [ "https://cdn.yoursite.com/images/hero.jpg", "https://cdn.yoursite.com/css/main.css" ] }' # Purge by path prefix curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "paths": ["/images/*"] }' # Purge everything curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "all": true }' Purge requests propagate to all edge nodes globally in under 200ms. Purge Speed <200ms Global propagation 100% Edge node coverage Instant Effect on new requests Best Practices Use versioned URLs Instead of purging, use versioned filenames (e.g., app.v1.2.3.js ) and update references. This is more reliable and allows for instant rollback. Be specific when purging Purge specific URLs or paths rather than everything. This maintains cache efficiency and reduces origin load. Integrate with your deployment Add cache purging to your CI/CD pipeline so it happens automatically after deployments. Next Steps Caching Learn about cache behavior Analytics Monitor cache performance Back to Docs Need help? --- ### CDN Analytics URL: https://edge.network/docs/cdn/analytics/ Markdown: https://edge.network/docs/cdn/analytics.md JSON: https://edge.network/json/docs/cdn/analytics.json _Edge CDN analytics: track requests, bandwidth, cache hit rate and top content per domain, with time ranges from 24 hours to 30 days and 12-month retention._ Analytics CDN Analytics Get insights into your CDN traffic, cache performance, and bandwidth usage. Analytics Dashboard Each CDN deployment includes a real-time analytics dashboard showing key performance metrics. Key Metrics Total Requests The total number of HTTP requests served by the CDN across all domains in the deployment. Cache Hits Requests served directly from the edge cache without contacting your origin server. Cache Misses Requests that required fetching content from your origin server. Bandwidth Total data transferred from the CDN to end users. Cache Hit Rate Your cache hit rate is one of the most important CDN metrics. It shows what percentage of requests are being served from cache vs. fetched from origin. Cache Hit Rate 87.3% Cache Hits: 8,730 Cache Misses: 1,270 <50% Needs optimization 50-80% Good >80% Excellent Time Ranges View analytics across different time periods: Last 24 hours Last 7 days Last 30 days Per-Domain Analytics Click on any domain in your deployment to see its individual analytics: cdn.yoursite.com 12.5K requests assets.yoursite.com 8.2K requests images.yoursite.com 3.1K requests Top Content Identify your most requested content with the Top Content tab. This feature tracks the most popular paths across your CDN deployment in real-time. Metrics Per Path Request count Bandwidth served Cache hits Cache misses # Path Requests Bandwidth Hit Rate 1 /assets/logo.png 15.4K 147 MB 98% 2 /images/hero.jpg 8.7K 437 MB 97% 3 /api/products 3.2K 12 MB 45% Use Cases Popular Content Identify which assets drive the most traffic to optimize their delivery. Cache Optimization Find paths with low hit rates that may benefit from configuration changes. Bandwidth Hotspots See which content consumes the most bandwidth for cost analysis. Real-time Tracking Top Content data is collected in real-time from edge nodes. Up to 100 paths per domain are tracked, sorted by request count. The data refreshes automatically every minute. Traffic Visualization View your traffic patterns over time with interactive charts: Requests Over Time See request volume trends and identify peak traffic periods. Cache Performance Compare cache hits vs misses over time to monitor caching effectiveness. Bandwidth Usage Track data transfer volumes and plan for capacity. Data Retention Analytics data is stored with the following retention periods: Minute-level data 24 hours Hourly aggregates 7 days Daily aggregates 30 days Monthly aggregates 12 months Improving Cache Performance If your cache hit rate is lower than expected, try these optimizations: 1 Increase Cache-Control max-age Longer TTLs mean content stays cached longer. Use versioned URLs for assets that change. 2 Normalize query strings Avoid unnecessary query parameters that create different cache keys for the same content. 3 Remove Set-Cookie from static assets Responses with Set-Cookie headers aren't cached. Ensure your origin doesn't set cookies on static files. Activity Log Every CDN deployment includes a comprehensive activity log that records all changes and events. Access it from the Activity tab in your deployment dashboard. What's Logged Deployment created/deleted Domains added/removed Configuration changes Cache purge operations DNS verification status SSL certificate issuance Completed Action completed successfully Pending Action in progress Failed Action encountered an error Real-time Updates The activity log refreshes automatically every 10 seconds. You can also filter by event type or search for specific activities. Related Documentation Caching Understand cache behavior Cache Purging Clear cached content Back to Docs Need help? --- ### CDN Caching URL: https://edge.network/docs/cdn/caching/ Markdown: https://edge.network/docs/cdn/caching.md JSON: https://edge.network/json/docs/cdn/caching.json _How Edge CDN caching works: cache hits and misses, x-cache debug headers, TTLs and Cache-Control, what gets cached, pause cache mode, and Set-Cookie handling._ Caching Cache Configuration Understand how Edge CDN caches your content and optimize cache behavior for maximum performance. How Caching Works When a request comes in, Edge CDN first checks if the content is in the cache: 1 Request arrives 2 Check edge cache 3 Serve or fetch CACHE HIT Content is in cache and still valid. Served directly from the edge node in milliseconds. CACHE MISS Content is not in cache. Fetched from origin, cached, then served to the user. Response Headers Edge CDN adds headers to help you debug cache behavior: HTTP/2 200 content-type: image/jpeg x-cache: HIT x-cache-hits: 47 x-edge-location: eu-west-1 cache-control: public, max-age=31536000 age: 3600 x-cache Whether the request was a HIT (served from cache) or MISS (fetched from origin) x-cache-hits Number of times this item has been served from this edge node x-edge-location The edge node that served the request age How long the item has been in cache (in seconds) Cache TTL (Time to Live) Cache TTL determines how long content stays in the cache before being refreshed from origin. Edge CDN respects Cache-Control headers from your origin. Set these headers on your origin server to control cache behavior. You can also configure path-based caching rules in the Configuration tab to override TTLs or bypass caching for specific paths. Recommended TTLs by content type Content Type Recommended TTL Cache-Control Header Images (versioned) 1 year public, max-age=31536000, immutable CSS/JS (versioned) 1 year public, max-age=31536000, immutable Images (non-versioned) 1 day public, max-age=86400 HTML pages 5 minutes public, max-age=300 API responses No cache private, no-cache What Gets Cached By default, Edge CDN caches responses that: Return a 200 OK status code Have a cacheable Cache-Control header Are GET or HEAD requests Content that is NOT cached Responses with Cache-Control: no-store or private POST, PUT, DELETE requests Responses with Set-Cookie headers Error responses (4xx, 5xx) Pause Cache (Proxy Mode) During development or debugging, you may want to temporarily bypass caching and have all requests go directly to your origin. The Pause Cache feature puts your CDN deployment into proxy mode. What happens when cache is paused: All requests skip cache lookup and go directly to origin Responses are NOT stored in cache Request metrics still record (as cache misses) Existing cached content remains in cache but is not served How to pause cache You can pause caching for a deployment from two places: Deployment header: Click the Pause Cache button in the top-right corner of any deployment detail page. Deployments table: Use the Pause button in the Actions column on the main CDN dashboard. Use cases Development See changes immediately without waiting for cache to expire or purging manually. Debugging Verify origin responses directly without cache interference when troubleshooting issues. Testing Test origin changes or new deployments with live traffic before enabling caching. Emergency bypass Quickly bypass caching if you suspect cached content is causing issues. Remember to resume caching when you're done debugging. Running in proxy mode means every request hits your origin, which increases load and latency. Click Resume Cache to restore normal caching behavior. Cache Hit Rate Monitor your cache hit rate in the analytics dashboard. A higher hit rate means more requests are being served from cache, reducing origin load and improving performance. Set-Cookie Response Handling To protect user privacy and prevent session security issues, Edge CDN automatically detects responses containing Set-Cookie headers and excludes them from caching. Why This Matters If a response containing a Set-Cookie header were cached and served to other users, those users would receive cookies intended for someone else. This could cause: Session hijacking – Users could be logged into another user's session Authentication issues – Tokens or session IDs shared between users Privacy violations – User-specific preferences exposed to others Tracking problems – Analytics cookies assigned to wrong users How It Works Without Set-Cookie Response is cached normally at the edge and served to all users requesting the same resource. With Set-Cookie Response is passed through directly to the requesting user without caching. Each request fetches fresh from origin. Best Practice: If you're setting cookies on static assets, consider whether they truly need cookies. Moving cookie-setting logic to dedicated API endpoints keeps your static assets cacheable while maintaining proper session handling. Next Steps Cache Purging Clear cached content when you need to Analytics Monitor cache performance Back to Docs Need help? --- ### CDN Configuration URL: https://edge.network/docs/cdn/configuration/ Markdown: https://edge.network/docs/cdn/configuration.md JSON: https://edge.network/json/docs/cdn/configuration.json _Configure Edge CDN deployments with presets for static sites, e-commerce, media and APIs, plus JSON caching rules, path patterns, and image optimization._ Configuration CDN Configuration Fine-tune your CDN behavior with presets, caching rules, and image optimization settings. Configuration Presets Start with a preset optimized for your use case, then customize as needed. Static Website Long cache times for assets, short for HTML. Perfect for blogs, marketing sites, and documentation. E-commerce Optimized for product catalogs with frequent updates. Caches images aggressively, bypasses cart/checkout. Media & Streaming Large file handling with long TTLs. Ideal for video platforms, podcasts, and file downloads. API Gateway Minimal caching with origin pass-through. Good for APIs that need CDN's global network without caching. Custom Full control with JSON configuration. Define your own caching rules and image optimization settings. Custom Configuration For advanced use cases, you can define custom rules using JSON. Switch to "Advanced (JSON)" mode in the Configuration tab. { "caching": { "defaultTtl": 86400, "respectOriginHeaders": true, "rules": [ { "path": "/static/**", "ttl": 31536000 }, { "path": "/api/**", "bypassCache": true }, { "path": "/assets/*.css", "ttl": 604800 } ] }, "imageOptimization": { "enabled": true, "defaultQuality": 85, "defaultFormat": "auto", "rules": [ { "path": "/thumbnails/**", "quality": 70, "maxWidth": 400 }, { "path": "/hero/**", "quality": 90, "format": "avif" } ] } } Caching Rules Define path-based rules to control how different content is cached. Property Type Description path string Path pattern to match (supports * and ** wildcards) ttl number Cache duration in seconds bypassCache boolean Skip caching entirely for matched paths ignoreQueryString boolean Cache without considering query parameters Rules are evaluated in order. The first matching rule wins. If no rules match, the default TTL is used. Path Patterns Use glob-style patterns to match paths: * Matches any characters except / ** Matches any characters including / # Match all files in /static/ and subdirectories /static/** # Match only .jpg files in /images/ /images/*.jpg # Match a specific path /assets/logo.png # Match all API routes /api/** Image Optimization Settings Configure default image optimization behavior and path-specific rules. Property Type Description enabled boolean Enable/disable image optimization entirely defaultQuality number (1-100) Default compression quality for images defaultFormat string Default output format: auto , webp, avif, jpeg, png Auto Format Set defaultFormat to auto to automatically serve the best format based on browser support. The CDN checks the browser's Accept header and serves AVIF → WebP → JPEG in order of preference. Cache Purge Required Changing defaultQuality or defaultFormat only affects newly cached images. Existing cached images will continue to use the old settings until they expire or you purge the cache . Image Optimization Rules Override image optimization settings for specific paths: Property Type Description path string Path pattern to match quality number Override compression quality format string Override output format maxWidth number Maximum width in pixels Simple vs Advanced Mode Simple Mode Use form controls to set basic options: Default cache TTL Enable/disable image optimization Default quality and format Advanced Mode Full JSON configuration for: Path-based caching rules Cache bypass for specific paths Per-path image optimization rules Next Steps Caching Understand cache behavior in depth Image Optimization URL parameters for on-the-fly transforms Back to Docs Need help? --- ### CDN Deployments URL: https://edge.network/docs/cdn/deployments/ Markdown: https://edge.network/docs/cdn/deployments.md JSON: https://edge.network/json/docs/cdn/deployments.json _Learn how to create, manage, and configure CDN deployments on Edge Network._ Deployments Managing CDN Deployments Deployments are containers for your CDN domains. Learn how to organize and manage them effectively. What is a Deployment? A CDN deployment is a logical grouping of domains that share configuration and analytics. You might organize deployments by: Project - One deployment per website or application Environment - Separate deployments for staging and production Client - If managing multiple clients, one deployment per client CDN deployments list showing domains, traffic stats, and cache performance Creating a Deployment Navigate to CDN in the main menu Click Deploy CDN Enter a descriptive name for your deployment Click Create Deployment Creating a new CDN deployment Deployment Dashboard Each deployment has its own dashboard showing: Domains All domains configured for this deployment Cache Hit Rate Percentage of requests served from cache Requests Total requests over the selected time period Bandwidth Total data transferred Deployment dashboard showing stats, domains, and traffic overview Deployment Status Deployments can have the following statuses: active The deployment is live and serving traffic provisioning The deployment is being set up (usually takes a few seconds) suspended The deployment has been suspended (contact support) Deleting a Deployment When you delete a deployment, all associated domains are removed and traffic will stop being served immediately. Warning: This action cannot be undone Deleting a deployment will immediately stop serving all domains. Make sure you've updated your DNS records before deleting. Navigate to the deployment you want to delete Click the Delete button in the top right Confirm the deletion in the modal Next Steps Domains & SSL Add domains to your deployment Analytics Understand your traffic patterns Back to Docs Need help? --- ### CDN Documentation URL: https://edge.network/docs/cdn/ Markdown: https://edge.network/docs/cdn.md JSON: https://edge.network/json/docs/cdn.json _Learn how to use Edge Network CDN for fast, global content delivery with automatic SSL and image optimization._ CDN Content Delivery Network Accelerate your websites and applications with Edge Network's global CDN. Automatic SSL, intelligent caching, and real-time image optimization. Get Started in 5 Minutes Deploy your first CDN and start serving content globally Key Features Global Edge Network Content served from edge locations worldwide for sub-50ms response times. Automatic SSL Free Let's Encrypt certificates issued automatically for all domains. Smart Image Optimization On-the-fly resizing with auto-format detection (AVIF/WebP/JPEG based on browser). Presets & Custom Rules Start with optimized presets or define custom caching and image rules per-path. Instant Purging Clear cached content globally in under 200ms. Real-time Analytics Monitor requests, bandwidth, cache hit rates, identify top content, and track all changes with the activity log. CDN Dashboard CDN Dashboard showing deployments and traffic stats Documentation Getting Started Create your first CDN deployment Deployments Manage CDN deployments and settings Domains & SSL Add domains and configure SSL certificates Configuration Presets, caching rules, and image optimization settings Caching Configure cache behavior, TTLs, and pause cache for debugging Cache Purging Clear cached content instantly Image Optimization Resize, convert, and optimize images on-the-fly Analytics Monitor traffic, cache performance, and bandwidth Back to Docs Need help? --- ### Domains & SSL URL: https://edge.network/docs/cdn/domains/ Markdown: https://edge.network/docs/cdn/domains.md JSON: https://edge.network/json/docs/cdn/domains.json _Add custom domains to Edge CDN with an external URL or storage bucket origin, CNAME setup, automatic SSL via Let's Encrypt, and optional password protection._ Domains & SSL Managing Domains Add custom domains to your CDN deployment with automatic SSL certificate provisioning. Adding a Domain Each domain you add to a deployment needs to be configured with a domain name and an origin source. Domain The domain or subdomain visitors will use (e.g., cdn.yoursite.com ) Origin Type Choose where CDN fetches content from: External URL Pull content from any HTTP/HTTPS endpoint - your origin server, another cloud provider's storage, or any web-accessible URL. Example: https://your-bucket.s3.amazonaws.com Storage Bucket Use an Edge Storage bucket as your origin. No external URL needed - select from your buckets directly. Perfect for serving static assets, images, and files. Learn more about Edge Storage → Storage Bucket Integration When using a Storage bucket as your origin, CDN fetches content directly via internal networking. This means faster origin fetches, no public bucket configuration required, and unified billing. DNS Configuration After adding a domain, you need to configure your DNS to point to Edge CDN. For subdomains (recommended) Add a CNAME record: cdn.yoursite.com. CNAME cdn.edge.network. Root domains (apex domains) Root domains (e.g., yoursite.com ) cannot use CNAME records. Use your DNS provider's ALIAS or ANAME record type, or consider using Edge DNS which supports this natively. Domain Status Domains go through several states during setup: DNS Status pending Waiting for you to configure DNS verified DNS is correctly configured failed DNS check failed - verify your CNAME record SSL Status issuing... Certificate is being issued (30-60 seconds) active Valid SSL certificate is in place failed Certificate issuance failed - check DNS Automatic SSL Certificates Edge CDN automatically provisions free SSL certificates for all domains using Let's Encrypt. Free Certificates No cost for SSL - included with every domain Auto-Renewal Certificates renew automatically before expiration Fast Issuance Certificates issued in under 60 seconds TLS 1.3 Modern encryption with the latest TLS version Editing Domain Origin You can change the origin for any domain at any time without removing and re-adding it. Click on the domain row you want to edit The Edit Domain Origin modal will open Select a new origin type (External URL or Storage Bucket) Enter the new origin URL or select a different bucket Click Save Changes No downtime Changing the origin is seamless. The CDN will start fetching from the new origin for subsequent requests while existing cached content remains available. Root Path Behavior Control what happens when visitors access the root path ( / ) of your CDN domain directly. Proxy to Origin (default) Requests to the root path are proxied to your origin as normal. Use this if your origin has content at its root. Redirect to URL Redirect visitors to a URL of your choice. Useful when your CDN subdomain should redirect to your main site. 301 Permanent: For permanent redirects (SEO-friendly, browsers cache it) 302 Temporary: For temporary redirects (not cached) Show Edge Info Page Display a simple branded page identifying the domain as an Edge CDN endpoint. Useful for CDN-only subdomains that shouldn't be browsed directly. Common Use Case If your CDN is at cdn.yoursite.com serving assets for yoursite.com , you might want to redirect root path visitors to your main site rather than showing a directory listing or 404 from your origin. Password Protection Any CDN domain can be protected with a username and password (HTTP Basic Auth). Visitors are prompted for credentials by their browser before anything is served — ideal for sharing a dev build or staging site on a public URL without making it public. Open your deployment's Domains tab Click the lock icon on the domain you want to protect Enable Require a username and password and set the credentials Click Save — protection is live on the edge within seconds Enforced at the Edge Credentials are checked before the cache and origin — protected content is never served without them, not even from cache Hashed Storage Passwords are stored as bcrypt hashes — edge nodes never see the plaintext, and failed attempts are naturally rate-limited by the hash cost SSL Keeps Working Certificate issuance and renewal are exempt from the check, so protected domains still get automatic SSL No Performance Cost Verified credentials are cached at the edge, so authenticated requests are served at full CDN speed Private dev previews Upload a build to an Edge Storage bucket, serve it on a test domain with the bucket as origin, and enable password protection. You get a shareable HTTPS URL that only people with the credentials can open. Removing a Domain You can remove a domain from your deployment at any time. Traffic will stop immediately When you remove a domain, traffic to that domain will stop being served by Edge CDN. Update your DNS records to point elsewhere before removing. Click the trash icon next to the domain you want to remove Confirm the removal in the modal The domain and its SSL certificate will be removed Next Steps Configure Caching Set cache TTLs for your domains Image Optimization Enable on-the-fly image processing Back to Docs Need help? --- ### Getting Started with CDN URL: https://edge.network/docs/cdn/getting-started/ Markdown: https://edge.network/docs/cdn/getting-started.md JSON: https://edge.network/json/docs/cdn/getting-started.json _Step-by-step guide to deploying a CDN on Edge Network: create a deployment, add a domain and origin, set a CNAME record, and get automatic SSL within a minute._ Getting Started Deploy Your First CDN This guide will walk you through creating a CDN deployment and adding your first domain. Prerequisites An Edge Network account ( sign up here ) A domain or subdomain you want to serve through the CDN Access to your domain's DNS settings An origin server (where your content lives - S3, your web server, etc.) 1 Create a CDN Deployment A deployment is a container for your CDN domains. You might have one deployment per project or environment. Navigate to CDN in the sidebar Click Deploy CDN Enter a name for your deployment (e.g., "My Website" or "Production") Click Create Deployment 2 Add a Domain Now add the domain you want to serve through the CDN. Click Add Domain Enter your domain (e.g., cdn.yoursite.com ) Enter your origin URL (e.g., https://origin.yoursite.com or an S3 bucket URL) Click Add Domain About Origins The origin is where your actual content lives. This could be an S3 bucket, another CDN, your web server, or any URL that serves your static files. 3 Configure DNS Point your domain to Edge CDN by adding a CNAME record. Add this CNAME record at your DNS provider: Type CNAME Name/Host cdn Value/Target cdn.edge.network Replace "cdn" with your subdomain. For a root domain, you may need to use your DNS provider's CNAME flattening feature or an ALIAS record. Log in to your DNS provider (Cloudflare, Route53, etc.) Add a CNAME record pointing to cdn.edge.network Wait for DNS propagation (usually 1-5 minutes) Click Check DNS in the Edge console 4 Wait for SSL Certificate Once DNS is verified, we automatically issue a free SSL certificate for your domain using Let's Encrypt. SSL: issuing... SSL: active Certificate issuance typically takes 30-60 seconds. The page will update automatically. You're live! Your domain is now being served through Edge CDN with automatic SSL. Visit your domain to see it in action. Host a Static Site You can serve a static website directly from an Edge Storage bucket through CDN. Upload your files to a storage bucket, create a CDN deployment with Storage Bucket as the origin type, and add your domain. When using a storage bucket origin, the CDN automatically serves index.html for directory paths — e.g. visiting example.com/ serves index.html from the bucket root. This gives you a fully static hosting solution with global CDN caching, automatic SSL, and zero egress fees. Create a storage bucket Upload your site files (index.html, CSS, JS, images) Create a CDN deployment Add a domain with origin type Storage Bucket Your site is live The agent API can do all of this in one call with POST /agent/deploy/static-site . Storage documentation → Test Your CDN Verify everything is working correctly: # Check the response headers curl -I https://cdn.yoursite.com/path/to/file.jpg # Look for these headers: # x-cache: HIT (served from cache) # Server: Edge CDN (confirmation that Edge served the request) Next Steps Configuration Presets, caching rules, and image settings Image Optimization Resize and optimize images on-the-fly Caching Understand cache behavior and TTLs View Analytics Monitor traffic and cache performance Back to Docs Need help? --- ### Image Optimization URL: https://edge.network/docs/cdn/image-optimization/ Markdown: https://edge.network/docs/cdn/image-optimization.md JSON: https://edge.network/json/docs/cdn/image-optimization.json _Learn how to use Edge CDN's on-the-fly image optimization for resizing, format conversion, and quality adjustment._ Image Optimization On-the-Fly Image Processing Resize, convert, and optimize images at the edge without modifying your origin files. How It Works Image optimization is built into Edge CDN. Simply add query parameters to any image URL to transform it on-the-fly. Transformed images are cached at the edge for instant delivery. # Original image https://cdn.yoursite.com/images/hero.jpg # Resized to 800px wide with WebP format https://cdn.yoursite.com/images/hero.jpg?width=800&format=webp # Thumbnail with quality adjustment https://cdn.yoursite.com/images/hero.jpg?width=200&height=200&fit=cover&quality=80 Transformation Parameters Resize Parameter Description Example width Target width in pixels width=800 height Target height in pixels height=600 fit How to fit: cover, contain, fill, inside, outside fit=cover Format Conversion Parameter Description Example format Output format: auto, webp, avif, jpeg, png format=webp Available Formats auto Automatically selects the best format based on browser support (AVIF → WebP → JPEG) avif Best compression, smallest files, supported by modern browsers webp Great compression with wide browser support jpeg Universal compatibility, good for photos png Lossless, supports transparency Recommended: Use format=auto The auto format inspects the browser's Accept header and serves AVIF to browsers that support it, WebP to those that don't, and JPEG as a fallback. This ensures the smallest possible file size for each visitor. Quality Parameter Description Example quality Compression quality 1-100 (default: 80) quality=75 Effects Parameter Description Example blur Gaussian blur amount (0.3-1000) blur=10 sharpen Sharpen the image sharpen=true grayscale Convert to grayscale grayscale=true Low Quality Image Placeholders (LQIP) Generate tiny placeholder images for lazy loading. Show a blurred preview while the full image loads. Parameter Description Example lqip=1 Returns a tiny (~20px wide) blurred image ?lqip=1 lqip=base64 Returns a base64-encoded data URL (embed directly in HTML) ?lqip=base64 lqip=blurhash Returns a BlurHash string (4-5 bytes, decode client-side) ?lqip=blurhash # Tiny blurred placeholder (raw image) https://cdn.yoursite.com/hero.jpg?lqip=1 # Base64 data URL (embed in src attribute) https://cdn.yoursite.com/hero.jpg?lqip=base64 # BlurHash (returns JSON with hash, width, height) https://cdn.yoursite.com/hero.jpg?lqip=blurhash # → {"blurhash": "LEHV6nWB2yk8pyo0adR*.7kCMdnj", "width": 4, "height": 3} Animated GIF Support Animated GIFs are processed with ImageMagick to preserve all animation frames. You can resize and convert animated GIFs without losing the animation. Operation Supported Notes Resize Yes All frames are resized, animation preserved Convert to WebP Yes Animated WebP output, often smaller than GIF Convert to PNG Yes Animated PNG (APNG) output Quality adjustment N/A GIF is lossless — quality param is ignored for GIF output # Resize animated GIF to 400px wide https://cdn.yoursite.com/animation.gif?width=400 # Convert animated GIF to WebP (smaller file, keeps animation) https://cdn.yoursite.com/animation.gif?width=400&format=webp Common Use Cases Responsive Images Generate multiple sizes for srcset: Thumbnail Grid Create consistent thumbnails: https://cdn.yoursite.com/product-1.jpg?width=300&height=300&fit=cover&format=webp Blur Placeholder (LQIP) Generate a tiny blurred placeholder for lazy loading: https://cdn.yoursite.com/hero.jpg?width=20&blur=10&quality=30 Supported Formats JPEG Input & Output PNG Input & Output WebP Input & Output AVIF Input & Output GIF Input only SVG Passed through Default Settings Configure default image optimization settings in the Configuration tab: Default Format Set to auto to serve AVIF/WebP/JPEG based on browser support Default Quality Set a global quality (1-100) applied when no URL param is specified Path Rules Override quality/format for specific paths like thumbnails Performance Image transformations happen at the edge and are cached after the first request: <100ms First transformation <10ms Cached delivery ~70% Avg. size reduction Next Steps Watermarking Overlay your logo on served images Caching Learn about cache behavior Analytics Monitor image delivery stats Back to Docs Need help? --- ### Regional Distribution URL: https://edge.network/docs/cdn/geo-distribution/ Markdown: https://edge.network/docs/cdn/geo-distribution.md JSON: https://edge.network/json/docs/cdn/geo-distribution.json _Understand your global traffic patterns with geographic distribution analytics showing requests, bandwidth, and cache performance by region._ Analytics Regional Distribution Visualize your CDN traffic distribution across global regions to understand where your audience is located and how content performs in different geographies. Geographic Analytics The Geo Distribution tab in your CDN deployment dashboard provides a visual breakdown of traffic by geographic region. This data helps you understand global traffic patterns, identify key markets, and optimize content delivery strategies. How Regional Data is Collected Regional distribution data is derived from the geographic location of Edge CDN nodes serving your content, not from client IP geolocation. This approach provides accurate aggregate data without the overhead of per-request IP lookups. Server-Based Aggregation Traffic is attributed to the region where the CDN server is located. Since users are routed to their nearest edge node via anycast, this closely approximates the geographic distribution of your end users. Low Overhead No per-request IP geolocation lookups means zero latency impact on content delivery. Aggregate Insights Regional data is designed for analytics and strategic planning, not individual request tracking. Global Regions Traffic is organized into seven major geographic regions. These regions align with how global internet traffic flows and how content delivery networks typically segment their infrastructure. North America United States, Canada, and Mexico. Features high traffic volume from dense urban centers and advanced infrastructure. Major internet exchange points include New York, Los Angeles, Chicago, and Toronto. USA Canada Mexico Latin America Central and South America. Growing mobile traffic and emerging markets with increasing internet penetration. Major hubs include São Paulo, Buenos Aires, and Mexico City. Brazil Argentina Colombia Chile Europe Western, Eastern, and Northern Europe. Strong regulatory focus with GDPR influencing data handling. Major exchange points in London, Amsterdam, Frankfurt, and Paris. UK Germany France Netherlands Middle East & Africa (MEA) Middle East, North Africa, and Sub-Saharan Africa. Varied infrastructure with rapid growth in mobile adoption. Key markets include UAE, Saudi Arabia, South Africa, and Nigeria. UAE Saudi Arabia South Africa Nigeria East Asia & Southeast Asia Japan, South Korea, Singapore, Thailand, Vietnam, Indonesia, Malaysia, and the Philippines. Highly connected markets with sophisticated digital ecosystems. Major hubs in Singapore, Tokyo, and Hong Kong. Japan South Korea Singapore Indonesia South Asia & Oceania India, Australia, New Zealand, and Pacific Islands. Large and rapidly growing markets with diverse infrastructure. Key hubs in Sydney, Mumbai, and Delhi. India Australia New Zealand China Mainland China is treated as a separate region due to its massive scale, unique regulatory environment (including the Great Firewall), and distinct infrastructure requirements. Delivery to China may require specific compliance and partnership considerations. Mainland China Metrics Per Region Each region displays the following metrics, providing comprehensive insight into how your content performs globally: Traffic Share The percentage of total requests originating from this region relative to your global traffic. Requests Total number of HTTP requests served to users in this region during the selected time period. Bandwidth Total data transferred to users in this region, helping identify bandwidth hotspots. Cache Hit Rate Percentage of requests served from cache in this region. Higher is better for performance and cost. Use Cases Regional distribution data enables several strategic and operational decisions: Market Analysis Understand where your users are located and identify growing markets for business expansion. Content Strategy Optimize content and assets for regions with the highest traffic and engagement. Scheduling Plan maintenance windows and deployments around regional peak traffic periods. Compliance Understand data flow patterns for regulatory compliance like GDPR in Europe. Time Ranges View regional distribution data across different time periods: Last hour Last 24 hours Last 7 days Last 30 days Data resolution: Minute-level data is available for the last 24 hours. Hourly aggregates are used for 7-day and 30-day views, providing efficient queries while maintaining analytical accuracy. Data Retention Regional distribution data follows the same retention policy as other CDN analytics: Minute-level regional data 24 hours Hourly regional aggregates 30 days Daily regional aggregates 1 year Related Documentation CDN Analytics Full analytics overview Caching Optimize cache behavior Back to Docs Need help? --- ### Watermarking URL: https://edge.network/docs/cdn/watermarking/ Markdown: https://edge.network/docs/cdn/watermarking.md JSON: https://edge.network/json/docs/cdn/watermarking.json _Automatically overlay your logo on every image served through Edge CDN. Configured per domain, applied at the edge, no origin changes required._ Watermarking Image Watermarking Overlay your logo or badge on every image served through a CDN domain — applied at the edge, cached like any other variant, with no changes to your origin files. How It Works Watermarking is configured per domain and applied automatically — there are no URL parameters to add. When an image is fetched from your origin and processed at the edge, the watermark is composited onto it before the result is cached. Subsequent requests serve the watermarked image straight from cache. Upload a watermark image (PNG or WebP with transparency, up to 1 MB) in your domain's settings. Choose position, size, opacity, and margins. Every image served through the domain is watermarked from then on. Watermarking requires image optimization to be enabled on the domain — it runs as part of the same edge processing pipeline. The watermark asset is stored in your Edge Storage account in a bucket named cdn-assets . Settings Setting Description Default Position 9-point grid: corners, edges, or centre bottom-right Size Watermark width as a percentage of the output image width (1–50%) 15% Opacity 0–100% 60% Margin Distance from the image edges in pixels 16px Minimum width Images narrower than this are served without a watermark (thumbnails, placeholders) 200px Behaviour Notes Works with transforms The watermark is applied after resizing and effects, so it scales correctly with ?width= and other image optimization parameters . Each transform variant is watermarked and cached independently. Animated GIFs are watermarked on every frame. Cache updates are automatic Changing the watermark image or its settings automatically applies to images as they are next requested — no purge required. Enabling watermarking on a busy domain causes a one-time re-cache of image variants. Availability first If the watermark asset is temporarily unavailable, images are served unwatermarked rather than failing — delivery is never blocked by watermarking. Placeholders are excluded LQIP placeholders and images below the minimum width are never watermarked — a logo on a 20px blur preview helps nobody. Best Practices Use a PNG or WebP with a transparent background — solid backgrounds look like a sticker. Upload at roughly 2x the largest size it will render (e.g. a 600px-wide logo file for a 15% overlay on 2000px images) so it stays crisp. 60–70% opacity marks images clearly without ruining them; use 100% only for hard branding. Keep the minimum-width threshold at or above your thumbnail size so grids stay clean. Next Steps Image Optimization Resize, convert, and compress at the edge Cache Purging Force-refresh cached content Back to Docs Need help? --- ## Documentation › DNS ### DNS Backups URL: https://edge.network/docs/dns/backups/ Markdown: https://edge.network/docs/dns/backups.md JSON: https://edge.network/json/docs/dns/backups.json _Automated daily backups of your DNS zones with download and one-click restore._ DNS DNS Backups Automated daily snapshots of your DNS zones. Download as JSON, restore in one click, and never lose a DNS configuration again. $1/month per zone Enable daily backups on any DNS zone. Includes automated daily snapshots, manual on-demand backups, JSON download, and one-click restore. Automated backups are retained for 30 days. How It Works 1 Open a DNS zone and navigate to the Backups tab 2 Click Enable — $1/mo to activate daily backups for the zone 3 Automated backups run daily at 02:00 UTC. You can also create manual backups at any time. Backup Types Auto Created automatically at 02:00 UTC daily. Subject to retention policy. Manual Created on-demand via the "Create Backup" button. Useful before making major changes. Pre-restore Created automatically before a restore operation, so you can always undo a restore. Retention Automated backups expire after 30 days. Manual and pre-restore backups do not expire automatically. Plan Retention Hobbyist 7 days Dev 7 days Startup 30 days Scaleup / Business 30 days Enterprise 90 days Restoring from a Backup Go to the Backups tab on the zone Click the restore icon on the backup you want to restore Confirm the restore — a safety backup of the current state is created automatically All records are replaced with those from the backup Changes are pushed to the DNS network immediately Safety First A pre-restore backup is always created before restoring. If the restore doesn't produce the desired result, you can restore from the pre-restore backup to undo it. Downloading Backups Click the download icon on any backup to save it as a JSON file. The file contains all DNS records for the zone at that point in time. API GET /api/dns/zones/:id/backups — List backups for a zone POST /api/dns/zones/:id/backups — Create a manual backup GET /api/dns/zones/:id/backups/:bid — Download a backup as JSON POST /api/dns/zones/:id/backups/:bid/restore — Restore from a backup DELETE /api/dns/zones/:id/backups/:bid — Delete a backup POST /api/dns/zones/:id/backups/enable — Enable daily backups ($1/mo) POST /api/dns/zones/:id/backups/disable — Disable daily backups Metrics & Analytics DNS Examiner Back to Docs Need help? --- ### DNS Examiner URL: https://edge.network/docs/dns/examiner/ Markdown: https://edge.network/docs/dns/examiner.md JSON: https://edge.network/json/docs/dns/examiner.json _AI-powered DNS zone analysis. Check email deliverability, security, nameserver delegation, and best practices._ DNS DNS Examiner AI-powered zone analysis that checks your DNS configuration for issues across email, security, web, and nameserver delegation — then gives you specific fixes. Included with every account DNS Examiner is available on all Edge DNS plans at no extra cost. Run examinations as often as you need. How to Use 1 Open a DNS zone and navigate to the Examiner tab 2 Click Run Examination — the analysis takes up to 30 seconds 3 Review your health score, issues, and recommendations. Fix issues directly in the Records tab. What It Checks Email Deliverability Validates SPF, DKIM, and DMARC records. Checks MX configuration and flags missing or misconfigured email authentication. Security Reviews CAA records, checks for overly permissive wildcards, and verifies security-related DNS configuration. Web Accessibility Confirms A/AAAA records resolve, checks for CNAME-at-apex conflicts, and verifies www subdomain setup. Nameserver Delegation Compares live NS lookups against your assigned Edge nameservers. Identifies delegation mismatches at your registrar. Best Practices Audits TTL values, flags duplicate or conflicting records, checks MX priority spread, and identifies orphaned entries. Health Score Each examination produces a health score from 0 to 100 based on the severity and number of issues found. Score Rating Meaning 80–100 Good health No critical issues. Minor improvements may be suggested. 60–79 Needs attention Some warnings that should be addressed. 0–59 Issues found Critical issues that may affect email delivery, security, or availability. Issue Severity Issues are categorised by severity to help you prioritise fixes. Critical Issues that directly impact functionality — missing SPF causing email rejection, nameserver delegation mismatch, etc. Warning Potential problems that may cause issues — missing DMARC policy, no CAA record, suboptimal TTLs. Info Suggestions for improvement — adding a www CNAME, optimising TTL values, etc. Saved Results Examination results are saved automatically. When you return to the Examiner tab, your most recent result is displayed with the date and time it was run. Click Re-run at any time to get a fresh analysis. CLI DNS Examiner is also available via the Edge CLI. # Run an examination edge dns examine # View the last result edge dns examine-last # Output as JSON edge dns examine --output json Backups test.network Back to Docs Need help? --- ### DNS Metrics & Analytics URL: https://edge.network/docs/dns/metrics/ Markdown: https://edge.network/docs/dns/metrics.md JSON: https://edge.network/json/docs/dns/metrics.json _Monitor DNS query volume, latency, and response patterns across your zones._ Analytics Metrics & Analytics Edge DNS provides detailed metrics on query volume, response times, and traffic patterns to help you understand how your domains are being used. Available Metrics Query Count Total number of DNS queries received for your zone, broken down by time period. Latency Average and maximum response times in microseconds. Typical resolution is under 10ms. Query Types Breakdown by record type (A, AAAA, MX, TXT, etc.) to understand query patterns. Response Codes Distribution of response types: NOERROR, NXDOMAIN, REFUSED, etc. Geographic Distribution Query volume by country based on resolver location (GeoIP). Node Distribution Which Edge nodes handled your queries, showing traffic distribution. Time Ranges View metrics at different granularities based on your analysis needs: Range Granularity Data Points Last Hour 1 minute ~60 points Last 24 Hours 1 minute ~1,440 points Last 7 Days 1 hour ~168 points Last 30 Days 1 day ~30 points Data Retention Metrics are automatically aggregated and pruned to optimize storage while maintaining useful historical data: 1m Minute-level data 24 hours 1h Hourly aggregates 7 days 1d Daily aggregates 90 days Viewing Metrics 1 Navigate to your zone Go to DNS → select your domain 2 Click the Metrics tab View charts and statistics for your zone 3 Select time range Choose 1h, 24h, 7d, or 30d to adjust the view API Access Fetch metrics programmatically for custom dashboards or monitoring: # Get zone metrics GET /api/dns/zones/:id/metrics?range=24h # Response { "metrics": { "zone": "example.com", "from": "2024-01-14T00:00:00Z", "to": "2024-01-15T00:00:00Z", "granularity": "1m", "data": [ { "timestamp": "2024-01-14T00:00:00Z", "queryCount": 1234, "byType": { "A": 800, "AAAA": 300, "MX": 134 }, "byResponse": { "NoError": 1200, "NXDomain": 34 }, "byCountry": { "US": 500, "GB": 300, "DE": 200 }, "latencyAvgUs": 2500, "latencyMaxUs": 15000 } ] } } # Get account-wide DNS stats GET /api/dns/stats # Response { "stats": { "totalQueries": 1234567, "avgLatencyMs": 8, "zoneCount": 5, "recordCount": 47 } } Common Use Cases Traffic Monitoring Track query volume over time to understand traffic patterns and identify unexpected spikes that might indicate issues or attacks. Performance Analysis Monitor latency metrics to ensure DNS resolution stays fast. Investigate if max latency spikes occur during high traffic periods. Error Detection Watch response code distribution. High NXDOMAIN rates might indicate misconfigurations or broken links pointing to non-existent subdomains. Geographic Insights See where your users are located based on query origins. Useful for planning geo-routing or understanding your audience. Related Topics Zone Management Create and configure zones Geographic Routing Route traffic by location Back to Docs Need help? --- ### DNS Overview URL: https://edge.network/docs/dns/ Markdown: https://edge.network/docs/dns.md JSON: https://edge.network/json/docs/dns.json _Overview of Edge DNS: free anycast DNS with instant propagation, geographic routing, ALIAS records, and support for A, AAAA, CNAME, MX, TXT, CAA and more._ DNS Edge DNS Enterprise-grade authoritative DNS with global anycast distribution, instant propagation, and advanced features like geographic routing and ALIAS records. Key Features Global Anycast Network DNS queries are automatically routed to the nearest point of presence for ultra-low latency resolution worldwide. Instant Propagation Changes propagate to all edge nodes within seconds. No more waiting for TTL expiration or delayed updates. DDoS Protection Built-in protection against DNS amplification attacks and query floods with automatic rate limiting and filtering. Geographic Routing Route traffic to different endpoints based on the geographic location of the DNS resolver for optimal user experience. Architecture Edge DNS uses a master/slave architecture for reliability and performance: M Master Server Handles zone management, record updates, and API requests. Pushes changes to all slave nodes in real-time via NATS messaging. S Slave Nodes Distributed globally via anycast. Handle all DNS queries with local zone cache. Report query metrics back to master for analytics. Supported Record Types Type Description Use Case A IPv4 address Point domain to server IP AAAA IPv6 address IPv6 connectivity CNAME Canonical name Alias one domain to another ALIAS Apex CNAME alternative Point root domain to another hostname MX Mail exchange Email routing TXT Text record SPF, DKIM, domain verification NS Name server Delegate subdomains CAA Certification Authority Authorization Control which CAs can issue certificates SRV Service record Service discovery (SIP, XMPP, etc.) PTR Pointer record Reverse DNS lookups Metrics & Data Retention Query metrics are collected and aggregated at multiple granularities: Minute-level data 24 hours Hourly aggregates 7 days Daily aggregates 90 days Get Started Getting Started Add your first domain in minutes Zone Management Create and manage DNS zones DNS Records Configure A, CNAME, MX, and more Nameservers Unique nameserver pairs & verification Test Domains Get a test.network subdomain for $1/month ed.ge Domains The shortest premium edge domain — $1/month Back to Docs Need help? --- ### DNS Records URL: https://edge.network/docs/dns/records/ Markdown: https://edge.network/docs/dns/records.md JSON: https://edge.network/json/docs/dns/records.json _Reference for DNS record types in Edge DNS: A, AAAA, CNAME, ALIAS, MX, TXT, CAA and SRV, with examples and best practices for TTLs and email authentication._ Records DNS Records DNS records map domain names to IP addresses, mail servers, and other destinations. Learn about each record type and when to use them. A Address Record (IPv4) Maps a domain name to an IPv4 address. This is the most common record type used to point your domain to a web server. Example: Name: @ TTL: 300 Data: 185.199.108.153 Use @ for the root domain (example.com) or a subdomain name like www or api . AAAA Address Record (IPv6) Maps a domain name to an IPv6 address. Use alongside A records for dual-stack connectivity. Example: Name: @ TTL: 300 Data: 2606:4700:3033::ac43:b4a7 CNAME Canonical Name Record Creates an alias from one domain to another. The browser follows the CNAME to find the actual IP address. Example: Name: www TTL: 300 Data: example.com CNAME Restrictions CNAME records cannot be created at the zone apex ( @ ). Use an ALIAS record instead for root domain aliasing. ALIAS ALIAS Record Edge-specific record that works like a CNAME but can be used at the zone apex. Perfect for pointing your root domain to a load balancer, CDN, or another hostname. Example: Name: @ TTL: 300 Data: cdn.edge.network ALIAS records are resolved at query time. Edge DNS looks up the target hostname and returns the IP addresses directly to the client. MX Mail Exchange Record Specifies mail servers responsible for receiving email for your domain. MX records include a priority value - lower numbers have higher priority. Example (Google Workspace): Priority Name Data 1 @ aspmx.l.google.com 5 @ alt1.aspmx.l.google.com 5 @ alt2.aspmx.l.google.com TXT Text Record Stores arbitrary text data. Commonly used for domain verification, SPF, DKIM, and DMARC. SPF Record (email authentication): v=spf1 include:_spf.google.com ~all Domain Verification: google-site-verification=abc123... DMARC Policy: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com CAA Certification Authority Authorization Specifies which Certificate Authorities (CAs) are allowed to issue SSL certificates for your domain. Helps prevent unauthorized certificate issuance. Example: @ CAA 0 issue "letsencrypt.org" @ CAA 0 issuewild "letsencrypt.org" @ CAA 0 iodef "mailto:security@example.com" CAA Tags issue - CAs allowed to issue certificates issuewild - CAs allowed to issue wildcard certificates iodef - Email/URL to report violations SRV Service Record Specifies the location of services like SIP, XMPP, or LDAP. Includes priority, weight, port, and target hostname. Format: _service._protocol.name TTL SRV priority weight port target Example (SIP): _sip._tcp.example.com 300 SRV 10 60 5060 sip.example.com Best Practices Use appropriate TTLs Lower TTLs (60-300s) for frequently changing records. Higher TTLs (3600-86400s) for stable records to reduce DNS lookups. Always add both A and AAAA If your server supports IPv6, add both record types for optimal connectivity. Configure email authentication Set up SPF, DKIM, and DMARC TXT records to prevent email spoofing. Add CAA records Restrict which CAs can issue certificates to improve security. Related Topics Geographic Routing Route traffic by visitor location Zone Management Create and configure zones Back to Docs Need help? --- ### DNS Zone Management URL: https://edge.network/docs/dns/zones/ Markdown: https://edge.network/docs/dns/zones.md JSON: https://edge.network/json/docs/dns/zones.json _How DNS zones work in Edge DNS: create and verify a zone, understand pending, active and suspended states, SOA and TTL settings, and manage zones via the API._ Zone Management DNS Zones A zone represents a domain in Edge DNS. Learn how to create, manage, and monitor your zones. What is a DNS Zone? A DNS zone is a container for all the DNS records of a domain. When you add a domain to Edge DNS, you're creating a zone that will hold all the records (A, CNAME, MX, etc.) that define how traffic is routed to your domain. Example Zone Structure: Zone: example.com ├── A @ → 185.x.x.x ├── CNAME www → example.com ├── MX @ → mail.example.com (priority 10) └── TXT @ → "v=spf1 include:_spf.google.com ~all" Zone Lifecycle Pending Zone created but nameservers not yet verified. You can add records, but the zone won't serve DNS queries until nameservers are updated. Active Nameservers verified and zone is live. Edge DNS is serving queries for your domain from our global anycast network. Suspended Zone suspended due to policy violation or billing issue. DNS queries will return SERVFAIL until the issue is resolved. Creating a Zone 1 Navigate to DNS Open the DNS section from the main navigation. 2 Click "Add Zone" Start the zone creation wizard. 3 Enter your domain Enter the root domain (e.g., example.com ). Do not include www or other subdomains. 4 Update nameservers Copy your unique nameservers and update them at your domain registrar. ✓ Verify and activate Click "Verify Nameservers" once you've updated your registrar. Your zone becomes active immediately upon verification. SOA Record Every zone has a Start of Authority (SOA) record that defines key zone parameters. Edge DNS manages this automatically: MNAME Primary nameserver (your assigned ns1) RNAME Hostmaster email (hostmaster@yourdomain.com) Serial Version number (YYYYMMDDNN format, auto-incremented) Refresh Secondary server check interval (3600s) Retry Retry interval on refresh failure (900s) Expire Zone expiration if unreachable (604800s / 7 days) Minimum TTL Negative caching TTL (300s) The SOA serial is automatically updated whenever you add, modify, or delete records. This ensures secondary DNS servers and caches correctly detect zone changes. Zone Settings Each zone has configurable settings accessible from the zone's Settings tab: Setting Description Default TTL Time-to-live for records that don't specify one (default: 300 seconds) DNSSEC Enable or disable DNSSEC signing (coming soon) Deleting a Zone Warning: This is Destructive Deleting a zone immediately removes all records and stops serving DNS queries for the domain. This action cannot be undone. To delete a zone: Navigate to the zone you want to delete Click the ⋯ menu Select Delete Zone Confirm the deletion After deletion, remember to update your domain's nameservers back to your registrar's defaults or another DNS provider. API Reference Manage zones programmatically via the DNS API: # List all zones GET /api/dns/zones # Create a zone POST /api/dns/zones { "domain": "example.com" } # Get a zone GET /api/dns/zones/:id # Delete a zone DELETE /api/dns/zones/:id # Verify nameservers POST /api/dns/zones/:id/verify # Sync zone to DNS servers POST /api/dns/zones/:id/sync Sync behavior: Record changes are stored locally first for instant feedback, then synced to DNS servers automatically in the background. Use the /sync endpoint to trigger immediate propagation. Related Topics DNS Records Add and manage records in your zone Nameservers Understanding unique nameserver pairs Back to Docs Need help? --- ### ed.ge Domains URL: https://edge.network/docs/dns/edge-domains/ Markdown: https://edge.network/docs/dns/edge-domains.md JSON: https://edge.network/json/docs/dns/edge-domains.json _Get the shortest premium edge domain for $5/month. Perfect for personal brands, APIs, short links, and portfolio sites._ Premium Domains ed.ge Domains The shortest premium edge domain. Get you.ed.ge for $5/month — a real, working domain with full DNS control. What you get Ultra-short domain e.g. joe.ed.ge — just 9 characters. Perfect for business cards, social bios, and APIs. Full DNS control Add A, AAAA, CNAME, MX, TXT, and more — your domain, your rules. Managed through the Edge console. Instant activation No registrar, no waiting. Pick a name and it's live on Edge DNS immediately — globally distributed, low latency. Use cases Personal brand Point yourname.ed.ge to your portfolio, LinkedIn, or personal site. API endpoint Give your API a memorable short domain: api.ed.ge is cleaner than a long subdomain. Short links Build your own URL shortener on go.ed.ge or similar. CDN custom domain Use your ed.ge domain with Edge CDN for fast, branded content delivery. How to register Navigate to DNS → ed.ge in the console Type your desired subdomain — availability is checked in real-time Click Register to activate ($5/month, billed to your account) Your domain is live immediately — add DNS records from the zone editor Managing your domain Your ed.ge domain appears under DNS → ed.ge . Click on it to access the zone editor where you can add, edit, and delete DNS records. Supported record types A AAAA CNAME ALIAS MX TXT SRV CAA Note: NS and SOA records are managed automatically and cannot be modified. This ensures your domain always resolves correctly through Edge DNS. Pricing $5 /month per domain Billed monthly to your Edge account Cancel anytime — domain is released immediately Up to 5 ed.ge domains per account Unlimited DNS records per domain Deleting a domain To delete an ed.ge domain, go to DNS → ed.ge , click the menu on your domain, and select Delete . This will: Remove the DNS zone and all records Cancel the $5/month subscription Release the subdomain for others to register Warning: Deletion is permanent. All DNS records for this domain will be removed and the domain will stop resolving immediately. Back to Docs Need help? --- ### Geographic Routing URL: https://edge.network/docs/dns/geo-routing/ Markdown: https://edge.network/docs/dns/geo-routing.md JSON: https://edge.network/json/docs/dns/geo-routing.json _Geographic DNS routing in Edge DNS: per-record geo overrides by continent, country or sub-region, resolution priority, and EDNS Client Subnet support._ Advanced Geographic Routing Direct users to the nearest server or region-specific content by routing DNS queries based on the geographic location of the resolver. How It Works When a DNS query reaches Edge DNS, we determine the geographic location of the requesting resolver using GeoIP data. Based on your routing rules, we return different IP addresses or hostnames for different regions. 1 User makes request User in Tokyo visits example.com 2 DNS query routed to Edge Query arrives at nearest Edge DNS node via anycast 3 Location determined Edge identifies resolver as being in Japan/Asia ✓ Region-specific response Returns IP of Tokyo datacenter instead of default Use Cases Latency Optimization Route users to the nearest datacenter for faster response times. Reduce round-trip latency by serving from local regions. Load Distribution Spread traffic across multiple datacenters geographically. Prevent overload on any single location. Regional Content Serve region-specific versions of your site. Direct EU users to GDPR-compliant servers, for example. Data Sovereignty Keep user data within specific geographic boundaries by routing to region-locked infrastructure. Configuring Geographic Routing Add geographic overrides to any record by specifying region-specific values: # Add record with geo routing via API POST /api/dns/zones/:id/records { "type": "A", "name": "@", "data": "185.1.1.1", // Default (fallback) "ttl": 300, "geo": { "NA": "185.2.2.2", // North America "EU": "185.3.3.3", // Europe "AS": "185.4.4.4" // Asia } } Fallback Behavior The main data field is always returned for regions without a specific override. Routing Priority Edge DNS uses a 3-level hierarchy to find the best match for each user: 1 Zone (US-WEST) → 2 Country (US) → 3 Region (NA) → 4 Default A user in Los Angeles will first check for US-WEST , then US , then NA , before falling back to the default record. Regions (Continents) Use these region codes for continent-level routing: Code Region Coverage NA North America US, Canada, Mexico, Caribbean, Central America SA South America Brazil, Argentina, Chile, Colombia, etc. EU Europe UK, Germany, France, Italy, Spain, etc. AS Asia Japan, Korea, Singapore, Thailand, Vietnam, etc. OC Oceania Australia, New Zealand, Pacific Islands AF Africa South Africa, Nigeria, Kenya, Egypt, etc. ME Middle East UAE, Saudi Arabia, Israel, Turkey, etc. Sub-Country Zones For large countries, route by sub-region for even lower latency: 🇺🇸 United States US-WEST CA, OR, WA, NV, AZ, etc. US-EAST NY, NJ, FL, GA, VA, etc. US-CENTRAL TX, IL, MN, MO, etc. US-MIDWEST OH, MI, IN, KY, etc. 🇨🇦 Canada CA-WEST BC, AB, SK, MB CA-EAST ON, QC, NB, NS 🇦🇺 Australia AU-EAST NSW, VIC, QLD, ACT AU-WEST WA, SA, NT 🇬🇧 United Kingdom GB-ENGLAND England GB-SCOTLAND Scotland GB-WALES Wales GB-NI Northern Ireland 🇨🇳 China CN-NORTH Beijing, Tianjin, etc. CN-EAST Shanghai, Jiangsu, etc. CN-SOUTH Guangdong, Hong Kong CN-WEST Sichuan, Chongqing, etc. 🇮🇳 India IN-NORTH Delhi, Punjab, UP IN-SOUTH Karnataka, Tamil Nadu IN-WEST Maharashtra, Gujarat IN-EAST West Bengal, Bihar Also supported: BR-SOUTH , BR-NORTH (Brazil), RU-WEST , RU-EAST (Russia), DE-NORTH , DE-SOUTH (Germany) Complete Example Combine zones, countries, and regions for maximum control: { "type": "A", "name": "cdn", "data": "185.1.1.1", // Default fallback "geo": { // Regions (broadest) "NA": "64.34.80.40", // North America default "EU": "185.2.2.2", // Europe "AS": "103.1.1.1", // Asia // Countries (more specific) "US": "64.34.80.41", // United States "JP": "103.2.2.2", // Japan "AU": "103.3.3.3", // Australia // Zones (most specific) "US-WEST": "64.34.80.42", // US West Coast "US-EAST": "64.34.80.43", // US East Coast "AU-EAST": "103.3.3.4" // Sydney region } } Resolution examples: • User in Los Angeles → US-WEST → 64.34.80.42 • User in New York → US-EAST → 64.34.80.43 • User in Dallas → US (no zone match) → 64.34.80.41 • User in Toronto → NA (no CA entry) → 64.34.80.40 • User in Sydney → AU-EAST → 103.3.3.4 • User in Perth → AU (no AU-WEST) → 103.3.3.3 • User in Paris → EU → 185.2.2.2 • User in São Paulo → Default → 185.1.1.1 Best Practices Always set a default The main data field should always contain a valid value for regions not covered by your geo rules. Use regions for broad coverage Start with region codes (NA, EU, AS) rather than individual countries. Add country overrides only when needed. Monitor with metrics Use the geographic breakdown in zone metrics to verify traffic is being routed as expected. Test from multiple locations Use tools like dig from different regions or online DNS checkers to verify your geo routing works as expected. EDNS Client Subnet Support Edge DNS fully supports EDNS Client Subnet (ECS) , which allows us to route based on the actual user's location, not just the resolver's location. User-based routing when ECS is present Major DNS resolvers including Google (8.8.8.8), Cloudflare (1.1.1.1), and OpenDNS send ECS data. When present, Edge DNS uses the client subnet for geographic decisions, providing accurate routing based on the end user's actual location. When ECS is not available (e.g., privacy-focused resolvers), we fall back to the resolver's IP address for geographic determination. Considerations Privacy-focused resolvers: Some resolvers (like Quad9 with privacy mode) don't send ECS data. Users of these services will be routed based on the resolver's location. GeoIP accuracy: Location data is generally accurate to the country level, but city-level precision is not guaranteed. VPN users: Users connecting via VPN will be routed based on their VPN exit node location, which may differ from their physical location. Related Topics DNS Records Learn about record types Metrics & Analytics Monitor geographic traffic patterns Back to Docs Need help? --- ### Getting Started with DNS URL: https://edge.network/docs/dns/getting-started/ Markdown: https://edge.network/docs/dns/getting-started.md JSON: https://edge.network/json/docs/dns/getting-started.json _Step-by-step guide to adding a domain to Edge DNS: create a zone, point your registrar at your unique nameservers, verify ownership, and add DNS records._ Getting Started Add Your First Domain This guide walks you through adding a domain to Edge DNS and verifying ownership. Prerequisites An Edge Network account ( sign up here ) A domain name you own or manage Access to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) 1 Create a DNS Zone A zone represents your domain in Edge DNS. Each domain you want to manage needs its own zone. Navigate to DNS in the sidebar Click Add Zone Enter your domain name (e.g., example.com ) Click Create Zone Zone vs. Subdomain Create a zone for your root domain (example.com). Subdomains (www, api, blog) are managed as records within the zone. 2 Note Your Unique Nameservers After creating your zone, you'll be shown your unique Edge nameservers. These are specific to your account and must be used for all domains. Your nameservers will look like: ns1-abc123.edge.network ns2-abc123.edge.network The abc123 part is unique to your account. Keep Your Nameservers Secure Your unique nameserver pair ensures only you can add domains to your account. Never share these with untrusted parties. 3 Update Your Domain Registrar Log in to your domain registrar and update the nameservers for your domain. Common Registrars: GoDaddy My Products → Domain → Manage → Nameservers → Change Namecheap Domain List → Manage → Nameservers → Custom DNS Cloudflare Domains → Manage → Update DNS configuration Google Domains DNS → Name servers → Use custom name servers Propagation Time DNS changes can take up to 48 hours to propagate globally, though most updates complete within a few hours. 4 Verify Nameservers Once you've updated your registrar, verify the change in the Edge console. Return to your zone in the Edge console Click Verify Nameservers or Check Nameservers Now Wait for confirmation (usually a few seconds) Zone Activated! Once verified, your zone status changes to Active and Edge DNS begins serving queries for your domain. If verification fails, the console will show the current nameservers detected. Wait a few more minutes for propagation and try again. 5 Add DNS Records With your zone active, you can now add DNS records. Click Records tab in your zone Click Add Record Select the record type (A, CNAME, MX, etc.) Enter the record details and click Add Common First Records: Type Name Value A @ 185.x.x.x CNAME www example.com MX @ mail.example.com (priority 10) Test Your DNS Verify your records are resolving correctly: # Check A record dig example.com A +short # Check all records dig example.com ANY # Query Edge DNS directly dig @ns1-abc123.edge.network example.com A Don't have a domain? If you don't have a domain yet, you can register a test.network subdomain for $1/month. Navigate to DNS → test.network in the console, pick a subdomain name (e.g. my-project.test.network ), and the DNS zone is created instantly — no registrar configuration needed. You get full control over the zone (A, AAAA, CNAME, MX, TXT records, etc.). Full details on test.network domains → Next Steps DNS Records Learn about all record types Geographic Routing Route traffic by location Metrics & Analytics Monitor query volume and latency Nameserver Security How unique NS pairs protect you Back to Docs Need help? --- ### Nameservers & Domain Verification URL: https://edge.network/docs/dns/nameservers/ Markdown: https://edge.network/docs/dns/nameservers.md JSON: https://edge.network/json/docs/dns/nameservers.json _How Edge DNS assigns each account a unique nameserver pair to verify domain ownership, prevent hijacking, and activate zones instantly after NS checks._ Security Nameservers & Domain Verification Edge DNS uses unique nameserver pairs per account to ensure only you can add and manage your domains. The Domain Ownership Problem Traditional DNS services use shared nameservers (e.g., ns1.provider.com ). This creates a security risk: anyone could potentially add your domain to their account if they know you're using the same provider. Without Unique Nameservers An attacker could add your domain to their account and intercept your traffic, read your emails, or issue fraudulent SSL certificates. Edge's Unique Nameserver Solution Every Edge account is assigned a unique pair of nameservers. When you add a domain, we verify that the domain's NS records point to your specific nameservers before activating the zone. Your Unique Nameservers: 1 ns1- {your-id} .edge.network 2 ns2- {your-id} .edge.network The {your-id} portion is a unique 6-character identifier assigned to your account. Cryptographic Binding Your unique nameserver pair creates a cryptographic binding between your account and your domains. No one else can use your nameservers, and no one else can add domains using your nameservers. How Verification Works 1 You add a domain Enter your domain name in the Edge console. The zone is created in "pending" status. 2 Update your registrar Change your domain's nameservers at your registrar to your unique Edge nameservers. 3 We verify ownership When you click "Verify", we query the public DNS for your domain's NS records using DNS-over-HTTPS for fresh, uncached results. ✓ Zone activated If both your nameservers are present in the response, your zone is instantly activated and begins serving DNS queries. Technical Details Verification Process Uses Cloudflare DNS-over-HTTPS (1.1.1.1) for fresh lookups Falls back to system resolver if DoH is unavailable Requires both nameservers to be present Case-insensitive comparison # Check your domain's current nameservers dig NS example.com +short # Expected output (your unique pair): ns1-abc123.edge.network. ns2-abc123.edge.network. Infrastructure: Wildcard DNS To support the unique nameserver system at scale, Edge uses a wildcard DNS record for all nameserver subdomains: # In edge.network zone: *.edge.network. 300 IN A 185.x.x.x *.edge.network. 300 IN A 185.x.x.y This means any ns1-*.edge.network or ns2-*.edge.network hostname automatically resolves to Edge's DNS servers. No per-customer DNS management required. Security Benefits Prevents Domain Hijacking No one can add your domain to their account because they don't have your unique nameservers. Proof of Control Updating nameservers requires access to your domain registrar, proving you control the domain. Audit Trail The unique identifier in your nameservers provides an audit trail linking domains to accounts. Instant Verification No waiting for TXT record propagation or email verification - just update NS and verify. Frequently Asked Questions Can I use the same nameservers for all my domains? Yes! Your unique nameserver pair is assigned to your account, not to individual domains. Use the same nameservers for all domains in your Edge account. What if verification keeps failing? DNS propagation can take up to 48 hours. Wait a few hours and try again. If issues persist, ensure your registrar shows the correct nameservers with no typos. Can I regenerate my nameservers? Currently, nameserver pairs are permanent. Contact support if you believe your nameservers have been compromised. Why two nameservers? DNS best practices require at least two nameservers for redundancy. Both resolve to Edge's anycast network but provide failover if one is unreachable. Related Topics Getting Started Add your first domain Zone Management Create and configure zones Back to Docs Need help? --- ### Test Domains URL: https://edge.network/docs/dns/test-domains/ Markdown: https://edge.network/docs/dns/test-domains.md JSON: https://edge.network/json/docs/dns/test-domains.json _Get a subdomain of test.network for $1/month. Perfect for development, staging, and testing — fully managed DNS you control._ DNS Test Domains Need a domain for development or testing? Get a subdomain of test.network for $1/month. No domain registrar needed — just pick a name and start building. What you get Your own subdomain e.g. my-project.test.network — a real, working domain you can use anywhere. Full DNS zone control Add A, AAAA, CNAME, MX, TXT, and all other record types. It's a fully delegated zone — you manage it like any domain. Automatic SSL Point your test domain at Edge CDN and SSL certificates are provisioned automatically via Let's Encrypt. Instant activation test.network domains are activated instantly — no nameserver verification needed. Pick a name, register, and your DNS zone is ready in seconds. How it works The zone is immediately active — there's no waiting for DNS propagation since Edge controls the parent zone. NS and SOA records are managed automatically and cannot be modified by the customer. Where to find test.network domains test.network domains don't appear in the main DNS Zones list — they have their own dedicated section in the console under DNS → test.network . 1 Choose a subdomain Navigate to DNS → test.network in the console. Enter your desired subdomain name. 2 Register Click Register — $1/month. A DNS zone is created in your account and NS delegation records are set up automatically. 3 Add records Manage your zone like any domain — add A records for servers, CNAME for CDN, MX for email, TXT for verification. 4 Use it Point your test domain at a VM, CDN deployment, or any external service. Use it for staging, demos, or development. Use cases Staging environments Give each project a staging URL like staging.test.network that your team can access. Client demos Deploy client work to client-name.test.network for review before going live on their domain. API development Host your API at api.test.network during development with real SSL and DNS. Learning and experimentation Try out DNS, CDN, and compute features with a real domain without buying one. Pricing $1 /month per subdomain (also available in £1 and €1) Full DNS zone control All record types supported Automatic SSL via CDN Cancel anytime Up to 5 per account See Also DNS Getting Started Add your first domain DNS Records Configure A, CNAME, MX, and more Back to Docs Need help? --- ### Zone Editor URL: https://edge.network/docs/dns/zone-editor/ Markdown: https://edge.network/docs/dns/zone-editor.md JSON: https://edge.network/json/docs/dns/zone-editor.json _Edit an entire DNS zone as JSON in Edge DNS: the zone file format, examples for every record type, bulk changes, and complex geo routing configurations._ Advanced Zone Editor Edit your entire DNS zone as JSON for maximum flexibility. Perfect for complex geo-routing configurations, bulk changes, and advanced record management. Accessing the Zone Editor There are two ways to use advanced JSON editing: Per-Record Advanced Mode Switch to the "Advanced" tab when adding or editing a single record to see and edit its full JSON representation, including geo routing. Click the "Advanced" tab in any record modal Full Zone Editor Toggle between Table and JSON view to edit all records at once. Ideal for bulk operations and complex configurations. Use the Table/JSON toggle in the Records page header Zone File Format The zone file is a JSON object where keys are record types and values are arrays of records: { "SOA": [{ "name": "@", "ttl": 3600, "mname": "ns1-abc123.edge.network.", "rname": "hostmaster.example.com.", "refresh": 3600, "retry": 900, "expire": 604800, "minimum": 300 }], "NS": [ { "name": "@", "data": "ns1-abc123.edge.network.", "ttl": 3600 }, { "name": "@", "data": "ns2-abc123.edge.network.", "ttl": 3600 } ], "A": [ { "name": "@", "data": "185.1.1.1", "ttl": 300 }, { "name": "www", "data": "185.1.1.1", "ttl": 300 }, { "name": "api", "data": "185.1.1.2", "ttl": 60 } ], "AAAA": [ { "name": "@", "data": "2001:db8::1", "ttl": 300 } ], "CNAME": [ { "name": "blog", "data": "www.example.com.", "ttl": 3600 } ], "MX": [ { "name": "@", "data": "mail.example.com.", "ttl": 3600, "priority": 10 } ], "TXT": [ { "name": "@", "data": "v=spf1 include:_spf.google.com ~all", "ttl": 3600 } ] } SOA and NS records are managed automatically The SOA record and apex NS records are shown for reference but are automatically generated when syncing to DNS servers. The SOA serial number is updated automatically whenever you make changes. Edits to these records in the JSON editor will be ignored. Record Types Reference SOA Record (Auto-managed) Start of Authority - defines zone parameters { "name": "@", "ttl": 3600, "mname": "ns1-abc123.edge.network.", "rname": "hostmaster.example.com.", "refresh": 3600, "retry": 900, "expire": 604800, "minimum": 300 } Note: SOA records are auto-generated by Edge DNS. The serial number (in YYYYMMDDNN format) is automatically updated whenever zone changes are synced. A Record Maps a domain to an IPv4 address { "name": "@", "data": "185.1.1.1", "ttl": 300, "geo": { "EU": "185.2.2.2", "US": "185.3.3.3", "AS": "185.4.4.4" } } geo is optional. See Geographic Routing . AAAA Record Maps a domain to an IPv6 address { "name": "@", "data": "2001:db8::1", "ttl": 300, "geo": { "EU": "2001:db8::2" } } CNAME Record Creates an alias pointing to another domain { "name": "www", "data": "example.com.", "ttl": 3600, "geo": { "US": "us.example.com.", "EU": "eu.example.com." } } Note: CNAME cannot be at the zone apex (@). Use ALIAS instead. ALIAS Record CNAME-like functionality at the zone apex { "name": "@", "data": "loadbalancer.edge.network.", "ttl": 300 } ALIAS records resolve the target hostname and return A/AAAA records. MX Record Specifies mail servers for the domain { "name": "@", "data": "aspmx.l.google.com.", "ttl": 3600, "priority": 1 } priority is required. Lower values = higher priority. Multiple MX records for redundancy: "MX": [ { "name": "@", "data": "aspmx.l.google.com.", "ttl": 3600, "priority": 1 }, { "name": "@", "data": "alt1.aspmx.l.google.com.", "ttl": 3600, "priority": 5 }, { "name": "@", "data": "alt2.aspmx.l.google.com.", "ttl": 3600, "priority": 5 }, { "name": "@", "data": "alt3.aspmx.l.google.com.", "ttl": 3600, "priority": 10 }, { "name": "@", "data": "alt4.aspmx.l.google.com.", "ttl": 3600, "priority": 10 } ] TXT Record Stores text data for various purposes (SPF, DKIM, verification) { "name": "@", "data": "v=spf1 include:_spf.google.com ~all", "ttl": 3600 } For long TXT records (like DKIM), use an array: { "name": "google._domainkey", "data": [ "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...", "...continuation of long key..." ], "ttl": 3600 } Array values are automatically joined for DNS responses. NS Record Delegates a subdomain to other nameservers Apex NS records (at @ ) are auto-managed by Edge DNS based on your account's assigned nameservers. Subdomain delegation: Use NS records to delegate subdomains to other providers: { "name": "subdomain", "data": "ns1.otherprovider.com.", "ttl": 3600 } Add multiple NS records for the same subdomain for redundancy. CAA Record Specifies which Certificate Authorities can issue certificates { "name": "@", "data": "0 issue letsencrypt.org", "ttl": 3600 } Format: . Tags: issue , issuewild , iodef . Common CAA configurations: "CAA": [ { "name": "@", "data": "0 issue letsencrypt.org", "ttl": 3600 }, { "name": "@", "data": "0 issuewild letsencrypt.org", "ttl": 3600 }, { "name": "@", "data": "0 iodef mailto:ssl@example.com", "ttl": 3600 } ] SRV Record Specifies service locations (used for SIP, XMPP, etc.) { "name": "_sip._tcp", "data": "10 5 5060 sipserver.example.com.", "ttl": 3600 } Format: PTR Record Reverse DNS lookup (IP to hostname) { "name": "1", "data": "server1.example.com.", "ttl": 3600 } Used in reverse DNS zones like 1.168.192.in-addr.arpa . Complex Geographic Routing The Zone Editor makes it easy to configure complex geo routing scenarios: Global CDN with Regional Endpoints { "A": [ { "name": "cdn", "data": "185.1.1.1", "ttl": 60, "geo": { "NA": "185.2.2.2", "US-WEST": "185.2.2.10", "US-EAST": "185.2.2.11", "CA": "185.2.2.12", "EU": "185.3.3.3", "GB": "185.3.3.10", "DE": "185.3.3.11", "NL": "185.3.3.12", "AS": "185.4.4.4", "JP": "185.4.4.10", "SG": "185.4.4.11", "IN": "185.4.4.12", "OC": "185.5.5.5", "AU": "185.5.5.10" } } ] } API with Failover by Region { "A": [ { "name": "api", "data": "10.0.0.1", "ttl": 300, "geo": { "US": "10.0.1.1", "EU": "10.0.2.1", "AS": "10.0.3.1" } }, { "name": "api", "data": "10.0.0.2", "ttl": 300, "geo": { "US": "10.0.1.2", "EU": "10.0.2.2", "AS": "10.0.3.2" } } ] } Multiple A records with the same name provide round-robin load balancing per region. Regional CNAME Aliases { "CNAME": [ { "name": "www", "data": "global.example.com.", "ttl": 300, "geo": { "US": "us.example.com.", "EU": "eu.example.com.", "AS": "asia.example.com." } } ] } Complete Zone Example Here's a complete zone configuration as shown in the Zone Editor. SOA and apex NS records are displayed for reference but managed automatically: { "SOA": [{ "name": "@", "ttl": 3600, "mname": "ns1-abc123.edge.network.", "rname": "hostmaster.example.com.", "refresh": 3600, "retry": 900, "expire": 604800, "minimum": 300 }], "NS": [ { "name": "@", "data": "ns1-abc123.edge.network.", "ttl": 3600 }, { "name": "@", "data": "ns2-abc123.edge.network.", "ttl": 3600 }, { "name": "subdomain", "data": "ns1.otherprovider.com.", "ttl": 86400 }, { "name": "subdomain", "data": "ns2.otherprovider.com.", "ttl": 86400 } ], "A": [ { "name": "@", "data": "185.1.1.1", "ttl": 300, "geo": { "EU": "185.2.2.2", "US": "185.3.3.3" } }, { "name": "www", "data": "185.1.1.1", "ttl": 300 }, { "name": "mail", "data": "185.1.1.10", "ttl": 3600 }, { "name": "api", "data": "185.1.1.20", "ttl": 60 } ], "AAAA": [ { "name": "@", "data": "2001:db8::1", "ttl": 300 }, { "name": "www", "data": "2001:db8::1", "ttl": 300 } ], "CNAME": [ { "name": "blog", "data": "www.example.com.", "ttl": 3600 }, { "name": "docs", "data": "docs.gitbook.io.", "ttl": 3600 }, { "name": "status", "data": "status.example.com.", "ttl": 3600 } ], "ALIAS": [ { "name": "cdn", "data": "gateway.edge.network.", "ttl": 300 } ], "MX": [ { "name": "@", "data": "aspmx.l.google.com.", "ttl": 3600, "priority": 1 }, { "name": "@", "da... --- ## Documentation › Storage ### Access Keys URL: https://edge.network/docs/storage/access-keys/ Markdown: https://edge.network/docs/storage/access-keys.md JSON: https://edge.network/json/docs/storage/access-keys.json _Generate S3 access keys for Edge Network storage, set read-only or read-write permissions, scope keys to specific buckets, and follow rotation best practices._ Storage Access Keys Access keys authenticate your applications with Edge Storage. Each key consists of an Access Key ID and a Secret Access Key. Key Components Access Key ID A unique identifier for your key. Safe to store in configuration files. EDGE1234567890ABCDEF Secret Access Key A secret token used to sign requests. Keep this secure! wJalrXUtnFEMI/K7MDENG... Generate a New Key 1 Navigate to Storage → Access Keys 2 Click Generate New Key 3 Copy both the Access Key ID and Secret Access Key 4 Store them securely (e.g., environment variables, secrets manager) Important: Save Your Secret Key The Secret Access Key is only shown once when the key is created. If you lose it, you'll need to generate a new key. Permissions & Bucket Scoping When creating a key, you can restrict its permissions and scope it to specific buckets. This follows the principle of least privilege — give each key only the access it needs. Read & Write Full access: upload, download, delete objects, create and delete buckets. Use for applications that manage content. Read Only Download and list only. Cannot upload, delete, or modify objects. Use for analytics, reporting, or public-facing read access. Bucket Scope By default, keys can access all buckets in the account. You can restrict a key to one or more specific buckets. A scoped key cannot see, access, or modify any bucket outside its scope. All buckets — no scope set. Key works with any bucket. This is the default. Specific buckets — key only works with the selected buckets. Requests to other buckets return AccessDenied . Backward Compatible Existing keys continue to work with full account-wide access. Scoping only applies to newly created keys where you explicitly set a bucket scope. Security Best Practices Use Environment Variables Never hardcode credentials in your source code. Use environment variables or a secrets manager. Rotate Keys Regularly Create new keys periodically and delete old ones. This limits exposure if a key is compromised. One Key Per Application Use separate keys for different applications or environments. Makes it easy to revoke access if needed. Separate Dev and Production Use different keys (and ideally different buckets) for development and production environments. Delete a Key To revoke access for a key: Go to Storage → Access Keys Find the key you want to delete Click the delete button and confirm The key is revoked immediately. Any applications using this key will no longer be able to authenticate. Example: Using Environment Variables Set variables in your shell: export AWS_ACCESS_KEY_ID="your-access-key-id" export AWS_SECRET_ACCESS_KEY="your-secret-access-key" export AWS_ENDPOINT_URL="https://storage.edge.network" Use in your code: import { S3Client } from '@aws-sdk/client-s3' // SDK automatically picks up environment variables const client = new S3Client({ endpoint: process.env.AWS_ENDPOINT_URL, region: 'us-east-1', forcePathStyle: true }) Back to Docs Need help? --- ### Bucket Management URL: https://edge.network/docs/storage/buckets/ Markdown: https://edge.network/docs/storage/buckets.md JSON: https://edge.network/json/docs/storage/buckets.json _How to create, list, and delete Edge Network storage buckets via console, CLI, or SDK, plus naming rules, lifecycle expiry rules, and public bucket access._ Storage Buckets Buckets are containers for your objects. Each bucket has a unique name within your account. Bucket Naming Rules 3-63 characters long Lowercase letters, numbers, and hyphens only Must start and end with a letter or number Cannot contain consecutive hyphens Unique within your account Create a Bucket Via Console Navigate to Storage → Buckets and click Create Bucket . Enter a name and click create. Via AWS CLI $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 mb s3://my-new-bucket Via SDK (JavaScript) import { S3Client, CreateBucketCommand } from '@aws-sdk/client-s3' const client = new S3Client({ endpoint: 'https://storage.edge.network', region: 'us-east-1', forcePathStyle: true, credentials: { accessKeyId: 'YOUR_ACCESS_KEY', secretAccessKey: 'YOUR_SECRET_KEY' } }) await client.send(new CreateBucketCommand({ Bucket: 'my-new-bucket' })) List Buckets $ aws --profile edge --endpoint-url https://storage.edge.network s3 ls 2025-01-15 09:00:00 assets 2025-02-01 14:30:00 backups 2025-02-10 11:15:00 uploads Delete a Bucket A bucket must be empty before it can be deleted. Empty and delete: # Delete all objects first $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 rm s3://my-bucket --recursive # Then delete the bucket $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 rb s3://my-bucket Warning Bucket deletion is permanent and cannot be undone. Bucket Statistics Each bucket tracks storage usage automatically: Metric Description storage_bytes Total size of all objects in bytes object_count Number of objects in the bucket created_at When the bucket was created Lifecycle Rules Lifecycle rules automatically delete objects older than a specified number of days. Useful for temporary uploads, log files, build artifacts, and session data. Creating a Rule Open a bucket and navigate to Settings Click Add Rule Set the number of days after which objects should be deleted Optionally set a prefix filter to only target objects with a specific path prefix (e.g. logs/ or tmp/ ) How It Works Rules are evaluated hourly. Objects whose last modified time exceeds the expiry threshold are deleted automatically. Prefix filters let you target specific folders. A rule with prefix logs/ only deletes objects under that path. You can have multiple rules per bucket. For example: delete tmp/ after 1 day and logs/ after 30 days. API GET /api/storage/buckets/:name/lifecycle — List rules for a bucket POST /api/storage/buckets/:name/lifecycle — Create a rule ({ "expire_days": 30, "prefix": "logs/" }) DELETE /api/storage/buckets/:name/lifecycle/:ruleId — Delete a rule Public Buckets Buckets can be made public, allowing anyone to access objects via a direct URL without authentication. Enabling Public Access Open a bucket and navigate to Settings Click Make Public Copy the public base URL Objects are then accessible at: https://storage.edge.network/_public/{customerId}/{bucket}/{object-key} Public GET and HEAD requests require no authentication. CORS headers are included for browser access. Private (default) All requests require S3 authentication or a presigned URL. This is the default for all new buckets. CDN Recommended for Production For production public content, consider using Edge CDN with a storage bucket origin instead. CDN provides caching, DDoS protection, and global edge delivery on top of public access. API PATCH /api/storage/buckets/:name/public — Toggle public access ({ "is_public": true }) Back to Docs Need help? --- ### Bucket Metrics URL: https://edge.network/docs/storage/metrics/ Markdown: https://edge.network/docs/storage/metrics.md JSON: https://edge.network/json/docs/storage/metrics.json _Monitor Edge Network storage with per-bucket metrics: usage, request volume, bandwidth, file type breakdown, and top objects over 24h, 7d, and 30d periods._ Storage Bucket Metrics Track storage usage, request patterns, and bandwidth consumption for each bucket in real-time. Overview Every bucket includes a Metrics tab that provides insights into how your storage is being used. Metrics are recorded in real-time and aggregated into hourly data points for charting. Metrics are available for all operations: S3 API calls, CLI commands, console actions, and CDN origin fetches. Available Metrics Storage Usage Total bytes stored and object count over time. Track how your bucket grows and identify storage trends. Request Volume Count of GET, PUT, and DELETE operations. Understand access patterns and peak usage times. Egress (Downloads) Bytes transferred out of your bucket. Track bandwidth consumption from downloads and CDN fetches. Ingress (Uploads) Bytes transferred into your bucket. Monitor upload activity and data ingest rates. Time Periods View metrics for different time ranges using the period selector: Period Data Points Best For 24h 24 hourly points Recent activity, troubleshooting 7d 168 hourly points Weekly patterns, trend analysis 30d 720 hourly points Monthly overview, capacity planning File Type Distribution The metrics dashboard shows a breakdown of storage by content type, helping you understand what types of files are consuming space: Images — JPEG, PNG, GIF, WebP, SVG Video — MP4, WebM, MOV, AVI Audio — MP3, WAV, OGG, FLAC Documents — PDF, DOC, XLS, PPT Archives — ZIP, TAR, GZ, RAR Data — JSON, XML, CSV File types are determined by the Content-Type header set during upload. Top Objects See which objects are most frequently accessed. This helps identify: Hot Content Files that should be cached or served via CDN Cost Drivers Objects consuming the most bandwidth Access Patterns Unusual activity that may indicate issues Accessing Metrics Console Navigate to Storage in your console Click on a bucket to open it Select the Metrics tab Use the period selector (24h / 7d / 30d) to change the time range API Metrics are also available via the API for programmatic access: # Get hourly metrics (last 7 days) GET /api/storage/buckets/:name/metrics?hours=168 # Get aggregate summary (last 24 hours) GET /api/storage/buckets/:name/metrics/summary?hours=24 # Get top 10 most accessed objects GET /api/storage/buckets/:name/metrics/top-objects?limit=10 # Get file type distribution GET /api/storage/buckets/:name/metrics/file-types Use Cases Capacity Planning Monitor storage growth trends over 30 days to predict when you'll need to adjust quotas or optimize content. Cost Optimization Identify high-bandwidth objects that could benefit from CDN caching or compression to reduce egress costs. Performance Monitoring Track request patterns to identify traffic spikes and ensure your application scales appropriately. Security Auditing Review access patterns to detect unusual download activity that might indicate unauthorized access. Data Retention Metrics data is retained based on granularity: Granularity Retention Hourly data points 90 days Top objects statistics Rolling (updated on each access) File type distribution Real-time (calculated from current objects) Back to Docs Need help? --- ### Getting Started with Storage URL: https://edge.network/docs/storage/getting-started/ Markdown: https://edge.network/docs/storage/getting-started.md JSON: https://edge.network/json/docs/storage/getting-started.json _Step-by-step guide to Edge Network storage: create an access key, configure the AWS CLI, then create a bucket and upload and verify your first object._ Storage Getting Started Set up Edge Storage and upload your first object in under 5 minutes. Prerequisites An Edge account ( sign up free ) AWS CLI installed (optional, but recommended) 1 Create an Access Key Navigate to Storage → Access Keys in your Edge account and click Generate New Key . Important Save your Secret Access Key immediately — it won't be shown again. 2 Configure AWS CLI Create a named profile for Edge Storage: $ aws configure --profile edge AWS Access Key ID [None]: YOUR_ACCESS_KEY AWS Secret Access Key [None]: YOUR_SECRET_KEY Default region name [None]: us-east-1 Default output format [None]: json 3 Create a Bucket Create your first bucket via CLI or the console: $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 mb s3://my-first-bucket make_bucket: my-first-bucket 4 Upload Your First Object Upload a file to your new bucket: $ echo "Hello, Edge Storage!" > hello.txt $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 cp hello.txt s3://my-first-bucket/ upload: ./hello.txt to s3://my-first-bucket/hello.txt 5 Verify the Upload List objects in your bucket: $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 ls s3://my-first-bucket/ 2025-02-12 10:30:00 21 hello.txt Pro Tip: Create an Alias Add this to your ~/.bashrc or ~/.zshrc : alias es='aws --profile edge --endpoint-url https://storage.edge.network s3' Then use it like this: $ es ls $ es cp file.txt s3://my-bucket/ $ es sync ./local-dir s3://my-bucket/backup/ Next Steps SDK Examples Integrate with your application Multipart Uploads Upload large files efficiently Back to Docs Need help? --- ### Multipart Uploads URL: https://edge.network/docs/storage/multipart-uploads/ Markdown: https://edge.network/docs/storage/multipart-uploads.md JSON: https://edge.network/json/docs/storage/multipart-uploads.json _Upload large files to Edge Network storage with multipart uploads: AWS CLI, JavaScript, and Python examples, part size guidance, and 5 TB object support._ Storage Multipart Uploads Upload large files in parts for reliability and resumability. Required for files over 5GB, recommended for files over 100MB. When to Use Multipart Uploads 100MB+ Recommended threshold 5GB Maximum single upload 5TB Maximum object size Benefits Resumable If a part fails, only retry that part instead of the entire file. Parallel Uploads Upload multiple parts simultaneously for faster throughput. Integrity Each part has its own ETag for verification. Supported Operations CreateMultipartUpload — Start a new multipart upload UploadPart — Upload a part (5MB minimum, except last part) CompleteMultipartUpload — Finalize and create the object AbortMultipartUpload — Cancel and clean up parts ListParts — List uploaded parts ListMultipartUploads — List in-progress uploads Using AWS CLI The AWS CLI handles multipart uploads automatically for large files: # AWS CLI automatically uses multipart for large files $ aws --profile edge --endpoint-url https://storage.edge.network \ s3 cp large-video.mp4 s3://my-bucket/videos/ # Configure part size (default is 8MB) $ aws configure set s3.multipart_chunksize 64MB JavaScript Example Use the Upload utility for automatic multipart handling: import { S3Client } from '@aws-sdk/client-s3' import { Upload } from '@aws-sdk/lib-storage' import { createReadStream } from 'fs' const client = new S3Client({ endpoint: 'https://storage.edge.network', region: 'us-east-1', forcePathStyle: true, credentials: { accessKeyId: process.env.EDGE_ACCESS_KEY, secretAccessKey: process.env.EDGE_SECRET_KEY } }) const upload = new Upload({ client, params: { Bucket: 'my-bucket', Key: 'large-video.mp4', Body: createReadStream('./large-video.mp4') }, queueSize: 4, // Parallel uploads partSize: 1024 * 1024 * 64 // 64MB parts }) // Track progress upload.on('httpUploadProgress', (progress) => { console.log(`${progress.loaded} / ${progress.total}`) }) await upload.done() Python Example boto3 handles multipart automatically with upload_file : import boto3 from boto3.s3.transfer import TransferConfig client = boto3.client( 's3', endpoint_url='https://storage.edge.network', aws_access_key_id=os.environ['EDGE_ACCESS_KEY'], aws_secret_access_key=os.environ['EDGE_SECRET_KEY'] ) # Configure multipart settings config = TransferConfig( multipart_threshold=1024 * 1024 * 100, # 100MB threshold multipart_chunksize=1024 * 1024 * 64, # 64MB parts max_concurrency=4 # Parallel uploads ) # Upload with progress callback def progress(bytes_transferred): print(f"Uploaded {bytes_transferred} bytes") client.upload_file( 'large-video.mp4', 'my-bucket', 'videos/large-video.mp4', Config=config, Callback=progress ) Part Size Recommendations File Size Recommended Part Size Approximate Parts 100MB - 1GB 16MB - 32MB 6-32 parts 1GB - 10GB 64MB - 128MB 16-80 parts 10GB - 100GB 128MB - 256MB 80-400 parts 100GB+ 256MB - 512MB Varies Note: Minimum part size is 5MB (except the last part). Maximum is 5GB. Maximum 10,000 parts per upload. Cleaning Up Incomplete Uploads Incomplete multipart uploads consume storage. Clean them up with: # List incomplete uploads $ aws --profile edge --endpoint-url https://storage.edge.network \ s3api list-multipart-uploads --bucket my-bucket # Abort a specific upload $ aws --profile edge --endpoint-url https://storage.edge.network \ s3api abort-multipart-upload \ --bucket my-bucket \ --key videos/large-video.mp4 \ --upload-id YOUR_UPLOAD_ID Back to Docs Need help? --- ### Presigned URLs URL: https://edge.network/docs/storage/presigned-urls/ Markdown: https://edge.network/docs/storage/presigned-urls.md JSON: https://edge.network/json/docs/storage/presigned-urls.json _Create time-limited presigned URLs for Edge Network storage so users can upload or download objects directly, using AWS S3 SDKs or the Edge API endpoint._ Storage Presigned URLs Generate time-limited signed URLs that allow anyone to upload or download objects directly — without exposing your credentials. Ideal for browser uploads, mobile apps, and sharing private files. How Presigned URLs Work A presigned URL is a time-limited, self-authenticating URL that grants temporary access to a specific object. The URL embeds the access credentials as query parameters using AWS Signature V4, so the recipient doesn't need API keys. Presigned Uploads Let users upload files directly to storage from their browser or app. No server-side proxy needed — the client PUTs directly to the signed URL. Presigned Downloads Share private files with time-limited links. Give a user a URL to download their invoice, report, or asset — the link expires after the set duration. Two Ways to Generate Presigned URLs 1 Using S3 SDKs (recommended) Generate presigned URLs client-side or server-side using any AWS S3 SDK. This is the standard approach and works identically to AWS S3. Requires your access key and secret key. 2 Using the Edge API Call POST /api/storage/buckets/:name/presign with your Edge API token. The server generates the presigned URL for you — no S3 credentials needed on the client. SDK Examples JavaScript / Node.js Install the S3 client and presigner: npm install @aws-sdk/client-s3 @aws-sdk/s3-request-presigner Generate a presigned upload URL import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3' import { getSignedUrl } from '@aws-sdk/s3-request-presigner' const client = new S3Client({ endpoint: 'https://storage.edge.network', region: 'us-east-1', forcePathStyle: true, credentials: { accessKeyId: process.env.EDGE_ACCESS_KEY, secretAccessKey: process.env.EDGE_SECRET_KEY } }) // Generate a presigned upload URL (valid for 1 hour) const url = await getSignedUrl(client, new PutObjectCommand({ Bucket: 'my-bucket', Key: 'uploads/photo.jpg', ContentType: 'image/jpeg', }), { expiresIn: 3600 }) Generate a presigned download URL import { GetObjectCommand } from '@aws-sdk/client-s3' import { getSignedUrl } from '@aws-sdk/s3-request-presigner' // Generate a presigned download URL (valid for 15 minutes) const url = await getSignedUrl(client, new GetObjectCommand({ Bucket: 'my-bucket', Key: 'invoices/invoice-001.pdf', }), { expiresIn: 900 }) Upload from a browser using the presigned URL // Browser: upload a file using the presigned URL const fileInput = document.querySelector('input[type="file"]') const file = fileInput.files[0] const response = await fetch(presignedUrl, { method: 'PUT', body: file, headers: { 'Content-Type': file.type, }, }) if (response.ok) { console.log('Upload complete') } Python Generate a presigned upload URL import boto3 client = boto3.client( 's3', endpoint_url='https://storage.edge.network', aws_access_key_id=os.environ['EDGE_ACCESS_KEY'], aws_secret_access_key=os.environ['EDGE_SECRET_KEY'], region_name='us-east-1' ) # Generate a presigned upload URL (valid for 1 hour) url = client.generate_presigned_url( 'put_object', Params={ 'Bucket': 'my-bucket', 'Key': 'uploads/photo.jpg', 'ContentType': 'image/jpeg', }, ExpiresIn=3600 ) print(url) Generate a presigned download URL # Generate a presigned download URL (valid for 15 minutes) url = client.generate_presigned_url( 'get_object', Params={ 'Bucket': 'my-bucket', 'Key': 'invoices/invoice-001.pdf', }, ExpiresIn=900 ) print(url) cURL Upload with a presigned URL # Upload using the presigned URL curl -X PUT "$PRESIGNED_URL" \ -H "Content-Type: image/jpeg" \ --data-binary @photo.jpg Download with a presigned URL # Download using the presigned URL curl -o invoice.pdf "$PRESIGNED_URL" Edge API If you don't want to manage S3 credentials on the client, you can generate presigned URLs server-side via the Edge API using your account's Bearer token. POST /api/storage/buckets/:name/presign Parameter Type Required Description key string Yes Object key (path) within the bucket action string No download (default) or upload expires string No Duration: 15m , 1h (default), 7d (max) Generate an upload URL # Generate a presigned upload URL via the Edge API curl -X POST https://api.edge.network/api/storage/buckets/my-bucket/presign \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "key": "uploads/photo.jpg", "action": "upload", "expires": "1h" }' # Response: # { # "url": "https://storage.edge.network/my-bucket/uploads/photo.jpg?X-Amz-Algorithm=...", # "method": "PUT", # "expires": "2026-03-12T01:00:00Z" # } Generate a download URL # Generate a presigned download URL via the Edge API curl -X POST https://api.edge.network/api/storage/buckets/my-bucket/presign \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "key": "invoices/invoice-001.pdf", "expires": "15m" }' Common Use Cases User avatar uploads Generate a presigned PUT URL server-side, return it to the browser, and let the user upload their photo directly to storage. Private file sharing Generate a presigned GET URL for an invoice or report. Send the link to the user — it expires after the set duration. Mobile app uploads Your backend generates a presigned URL, sends it to the mobile app, and the app uploads directly. No proxy, no extra bandwidth on your server. Third-party integrations Give a partner or webhook a presigned URL to upload data into your bucket without sharing credentials. Security Considerations URLs are bearer tokens. Anyone with the URL can use it until it expires. Share them over secure channels (HTTPS, encrypted messages). Keep expiry times short. Use the minimum duration needed — 15 minutes for downloads, 1 hour for uploads. Maximum is 7 days. URLs are scoped to a single object. A presigned URL for photos/image.jpg cannot be used to access any other object. Revoking access. Delete or rotate the access key used to generate the URL. All presigned URLs created with that key become invalid immediately. SDK Examples Multipart Uploads Back to Docs Need help? --- ### SDK Examples URL: https://edge.network/docs/storage/sdk-examples/ Markdown: https://edge.network/docs/storage/sdk-examples.md JSON: https://edge.network/json/docs/storage/sdk-examples.json _Code examples for connecting AWS S3 SDKs to Edge Network storage in JavaScript, Python, Go, and Ruby, covering setup, uploads, downloads, and object listing._ Storage SDK Examples Edge Storage is fully compatible with AWS S3 SDKs. Use the official AWS SDK for your language with our endpoint. JS JavaScript / TypeScript Installation npm install @aws-sdk/client-s3 Client Setup import { S3Client, PutObjectCommand, GetObjectCommand, ListObjectsV2Command } from '@aws-sdk/client-s3' const client = new S3Client({ endpoint: 'https://storage.edge.network', region: 'us-east-1', forcePathStyle: true, credentials: { accessKeyId: process.env.EDGE_ACCESS_KEY, secretAccessKey: process.env.EDGE_SECRET_KEY } }) Upload an Object await client.send(new PutObjectCommand({ Bucket: 'my-bucket', Key: 'images/photo.jpg', Body: fileBuffer, ContentType: 'image/jpeg' })) Download an Object const response = await client.send(new GetObjectCommand({ Bucket: 'my-bucket', Key: 'images/photo.jpg' })) const body = await response.Body.transformToByteArray() List Objects const response = await client.send(new ListObjectsV2Command({ Bucket: 'my-bucket', Prefix: 'images/' })) for (const obj of response.Contents || []) { console.log(obj.Key, obj.Size) } PY Python Installation pip install boto3 Client Setup import boto3 import os client = boto3.client( 's3', endpoint_url='https://storage.edge.network', aws_access_key_id=os.environ['EDGE_ACCESS_KEY'], aws_secret_access_key=os.environ['EDGE_SECRET_KEY'], region_name='us-east-1' ) Upload an Object # Upload a file client.upload_file('local-file.txt', 'my-bucket', 'remote-file.txt') # Or upload bytes directly client.put_object( Bucket='my-bucket', Key='hello.txt', Body=b'Hello, Edge Storage!' ) Download an Object # Download to file client.download_file('my-bucket', 'remote-file.txt', 'local-file.txt') # Or get bytes response = client.get_object(Bucket='my-bucket', Key='hello.txt') data = response['Body'].read() List Objects response = client.list_objects_v2( Bucket='my-bucket', Prefix='images/' ) for obj in response.get('Contents', []): print(obj['Key'], obj['Size']) GO Go Installation go get github.com/aws/aws-sdk-go-v2 go get github.com/aws/aws-sdk-go-v2/service/s3 go get github.com/aws/aws-sdk-go-v2/credentials Client Setup package main import ( "context" "os" "github.com/aws/aws-sdk-go-v2/aws" "github.com/aws/aws-sdk-go-v2/config" "github.com/aws/aws-sdk-go-v2/credentials" "github.com/aws/aws-sdk-go-v2/service/s3" ) func main() { cfg, _ := config.LoadDefaultConfig(context.TODO(), config.WithRegion("us-east-1"), config.WithCredentialsProvider(credentials.NewStaticCredentialsProvider( os.Getenv("EDGE_ACCESS_KEY"), os.Getenv("EDGE_SECRET_KEY"), "", )), ) client := s3.NewFromConfig(cfg, func(o *s3.Options) { o.BaseEndpoint = aws.String("https://storage.edge.network") o.UsePathStyle = true }) } Upload an Object _, err := client.PutObject(context.TODO(), &s3.PutObjectInput{ Bucket: aws.String("my-bucket"), Key: aws.String("hello.txt"), Body: strings.NewReader("Hello, Edge Storage!"), }) RB Ruby Installation gem install aws-sdk-s3 Client Setup & Usage require 'aws-sdk-s3' client = Aws::S3::Client.new( endpoint: 'https://storage.edge.network', region: 'us-east-1', force_path_style: true, access_key_id: ENV['EDGE_ACCESS_KEY'], secret_access_key: ENV['EDGE_SECRET_KEY'] ) # Upload client.put_object( bucket: 'my-bucket', key: 'hello.txt', body: 'Hello, Edge Storage!' ) # Download response = client.get_object(bucket: 'my-bucket', key: 'hello.txt') puts response.body.read Common Configuration Regardless of the SDK you use, you'll need these settings: Setting Value Notes endpoint https://storage.edge.network Required region us-east-1 Use any valid region string forcePathStyle true Required for Edge Storage Back to Docs Need help? --- ### Storage Overview URL: https://edge.network/docs/storage/ Markdown: https://edge.network/docs/storage.md JSON: https://edge.network/json/docs/storage.json _Overview of Edge Network object storage: S3-compatible API, CDN origin support, console features, and upload limits. First 5 GB free with zero egress fees._ Storage Edge Storage S3-compatible object storage designed for performance and simplicity. Use your existing S3 tools, SDKs, and workflows with Edge infrastructure. Key Features S3 Compatible Full AWS S3 API compatibility. Use the AWS CLI, SDKs in any language, or any S3-compatible tool without changes. Per-Account Isolation Each account has dedicated storage and metadata databases. Complete isolation for security and performance. Optimized Metadata SQLite-based metadata storage enables fast prefix queries, object listing, and efficient bucket operations at any scale. Multipart Uploads Upload large files in parts for reliability and resumability. Perfect for video files, backups, and large datasets. CDN Integration Use Storage buckets as CDN origins. Serve static assets globally with edge caching, automatic SSL, and no origin configuration needed. Built-in Metrics Real-time metrics per bucket including storage usage, request volume, bandwidth, file type distribution, and top accessed objects. CDN Integration Storage buckets can be used directly as origins for Edge CDN deployments, enabling global edge caching of your stored content. Why use Storage + CDN together? No external URLs - Select your bucket directly, no URL configuration Internal networking - Faster origin fetches via internal connections Private buckets work - CDN authenticates internally, no public access needed Unified billing - Storage and CDN usage in one invoice To use a bucket as a CDN origin, create a CDN deployment and select "Storage Bucket" as the origin type when adding a domain. Learn more about CDN domains → Supported S3 Operations Edge Storage supports the core S3 API operations: Bucket Operations CreateBucket DeleteBucket ListBuckets HeadBucket Object Operations PutObject GetObject DeleteObject HeadObject ListObjectsV2 CopyObject Console Manage buckets and objects directly from your browser — no CLI or SDK required. Drag & Drop Uploads Drag files or entire folders into any bucket. Folder structure is preserved automatically. Upload Progress Tracking A persistent overlay shows real-time progress for each file. Cancel individual uploads, minimise the panel, or retry failures. File Preview Preview images, videos, and audio files directly in the browser. Navigate between files with arrow keys. Bucket Metrics View storage usage, request volume, bandwidth, file type distribution, and top objects per bucket. Learn more Connection Details Endpoint storage.edge.network Region us-east-1 Path Style true Limits Resource Limit Console upload (per request) 1 GB S3 API single object upload 5 GB Multipart upload part size 5 MB – 5 GB Multipart upload max parts 10,000 Buckets per account 100 Objects per bucket Unlimited For uploads larger than 1 GB via the console, use the S3 API with multipart uploads. See Multipart Uploads for details. Get Started Getting Started Create your first bucket in minutes Access Keys Generate and manage API credentials SDK Examples Code samples for popular languages Multipart Uploads Upload large files reliably Back to Docs Need help? --- ## Documentation › Shield ### Getting Started with Shield URL: https://edge.network/docs/shield/getting-started/ Markdown: https://edge.network/docs/shield/getting-started.md JSON: https://edge.network/json/docs/shield/getting-started.json _Create a widget, add two lines to your page, and validate tokens on your server — bot protection in five minutes._ Shield Getting Started Three steps: create a widget, embed it, validate tokens. Most integrations take under five minutes. 1. Create a Widget In the console , go to Shield → Create Widget . Give it a name, optionally restrict it to your hostnames, and choose a mode (Managed is recommended — see Widget Modes ). You'll receive two keys: Key Format Where it lives Sitekey es_… Public — embedded in your pages Secret key es_secret_… Server-side only — shown once at creation The secret key is stored hashed and cannot be displayed again. If you lose it, revoke the widget and create a new one. 2. Add the Widget to Your Page Include the script once, and place a div.edge-shield inside any form you want to protect:
The widget verifies the visitor and appends a hidden edge-shield-response input to the form. Tokens auto-refresh before they expire, so slow form-fillers aren't penalised. The bundle is under 15KB and solves its challenge in a Web Worker. 3. Validate the Token on Your Server When the form is submitted, POST the token and your secret key to siteverify: curl -X POST https://shield.edge.network/siteverify \ -d "secret=es_secret_..." \ -d "response=" Response: { "success": true, "score": 92, "challenge_ts": "2026-07-21T08:00:00.000Z", "hostname": "example.com", "error-codes": [] } A complete server-side example: // Express example app.post('/signup', async (req, res) => { const token = req.body['edge-shield-response'] const result = await fetch('https://shield.edge.network/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ secret: process.env.SHIELD_SECRET, response: token, }), }).then(r => r.json()) if (!result.success) { return res.status(400).send('Verification failed') } if (result.score < 40) { return res.status(403).send('Blocked') // or redirect automation to your API } // ... create the account }) Always validate server-side The hidden input can be forged by an attacker — only a successful siteverify call proves the token is genuine, unexpired, and unused. Tokens are single-use: a second siteverify call with the same token returns timeout-or-duplicate . No server to call it from? See Shield on a Static Site for how to test the check from your terminal and what to add to protect a real form. Next Steps Widget Modes Choose how visible verification is Server-Side Validation Error codes and using the score Testing & CI Develop against fixed test sitekeys Offline Verification Verify tokens locally via JWKS Back to Docs Need help? --- ### Migrating from Turnstile URL: https://edge.network/docs/shield/turnstile-migration/ Markdown: https://edge.network/docs/shield/turnstile-migration.md JSON: https://edge.network/json/docs/shield/turnstile-migration.json _Move from Cloudflare Turnstile to Edge Shield — same siteverify response shape, same key model, one URL swap._ Shield Migrating from Turnstile Shield was designed to be a drop-in replacement: the same sitekey/secret model, and a siteverify response that matches Turnstile's field for field. Most migrations are a URL swap and a pair of new keys. 1. Create a Shield Widget In the console , create a widget matching your Turnstile configuration — same hostnames, and the equivalent mode (Turnstile's Managed/Non-Interactive/Invisible map one-to-one to Shield's). Note your new sitekey and secret. 2. Swap the Client Snippet
Compatibility mode data-compat="turnstile" makes the widget also populate a cf-turnstile-response hidden input, so server code that reads Turnstile's field name keeps working without changes during the transition. Shield's callbacks ( data-callback , data-error-callback , data-expired-callback ) follow the same conventions as Turnstile's. 3. Swap the Siteverify URL and Secret // Before const url = 'https://challenges.cloudflare.com/turnstile/v0/siteverify' // After — the response shape is identical (plus a "score" field) const url = 'https://shield.edge.network/siteverify' Replace the secret with your es_secret_… key. The response contains the same fields — success , challenge_ts , hostname , error-codes — with familiar error code names ( timeout-or-duplicate , invalid-input-secret , etc.), so existing error handling carries over. 4. Optional: Use the Score Turnstile gives you pass/fail. Shield's responses additionally carry a score (1–100) — once migrated, you can add graduated handling: auto-approve high scores, step up uncertain ones, and route or block automation. See Server-Side Validation . Differences to Be Aware Of Key formats differ: sitekeys are es_… and secrets es_secret_… . If you validate key formats anywhere, update the patterns. The default hidden input is edge-shield-response — use data-compat="turnstile" during transition, then switch your server to the new field name at leisure. Shield stores no per-visitor data and sets no cookies — if your privacy policy documented Turnstile's cookies, you can simplify it. Idempotency: like Turnstile, tokens are single-use and expire after 5 minutes. Next Steps Server-Side Validation Full API reference and error codes Analytics Watch your migrated traffic verify Back to Docs Need help? --- ### Shield Analytics URL: https://edge.network/docs/shield/analytics/ Markdown: https://edge.network/docs/shield/analytics.md JSON: https://edge.network/json/docs/shield/analytics.json _Per-widget verification metrics, humanity score trends, and what Shield does — and deliberately doesn't — store._ Shield Analytics Every widget has a Metrics tab in the console with verification volumes, humanity score trends, and failure counts — built entirely from hourly aggregates. Available Metrics Open Shield → your widget → Metrics and select a range (24 hours, 7 days, or 30 days): Metric What it tells you Verifications Successful siteverify calls — traffic your server accepted a token for Challenges issued How many verification attempts started — the widget's raw traffic Average humanity score Score trend over time — a sudden drop is an early warning of a bot campaign Solve rate Challenges solved ÷ issued — low rates suggest clients abandoning or failing the challenge Interactive shown How often managed mode escalated to the "I am human" confirmation Failed / replayed Rejected siteverify calls, including replay attempts — your token-abuse signal Tarpit challenges Escalated-difficulty challenges served to repeat offenders — how hard the tarpit is working Shadow would-fail / would-escalate For widgets in shadow (report-only) mode: what strict enforcement would have rejected or escalated — your trial scorecard Reading the Data Average score falling while volume rises usually means automated traffic has arrived. Check the interactive-shown count — in managed mode it should rise with it. Replays above zero mean something is resubmitting used tokens — typically a naive bot re-posting a captured form. Shield rejects these automatically. Issued far exceeding verifications is normal — every page load with a widget issues a challenge, but only submitted forms reach siteverify. Data Retention & Privacy All analytics are hourly aggregate counters per widget . Shield does not store visitor IP addresses, fingerprints, cookies, or any per-visitor records — the signals used for scoring are processed in memory during the request and discarded. There is no per-visitor drill-down because there is no per-visitor data. This is what makes Shield GDPR/CCPA-friendly by default: there's nothing to consent to, export, or delete. Next Steps Server-Side Validation Act on the humanity score Getting Started Protect your first form Back to Docs Need help? --- ### Shield Examiner URL: https://edge.network/docs/shield/examiner/ Markdown: https://edge.network/docs/shield/examiner.md JSON: https://edge.network/json/docs/shield/examiner.json _AI-powered review of your Shield widget's traffic: bot pressure, escalation calibration, abuse signals, and recommended siteverify thresholds — from aggregate data only._ Shield Shield Examiner An AI review of your widget's traffic that turns 30 days of metrics into a plain-English assessment — what's healthy, what's under attack, what to tune — with specific fixes. Included with every widget The Examiner is part of Edge Shield's free offering — run reviews as often as you need, on every widget. How to Use 1 Open a Shield widget and navigate to the Examiner tab 2 Click Run review — the analysis covers your last 30 days of traffic and takes a few seconds 3 Review the health score, findings, and recommendations — apply fixes in the widget's Settings tab or in your own siteverify handling What It Reviews Traffic Health Challenge volumes, solve rates, and verification patterns — and what they mean for your site rather than raw numbers. Bot Pressure How much automation is hitting the widget, whether it's declared (verified agents) or anonymous, and whether it's trending up. Escalation Calibration Whether the interactive-confirmation rate suggests genuine suspicious traffic or an over-challenged audience (VPNs, privacy browsers), and what to do about it. Abuse Signals Token replays, verification failures, score collapses, and drift-detector anomalies — the traces real attacks leave in aggregates. Configuration Whether your widget mode, verified-agents policy, and hostname allowlist fit the traffic you're actually receiving — plus recommended siteverify score thresholds. Health Score Each review produces a health score from 0 to 100 based on the severity and number of findings. Score Rating Meaning 80–100 Good health Traffic looks normal; minor tuning may be suggested. 50–79 Needs attention Calibration or bot-pressure warnings worth acting on. 0–49 Issues found Active abuse signals or configuration problems affecting protection. What Gets Analysed The Examiner reviews hourly aggregate counters only — challenge volumes, solve rates, score averages, and abuse counts — plus your widget's configuration. Shield holds no per-visitor data, so none can be analysed or shared. That's not a policy; it's the architecture. Saved Results Reviews are saved automatically. When you return to the Examiner tab, your most recent result is shown with the date and time it was run. Click Run again at any time for a fresh analysis — Shield keeps your last ten. Analytics Shield Overview Back to Docs Need help? --- ### Shield JavaScript API URL: https://edge.network/docs/shield/js-api/ Markdown: https://edge.network/docs/shield/js-api.md JSON: https://edge.network/json/docs/shield/js-api.json _Explicit rendering, programmatic execution, and SPA integration for the Edge Shield widget._ Shield JavaScript API The widget renders implicitly from markup by default, and exposes a small global API for explicit rendering, SPAs, and on-demand verification. Implicit Rendering With no JavaScript on your side, the script scans for .edge-shield[data-sitekey] elements on load, renders each one, and appends a hidden edge-shield-response input to the enclosing form:
Explicit Rendering For full control, render programmatically. edgeShield.render() returns a widget ID used with the other methods: const widgetId = edgeShield.render(document.getElementById('my-container'), { sitekey: 'es_...', mode: 'managed', // optional callback: (token) => { // token issued / refreshed submitButton.disabled = false }, errorCallback: (err) => { // verification failed console.warn('shield:', err) }, expiredCallback: () => { // token expired (auto re-verifies) submitButton.disabled = true }, }) Methods edgeShield.getResponse(widgetId) // current token, or null edgeShield.reset(widgetId) // clear the token and re-verify edgeShield.execute(widgetId) // run verification on demand (invisible mode) Method Description render(el, options) Render a widget into a container. Returns a widget ID. Options mirror the data attributes. getResponse(id?) The current token, or null if not yet verified. Omit the ID to use the first widget. reset(id?) Clear the current token and run verification again. execute(id?) Run verification on demand — the usual pattern for invisible mode (e.g. just before submit). Single-Page Applications In an SPA, render explicitly when your form mounts and send the token with your API request instead of relying on a form post: // React example — render on mount, clean up by resetting useEffect(() => { const id = edgeShield.render(containerRef.current, { sitekey: 'es_...', callback: setToken, }) return () => edgeShield.reset(id) }, []) // Submit the token with your API call await fetch('/api/signup', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ email, 'edge-shield-response': token }), }) Tokens auto-refresh about a minute before their 5-minute expiry, and the callback fires again with the fresh token — keep your local copy up to date from the callback rather than caching the first value. Next Steps Server-Side Validation Validate tokens from your backend Widget Modes Data attributes and mode behaviour Back to Docs Need help? --- ### Shield Offline Token Verification URL: https://edge.network/docs/shield/offline-verification/ Markdown: https://edge.network/docs/shield/offline-verification.md JSON: https://edge.network/json/docs/shield/offline-verification.json _Verify Shield tokens locally with zero network calls — tokens are Ed25519-signed JWTs, and the public key is published at a standard JWKS endpoint._ Shield Offline Token Verification Shield response tokens are Ed25519-signed JWTs. The public key is published at a standard JWKS endpoint, so your server can verify tokens locally — no network round trip, no added latency, no dependency on shield.edge.network being reachable. The Key Endpoint GET https://shield.edge.network/.well-known/jwks.json { "keys": [ { "kty": "OKP", "crv": "Ed25519", "x": "…", "kid": "a1b2c3d4e5f60718", "alg": "EdDSA", "use": "sig" } ] } Cache the key set for up to an hour. If you encounter a token with an unknown kid header, refetch once — that's how key rotation propagates. Keys rotate automatically roughly every 60 days, and the retiring public key stays in the key set for 24 hours after rotation, so an hourly cache never verifies against a stale set. Verifying a Token Any JWT library that supports EdDSA works. With jose in Node: import { createRemoteJWKSet, jwtVerify } from 'jose' const JWKS = createRemoteJWKSet( new URL('https://shield.edge.network/.well-known/jwks.json') ) async function verifyOffline(token, sitekey) { const { payload } = await jwtVerify(token, JWKS, { issuer: 'edge-shield', subject: sitekey, // REQUIRED — binds the token to YOUR widget }) return { score: payload.score, // 1–100 humanity score hostname: payload.hn, // hostname the widget ran on agent: payload.agt || null // verified agent domain, if declared } } Your verification must check, in order: The signature, against a JWKS key matching the token's kid iss equals edge-shield sub equals your sitekey — without this check, a token minted for any Shield widget anywhere would pass exp — tokens live 5 minutes Optionally, that hn is one of your hostnames The claims you get back: { "iss": "edge-shield", "sub": "es_...", // the widget's sitekey "jti": "b3f9…", // unique token id (replay ledger key) "iat": 1785459151, "exp": 1785459451, // 5-minute lifetime "score": 92, // 1–100 humanity score "hn": "example.com", // hostname the widget ran on "agt": "crawler.example", // optional: verified agent domain "agm": "web-bot-auth" // optional: agent verification method } The Trade-Off: No Single-Use Guarantee The one thing offline verification cannot give you is replay protection. The ledger of spent tokens lives on Shield's servers, so only siteverify guarantees that a token verifies exactly once. Verified offline, the same token is valid for its full 5-minute lifetime, as many times as it's presented. Use offline verification for high-throughput, lower-stakes endpoints — search, previews, read APIs — where latency matters more than strict single-use. Keep siteverify for signups, logins, payments, and anything a farmed token shouldn't touch. You can narrow the replay window further by rejecting tokens whose iat is older than your form could plausibly take to submit — 60 seconds is a common choice. Next Steps Server-Side Validation The strict path, with single-use enforcement Testing & CI Fixed test keys that never hit the network's real state Back to Docs Need help? --- ### Shield on a Static Site (No Server) URL: https://edge.network/docs/shield/static-sites/ Markdown: https://edge.network/docs/shield/static-sites.md JSON: https://edge.network/json/docs/shield/static-sites.json _You've embedded the Shield widget on a static site and hit 'validate server-side'. Here's how to test the check from your laptop, what Shield can and can't protect without a backend, and the smallest thing you can add to protect a real form._ Shield Shield on a Static Site You've added the widget to a site with no backend, it renders and produces a token, and the docs say "always validate server-side". This page is for that moment: how to see the check working from your own laptop, what Shield does and doesn't protect without a server, and the smallest thing you can add to protect a real form. Where the check lives Shield has two halves. The widget runs in the visitor's browser, talks only to shield.edge.network , and drops a signed token into a hidden edge-shield-response input. The check is a single HTTP call to siteverify with your secret key, which confirms the token is genuine, unexpired and unused, and returns a humanity score. The check has to run somewhere that can hold the secret, which rules out the page itself. On a static site there's nothing on your side to run it, so from the browser the integration looks half-finished. It isn't. The widget half is done; the check simply needs a place to live, and for testing that place can be your terminal. What a static site has to protect Shield gates actions : a form submit, a signup, an API call. It does not gate page views, and it can't stop a bot reading a page the CDN serves to everyone. If your site has no form or endpoint that posts anywhere, there's nothing for Shield to check yet, and that's a fine place to be until there is. Test the check from your laptop siteverify is just an HTTP call. You can make it with curl and watch the whole flow work end to end, no server required. 1 Embed the widget Use your real sitekey from Control → Shield . The form doesn't need a real action yet.
2 Complete the widget and copy the token Load the page, let the widget reach its success state, then read the hidden input in the browser console. The token is a long string starting ey… . // In your browser's console, after the widget shows its success state: document.querySelector('[name="edge-shield-response"]').value // Or via the JS API if you rendered the widget yourself: edgeShield.getResponse(widgetId) 3 Verify it from a terminal This is exactly the call a server would make. Your secret is also in Control → Shield. You have five minutes from the widget completing before the token expires. # From a terminal on your own machine. Never put the secret in your page. curl -X POST https://shield.edge.network/siteverify \ -d "secret=es_secret_..." \ -d "response=PASTE_THE_TOKEN_HERE" You should see the token accepted, with a score and the hostname it was minted for: { "success": true, "score": 87, "challenge_ts": "2026-09-13T20:41:12.000Z", "hostname": "www.example.com", "error-codes": [] } 4 Run it again Repeat the same curl with the same token. It fails. Tokens are strictly single-use, which is what stops a bot replaying one good solve across a thousand submissions. { "success": false, "score": 0, "hostname": "www.example.com", "error-codes": ["timeout-or-duplicate"] } Don't want to touch real keys yet? Shield ships fixed test keys that work on any hostname, including a page opened straight from disk, and record no analytics:
# Terminal: always succeeds, score 90 curl -X POST https://shield.edge.network/siteverify \ -d "secret=es_secret_test_pass" \ -d "response=anything" Swap to es_test_block to see the no-token path, or es_secret_test_spent to see the replayed-token response. Full list on Testing & CI . Protecting a real form Once you're happy the check works, the question becomes: where does the form post to? Whatever answers that is where the siteverify call goes. Cheapest first: Your existing form service If your forms already post to a hosted form backend, check whether it can call an HTTP endpoint before accepting a submission, or supports a custom verification step. If it does, point that at siteverify with your secret and forward the edge-shield-response field. If it can't, it can't verify anything, and the widget is decoration. A small function or VM in front of the form About fifteen lines in any runtime. A serverless function, or the smallest Edge Compute VM, receives the submission, verifies the token, and only then does whatever the form is for. Keep the secret in an environment variable, never in the page. // The whole job of the function: verify, then do the thing. // Any serverless runtime, or a tiny Edge Compute VM, is enough. export default async function handler(req) { const form = await req.formData() const token = form.get('edge-shield-response') const verify = await fetch('https://shield.edge.network/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ secret: process.env.SHIELD_SECRET, response: token ?? '', remoteip: req.headers.get('x-forwarded-for') ?? '' }) }).then(r => r.json()) if (!verify.success || verify.score < 60) { return new Response('Verification failed', { status: 403 }) } // Verified human. Email it, post it to a webhook, write it to storage... await sendEmail({ to: 'hello@example.com', body: form.get('message') }) return Response.redirect('/thanks', 303) } Offline verification, if you have a function but want zero round trips Tokens are Ed25519-signed JWTs and the public key is published at a JWKS endpoint, so a function can verify them locally with no call to Shield. You give up strict single-use, so keep siteverify for signups, logins and payments. See Offline Verification . Never call siteverify from the page. Doing so means shipping your secret to every visitor, and a secret in a static bundle is public within the hour. The terminal test above works because your laptop isn't your website. The same call belongs on a server, a function, or a service you trust with the key, and nowhere else. In short The widget works on any static site with no configuration. That half is done. To see the check work, grab the token from the console and curl siteverify from your terminal. To use the check, the form has to post somewhere that can hold the secret: a form service that supports it, or a small function or VM. Shield can't protect page views on a static site, and a widget with no server-side check protects nothing. Next Steps Server-Side Validation The siteverify API, error codes and the humanity score Testing & CI Fixed test keys, deterministic behaviour Back to Docs Need help? --- ### Shield Overview URL: https://edge.network/docs/shield/ Markdown: https://edge.network/docs/shield.md JSON: https://edge.network/json/docs/shield.json _Free, privacy-first bot protection without puzzles. Verify humans, route agents, and stop abuse with a 1–100 humanity score on every check._ Shield Edge Shield A lightweight CAPTCHA alternative. Shield verifies visitors invisibly — no puzzles, no cookies, no tracking — and returns a 1–100 humanity score your application can act on. Free forever, with unlimited verifications. Key Features Invisible Verification A proof-of-work challenge solved in a background thread. Real visitors almost never see anything — and never label traffic lights. Humanity Score Every verification carries a 1–100 score — 1 is confirmed automation, 100 a confirmed human. Allow, step up, redirect, or block on your own thresholds. Privacy by Architecture No cookies, no fingerprint database, no per-visitor storage. Only hourly aggregate counters are kept — GDPR and CCPA friendly by default. Turnstile-Compatible The siteverify response matches Cloudflare Turnstile's exactly, plus the score. Migrating is a URL and key swap. Shadow Mode & Test Keys Trial Shield in report-only mode on live traffic — nothing is ever blocked — and run CI against fixed test keys that never touch real state. Offline Verification Tokens are Ed25519-signed JWTs with a public JWKS endpoint — verify them locally with zero network calls when latency matters. How It Works 1 The widget requests a challenge A cryptographically signed challenge is issued by the Shield service. Difficulty adapts to risk signals — clean browsers get trivial work. 2 The browser solves it invisibly A SHA-256 proof-of-work runs in a Web Worker — tens of milliseconds on a phone, with no impact on your Core Web Vitals. 3 A response token is minted The solution plus coarse environment signals produce a signed, single-use token containing the humanity score. It's added to your form automatically. 4 The score refines as the visitor interacts Verification runs at page load, before any real interaction. As the visitor types or moves the pointer, the widget sends a one-off summary of that interaction — aggregate statistics only, computed in the browser — and the token is re-minted with a behaviour-informed score. Human motor noise raises it; machine-perfect input lowers it. 5 Your server validates the token One POST to siteverify with your secret key returns the verdict, hostname, and score. Tokens expire after 5 minutes and can be used exactly once. Pricing Shield's core protection is free forever — unlimited widgets, unlimited verifications, all three widget modes, and the humanity score included. There are no monthly assessment caps and no credit card required. Get Started Getting Started Protect your first form in five minutes Widget Modes Managed, non-interactive, and invisible Server-Side Validation The siteverify API and humanity score Migrating from Turnstile A drop-in swap, step by step Offline Verification Verify tokens locally via JWKS Testing & CI Fixed test keys, deterministic behaviour Static Sites No server? Test the check from your laptop Back to Docs Need help? --- ### Shield Server-Side Validation URL: https://edge.network/docs/shield/siteverify/ Markdown: https://edge.network/docs/shield/siteverify.md JSON: https://edge.network/json/docs/shield/siteverify.json _Validate Shield tokens with the siteverify API — Turnstile-compatible responses, error codes, and how to use the 1–100 humanity score._ Shield Server-Side Validation Every token must be validated from your server with the siteverify endpoint. The response shape is compatible with Cloudflare Turnstile, plus a humanity score. The Endpoint POST https://shield.edge.network/siteverify Content-Type: application/x-www-form-urlencoded secret=es_secret_...&response= Both application/x-www-form-urlencoded and application/json bodies are accepted. Parameter Required Description secret Yes Your widget's secret key ( es_secret_… ) response Yes The token from the edge-shield-response form input remoteip No The submitting visitor's IP address. Recommended: tokens are bound to the IP they were issued to, so passing this rejects tokens farmed on one machine and spent from another Responses Success: { "success": true, "score": 92, "challenge_ts": "2026-07-21T08:00:00.000Z", "hostname": "example.com", "error-codes": [] } Failure: { "success": false, "error-codes": ["timeout-or-duplicate"] } Field Description success Whether the token is genuine, unexpired, unused, and matches your widget score Humanity score, 1–100. Not present on failures. (Shield extension — not in Turnstile) challenge_ts ISO 8601 timestamp of when the token was issued hostname The hostname the widget ran on agent Present when the token belongs to a verified agent that declared its identity. (Shield extension — not in Turnstile) shadow Present only for widgets in shadow (report-only) mode — see below. (Shield extension — not in Turnstile) error-codes Machine-readable failure reasons (see below) Error Codes Code Meaning missing-input-secret No secret was supplied invalid-input-secret The secret doesn't match any active widget missing-input-response No token was supplied invalid-input-response The token is malformed, expired, from a different widget, or from a disallowed hostname timeout-or-duplicate The token was already used — tokens are strictly single-use agent-blocked A verified agent was rejected because the widget's agent policy is set to Block Verified Agent Tokens When automation cryptographically declares its identity (via Web Bot Auth or a confirmed crawler check) and your widget's agent policy allows it, the token carries the verified identity. The score stays an honest humanity estimate — low, because it's automation — and the agent field is how you route: { "success": true, "score": 8, "agent": { "domain": "agent.bot.goog", "verified": true, "method": "web-bot-auth" }, "challenge_ts": "2026-07-21T08:00:00.000Z", "hostname": "example.com", "error-codes": [] } Check agent.verified before trusting a low score: a verified agent is declared automation you may want to serve, while a low score with no agent field is automation that refused to identify itself. Shadow (Report-Only) Mode A widget can be switched to shadow mode in the dashboard (Shield → widget → Settings). In shadow mode siteverify never returns success: false — nothing is ever blocked — and instead the response carries what strict enforcement would have decided: { "success": true, "shadow": { "enabled": true, "enforced": false, "would_succeed": false, "error-codes": ["invalid-input-response"] }, "error-codes": [] } Log shadow.would_succeed and shadow["error-codes"] during the trial; would-fail and would-escalate counts also accumulate in your widget's analytics . When the numbers look right, switch shadow mode off — no code changes needed, since a correct integration already checks success . Shadow mode is the risk-free way to trial Shield on production traffic: real visitors can't be inconvenienced, and you get a fully quantified preview of what enforcement would have done. Testing Your Integration Fixed test secrets ( es_secret_test_pass , es_secret_test_fail , es_secret_test_spent ) return deterministic responses so your test suite can exercise every branch without real keys. See Testing & CI . Using the Humanity Score The score expresses confidence: 1 is confirmed automation, 100 is a confirmed human . "Not human" doesn't have to mean "not welcome" — a legitimate AI agent acting for a customer will score low, and you may prefer to route it to your API rather than block it. const { success, score } = await siteverify(token) if (!success) reject() // invalid, expired, or replayed token else if (score >= 70) allow() // confident human else if (score >= 40) stepUp() // uncertain — e.g. require email confirmation else routeOrBlock() // automation — block, or redirect to your API The thresholds are yours to tune. As reference points: in managed mode , background attempts scoring below 40 are automatically escalated to an interactive confirmation before a token is issued, so tokens arriving at your server from managed widgets already had a floor applied. The score you receive is also the freshest available: the widget verifies at page load, then re-mints its token with a behaviour-informed score once the visitor has actually typed or moved the pointer. By the time the form is submitted, the token usually reflects real interaction — human motor noise raises the score, machine-perfect input lowers it — not just the load-time environment. Token lifetime is 5 minutes and each token is valid for exactly one siteverify call. Validate at the moment of form processing, not ahead of time. Next Steps Offline Verification Verify tokens locally via JWKS — zero network calls Migrating from Turnstile Same response shape — swap and go Back to Docs Need help? --- ### Shield Verified Agents URL: https://edge.network/docs/shield/verified-agents/ Markdown: https://edge.network/docs/shield/verified-agents.md JSON: https://edge.network/json/docs/shield/verified-agents.json _Identify legitimate AI agents and crawlers with Web Bot Auth (RFC 9421) signatures, set per-widget agent policies, and verify agents server-side with the agentverify API._ Shield Verified Agents More than half of web traffic is automated, and a growing share of it is legitimate — AI agents shopping, booking, and researching for real customers. Shield identifies automation that declares itself, so aggressive treatment is reserved for automation that refuses to. How Identification Works Shield verifies agent identity two ways, in order of preference: 1. Web Bot Auth (HTTP Message Signatures) The emerging IETF standard (RFC 9421 signatures with the web-bot-auth tag) backed by OpenAI, Google, Amazon, and Cloudflare. The agent signs each request with an Ed25519 key and points to its published key directory via the Signature-Agent header. Shield fetches the directory, checks the signature, and confirms exactly which agent is calling — identity that can't be spoofed by copying a user-agent string. GET /products HTTP/1.1 Host: example.com Signature-Agent: "https://agent.bot.goog" Signature-Input: sig1=("@authority" "signature-agent");created=1753100000;\ keyid="poqkLGiy...";alg="ed25519";expires=1753100300;nonce="e8N7...";tag="web-bot-auth" Signature: sig1=:jdq0SqOwHdyHr9+r5jw3iYZH6aNGKijYp/EstF4RQTQdi5N5YYKrD+mCT1HA1nZDsi6nJKuHxUi/5Syp3rLWBA==: 2. Confirmed crawlers (reverse DNS) Established crawlers that predate Web Bot Auth — Googlebot, Bingbot, Applebot — are confirmed the way their operators document: reverse-DNS lookup of the calling IP, forward-confirmed back to the same address. A client merely claiming to be Googlebot from an unrelated IP gets no credit, and its user-agent lie counts against its humanity score. Verification happens automatically on every /challenge and /solve request an agent makes through the widget flow. A verified identity is bound into the response token and surfaced in the siteverify response as the agent field. Per-Widget Agent Policy Each widget chooses how verified agents are treated, in the widget's settings: Policy Behaviour allow default Verified agents pass without interactive escalation. The token carries their identity; the humanity score stays honest (low — they're automation). You route on the agent field. challenge No identity credit. Verified agents are scored like any anonymous client — clear automation signals will cap their score and trigger escalation in managed mode. block Verified agents are rejected at solve time with the agent-blocked error code. Whatever the policy, anonymous automation is always treated aggressively : clear automation signals with no declared identity hard-cap the humanity score. Declaring identity is the fast path — that's the incentive. Routing on Identity The score answers "is this a human?"; the agent field answers "then who is it?". Use both: const result = await siteverify(token) if (!result.success) reject() else if (result.agent?.verified) { // Declared automation — route it, don't fight it routeToApi(result.agent.domain) } else if (result.score >= 40) { allow() // human traffic } else { block() // automation that refused to identify itself } Server-Side Verification: agentverify Agents don't only arrive through forms. When a signed request hits your origin directly — an API endpoint, a content page — forward its signature headers to agentverify and Shield does the verification for you. No widget, no JavaScript, no challenge. POST https://shield.edge.network/agentverify Content-Type: application/json { "secret": "es_secret_...", "authority": "example.com", "headers": { "signature-agent": "...", "signature-input": "...", "signature": "..." } } Response: { "success": true, "agent": { "domain": "agent.bot.goog", "verified": true, "method": "web-bot-auth" }, "policy": "allow", "error-codes": [] } authority is the Host the agent addressed (signatures cover it, so it must match), and headers are the three signature headers verbatim from the incoming request. Failures return success: false with missing-signature-headers or signature-verification-failed . Web Bot Auth adoption is early and uneven — Google signs its AI-browsing agent but not Googlebot indexing, and rollouts are gradual. Treat a valid signature as strong positive identity; treat its absence as neutral, not negative. What Shield Stores Nothing new. Agent verification is stateless — key directories are cached briefly in memory, and the only persisted artefact is the hourly verified agent counter in your widget's analytics. No per-request logs, no agent request history. Next Steps Server-Side Validation The agent field in siteverify responses Analytics Verified agent counts per widget Back to Docs Need help? --- ### Shield Widget Modes URL: https://edge.network/docs/shield/widget-modes/ Markdown: https://edge.network/docs/shield/widget-modes.md JSON: https://edge.network/json/docs/shield/widget-modes.json _Managed, non-interactive, and invisible — choose how visible verification is, and configure the widget with data attributes._ Shield Widget Modes All three modes run the same verification pipeline — the only difference is what the visitor sees. No mode ever shows a puzzle. Managed Recommended Verification is invisible for real users. If the humanity score of a background attempt is low, the widget escalates: it shows a single "I am human" confirmation, and the click triggers a harder proof-of-work challenge. Most visitors never see it. Best for: signup, login, and checkout forms — anywhere you want maximum protection with a human fallback. Non-Interactive Background verification with a small status badge ("Verifying… / Verified") so visitors can see protection is active. Never asks for input — traffic that fails simply doesn't receive a token. Best for: contact forms and comment boxes where a visible trust signal is useful. Invisible No visible widget at all. Verification runs on page load, or on demand via the JS API ( edgeShield.execute() ). Because there is no visible element, there is no interactive escalation — low-scoring traffic fails silently. Best for: seamless UX on login pages and SPAs where you handle low scores server-side. Per-Widget Behaviours Two further switches sit alongside the mode in the dashboard. They change how verification behaves, not what the visitor sees: Shadow Mode Report-only Nothing is ever blocked: managed mode stops escalating, and siteverify always returns success — with what strict enforcement would have decided reported in a shadow object and counted in analytics. Best for: trialling Shield on production traffic with zero risk of inconveniencing a real customer, then switching enforcement on once the numbers look right. Tarpit On by default Clients that keep failing — wrong solutions, too-fast interactive answers, repeated low-score escalations — are served progressively harder proof-of-work. Each repeat offence quadruples the compute cost of the next attempt; one successful verification clears the slate immediately. Persistent bots pay an exponentially growing electricity bill; a human who stumbles once pays a few hundred extra milliseconds. Disable it per widget if you'd rather repeat failures stay cheap. Setting the Mode The mode is configured per widget in the dashboard (Shield → widget → Settings) and takes effect on the next challenge issued — no redeploy needed. You can also override it per-placement with data-mode :
Data Attribute Reference Attribute Default Description data-sitekey required The widget's public sitekey data-mode managed managed , non-interactive , or invisible data-callback — Global function name called with the token on success data-error-callback — Global function name called with an error string data-expired-callback — Called when a token expires (the widget auto-refreshes afterwards) data-input-name edge-shield-response Name of the hidden form input the token is written to data-compat — Set to turnstile to also populate a cf-turnstile-response input Next Steps JavaScript API Explicit rendering and SPA integration Server-Side Validation The siteverify API and humanity score Back to Docs Need help? --- ### Testing Shield in CI & Local Dev URL: https://edge.network/docs/shield/testing/ Markdown: https://edge.network/docs/shield/testing.md JSON: https://edge.network/json/docs/shield/testing.json _Fixed test sitekeys and secrets that behave deterministically — run your test suite against Shield with no real keys, no network state, and no analytics pollution._ Shield Testing & CI Shield ships fixed test keys with deterministic behaviour, so your test suite never needs real credentials, never depends on scoring outcomes, and never pollutes your widget's analytics. They work on any hostname. Test Sitekeys (Client Side) Use these in place of your real sitekey to force a specific widget behaviour: Sitekey Behaviour es_test_pass Always verifies — the widget shows the normal success state and produces a token es_test_block Every solve fails — exercise your error handling and no-token paths es_test_interactive Background attempts always escalate to the "I am human" confirmation first
Test Secrets (Server Side) Use these in place of your real secret to force a specific siteverify response, regardless of the token you send: Secret siteverify response es_secret_test_pass success: true , score 90 es_secret_test_fail success: false with invalid-input-response es_secret_test_spent success: false with timeout-or-duplicate — the replayed-token path # Always succeeds, score 90 curl -X POST https://shield.edge.network/siteverify \ -d "secret=es_secret_test_pass" \ -d "response=anything" { "success": true, "score": 90, "challenge_ts": "…", "hostname": "localhost", "error-codes": [] } What Test Traffic Can and Can't Do Test keys work on any hostname, including localhost , with no widget configuration. Test challenges use trivial proof-of-work, so CI runs stay fast. Test traffic records no analytics and no scoring signals — it cannot skew your real widgets' metrics or the network's scoring. Tokens minted by test sitekeys are dummy strings that only test secrets accept — a real secret will never validate one, and vice versa. Never ship test keys to production. es_secret_test_pass accepts anything — a form "protected" by it is protected by nothing. Keep test keys in test configuration only, exactly as you would a mock. Next Steps Getting Started Protect your first form in five minutes Server-Side Validation The siteverify API and humanity score Back to Docs Need help? --- ## Documentation › Assist ### Assist Answer Caching URL: https://edge.network/docs/assist/caching/ Markdown: https://edge.network/docs/assist/caching.md JSON: https://edge.network/json/docs/assist/caching.json _How Edge Assist caches answers: repeat questions are served instantly from your site's cache, invalidated the moment your content changes._ Assist Answer Caching Visitor questions follow a power law: a handful of questions make up most of the traffic. Assist answers each one once, caches it per site, and replays it instantly for everyone who asks after — with identical, consistent wording. What Gets Cached First questions only. The opening question of a conversation is cacheable; follow-ups depend on everything said before them and always go to the model. Questions are normalised before lookup — case and punctuation don't matter, so "How much is storage?" and "how much is Storage" share one cache entry. Cached site-wide. The same question asked on any page of your site hits the same entry. The one exception: questions that point at the visitor's current page ("is there a limit on this page?", "what does this product cost?") are answered against that page and cached per page. Cache hits still stream. The answer is replayed word by word — instantly available, but never a jarring wall of text. Invalidation A cached answer is only served while everything it was built from is still true: Content changes — every cache entry is stamped with the content hash it was answered from. A re-ingest clears the site's cache entirely; the next asks rebuild it from the new content. Assistant changes — entries are also stamped with a version of the assistant's instructions, so improvements to how Assist answers roll out without stale replays. Your pinned facts are part of that version: edit a fact in Assist → Overrides and cached answers stop matching immediately. Time — a 7-day TTL backstop means nothing lives forever, even if your content never changes. Need it gone now? Assist → Ingestion → Purge answer cache clears your site's cache instantly and for free — for "I fixed the content upstream but haven't re-deployed" or "that cached answer needs to go". Overrides Answer First Curated Q&As ( Assist → Overrides ) are checked before the cache and before any model call: a first-turn question that strongly matches one returns your exact words, instantly. Pinned facts steer every model-composed answer and take precedence over page content. Overrides are free on every site. Cached Answers & Billing Cached answers count as answered questions — metering is per question asked, however it's answered. The cache is a speed and consistency win for your visitors, not a billing discount. Cache statistics (entries, hits, share of traffic) are on your site's Overview page. Cache Pre-Warming Rather than waiting for visitors to fill the cache, pre-warming reads your ingested content, generates the questions visitors are likely to ask, and answers them into the cache ahead of time — so your most-asked questions are instant from the very first visitor. It lives in your site's Ingestion tab in Control: pick a scale (up to 100, 250 or 1,000 questions), review and prune the generated list — nothing is spent until you confirm — and optionally turn on auto re-warm, which refills the cache automatically after every content change. Pre-warming is a paid feature; each pre-warmed answer meters at the normal per-question rate, and anything Assist couldn't answer from your content lands in the question log as a content gap. See pricing . Next Steps Content Ingestion — the refresh cycle that drives invalidation Limits & Billing — what a question costs Back to Docs Need help? --- ### Assist API Reference URL: https://edge.network/docs/assist/api/ Markdown: https://edge.network/docs/assist/api.md JSON: https://edge.network/json/docs/assist/api.json _The HTTP API behind the Edge Assist widget: config, instant search, streamed answers over Server-Sent Events, and human handoff._ Assist API Reference The widget is built entirely on this API — if you'd rather build your own UI, a Slack bot, or a support-tool integration, you get exactly the same capabilities. Base URL: https://assist.edge.network . Authentication For public sites there are no secret keys. Every request carries your public sitekey, and the endpoints that do work ( /api/search , /api/ask , /api/handoff ) enforce the request's Origin : it must be your site's registered hostname or a subdomain of it. Requests from anywhere else get a 403 . Private sites (the bucket/knowledge-base tier ) replace the Origin check with credentials: send a per-site API key as Authorization: Bearer eak_… (server-side), or a short-lived visitor token — minted below — as a token query parameter (GET) or body field (POST). Anonymous requests get a 401 . localhost origins are always allowed on public sites, so browser-based development works before you deploy. Server-to-server calls (which send no Origin) are rejected on public sites — use a private site with an API key for headless access. Token (private sites) Exchanges a per-site API key for a visitor token: site-scoped, HMAC-signed, 15-minute expiry. Call it from your server when rendering a page behind your own login, and pass the token to the widget via data-token — the key itself never reaches a browser. Keys are created in Assist → Settings → Access . POST https://assist.edge.network/api/token Authorization: Bearer eak_your_site_api_key Content-Type: application/json { "sitekey": "ea_your_sitekey" } { "token": "eat_…", "expiresIn": 900 } Config Everything a client needs to render an assistant for a site: names, branding, suggested questions, and whether the site is currently over its monthly cap ( limited — when true, ask is unavailable and clients should fall back to search). GET https://assist.edge.network/api/config?sitekey=ea_your_sitekey { "name": "Example Inc", "assistantName": "Edge Assist", "hostname": "example.com", "welcome": "Hi! Ask me anything about Example.", "placeholder": null, "position": "bottom-right", "theme": { "accent": "#0BC95E" }, "prompts": ["How can we help?"], "suggested": ["What does it cost?", "How do I get started?"], "explore": [{ "title": "Pricing", "url": "/pricing" }], "badge": true, "whiteLabel": false, "handoff": true, "extended": false, "limited": false } Search Instant full-text results over the ingested content — no AI call, free and unlimited. Queries under 2 characters return an empty list; up to 8 results, one per page, best-matching first. Snippets mark matched terms with square brackets. GET https://assist.edge.network/api/search?sitekey=ea_your_sitekey&q=storage+pricing { "results": [ { "url": "/storage/pricing", "title": "Storage Pricing", "section": "storage", "snippet": "…[Storage] is billed at $0.015 per GB per month…" } ] } Ask Composes an answer over the ingested content and streams it. Questions must be 3–500 characters. Include history (the prior turns of the conversation) to make follow-ups work; include page so questions like "is there a limit on this page?" resolve against the page the visitor is reading. POST https://assist.edge.network/api/ask Content-Type: application/json { "sitekey": "ea_your_sitekey", "question": "How much does storage cost?", "history": [], // optional: prior turns [{ role, content }] "page": "/storage/pricing", // optional: page the visitor is on "conversationId": "…" // optional: groups turns in your question log } The response is Server-Sent Events : a sources event first (retrieval is instant), then delta events carrying JSON-encoded answer fragments (decode each with JSON.parse — that's how newlines survive SSE framing), then done : // Response: Server-Sent Events event: sources data: [{ "url": "/storage/pricing", "title": "Storage Pricing", … }] event: delta data: "Storage is billed at " event: delta data: "$0.015 per GB per month…" event: done data: {} Answers are markdown with inline citations as relative links. Each answered question is one metered question — including answers served from the cache . When a site is over its monthly cap, ask returns: HTTP/1.1 429 Too Many Requests { "error": "monthly-limit", "limited": true } Handoff Hands the conversation to a human. Requires a handoff email configured on the site (Control → Widget) — otherwise returns 404. The visitor's email, message, and recent transcript are forwarded to that address; replying to the email reaches the visitor directly. Handoffs are free (no metered question). POST https://assist.edge.network/api/handoff Content-Type: application/json { "sitekey": "ea_your_sitekey", "email": "visitor@example.com", "message": "I'd like a demo", // optional "page": "/pricing", // optional "transcript": [ // optional: recent turns (max 12) { "role": "user", "content": "Can I talk to someone?" }, { "role": "assistant", "content": "Of course — …" } ] } { "success": true } Errors & Rate Limits Errors are JSON with an error message: 400 for invalid input, 401 for a private site without valid credentials, 403 for a disallowed origin, 404 for an unknown sitekey, 429 when rate-limited or over the monthly cap. Rate limits are per visitor IP: Endpoint Limit GET /api/config 120 / minute GET /api/search 60 / minute POST /api/ask 10 / 5 minutes POST /api/handoff 3 / hour POST /api/token 60 / minute Next Steps Widget & Embedding — the prebuilt UI on these endpoints Limits & Billing — caps, budgets, and pricing Back to Docs Need help? --- ### Assist Bucket Ingestion URL: https://edge.network/docs/assist/bucket-ingestion/ Markdown: https://edge.network/docs/assist/bucket-ingestion.md JSON: https://edge.network/json/docs/assist/bucket-ingestion.json _Point Edge Assist at an Edge Storage bucket: supported document formats, the ETag diff cycle, the 10,000-document cap, and private access with per-site API keys and visitor tokens._ Assist Bucket Ingestion The knowledge-base tier: point Assist at an Edge Storage bucket and drop documents in. No index file, no build step — the bucket is the source of truth, and Assist keeps itself in sync with it. Available on pay-as-you-go. How It Works Create a bucket in Storage and upload your documents. In Assist → Ingestion , switch the content source to Storage bucket , pick the bucket (and an optional key prefix like docs/ ), and save. Assist lists the bucket hourly and diffs it by ETag: new and changed objects are parsed and indexed, deleted objects drop out of the index. Only what changed is re-processed. There is no push API by design — uploading, replacing, or deleting objects in the bucket is the ingestion interface. Any tool that can write to Edge Storage (the S3-compatible API, the Console, a CI job) can maintain the knowledge base. Any content change clears the site's answer cache , exactly as with index-file ingestion — and "Re-ingest now" in Control forces a diff immediately. Supported Formats Extension Notes .md / .markdown Front matter is stripped; the first heading becomes the document title; code fences are skipped. .txt Ingested as-is. The filename becomes the title. .html / .htm Tags, scripts, and styles are stripped; the becomes the document title. .pdf Text extraction only — scanned or image-only PDFs have no extractable text and are recorded as parse errors. Everything else in the bucket is skipped. Documents are chunked into ~1,400-character passages on paragraph and sentence boundaries — the same retrieval unit as the index-file tier — and cited in answers by document name. A document that fails to parse never blocks the rest of the bucket; it's listed with its error on the Ingestion tab and retried automatically when its content changes (or on a forced re-ingest). Limits Limit Value Documents per site 10,000 Size per document 20 MB Chunks per site 50,000 Knowledge bases beyond 10,000 documents are handled by Expert Services — custom retrieval, access control per prefix, and dedicated capacity. Private Access Bucket-sourced sites are private by default — an internal knowledge base shouldn't be one lifted sitekey away from public. A private site rejects anonymous search, ask, and config calls; access comes from per-site API keys , managed in Assist → Settings → Access . Keys are shown once at creation and stored hashed. (You can flip a site back to public there too — public sites are protected by the Origin check instead.) The widget on a private site Browsers never see the API key. Your server exchanges it for a short-lived visitor token (15-minute expiry, site-scoped) and renders the token into the embed: # Server-side: exchange your API key for a short-lived visitor token curl -X POST https://assist.edge.network/api/token \ -H "Authorization: Bearer eak_your_site_api_key" \ -H "Content-Type: application/json" \ -d '{"sitekey": "ea_your_sitekey"}' # → { "token": "eat_…", "expiresIn": 900 } <!-- Render the token into the embed — the API key never reaches the browser --> <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" data-token="eat_…" defer></script> Mint the token in the request that serves the page (behind your own login), and only authenticated users can ever reach the assistant. The hosted view works the same way: link to /w/<sitekey>?token=eat_… . Headless use Server-side callers can skip tokens entirely and present the API key directly: # Headless: the API key works directly on search and ask curl "https://assist.edge.network/api/search?sitekey=ea_your_sitekey&q=refund+policy" \ -H "Authorization: Bearer eak_your_site_api_key" Next Steps Content Ingestion — the index-file tier for website content API Reference — search, ask, and token endpoints Edge Storage — buckets, uploads, and the S3-compatible API Back to Docs Need help? --- ### Assist Content Ingestion URL: https://edge.network/docs/assist/ingestion/ Markdown: https://edge.network/docs/assist/ingestion.md JSON: https://edge.network/json/docs/assist/ingestion.json _How Edge Assist ingests your content: the index file format, chunking guidance, the hourly refresh cycle, and ingestion limits._ Assist Content Ingestion Assist answers only from content you give it. You publish a JSON index of your content at a URL; Assist polls it hourly and re-indexes whenever it changes. Your build pipeline is the source of truth. The Index File A single JSON document, deliberately small — most site generators can emit it in a few dozen lines of build script. Delegating the build to an AI agent? Hand it SKILL.md — this whole spec in a form an agent can fetch and follow directly. { "hash": "3f9c2a71b4e8d05c", "chunks": [ { "url": "/pricing", "title": "Pricing", "section": "pricing", "text": "Storage is billed at $0.015 per GB per month. There are no egress fees within…" }, { "url": "/docs/storage/buckets", "title": "Buckets", "section": "docs", "text": "A bucket is a flat namespace for objects. Names must be globally unique and…" } ] } Field Notes hash Required Any string that changes when the content changes (a content hash is ideal). Assist re-fetches the index hourly but only re-indexes when the hash differs — and a changed hash also invalidates the answer cache. chunks[].url Required The page the text came from, as a relative path (e.g. /pricing). Used for citations and search results. chunks[].title Recommended The page title, shown in search results and citation chips. chunks[].section Optional A coarse grouping label (e.g. docs, pricing, blog). Shown in search results. chunks[].text Required The chunk content: plain text, no HTML. Chunking Guidance A chunk is the unit of retrieval: when a visitor asks a question, Assist pulls the best-matching chunks into the answer. Good chunking is most of the quality: Aim for ~1,400 characters per chunk , split on sentence or paragraph boundaries. A chunk should read as a coherent passage on its own. Skip boilerplate. Navigation, footers, and cookie banners add noise, not answers. Very short fragments (under ~80 characters) aren't worth indexing. Keep facts with their subject. If a price or limit lives in a table, render it into the chunk as a sentence ("The free tier includes 250 questions per month") so retrieval can find it. One page, many chunks. Repeat the same url / title across a long page's chunks — citations group by page automatically. The Refresh Cycle Assist fetches your index URL hourly . If the hash matches the last ingest, nothing happens. If it changed, the site's search index is rebuilt from the new chunks and the answer cache is cleared — stale answers can't outlive the content they came from. Deployed something and don't want to wait? Assist → Ingestion → Re-ingest now forces a fetch immediately. The same page shows the index status: page and chunk counts, last refresh time, and the last ingest error if a fetch or parse failed. Ingestion failures never take the assistant down — it keeps answering from the last good index until a fetch succeeds again. Ingestion Limits Limit Free Paid Pages (distinct URLs) per site 500 10,000 Chunks per site 50,000 Knowledge bases beyond 10,000 documents are handled by Expert Services . Other Ingestion Sources The index URL is the most direct path for website content. For document collections that don't live on a website, bucket ingestion points Assist at an Edge Storage bucket of markdown, text, HTML, or PDF files — with private access control built in. Crawl-based ingestion (give Assist your site URL and it follows your sitemap itself — no build step) is on the way. Every source feeds the same index and behaves identically downstream. Next Steps Answer Caching — what happens to answers when content changes API Reference — search and ask over the ingested content Back to Docs Need help? --- ### Assist Limits & Billing URL: https://edge.network/docs/assist/limits-and-billing/ Markdown: https://edge.network/docs/assist/limits-and-billing.md JSON: https://edge.network/json/docs/assist/limits-and-billing.json _Edge Assist's free allowance, per-question pricing, pay-as-you-go billing, and every operational limit in one place._ Assist Limits & Billing One billable unit: the answered question. Search is free and unlimited, forever. Every site answers 250 questions free each month; beyond that it's $0.01 per question. How Billing Works A question = one AI-composed answer. Follow-ups each count as one question. Searches, config fetches, and handoffs are free. Cached answers still count — metering is per question asked. 250 free per site per month. No credit card required; the allowance resets on the first of the month. Beyond that: $0.01 per question ($10 per 1,000), billed pay-as-you-go from your account's prepaid balance — the same machinery as the rest of Edge. Pay-as-you-go is active automatically once you have a card on file, with an optional monthly spend cap if you want a hard ceiling. No plans, no seats, no per-page fees. Extended conversations meter at 2× on their deep turns — longer threads carry more context, which costs more to produce. It's an optional per-site setting. Worked examples are on the pricing page . What Happens at the Cap When a site reaches its monthly allowance (and there's no pay-as-you-go headroom to continue against), the widget degrades gracefully rather than breaking: Instant search keeps working — it's free and unlimited. Ask is paused: the widget shows a capacity notice and stops offering AI answers; the API returns 429 { "error": "monthly-limit" } . Answering resumes automatically when the month rolls over, or immediately when you add a card in Billing (pay-as-you-go activates with it) or top up an empty balance. Your site's Overview page in Control shows this month's usage against the cap, with the same warning thresholds your bill sees. All Limits Limit Value Answered questions (free) 250 / month / site Question length 500 characters Questions per conversation 20 (100 with extended conversations) History window per ask 6 turns (12 with extended conversations) Pages per site 500 free · 10,000 paid Chunks per site 50,000 Search rate limit 60 / minute / visitor Ask rate limit 10 / 5 minutes / visitor Handoff rate limit 3 / hour / visitor Paid Features A site becomes "paid" the moment pay-as-you-go is active on your account — automatic with a card on file, with or without a monthly cap. That unlocks, at no extra flat fee: Higher ingestion ceiling — 10,000 pages instead of 500. White label — name the assistant after your product and remove the "Powered by Edge Assist" badge. Extended conversations — longer threads with a deeper memory (metered 2× on deep turns). Cache pre-warming — answer likely questions ahead of time, with a review step before anything is spent (each answer meters at the normal rate). Next Steps Pricing — worked examples for real sites Getting Started — live in under ten minutes Back to Docs Need help? --- ### Assist Widget & Embedding URL: https://edge.network/docs/assist/widget/ Markdown: https://edge.network/docs/assist/widget.md JSON: https://edge.network/json/docs/assist/widget.json _Every way to put Edge Assist in front of visitors: floating launcher, inline embed, hosted page, hotkeys, custom triggers, and the JavaScript API._ Assist Widget & Embedding The widget is a single dependency-free script. It can float as a launcher, live inline in a page, open from your own buttons or a keyboard shortcut — or you can skip integration entirely and link to the hosted page. Floating Launcher (default) <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" defer></script> With no other markup, the widget renders a launcher pill (position and label configurable in Control). Clicking it opens the assistant as a centered overlay; on mobile it fills the screen. The pill samples the page behind it and inverts to stay readable over dark sections. Styles are isolated in a shadow root, so your CSS can't break the widget and the widget can't leak into your page. Typography follows your page's font family. Script Tag Options Attribute Meaning data-sitekey Required. Your site's public key ( ea_… ). data-hotkey Optional. A single key that opens the assistant in search mode with Cmd/Ctrl — e.g. data-hotkey="k" for ⌘K. data-token Private sites only. A visitor token your server minted with a per-site API key — see Bucket Ingestion . defer Recommended. The widget never blocks your page load either way. <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" data-hotkey="k" defer></script> Your Own Triggers Any element with data-edge-assist-open opens the assistant on click — a nav search icon, a "Chat with us" button on your contact page, a "Can't find it? Ask" link on your 404: <!-- Any element becomes an open trigger --> <button data-edge-assist-open>Chat with us</button> <!-- Open in search mode instead of chat --> <button data-edge-assist-open="search">Search the site</button> Or drive it from JavaScript: // Available once widget.js has loaded window.EdgeAssist.open() // open in chat mode window.EdgeAssist.open('search') // open in search mode window.EdgeAssist.close() window.EdgeAssist.toggle() // Or fire an event (no reference to the API object needed) window.dispatchEvent(new CustomEvent('edge-assist:open')) Inline Embed Give the widget a mount point and the panel renders in the page flow instead of floating — a persistent ask box for help centres, docs sidebars, and support pages: <!-- The panel renders inside this element instead of floating --> <div data-edge-assist></div> <!-- Fill the container completely (used by the hosted page) --> <div data-edge-assist data-mode="page"></div> The inline panel and the overlay are the same assistant with the same conversation state. Size the container however you like; the panel fills it. Hosted Page (zero integration) Every site gets a full-page assistant at https://assist.edge.network/w/<sitekey> — link to it from an email signature, a social bio, or a support menu before you've touched your site's code. The exact URL is on your site's Overview page in Control. Conversation Behaviour Conversations are stored in the visitor's browser session and survive page navigations and close/reopen. They expire after 30 minutes idle or when the tab closes. "New conversation" ends a thread explicitly. Follow-ups carry context: the assistant sees the recent turns, so "why?" and "how much?" work naturally. Threads cap at 20 questions (100 with extended conversations ) — long threads on a marketing or docs site are almost always a support case, which is what handoff is for. If the visitor's question can't be answered from your content, Assist says so and — when a handoff email is configured — offers to bring in a human. Customisation (Control → Widget) Everything below is a setting, not code — changes apply to live widgets within minutes: Setting What it does Accent colour Brand colour for links, chips, and highlights. Position Launcher corner: bottom-right or bottom-left. Welcome message & placeholder The greeting and the input hint. Suggested questions Up to four one-click chips shown before the first question. Launcher prompts Labels the floating pill rotates through every few seconds. Keep exploring links Curated links shown alongside citations in the expanded view. Handoff email Enables "Need a human?" — conversations are forwarded here with the transcript. White label & assistant name Paid: name the assistant after your product and remove the "Powered by Edge Assist" badge. Extended conversations Paid: longer threads with deeper memory. Deep turns meter at 2× — see Limits & Billing . Next Steps API Reference — build your own UI on the same endpoints Content Ingestion — what the assistant answers from Back to Docs Need help? --- ### Edge Assist URL: https://edge.network/docs/assist/ Markdown: https://edge.network/docs/assist.md JSON: https://edge.network/json/docs/assist.json _Add AI answers to your website with one script tag. Assist answers visitor questions from your own content, with citations, streamed word by word._ Assist Edge Assist Edge Assist adds AI answers to your website. Visitors ask questions in a search-and-ask widget, and Assist answers from your own content — with citations, streamed word by word. One script tag to embed; no model keys, no infrastructure. How It Works You give Assist your content. Your site publishes a small JSON index that Assist re-fetches hourly, so answers track your content automatically. See Content Ingestion . Visitors search or ask. The widget gives instant full-text results as they type (free, unlimited), and composes an AI answer when they ask a question — grounded in your content and cited, so it links the pages it drew from. Repeat questions come from cache. Answered questions are cached per site and replayed instantly, invalidated the moment your content changes. See Answer Caching . Humans stay in the loop. A visitor can hand the conversation to your team at any point — Assist emails you the transcript and their address, and you reply directly. Assist is grounded: it answers from the retrieved passages and the conversation, and declines rather than inventing facts your content doesn't contain. Every answer cites its sources. Quick Start Create a site in the console , point it at your content, and add one line to your pages: <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" defer></script> That renders a floating launcher on every page. The full walkthrough — including inline embeds, the hosted page, and keyboard shortcuts — is in Getting Started . Key Concepts Concept What it is Site One Assist deployment: a hostname, a content index, widget settings, and metrics. Accounts can have multiple sites. Sitekey A public identifier ( ea_… ) embedded in your pages. There is no secret key — see origin enforcement below. Origin enforcement Search, ask, and handoff only accept requests from your registered hostname (and subdomains), so a copied sitekey is useless on another domain. localhost is always allowed for development. Question The billable unit: one AI-composed answer. Searches are free and unlimited. Every site answers 250 questions free each month. Override Your final word: pinned facts take precedence over site content in every answer, and curated Q&As return your exact wording verbatim when a question strongly matches. Free on every site, managed in Control. In This Section Getting Started Create a site, ingest your content, embed the widget — live in minutes. Widget & Embedding Launcher, inline embeds, hosted page, hotkeys, the JavaScript API, and every customisation option. Content Ingestion The index file format, chunking guidance, refresh cycle, and limits. Answer Caching How repeat questions are answered instantly, and how the cache invalidates. API Reference The HTTP API behind the widget: config, search, ask (SSE), and handoff. Limits & Billing The free allowance, per-question pricing, rate limits, and every cap. Learn More Edge Assist overview Live demo Pricing Back to Docs Need help? --- ### Getting Started with Assist URL: https://edge.network/docs/assist/getting-started/ Markdown: https://edge.network/docs/assist/getting-started.md JSON: https://edge.network/json/docs/assist/getting-started.json _Create an Assist site, point it at your content, and add the widget to your pages — AI answers live in minutes._ Assist Getting Started Four steps: create a site, ingest your content, embed the widget, make it yours. Most integrations take under ten minutes. 1. Create a Site In the console , go to Assist → Create Site . Give it a name and the hostname it will run on (e.g. example.com ). You'll receive a sitekey ( ea_… ). It's public — it goes straight into your HTML. There is no secret key: the API only accepts requests for your sitekey from your registered hostname and its subdomains, so the key is useless anywhere else. localhost is always allowed, so you can test before deploying. The hostname matters: it's what the origin check enforces. If your site moves domains, update the hostname in Assist → Settings or the widget will stop answering. 2. Ingest Your Content Assist answers only from content you give it. Publish a JSON index somewhere on your domain (e.g. /assist-index.json ), usually as part of your site build: { "hash": "sha256-of-the-content", "chunks": [ { "url": "/pricing", "title": "Pricing", "section": "pricing", "text": "One chunk of page content, up to ~1,400 characters,\nsplit on sentence boundaries…" } ] } Set the index URL in Assist → Ingestion and hit Re-ingest now . From then on Assist re-fetches it hourly and re-indexes whenever the hash changes — a site rebuild is all it takes to update what Assist knows. The full format, chunking guidance, and limits are in Content Ingestion . 3. Add the Widget One script tag, anywhere in your HTML (the exact snippet with your sitekey is on the site's Overview page in Control): <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" defer></script> This renders a floating launcher pill. Clicking it opens the assistant: instant search results as visitors type, AI answers when they ask. Conversations survive page navigations within the session. Want it inline in a help centre, bound to ⌘K , or with no integration at all (a hosted page you can link to)? All the embedding modes are in Widget & Embedding . 4. Make It Yours Under Assist → Widget you can set, without touching code: Welcome message and placeholder — the first thing visitors read. Suggested questions — chips shown before the first question; great for steering visitors to your best answers. Launcher prompts — rotating labels on the floating pill ("How can we help?", "Ask about pricing…"). Accent colour and position — match your brand; bottom-right or bottom-left. Handoff email — set this to enable "Need a human?": visitors leave their email and the conversation lands in your inbox. Keep exploring links — curated links shown in the expanded view. Then watch Assist → Overview and Questions : every question, answered or not, is logged — unanswered questions are a to-do list for your content. Next Steps Widget & Embedding — every integration mode Content Ingestion — the index format in full Limits & Billing — what's free and what a question costs Back to Docs Need help? --- ## Documentation › Account ### Account & Support URL: https://edge.network/docs/account/ Markdown: https://edge.network/docs/account.md JSON: https://edge.network/json/docs/account.json _Manage your Edge Network account, team members, security settings, and access comprehensive support resources._ Account Management Account & Support Everything you need to manage your Edge account, collaborate with your team, and secure your infrastructure. Edge Network provides comprehensive account management features to help you collaborate effectively with your team while maintaining security and compliance. Whether you're a solo developer or part of a large organization, you have the tools to manage access and protect your resources. Teams Invite team members, manage roles, and control access to your resources. Security Protect your account with 2FA, session management, and audit logging. Two-Factor Authentication Add an extra layer of protection with TOTP-based 2FA. Audit Log Track all activity for compliance and security investigations. Cost Advisor AI analysis of your usage and spend, with savings opportunities in real dollar amounts. How Accounts Work Edge Network uses a flexible account model that separates your login identity from your resources: User (Login Identity) Your email and password (or OAuth connection) that you use to log in. A single user can belong to multiple accounts. Account (Resource Container) A container for your resources (VMs, CDN deployments, DNS zones, etc.). Each account has its own team members, billing, and settings. This model allows you to: Have a personal account for your own projects Be a member of multiple team accounts Switch between accounts without logging out Use the same login for work and personal projects Default Account If you belong to more than one account, you can choose which account to sign in to by default. This is the account you'll land on each time you log in. To set your default account, go to Account → Settings → Profile . When you have multiple accounts, a Default Account section will appear where you can select your preferred account. Click Set as Default next to any account to make it your landing account on login. You can switch between accounts at any time using the account switcher in the top-right menu, regardless of which account is set as your default. Quick Links Manage Team Security Settings Activity Log Run the Cost Advisor Contact Support Back to Docs Need help? --- ### Alerts & Notifications URL: https://edge.network/docs/account/alerts/ Markdown: https://edge.network/docs/account/alerts.md JSON: https://edge.network/json/docs/account/alerts.json _Stay informed about your infrastructure with real-time alerts for all Edge Network services._ Account Alerts & Notifications Real-time alerts keep you informed about important events across your infrastructure. Overview The alerts page aggregates notifications from all Edge services into a single feed. You'll be notified about operational events, security updates, resource warnings, and product announcements. Access alerts from Account → Alerts or via the bell icon in the navigation bar. Alert Types Error Something needs immediate attention. Failed uploads, service errors, or security incidents. Warning Something may need attention soon. Resource limits approaching, high usage, or configuration issues. Success An operation completed successfully. SSL renewals, scaling operations, DNS propagation. Info General information. Scheduled maintenance, product updates, and feature announcements. What Triggers Alerts Compute Alert Type Description High CPU usage Warning CPU usage exceeded 90% for more than 15 minutes VM scaling completed Success VM resize operation finished Disk space low Warning Disk usage exceeded 85% CDN Alert Type Description SSL certificate renewed Success Automatic SSL renewal completed SSL certificate expiring Warning Certificate expires within 7 days and auto-renewal failed Origin errors Error Origin server returning errors for multiple requests Storage Alert Type Description Storage quota approaching Warning Bucket is at 85% or more of capacity Upload failed Error File upload failed due to rate limiting or size limits DNS Alert Type Description DNS propagation complete Success All DNS changes have propagated globally Zone sync failed Error Failed to sync zone to DNS network System Alert Type Description Scheduled maintenance Info Upcoming maintenance window with expected impact New features Info Product updates and new feature announcements Managing Alerts Filtering Use the filter buttons to view specific alert types: All — Every notification Unread — Only unread notifications Warnings — Resource limits, performance issues Errors — Failures requiring attention Actions Mark as read — Click an alert to mark it as read Mark all read — Clear all unread indicators at once Delete — Remove individual alerts from your feed Take action — Some alerts include a direct link to the relevant resource Unread Badge The bell icon in the navigation bar shows a badge with the number of unread alerts. This updates in real-time so you can stay aware of new events without visiting the alerts page. See Also Audit Log Detailed history of all account activity Security Account security and access controls Back to Docs Need help? --- ### Audit Log URL: https://edge.network/docs/account/audit-log/ Markdown: https://edge.network/docs/account/audit-log.md JSON: https://edge.network/json/docs/account/audit-log.json _Track all account and infrastructure activity with Edge Network's comprehensive audit trail. Essential for compliance and security investigations._ Compliance & Monitoring Audit Log Comprehensive activity tracking for security, compliance, and operational visibility. Overview Edge Network maintains a detailed audit trail of all activity across your account and infrastructure. Every action—from user sign-ins to configuration changes—is logged with timestamps, IP addresses, and contextual details. The audit log is essential for: Security Investigations Quickly identify unauthorized access attempts or suspicious activity patterns. Compliance Audits Demonstrate adherence to SOC 2, ISO 27001, GDPR, and other frameworks. Change Tracking Understand who changed what and when for troubleshooting and accountability. Operational Visibility Monitor team activity and infrastructure operations in real-time. What's Logged The audit log aggregates events from all Edge Network services into a single, unified view: Account Events Event Description Sign in User signed in (includes method: email, Google, GitHub) Password changed Account password was updated 2FA enabled/disabled Two-factor authentication status changed Session revoked User session was terminated Profile updated Account profile information was modified Team Events Event Description Member invited Invitation sent to a new team member Invite accepted Team member accepted an invitation Invite cancelled Pending invitation was cancelled Role changed Team member's role was updated Member removed Team member was removed from the account CDN Events Event Description Deployment created/deleted CDN deployment lifecycle events Domain added/removed Domain configuration changes Cache purged Cache invalidation requests Configuration updated Caching rules or optimization settings changed SSL certificate issued TLS certificate provisioned or renewed Compute Events Event Description VM created/deleted Virtual machine lifecycle events VM started/stopped/restarted Power state changes VM resized Resource allocation changes (vCPU, RAM, storage) Backup created/restored Backup and recovery operations Snapshot created/restored Point-in-time snapshot operations DNS Events Event Description Zone created/deleted DNS zone lifecycle events Record added/updated/deleted DNS record changes Zone verified Domain ownership verification completed Zone synced Records synchronized to DNS network Storage Events Event Description Bucket created/deleted Storage bucket lifecycle events Object uploaded Files uploaded to a bucket Object deleted Files removed from a bucket Object copied Files copied within or between buckets Folder created/deleted Folder structure changes Accessing the Audit Log Navigate to Account → Activity in your console You'll see a chronological list of all recent activity Use the filters to narrow down by service (Account, CDN, Compute, DNS) or event level Use the search box to find specific events by keyword Event Details Each audit log entry includes: Timestamp — When the event occurred (UTC) Service — Which service the event relates to (Account, CDN, Compute, DNS, Storage) Event type — The specific action that was performed Severity level — Info, Success, Warning, or Error Description — Human-readable summary of the event Actor — The team member who performed the action (for accounts with multiple members) Source — How the action was triggered: Web (console), CLI, or API IP address — Source IP for user-initiated actions (where applicable) Pro tip: Color-coded severity levels help you quickly identify issues. Red (error) and amber (warning) events should be reviewed promptly. CLI & API Attribution: Actions performed via the Edge CLI or API are automatically tagged with a CLI or API badge in the activity log. This helps teams distinguish between automated actions (scripts, CI/CD pipelines) and manual changes made through the console. Filtering & Search The audit log provides several ways to find the events you're looking for: Filter by Service Click the service buttons (All, Account, CDN, Compute, DNS, Storage) to show only events from that service. Filter by Severity Use the dropdown to filter by event level: Info, Success, Warning, or Error. Keyword Search Enter keywords in the search box to find events containing that text. Useful for finding events related to specific resources (e.g., a VM name or domain). Compliance & Audit Readiness Edge Network's audit log is designed to support your compliance requirements: SOC 2 Type II Comprehensive logging supports the security and availability trust principles. ISO 27001 Audit trails help demonstrate control effectiveness for information security management. GDPR Track data access and modifications for data protection compliance. HIPAA Audit logging supports access tracking requirements for healthcare workloads. Enterprise Features Enterprise customers have access to additional audit log capabilities: Available on Enterprise Plans Extended log retention (up to 7 years) Log export to your SIEM (Splunk, Datadog, etc.) Custom retention policies by event type API access for programmatic log retrieval Tamper-proof log storage with cryptographic verification Contact Sales Back to Docs Need help? --- ### Cost Advisor URL: https://edge.network/docs/account/cost-advisor/ Markdown: https://edge.network/docs/account/cost-advisor.md JSON: https://edge.network/json/docs/account/cost-advisor.json _AI analysis of your account-wide usage and spend: VM right-sizing, waste detection, and capacity pressure — with specific recommendations and real dollar amounts._ Account & Support Cost Advisor An AI review of everything you run on Edge — VM utilisation, storage, CDN traffic, DNS, and add-ons — that identifies wasted spend and capacity pressure, with specific recommendations and the dollar amounts to back them up. Included with every account The Cost Advisor is free to run, as often as you like. If it finds ways for you to pay us less, it says so — that's the point. How to Use 1 Open Billing in the console and switch to the Cost Advisor tab 2 Click Analyse My Account — the analysis covers your last 7 days of resource metrics and takes about 30 seconds 3 Review the efficiency score, spend breakdown, VM utilisation charts, and prioritised recommendations — each one names the exact resource and the action to take What It Analyses VM Right-Sizing Seven days of CPU, memory, and disk metrics per VM. A VM averaging 3% CPU with low memory use gets a downsize recommendation and the exact monthly saving; a VM pinned at 100% gets an upgrade recommendation instead. Waste Detection Stopped VMs still paying for allocated disk, unused extra IPs, forgotten snapshots, and add-ons you may no longer need — everything idle that still costs money. Capacity Pressure Usage approaching plan limits, memory above 85%, disks nearly full — situations where more capacity costs less than the outage it prevents. Plan Fit Whether your total usage fits a cheaper plan, whether annual billing would save you money, and — for pay-as-you-go accounts — where your hourly spend actually goes. Protection Gaps Production VMs without snapshots, DNS zones without backups , low CDN cache-hit rates hammering your origin — cheap fixes that prevent expensive problems. Recommendation Types Every recommendation carries a monthly dollar figure so you can see exactly what acting on it does to your bill. Type Badge Meaning Saving Save $X/mo Genuine waste — downsizing, removing, or consolidating cuts your bill by this amount. Investment +$X/mo More capacity or an upgrade where the data shows pressure. Costs more; prevents worse. Protection Protection Backups, snapshots, and resilience gaps worth closing. Free Free Configuration improvements that cost nothing — cache tuning, housekeeping. Efficiency Score Each analysis produces a spend-efficiency score from 0 to 100 — how well your resources match your actual usage. Score Rating Meaning 80–100 Well optimised Resources match usage; little or no wasted spend found. 50–79 Room to improve Some over-provisioned or idle resources worth acting on. 0–49 Significant waste Meaningful monthly savings available from right-sizing. How the Dollar Amounts Work Savings are computed from your real pricing, never estimated by the AI: Pay-as-you-go accounts — compute bills hourly, so downsizing or deleting a VM is a direct cash saving at the published per-resource rates. Stopped VMs still pay for their allocated disk, and the Advisor will tell you so. Subscription plans — compute is included in your plan, so downsizing a VM frees headroom rather than cutting the bill. The real saving the Advisor looks for is whether your total usage fits a cheaper plan. If your account is already efficient, the report says so and lists what you're doing right. The Advisor never pads a report to look useful — and yes, it will sometimes recommend spending more, when seven days of data show a resource under real pressure. What Gets Analysed The Advisor works from aggregate usage data only: per-VM resource metrics, storage totals, CDN request counts, DNS query volumes, add-on inventory, and your plan's pricing. It never reads the contents of your VMs, buckets, or zones. Saved Results Analyses are saved automatically. When you return to the Cost Advisor tab, your most recent report is shown with the date and time it was run. Click Re-analyse at any time for a fresh report — your last ten are kept. Back to Docs Need help? --- ### Referral Program URL: https://edge.network/docs/account/referral-program/ Markdown: https://edge.network/docs/account/referral-program.md JSON: https://edge.network/json/docs/account/referral-program.json _Refer customers to Edge and earn 15% of everything they spend in year one, 10% in year two, and 5% in year three — credited straight to your balance. Your referrals get $10 of free credit._ Account & Support Referral Program Earn a share of everything your referrals spend, for three years. They get free credit to start. Overview Every Edge account gets a referral code. When someone signs up through it, two things happen: they receive $10 of free prepaid credit on their first top-up, and you start earning revenue share on everything they spend — 15% in year one, 10% in year two, 5% in year three. Earnings are credited straight to your prepaid balance as your referrals spend, with no minimum payout and nothing to configure. Your Referral Code Your referral code is found in Account → Referral Program . It is auto-generated as REF-XXXXXXXX , but you can customise it to any alphanumeric string. Share your referral link: edge.network/r/{code} What Your Referrals Get Referred customers get $10 of free prepaid credit . The credit is added to their balance automatically once they've verified their email and made their first top-up of $10 or more — effectively doubling their first top-up. What You Earn You earn a percentage of your referrals' actual spend — usage billed from their balance and any subscription payments — for three years from their first spend: Period Your share Year 1 15% Year 2 10% Year 3 5% Earnings are credited to your prepaid balance automatically as your referrals spend (batched into roughly $1 increments to keep your balance history readable). There is no minimum payout, no payout schedule, and no configuration — the money is simply there to spend on anything on Edge, or to sit alongside your top-ups. Refer a customer spending $500 a month and you earn about $75 a month in year one — $900 over the year, $1,500 over the full three years. A handful of real referrals covers most bills. How It Works Share your referral link with potential customers They sign up through it and get $10 of credit on their first top-up of $10 or more Their first spend activates your revenue share and starts the 3-year clock As they spend, your share is credited to your prepaid balance automatically Track referrals, earnings, and history in Account → Referral Program Promotional Tools The Referral Program page includes tools to help you share: Pre-written social media posts Email templates Copy-paste share links Rules To keep the program fair for everyone: Self-referral is blocked — you cannot refer your own accounts One referrer per customer — the code used at signup wins Revenue share applies to real spend only: top-ups themselves, refunds, and promotional credits don't count until they're spent Referrals made to game the system (fake accounts, same-person signups) are voided Customers referred under the legacy subscription programme continue under the terms that applied when those referrals were made Back to Docs Need help? --- ### Security URL: https://edge.network/docs/account/security/ Markdown: https://edge.network/docs/account/security.md JSON: https://edge.network/json/docs/account/security.json _Secure your Edge Network account with two-factor authentication, session management, and comprehensive audit logging for compliance._ Account & Support Security Protect your infrastructure with enterprise-grade security features. Edge Network provides comprehensive security features to protect your account and meet compliance requirements. From multi-factor authentication to detailed audit trails, you have the tools to secure your infrastructure and demonstrate compliance to auditors and stakeholders. Two-Factor Authentication Add an extra layer of protection with TOTP-based 2FA. Audit Log Track all activity for compliance and security investigations. Security Features Multi-Factor Authentication Protect your account with TOTP-based two-factor authentication. Compatible with Google Authenticator, Authy, 1Password, and other authenticator apps. Session Management View and manage all active sessions. Revoke access from any device, anywhere, at any time. Comprehensive Audit Trail Every action is logged with timestamps, IP addresses, and user context. Essential for SOC 2, ISO 27001, and other compliance frameworks. OAuth Integration Sign in with Google or GitHub for passwordless authentication while still benefiting from 2FA protection. Role-Based Access Control Assign team members specific roles (Owner, Admin, Developer, Viewer) to control what they can access and modify. Learn more about teams . Enterprise & Compliance Our security features are designed with enterprise requirements in mind. Whether you're a startup preparing for your first SOC 2 audit or an enterprise with mature security practices, Edge Network provides the tools you need. Enterprise Security Need SSO/SAML, custom retention policies, or advanced security features? Contact our enterprise team for custom solutions. Contact Sales Getting Started We recommend enabling all security features for maximum protection: Enable two-factor authentication for your account Review your activity log regularly Manage active sessions and revoke any you don't recognize Use role-based access to limit team member permissions Back to Docs Need help? --- ### Support Tickets URL: https://edge.network/docs/account/support/ Markdown: https://edge.network/docs/account/support.md JSON: https://edge.network/json/docs/account/support.json _Submit and track support tickets to get help from the Edge Network team._ Account & Support Support Tickets Submit tickets, track progress, and communicate with the Edge support team directly from your console. Overview The support system provides a direct line to the Edge team for technical issues, billing questions, and account assistance. All communication is tracked in a threaded ticket format so nothing gets lost. Access support from Account → Support in your console. Creating a Ticket Navigate to Support and click New Ticket Enter a clear, descriptive subject Select the category that best matches your issue (CDN, Compute, DNS, Storage, Billing, Account) Set the priority based on urgency Describe your issue in detail in the description field Click Submit Ticket Tips for faster resolution Include the specific resource affected (VM name, domain, bucket name) Describe what you expected vs what actually happened Include any error messages you're seeing Note when the issue started Priority Levels Priority Use When Target Response High Production service is down or severely degraded Within 1 hour Medium Non-critical issue affecting functionality Within 4 hours Low General question, feature request, or non-urgent issue Within 24 hours Ticket Statuses Ticket statuses update automatically based on actions taken: Open Your ticket has been submitted and is awaiting a response from the support team. In Progress A support agent has replied and is working on your issue. Pending Resolution The agent believes the issue is resolved and is waiting for your confirmation. You can confirm it's resolved or reply if you still need help. Tickets auto-close after 7 days if no response is received. Resolved The issue has been resolved. You can reopen the ticket if you need further assistance. Replying to Tickets Click on any ticket to view the full conversation thread. You can: Reply — Send a message to the support agent using the reply box at the top Confirm resolved — When the agent marks your ticket as resolved, confirm it's fixed or reply if you still need help Reopen — If a resolved ticket needs further attention, reopen it to continue the conversation Categories Category Examples CDN Cache issues, SSL certificates, domain configuration, performance Compute VM connectivity, scaling, provisioning, OS issues DNS Propagation delays, record issues, zone configuration Storage Upload issues, access keys, bucket configuration, S3 compatibility Billing Invoice questions, payment issues, plan changes Account Team management, permissions, security, quota increases See Also Alerts & Notifications Real-time infrastructure alerts Audit Log Track all account activity Back to Docs Need help? --- ### Teams URL: https://edge.network/docs/account/teams/ Markdown: https://edge.network/docs/account/teams.md JSON: https://edge.network/json/docs/account/teams.json _Learn how to invite team members, manage roles and permissions, and collaborate effectively on your Edge Network account._ Account & Support Teams Collaborate with your team by inviting members and assigning roles based on their responsibilities. Edge Network's team features allow you to invite colleagues to your account with specific roles that control what they can access and modify. Whether you're a small team or a large organization, you can structure access to match your workflow. Users vs Accounts A user can belong to multiple accounts. When invited to a team, you don't need a separate login—you can switch between accounts using the account selector in the top navigation. Roles & Permissions Each team member is assigned a role that determines what actions they can perform. Choose the right role based on each person's responsibilities. Role Description Resources Team Billing Owner Full access to everything. Can transfer ownership. Admin Manage resources and team. Cannot access billing or assign Admin/Owner roles. Developer Create, modify, and delete resources. Generate API keys. View only Viewer Read-only access to all resources. Cannot make changes. View only View only Detailed Permissions Resource Permissions Action Owner Admin Developer Viewer View resources Create resources Delete resources Manage API keys Team Permissions Action Owner Admin Developer Viewer View team members Invite members Remove members Assign Admin role Transfer ownership Inviting Team Members 1 Go to Team Settings Navigate to Account → Team in your dashboard. 2 Click "Invite Member" Enter their email address and select the appropriate role. 3 They Accept the Invitation They'll receive an email with a link to accept. If they don't have an Edge account, they'll create one during acceptance. Invitation Expiry Invitations expire after 7 days. If an invitation expires, you can cancel it and send a new one. Accepting an Invitation When you're invited to a team, you'll receive an email with an invitation link. Existing Edge Users Log in with your existing account to accept. The team account will be added to your account switcher. New Users Create an Edge account using the invitation email address. You'll be added to the team immediately after signup. No Personal Account Required When you sign up via a team invitation, you won't automatically get a personal account. You can create your own accounts later from the account switcher if needed. Switching Between Accounts If you belong to multiple accounts (personal and team accounts), you can switch between them easily: Click your profile avatar in the top-right corner You'll see your current account and other available accounts Click on any account to switch to it The account switcher shows your role in each account and highlights the currently active one. Managing Team Members Changing Roles Owners can assign any role. Admins can only assign Developer or Viewer roles. To change a member's role, click on their current role in the team list and select a new one. Removing Members Owners and Admins can remove team members. Note that Admins cannot remove other Admins—only the Owner can do this. Removing a member immediately revokes their access to all resources. Canceling Invitations If someone hasn't accepted their invitation yet, you can cancel it from the team page. This is useful if you invited the wrong email or need to change the role. Activity Tracking All team actions are logged in the Activity Log : Member invitations sent Invitations accepted or cancelled Role changes Member removals This provides a complete audit trail for compliance and security purposes. Best Practices Principle of Least Privilege Assign the minimum role needed for each person's job. Use Viewer for stakeholders who only need to monitor, Developer for those who build, and Admin only for team managers. Remove Inactive Members Regularly review team members and remove anyone who no longer needs access. This reduces security risk. Require 2FA Encourage all team members to enable two-factor authentication for added security. Have Multiple Admins For business continuity, have at least one Admin in addition to the Owner. This ensures someone can manage the team if the Owner is unavailable. API Reference Manage team members programmatically using the Edge API. GET /api/team/members List all members of the current account POST /api/team/members Invite a new member (requires Admin+ role) PATCH /api/team/members/:id Update a member's role DELETE /api/team/members/:id Remove a member from the account Back to Docs Need help? --- ### Two-Factor Authentication URL: https://edge.network/docs/account/two-factor-authentication/ Markdown: https://edge.network/docs/account/two-factor-authentication.md JSON: https://edge.network/json/docs/account/two-factor-authentication.json _Secure your Edge Network account with TOTP-based two-factor authentication. Compatible with Google Authenticator, Authy, 1Password, and more._ Account Security Two-Factor Authentication Add an extra layer of security to your account with TOTP-based 2FA. Overview Two-factor authentication (2FA) requires both your password and a time-based one-time password (TOTP) from your authenticator app to sign in. Even if your password is compromised, attackers cannot access your account without the second factor. Recommendation: We strongly recommend enabling 2FA for all accounts, especially those with access to production infrastructure. Works with OAuth 2FA is enforced even when signing in with Google or GitHub. Recovery Codes Backup codes ensure you're never locked out of your account. Industry Standard TOTP-based, compatible with all major authenticator apps. Compatible Authenticator Apps Any TOTP-compatible authenticator app will work. Popular options include: Google Authenticator — Available for iOS and Android Authy — Cross-device sync and desktop app 1Password — Integrated password manager with TOTP Microsoft Authenticator — Works with Microsoft accounts too Bitwarden — Open-source password manager with TOTP Enabling Two-Factor Authentication Navigate to Settings → Security in your console Find the Two-Factor Authentication section and click Enable Scan the QR code with your authenticator app (or enter the secret manually) Enter the 6-digit code from your app to verify Save your recovery codes in a secure location Save Your Recovery Codes Recovery codes are shown only once when you enable 2FA. Store them securely — they're the only way to access your account if you lose your authenticator device. Signing In with 2FA Enabled Once 2FA is enabled, the sign-in process requires an additional step: Enter your email and password (or sign in with Google/GitHub) You'll be prompted for your 6-digit authentication code Open your authenticator app and enter the current code You're now signed in The authentication code changes every 30 seconds. If a code doesn't work, wait for the next one and try again. Recovery Codes When you enable 2FA, you'll receive a set of recovery codes. Each code can only be used once and allows you to access your account if you lose your authenticator device. Best Practices Store recovery codes in a password manager or secure vault Keep a printed copy in a secure physical location Never share recovery codes with anyone Generate new codes if you suspect they've been compromised Generating New Recovery Codes If you've used most of your recovery codes or suspect they've been compromised, you can generate a new set: Navigate to Settings → Security In the 2FA section, you'll see how many recovery codes remain Click to generate new codes (requires your current 2FA code) Important: Generating new codes invalidates all previous codes Disabling Two-Factor Authentication If you need to disable 2FA (not recommended): Navigate to Settings → Security Click Disable 2FA Enter your current authentication code or a recovery code to confirm Disabling 2FA significantly reduces your account security. Consider keeping it enabled and using recovery codes if you're concerned about device access. Troubleshooting Code not working? TOTP codes are time-based. Ensure your device's clock is accurate. Most authenticator apps handle this automatically, but if you're having issues, check your device's time settings. Lost your authenticator device? Use one of your recovery codes to sign in. Once signed in, you can disable 2FA and set it up again with your new device. Lost both device and recovery codes? Contact support . You'll need to verify your identity before we can help recover your account. This process may take several business days. Back to Docs Need help? --- ## Documentation › REST API ### Authentication URL: https://edge.network/docs/api/authentication/ Markdown: https://edge.network/docs/api/authentication.md JSON: https://edge.network/json/docs/api/authentication.json _Authenticate with the Edge REST API using API keys._ Authentication Every request to the REST API is authenticated with an API key passed as a Bearer token. Creating an API Key Go to Account → API Keys in the console Click Create API Key Give it a descriptive name (e.g. "Deploy pipeline — production") Copy the key immediately — it is shown only once and stored hashed Keys start with ek_live_ and can be created with an optional expiry (30 days, 90 days, 1 year, or never). Keys can be revoked at any time; revocation takes effect immediately. Keys are account-wide An API key carries full access to the account that created it — treat it like a password. Never commit keys to version control, and prefer one key per integration so individual keys can be revoked without breaking everything else. Making Authenticated Requests Pass the key in the Authorization header: curl https://edge.network/api/compute/vms \ -H "Authorization: Bearer ek_live_abc123def456..." A missing, malformed, revoked, or expired key returns 401 : HTTP/1.1 401 Unauthorized { "error": "Invalid or expired API key", "code": "AUTHENTICATION_ERROR" } Managing Keys via the API API keys can themselves be managed programmatically (using an existing key or console session): Endpoint Description GET /api/account/keys List keys — returns name, prefix, last-used, and expiry (never the secret) POST /api/account/keys Create — { name, expiresIn? } where expiresIn is e.g. 30d , 90d , 1y , or never . The full secret is returned once. PATCH /api/account/keys/:keyId Rename a key DELETE /api/account/keys/:keyId Revoke a key immediately Need Narrower Access? API keys are all-or-nothing. If you're granting access to an AI agent or third-party tool and want per-product permissions and spending caps, use an Agent Access Code ( ea_live_... ) with the Agent API instead. Credential Prefix Scope Used with API key ek_live_ Full account access REST API ( /api/* ), CLI Agent access code ea_live_ Per-product permissions, budget caps Agent API ( /agent/* ) Back to Docs Need help? --- ### CDN API URL: https://edge.network/docs/api/cdn/ Markdown: https://edge.network/docs/api/cdn.md JSON: https://edge.network/json/docs/api/cdn.json _Manage CDN deployments, domains, SSL, and cache purging over the Edge REST API._ CDN API Manage CDN deployments, domains, SSL, caching, and analytics under /api/cdn . All endpoints require authentication . Quick Start A deployment is a container for one or more domains, each with its own origin and cache settings: # Create a deployment curl -X POST https://edge.network/api/cdn/deployments \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "my-site" }' # Add a domain with an origin curl -X POST https://edge.network/api/cdn/deployments/DEPLOYMENT_ID/domains \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "domain": "cdn.example.com", "originType": "url", "origin": "https://origin.example.com", "cacheTtlSeconds": 3600 }' Deployments Endpoint Description GET /api/cdn/deployments List deployments POST /api/cdn/deployments Create — body { "name": "..." } , returns 201 GET /api/cdn/deployments/:id Get one deployment with its domains DELETE /api/cdn/deployments/:id Delete a deployment GET | POST /api/cdn/deployments/:id/pause Get / toggle cache pause — body { "paused": true } GET /api/cdn/usage Account-wide requests, bytes served, and cache hit rate GET /api/cdn/edge-nodes Status of the edge node network Domains & SSL Endpoint Description POST /api/cdn/deployments/:id/domains Add a domain — { domain, originType?, origin?, storageBucket?, cacheTtlSeconds?, jitImageEnabled? } PATCH /api/cdn/deployments/:id/domains/:domainId Update origin, TTL, image optimization, root-path behaviour, and custom config DELETE /api/cdn/deployments/:id/domains/:domainId Remove a domain POST .../domains/:domainId/check-dns Verify the CNAME is pointing at Edge POST .../domains/:domainId/retry-ssl Re-attempt SSL certificate issuance POST | DELETE .../domains/:domainId/watermark Upload (raw PNG/WebP body) or remove a watermark image PUT .../domains/:domainId/protection Enable or disable password protection (HTTP Basic Auth) — body: enabled , username , password GET .../domains/:domainId/stats Per-domain traffic stats originType is url (default, requires origin ) or storage (requires storageBucket — serve directly from Edge Storage ). Cache Purging curl -X POST https://edge.network/api/cdn/deployments/DEPLOYMENT_ID/purge \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "type": "prefix", "path": "/images/" }' Purge type Required field Effect single url Purge one exact URL prefix path Purge everything under a path prefix regex pattern Purge URLs matching a regular expression everything — Purge the whole deployment Purge history is available at GET /api/cdn/deployments/:id/purge-history . Analytics Endpoint Description GET /api/cdn/deployments/:id/stats Live stats snapshot GET .../stats/history?range=24h History — range is 1h , 24h , 7d , 30d , or 1y GET .../region-stats?range=24h Traffic by region across the edge network GET .../top-content?limit=100 Most-requested paths GET .../cache-stats Cached object count and size GET .../events?limit=50 Deployment activity log Back to Docs Need help? --- ### Compute API URL: https://edge.network/docs/api/compute/ Markdown: https://edge.network/docs/api/compute.md JSON: https://edge.network/json/docs/api/compute.json _Create and manage VMs, SSH keys, security groups, backups, and startup scripts over the Edge REST API._ Compute API Manage virtual machines and everything around them — SSH keys, security groups, snapshots, backups, private networks, and startup scripts — under /api/compute . All endpoints require authentication . Create a VM curl -X POST https://edge.network/api/compute/vms \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "web-01", "region": "london", "osTemplate": "ubuntu-24.04", "vcpu": 2, "ram": 4, "disk": 80, "sshKeyIds": ["key_abc123"], "setupScript": "#!/bin/bash\napt update" }' Field Required Description name Yes 1–64 characters, letters, digits, and hyphens region Yes Region id from GET /api/compute/regions osTemplate Yes Template id from GET /api/compute/os-templates vcpu / ram / disk Yes vCPUs (1–128), RAM in GB (1–512), disk in GB (10–10000) sshKeyIds No SSH key ids to attach at first boot securityGroupIds No Security group ids to attach password No Root password (min 8 chars). Omit to have one generated and returned once. setupScript No Bash script to run on first boot. See Startup Scripts for the library. Returns 201 : { "vm": { "id": "vm_xyz789", "name": "web-01", "status": "provisioning", "region": "london", "vcpu": 2, "ram": 4, "disk": 80, "os": { "name": "Ubuntu 24.04" }, "network": { "publicIp": "pending" }, "createdAt": "2026-07-31T15:04:05Z" }, "generatedPassword": "..." } VMs Endpoint Description GET /api/compute/vms List VMs — returns { vms } GET /api/compute/vms/:id Get a VM — returns { vm } PATCH /api/compute/vms/:id Rename — body { "name": "..." } DELETE /api/compute/vms/:id Destroy the VM POST /api/compute/vms/:id/start | stop | restart | reset Power actions — each returns the updated { vm } POST /api/compute/vms/:id/suspend | resume Suspend / resume POST /api/compute/vms/:id/resize Change specs — body { vcpu?, ram?, disk? } POST /api/compute/vms/:id/reinstall Reinstall the OS — body { osId } POST /api/compute/vms/:id/password Change the root password POST /api/compute/vms/:id/hostname Change the hostname Stats, Metrics & Console Endpoint Description GET /api/compute/vms/:id/stats Live CPU / RAM / disk / network usage GET /api/compute/vms/:id/metrics?period=24h Metric history — period is 1h , 6h , 24h , or 7d POST /api/compute/vms/:id/console Create a VNC console session (returns session token + password) GET /api/compute/vms/:id/events Recent lifecycle events for one VM GET /api/compute/vms/:id/bandwidth?month=2026-07 Monthly bandwidth usage SSH Keys & Security Groups Endpoint Description GET | POST /api/compute/ssh-keys List keys / add a key — body { name, publicKey } DELETE /api/compute/ssh-keys/:id Remove a key GET | POST | DELETE /api/compute/vms/:id/ssh-keys/:keyId List / attach / detach keys on a VM GET | POST /api/compute/security-groups List / create groups — body { name, description?, rules? } GET | PATCH | DELETE /api/compute/security-groups/:id Get / update / delete a group GET | POST /api/compute/security-groups/:id/rules List / add rules — { direction, protocol, portRange?, source, description? } PATCH | DELETE /api/compute/security-groups/:sgId/rules/:ruleId Update / remove a rule GET | POST | DELETE /api/compute/vms/:id/security-groups/:sgId List / attach / detach groups on a VM Snapshots & Backups Endpoint Description GET | POST /api/compute/vms/:id/snapshots List / create snapshots — body { name } POST /api/compute/vms/:id/snapshots/:snapshotId/restore Restore a snapshot DELETE /api/compute/vms/:id/snapshots/:snapshotId Delete a snapshot GET | POST /api/compute/vms/:id/backups List / create full backups POST /api/compute/vms/:id/backups/:backupId/restore Restore a backup DELETE /api/compute/vms/:id/backups/:backupId Delete a backup GET | POST | DELETE /api/compute/vms/:id/backup-schedule Get / set / clear the schedule — { frequency, time, retention } IPs & Private Networks Endpoint Description GET | POST /api/compute/vms/:id/ips List / add extra public IPs DELETE /api/compute/vms/:id/ips/:ipId Remove an extra IP GET | POST /api/compute/networks List / create private networks — body { name, region } DELETE /api/compute/networks/:id Delete a private network GET | POST /api/compute/vms/:id/networks List / attach networks — body { networkId } DELETE /api/compute/vms/:id/networks/:networkId Detach a network Startup Scripts Endpoint Description GET /api/compute/scripts Edge library scripts plus your custom scripts GET /api/compute/scripts/library Edge library scripts only GET /api/compute/scripts/:id Get one script with its content and parameters POST /api/compute/scripts Create a custom script — { name, scriptContent, description?, category?, parameters? } PUT | DELETE /api/compute/scripts/:id Update / delete a custom script (library scripts are read-only) GET /api/compute/vms/:id/scripts Script execution history for a VM To run a script at VM creation, substitute its parameters into the content and pass the result as setupScript . The CLI and Agent API do this for you. Discovery & Account Endpoint Description GET /api/compute/regions Available deployment regions GET /api/compute/os-templates Available operating systems GET /api/compute/pricing Pay-as-you-go rates and prepaid balance GET /api/compute/usage Current resource usage against account limits GET /api/compute/events Recent compute events across the account Back to Docs Need help? --- ### DNS API URL: https://edge.network/docs/api/dns/ Markdown: https://edge.network/docs/api/dns.md JSON: https://edge.network/json/docs/api/dns.json _Manage DNS zones and records over the Edge REST API._ DNS API Manage zones, records, backups, and development domains under /api/dns . All endpoints require authentication . Quick Start # Create a zone curl -X POST https://edge.network/api/dns/zones \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "domain": "example.com" }' # Add an A record curl -X POST https://edge.network/api/dns/zones/ZONE_ID/records \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "type": "A", "name": "www", "data": "203.0.113.10", "ttl": 3600 }' After creating a zone, point your domain at the Edge nameservers and call POST /api/dns/zones/:id/verify to confirm delegation. Zones Endpoint Description GET /api/dns/zones List zones POST /api/dns/zones Create — body { "domain": "example.com" } , returns 201 GET /api/dns/zones/:id Get a zone DELETE /api/dns/zones/:id Delete a zone and its records POST /api/dns/zones/:id/verify Check nameserver delegation — returns { verified, currentNs } GET /api/dns/zones/:id/metrics?range=24h Query metrics — range is 1h , 24h , 7d , or 30d GET /api/dns/zones/:id/events Zone activity log GET | POST /api/dns/zones/:id/examine Fetch / run the DNS Examiner AI analysis GET /api/dns/usage Zone count and per-zone query usage against limits Records Endpoint Description GET /api/dns/zones/:id/records List records in a zone POST /api/dns/zones/:id/records Add — { type, name, data, ttl?, priority?, geo? } ( priority required for MX) PUT /api/dns/zones/:id/records/:recordId Update any of the same fields DELETE /api/dns/zones/:id/records/:recordId Delete a record Supported types: A , AAAA , CNAME , MX , TXT , NS , ALIAS , CAA , PTR , SRV . The geo field enables geographic routing . Zone Backups Endpoint Description GET | POST /api/dns/zones/:id/backups List backups / take a manual backup GET /api/dns/zones/:id/backups/:backupId Download a backup POST /api/dns/zones/:id/backups/:backupId/restore Restore — takes a safety backup first unless createPreBackup: false DELETE /api/dns/zones/:id/backups/:backupId Delete a backup POST /api/dns/zones/:id/backups/enable | disable Turn automatic zone backups on or off Development Domains test.network and ed.ge subdomains can be purchased and managed through the API: Endpoint Description GET /api/dns/test-domains | edge-domains List your domains GET .../check/:subdomain Check availability POST /api/dns/test-domains | edge-domains Purchase — body { "subdomain": "myapp" } (card on file required) DELETE .../:id Release a domain Back to Docs Need help? --- ### Errors URL: https://edge.network/docs/api/errors/ Markdown: https://edge.network/docs/api/errors.md JSON: https://edge.network/json/docs/api/errors.json _Error format, status codes, and rate-limit behaviour for the Edge REST API._ Errors The API uses conventional HTTP status codes and returns a consistent JSON body for every error, with a human-readable message and a stable machine-readable code. Error Format HTTP/1.1 404 Not Found Content-Type: application/json { "error": "VM not found", "code": "NOT_FOUND" } Requests rejected by schema validation additionally include a details array describing each failed field: HTTP/1.1 400 Bad Request Content-Type: application/json { "error": "Validation error", "code": "VALIDATION_ERROR", "details": [ { "path": ["name"], "message": "Required" } ] } Error Codes HTTP Status Code Meaning 400 VALIDATION_ERROR The request body or parameters are invalid. Check details if present. 401 AUTHENTICATION_ERROR Missing, invalid, expired, or revoked API key. 403 AUTHORIZATION_ERROR Authenticated, but not permitted to perform this action. 404 NOT_FOUND The resource doesn't exist or belongs to a different account. 409 CONFLICT The request conflicts with current state (e.g. duplicate name). 429 RATE_LIMIT Too many requests. Back off and retry after Retry-After seconds. 500 INTERNAL_ERROR Something went wrong on our side. Safe to retry with backoff. Individual endpoints may return more specific codes (e.g. SCRIPT_NOT_FOUND ) — always branch on the HTTP status first and treat code as a refinement. Rate Limits The API allows 600 requests per minute per IP , measured over a sliding window. Every response carries the IETF standard rate-limit headers ( draft-ietf-httpapi-ratelimit-headers ) so clients can self-throttle in real time. The legacy X-RateLimit-* pair is also sent for older clients. Header Meaning RateLimit-Limit Maximum requests allowed in the window RateLimit-Remaining Requests remaining in the current window RateLimit-Reset Seconds until the quota resets RateLimit-Policy The quota policy: 600;w=60 means 600 requests per 60-second window Retry-After Seconds to wait before retrying (on 429 responses only) X-RateLimit-Limit / -Remaining Legacy pair, kept for older clients — prefer the RateLimit-* headers HTTP/1.1 429 Too Many Requests Retry-After: 12 RateLimit-Limit: 600 RateLimit-Remaining: 0 RateLimit-Reset: 12 RateLimit-Policy: 600;w=60 X-RateLimit-Limit: 600 X-RateLimit-Remaining: 0 { "error": "Too many requests. Try again in 12s.", "code": "RATE_LIMIT" } Back to Docs Need help? --- ### REST API URL: https://edge.network/docs/api/ Markdown: https://edge.network/docs/api.md JSON: https://edge.network/json/docs/api.json _Manage every Edge resource over HTTPS. The same API that powers the Edge console and CLI, authenticated with API keys._ REST API Everything you can do in the Edge console, you can do over HTTPS. The REST API is the same API that powers the console and the Edge CLI — there is no separate, cut-down surface for programmatic access. Base URL https://edge.network/api All requests use HTTPS. Request and response bodies are JSON — send Content-Type: application/json on POST , PUT , and PATCH requests. Authentication Authenticate with an API key passed as a Bearer token. Keys are created in the console and start with ek_live_ . curl https://edge.network/api/compute/vms \ -H "Authorization: Bearer ek_live_..." See Authentication for creating and managing keys. Quick Start: Create a VM curl -X POST https://edge.network/api/compute/vms \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "web-01", "osTemplate": "ubuntu-24.04", "vcpu": 2, "ram": 4, "disk": 80, "region": "london" }' The response includes the new VM object and, if no SSH key was attached, a generated root password. Full request and response details are on the Compute API page. API Reference Product Base Path Covers Compute /api/compute VMs, SSH keys, firewall, startup scripts, backups CDN /api/cdn Deployments, domains, cache purging, analytics DNS /api/dns Zones, records, nameservers Storage /api/storage Buckets, S3 access keys, objects, presigned URLs Shield /api/shield Widget management and stats Errors Errors return an appropriate HTTP status code and a JSON body with a message and a stable machine-readable code: { "error": "VM not found", "code": "NOT_FOUND" } See Errors for the full list of codes and rate-limit behaviour. Rate Limits Requests are rate limited to 600 requests per minute per IP across the API. Every response includes X-RateLimit-Limit and X-RateLimit-Remaining headers; exceeding the limit returns 429 with a Retry-After header. Other Ways to Integrate Edge CLI A command-line client for this API. Ideal for scripts and CI pipelines. Agent API A self-describing API for AI agents, with scoped tokens, budgets, and dry-run support. Back to Docs Need help? --- ### Shield API URL: https://edge.network/docs/api/shield/ Markdown: https://edge.network/docs/api/shield.md JSON: https://edge.network/json/docs/api/shield.json _Manage Edge Shield widgets and view stats over the Edge REST API._ Shield API Manage Edge Shield widgets and view protection stats under /api/shield . Note that token verification itself doesn't happen here — send verification requests to shield.edge.network as described in Server-Side Validation . Create a Widget curl -X POST https://edge.network/api/shield/widgets \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "Marketing site", "hostnames": ["example.com", "www.example.com"], "mode": "managed", "agentPolicy": "challenge" }' # Response (201) — the secret is shown only once { "widget": { "id": "wgt_abc123", "name": "Marketing site", "sitekey": "sk_...", "secretPrefix": "ss_...", "hostnames": ["example.com", "www.example.com"], "mode": "managed", "agentPolicy": "challenge", "shadow": false, "tarpit": false }, "secret": "ss_live_...", "message": "Save the secret now — it will not be shown again." } Field Required Description name Yes Display name for the widget hostnames No Hostnames the sitekey may be used on mode No Widget mode — see Widget Modes agentPolicy No allow , challenge , or block — how verified agents are treated shadow No Shadow mode — score traffic without enforcing tarpit No Slow down suspected bots instead of failing fast Widget Management Endpoint Description GET /api/shield/widgets List widgets POST /api/shield/widgets Create — returns the widget and its secret (once) PATCH /api/shield/widgets/:widgetId Update any subset of name , hostnames , mode , agentPolicy , shadow , tarpit DELETE /api/shield/widgets/:widgetId Revoke a widget — its sitekey and secret stop working GET /api/shield/widgets/:widgetId/stats?hours=24 Hourly challenge/verify stats plus anomaly detection (up to 720 hours) GET | POST /api/shield/widgets/:widgetId/examine Fetch / run the Shield Examiner AI analysis Verifying Tokens Widget creation gives you a sitekey (public, rendered in the browser widget) and a secret (server-side). Verify tokens by POSTing to the Shield service directly — https://shield.edge.network/siteverify — or verify offline with our published JWKS keys. See Server-Side Validation and Offline Verification . Back to Docs Need help? --- ### Storage API URL: https://edge.network/docs/api/storage/ Markdown: https://edge.network/docs/api/storage.md JSON: https://edge.network/json/docs/api/storage.json _Manage buckets, S3 access keys, and objects over the Edge REST API._ Storage API Manage buckets, S3 access keys, and objects under /api/storage . For high-volume object traffic, use the S3-compatible endpoint at storage.edge.network with any S3 SDK — see SDK Examples . Quick Start # Create a bucket curl -X POST https://edge.network/api/storage/buckets \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "my-assets" }' # Create S3 credentials curl -X POST https://edge.network/api/storage/keys \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "name": "app-uploads" }' Buckets Endpoint Description GET | POST /api/storage/buckets List / create buckets — body { name, notes? } GET | PATCH | DELETE /api/storage/buckets/:name Get / update notes / delete (bucket must be empty) PATCH /api/storage/buckets/:name/public Toggle public access — body { "is_public": true } GET | POST /api/storage/buckets/:name/lifecycle List / add expiry rules — { prefix?, expire_days } DELETE .../lifecycle/:ruleId Remove a lifecycle rule GET /api/storage/usage Total bytes, object counts, and per-bucket breakdown S3 Access Keys Endpoint Description GET | POST /api/storage/keys List / create S3 credentials — { name?, permissions?, bucketScope? } DELETE /api/storage/keys/:id Delete credentials GET /api/storage/endpoint S3 connection details — { endpoint, port, region } These are separate from your account API keys — they authenticate S3 SDKs against storage.edge.network . See Access Keys . Objects Endpoint Description GET /api/storage/buckets/:name/objects?prefix=&marker= List objects, optionally under a prefix POST /api/storage/buckets/:name/upload Upload — multipart or raw body GET /api/storage/buckets/:name/download/* Download an object (also accepts presigned ?token= ) DELETE /api/storage/buckets/:name/objects/* Delete an object POST /api/storage/buckets/:name/copy Copy within a bucket — { source_key, dest_key } POST /api/storage/buckets/:name/folders Create a folder — { path } POST /api/storage/buckets/:name/download-zip Download up to 100 objects as a ZIP — { keys: [...] } Presigned URLs Generate time-limited upload or download URLs to hand to browsers and untrusted clients: curl -X POST https://edge.network/api/storage/buckets/my-assets/presign \ -H "Authorization: Bearer ek_live_..." \ -H "Content-Type: application/json" \ -d '{ "key": "uploads/photo.jpg", "action": "upload", "expires": "1h" }' # Response { "url": "https://storage.edge.network/...", "method": "PUT", "expires": "1h" } expires accepts values like 30m , 1h , 7d (default 1h, max 7d). See Presigned URLs . Activity & Metrics Endpoint Description GET /api/storage/buckets/:name/events?limit=50 Bucket activity log GET /api/storage/buckets/:name/metrics?hours=168 Hourly request and bandwidth metrics GET .../metrics/summary?hours=24 Aggregated metrics for a window GET .../metrics/top-objects?limit=10 Most-accessed objects GET .../metrics/file-types Storage broken down by file type Back to Docs Need help? --- ### Versioning & Deprecation URL: https://edge.network/docs/api/versioning/ Markdown: https://edge.network/docs/api/versioning.md JSON: https://edge.network/json/docs/api/versioning.json _Edge Network API versioning strategy and deprecation policy — how we signal changes so integrations never break without warning._ Versioning & Deprecation The Edge Network API is versioned so agents and integrations can rely on a stable surface. This page is the policy: what we consider a breaking change, how we signal one, and how much notice you get. Current Version The current major version is 1 . Every API response — REST API ( /api/* ), Agent API ( /agent/* ), and MCP endpoint ( /mcp ) — carries an X-API-Version header: HTTP/1.1 200 OK Content-Type: application/json X-API-Version: 1 What Changes Without a Version Bump Additive changes ship continuously and are always backwards-compatible. Your integration must tolerate: New endpoints and new HTTP methods on existing paths New optional request fields and query parameters New fields in response bodies (parse what you need, ignore the rest) New values in open-ended enums (e.g. new regions, OS templates, or resource states) New response headers The published OpenAPI specification is regenerated with every release and its info.version follows semver: minor bumps are additive, major bumps are breaking. What Counts as Breaking Removing or renaming an endpoint, request field, or response field Making an optional field required, or changing a field's type Changing the meaning of an existing value or error code Tightening validation in a way that rejects previously valid requests Deprecation Process Breaking changes ship under a new URL prefix (e.g. /agent/v2/ ) and the old surface keeps working during a migration window of at least 6 months . During that window, responses from the deprecated surface carry: HTTP/1.1 200 OK Content-Type: application/json X-API-Version: 1 Deprecation: true Sunset: Sat, 27 Feb 2027 00:00:00 GMT Link: <https://edge.network/docs/api/versioning>; rel="deprecation" Header Meaning Deprecation This surface is deprecated — plan your migration Sunset The date the surface stops working ( RFC 8594 ) — always ≥ 6 months out Link rel="deprecation" Migration guide for the specific change Deprecations are also announced in the changelog and by email to affected accounts. Nothing is ever removed silently. Guidance for Agents Read X-API-Version once per session; alert your operator if it changes unexpectedly. Treat a Deprecation or Sunset header as a signal to surface a migration task, not an error. Re-fetch /openapi.json to discover new capabilities — additive changes appear there first. Back to Docs Need help? --- ## Documentation › Tooling & CLI ### CLI Authentication URL: https://edge.network/docs/cli/authentication/ Markdown: https://edge.network/docs/cli/authentication.md JSON: https://edge.network/json/docs/cli/authentication.json _Authenticate the Edge CLI with an API key: generate a key in the console, log in with edge auth login, use the EDGE_API_KEY variable, and set up CI/CD._ CLI Authentication Authenticate the CLI with your Edge account using API keys. 1 Generate an API Key Create an API key in your Edge account: Go to Account → API Keys Click Create API Key Give it a name (e.g., "CLI - MacBook") Copy the key immediately — it won't be shown again Important API keys have the same permissions as your user account. Keep them secure and never commit them to version control. The same key also authenticates direct HTTPS calls — see the REST API documentation . 2 Log In Interactive Login Run the login command and paste your API key when prompted: $ edge auth login ? Enter your API key: ek_live_•••••••••••••••••••••••• ✓ Authenticated successfully Account: Acme Corp User: john@example.com Non-Interactive Login Pass the key directly (useful for scripts): edge auth login --key ek_live_abc123def456... Check Authentication Status $ edge auth status ✓ Authenticated Account: Acme Corp User: john@example.com Key: ek_live_abc1**** Expires: Never Log Out Remove stored credentials: $ edge auth logout ✓ Credentials removed Environment Variable You can also authenticate using the EDGE_API_KEY environment variable: # Set for current session export EDGE_API_KEY=ek_live_abc123def456... # Or add to your shell profile (~/.bashrc, ~/.zshrc) echo 'export EDGE_API_KEY=ek_live_abc123...' >> ~/.zshrc The environment variable takes precedence over the stored config file. Config File Location Credentials are stored in: ~/.edge/config.json macOS / Linux %USERPROFILE%\.edge\config.json Windows Example config: { "api_key": "ek_live_abc123def456...", "default_region": "london", "output": "table" } CI/CD Integration Use environment variables in your CI/CD pipelines: # GitHub Actions example jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install Edge CLI run: curl -fsSL https://edge.network/install.sh | sh - name: Deploy env: EDGE_API_KEY: ${{ secrets.EDGE_API_KEY }} run: | edge cdn purge my-deployment edge storage sync ./dist my-bucket/app/ Tip Create a dedicated API key for CI/CD with a descriptive name like "GitHub Actions - Production". Authentication Priority The CLI checks for credentials in this order: Command-line flag: --api-key Environment variable: EDGE_API_KEY Config file: ~/.edge/config.json Activity Tracking All actions performed via the CLI are logged in your account activity log with full attribution: Source badge: CLI actions are tagged with a CLI badge to distinguish them from web or API actions User attribution: For accounts with team members, the activity log shows which user performed each action Full audit trail: All create, update, and delete operations are logged with timestamps This helps teams track automated deployments, distinguish CI/CD activity from manual changes, and maintain compliance records. Next Steps Compute Commands Manage virtual machines Configuration Customize CLI settings Back to Docs Need help? --- ### CLI CDN Commands URL: https://edge.network/docs/cli/cdn/ Markdown: https://edge.network/docs/cli/cdn.md JSON: https://edge.network/json/docs/cli/cdn.json _Edge CLI CDN command reference: create deployments, add custom domains with URL or storage origins, purge cached paths, and view traffic and cache metrics._ CLI CDN Commands Create deployments, manage domains, and purge cache from your terminal. Deployments List Deployments $ edge cdn list ID NAME DOMAINS STATUS CREATED cdn-abc123 production 3 active 2025-01-15 cdn-def456 staging 1 active 2025-02-01 cdn-ghi789 legacy 2 active 2024-12-10 Create a Deployment $ edge cdn create --name my-cdn Creating CDN deployment... done ID: cdn-jkl012 Name: my-cdn Status: active Add a domain to start using your CDN: edge cdn domains add cdn-jkl012 --domain cdn.example.com --origin https://origin.example.com Get Deployment Details $ edge cdn get cdn-abc123 ID: cdn-abc123 Name: production Status: active Created: 2025-01-15 10:30:00 UTC Domains: cdn.example.com → https://origin.example.com SSL: active assets.example.com → storage://my-bucket SSL: active static.example.com → https://s3.amazonaws.com/... SSL: active Statistics (24h): Requests: 1,245,678 Bandwidth: 45.2 GB Cache Hit: 94.5% Delete a Deployment # Delete with confirmation edge cdn delete cdn-abc123 # Delete without confirmation edge cdn delete cdn-abc123 --yes Domains List Domains $ edge cdn domains list cdn-abc123 DOMAIN ORIGIN SSL CACHE TTL cdn.example.com https://origin.example.com active 86400s assets.example.com storage://my-assets active 604800s static.example.com https://s3.amazonaws.com/... active 2592000s Add a Domain # Add domain with external origin edge cdn domains add cdn-abc123 \ --domain cdn.example.com \ --origin https://origin.example.com \ --cache-ttl 86400 # Add domain with Storage bucket as origin edge cdn domains add cdn-abc123 \ --domain assets.example.com \ --origin-type storage \ --storage-bucket my-assets # Enable JIT image optimization edge cdn domains add cdn-abc123 \ --domain images.example.com \ --origin https://origin.example.com \ --jit-image Update a Domain # Update origin edge cdn domains update cdn-abc123 dom-xyz789 \ --origin https://new-origin.example.com # Update cache TTL edge cdn domains update cdn-abc123 dom-xyz789 \ --cache-ttl 3600 Remove a Domain edge cdn domains remove cdn-abc123 dom-xyz789 Cache Purging Purge All $ edge cdn purge cdn-abc123 Purging all cached content... done Cache cleared for all domains in cdn-abc123 Selective Purge # Purge specific path edge cdn purge cdn-abc123 --path /images/* # Purge specific URL edge cdn purge cdn-abc123 --url https://cdn.example.com/asset.js # Purge multiple paths edge cdn purge cdn-abc123 --path /css/* --path /js/* Metrics $ edge cdn metrics cdn-abc123 Period: Last 24 hours Total Requests: 1,245,678 Bandwidth: 45.2 GB Cache Hit Rate: 94.5% Cache Misses: 68,412 By Domain: cdn.example.com 892,345 requests 32.1 GB assets.example.com 312,456 requests 10.8 GB static.example.com 40,877 requests 2.3 GB # Specify time period edge cdn metrics cdn-abc123 --period 7d # Filter by domain edge cdn metrics cdn-abc123 --domain cdn.example.com # Export as CSV edge cdn metrics cdn-abc123 --export csv > cdn-metrics.csv Common Flags Flag Description --name, -n Deployment name --domain Domain hostname --origin Origin URL --origin-type Origin type: url or storage --storage-bucket Storage bucket name (when origin-type is storage) --cache-ttl Cache TTL in seconds --jit-image Enable JIT image optimization --path Path pattern to purge --url Specific URL to purge --yes, -y Skip confirmation prompts See Also DNS Commands Manage zones and records CDN Docs Full CDN documentation Back to Docs Need help? --- ### CLI Compute Commands URL: https://edge.network/docs/cli/compute/ Markdown: https://edge.network/docs/cli/compute.md JSON: https://edge.network/json/docs/cli/compute.json _Edge CLI compute command reference: create, resize, and SSH into virtual machines, run startup scripts, and manage SSH keys, security groups, and metrics._ CLI Compute Commands Create and manage virtual machines, SSH keys, and security groups. Virtual Machines List VMs $ edge compute list ID NAME STATUS IP SIZE REGION vm-abc123 web-1 running 192.0.2.10 s-2vcpu-4gb london vm-def456 api-server running 192.0.2.11 s-4vcpu-8gb london vm-ghi789 database stopped 192.0.2.12 s-8vcpu-16gb london Create a VM $ edge compute create \ --name web-2 \ --size s-2vcpu-4gb \ --image ubuntu-24 \ --region london \ --ssh-key my-laptop Creating VM... done ID: vm-jkl012 Name: web-2 Status: creating IP: Assigning... Size: s-2vcpu-4gb Region: london Or use interactive mode: $ edge compute create ? VM name: my-webserver ? Size: s-2vcpu-4gb (2 vCPU, 4 GB RAM) ? Image: ubuntu-24 ? Region: london ? SSH key: my-laptop Creating VM... done Get VM Details $ edge compute get vm-abc123 ID: vm-abc123 Name: web-1 Status: running IP: 192.0.2.10 IPv6: 2001:db8::1 Size: s-2vcpu-4gb vCPUs: 2 Memory: 4 GB Disk: 50 GB Image: ubuntu-24.04-x64 Region: london Created: 2025-02-10 14:30:00 UTC SSH Keys: my-laptop, deploy-key VM Actions # Start a stopped VM edge compute start vm-abc123 # Stop a running VM edge compute stop vm-abc123 # Restart a VM edge compute restart vm-abc123 # Delete a VM (with confirmation) edge compute delete vm-abc123 # Delete without confirmation edge compute delete vm-abc123 --yes Resize a VM $ edge compute resize vm-abc123 --size s-4vcpu-8gb Resizing VM... done Note: VM will be restarted to apply new size. SSH Access # SSH into a VM by ID edge compute ssh vm-abc123 # SSH with a specific user edge compute ssh vm-abc123 --user root # Open web console in browser edge compute console vm-abc123 Metrics $ edge compute metrics vm-abc123 Period: Last 24 hours CPU Usage: 12.5% avg, 45.2% peak Memory Usage: 1.2 GB / 4 GB (30%) Disk Read: 150 MB Disk Write: 45 MB Network In: 2.3 GB Network Out: 890 MB # Specify time period edge compute metrics vm-abc123 --period 7d # Export as CSV edge compute metrics vm-abc123 --period 30d --export csv > metrics.csv # Show specific metric edge compute metrics vm-abc123 --metric cpu Startup Scripts Startup scripts run on a VM after its first boot. The Edge library ships ready-made scripts (Docker, Node.js, WordPress, and more), and you can create your own. See the Startup Scripts documentation for details. List Scripts $ edge compute scripts list ID NAME CATEGORY SOURCE PARAMS docker Docker app edge library - nodejs Node.js web edge library node_version wordpress WordPress app edge library site_title, admin_email, db_password a1b2c3d4 My Setup custom custom - View a Script # Show a script's details and content edge compute scripts get docker # Print only the content (for piping to a file) edge compute scripts get docker --content > docker.sh Create a Custom Script # Create a custom script from a file edge compute scripts create --name "My Setup" --file setup.sh \ --description "Installs our standard tooling" # Or pipe from stdin cat setup.sh | edge compute scripts create --name "My Setup" --file - Update & Delete # Update a custom script edge compute scripts update a1b2c3d4 --file setup-v2.sh edge compute scripts update a1b2c3d4 --name "My Setup v2" # Delete a custom script (library scripts can't be modified or deleted) edge compute scripts delete a1b2c3d4 Run a Script on a New VM # Run a script on first boot when creating a VM edge compute create \ --name web-2 \ --size s-2vcpu-4gb \ --image ubuntu-24 \ --region london \ --script docker # Library scripts with parameters edge compute create \ --name blog \ --size s-2vcpu-4gb \ --image ubuntu-24 \ --region london \ --script wordpress \ --script-param site_title="My Blog" \ --script-param admin_email=me@example.com SSH Keys List Keys $ edge compute keys list ID NAME FINGERPRINT CREATED key-abc my-laptop SHA256:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczC... 2025-01-15 key-def deploy-key SHA256:vM9Jxk8sxCHd0ccjU4e9BmjRXYVpLaJEUNe1... 2025-02-01 key-ghi backup-server SHA256:wK0Kyl9tyCIe1ddkV5f0CnkSYWWqMbKFVO... 2025-02-10 Create a Key # Create from file edge compute keys create --name work-laptop --public-key-file ~/.ssh/id_rsa.pub # Create with inline key edge compute keys create --name ci-server --public-key "ssh-rsa AAAA..." Delete a Key edge compute keys delete key-abc Security Groups List Groups $ edge compute groups list ID NAME RULES VMs grp-abc123 webserver 3 2 grp-def456 database 1 1 grp-ghi789 default 0 5 Get Group Details $ edge compute groups get grp-abc123 ID: grp-abc123 Name: webserver VMs: web-1, web-2 Rules: 1. Allow TCP 22 from 0.0.0.0/0 (SSH) 2. Allow TCP 80 from 0.0.0.0/0 (HTTP) 3. Allow TCP 443 from 0.0.0.0/0 (HTTPS) Manage Groups # Create a security group edge compute groups create --name api-servers # Add rules edge compute groups add-rule grp-abc123 --port 443 --protocol tcp --source 0.0.0.0/0 edge compute groups add-rule grp-abc123 --port 22 --protocol tcp --source 10.0.0.0/8 # Remove a rule edge compute groups remove-rule grp-abc123 rule-xyz # Delete a group edge compute groups delete grp-abc123 Common Flags Flag Description --name, -n Name for the resource --size, -s VM size (e.g., s-2vcpu-4gb) --image, -i OS image (e.g., ubuntu-24, debian-12) --region, -r Datacenter region --disk Disk size in GB (default: 50) --ssh-key SSH key name or ID to attach --security-group Security group name or ID --script Startup script ID to run after first boot --script-param Startup script parameter as name=value (repeatable) --yes, -y Skip confirmation prompts See Also CDN Commands Manage deployments and domains Compute Docs Full Compute documentation Back to Docs Need help? --- ### CLI Configuration URL: https://edge.network/docs/cli/configuration/ Markdown: https://edge.network/docs/cli/configuration.md JSON: https://edge.network/json/docs/cli/configuration.json _Configure the Edge CLI with edge config: default region, output formats (table, JSON, quiet), global flags, environment variables, and scripting examples._ CLI Configuration Customize CLI behavior with persistent settings and flags. Configuration Commands List All Settings $ edge config list api_url https://api.edge.network output table default_region london no_color false Get a Setting $ edge config get output table $ edge config get default_region london Set a Value # Set default output format edge config set output json # Set default region edge config set default_region london # Disable colored output edge config set no_color true Unset a Value # Remove a setting (use default) edge config unset default_region Available Settings Setting Description Default api_url API endpoint URL https://api.edge.network output Default output format (table, json, yaml) table default_region Default region for new resources - no_color Disable colored output false Config File Settings are stored in a JSON file: ~/.edge/config.json macOS / Linux %USERPROFILE%\.edge\config.json Windows { "api_key": "ek_live_abc123...", "api_url": "https://api.edge.network", "output": "table", "default_region": "london", "no_color": false } Global Flags Override settings for individual commands: # Override output format for single command edge compute list --output json # Override output format shorthand edge compute list -o json # Quiet mode (IDs only) edge compute list --quiet edge compute list -q # Verbose mode (debug info) edge compute list --verbose edge compute list -v # Skip confirmation prompts edge compute delete vm-abc123 --yes edge compute delete vm-abc123 -y # Specify API key directly edge compute list --api-key ek_live_xyz... Output Formats Table (default) Human-readable tabular format: $ edge compute list ID NAME STATUS IP SIZE REGION vm-abc123 web-1 running 192.0.2.10 s-2vcpu-4gb london vm-def456 api-server running 192.0.2.11 s-4vcpu-8gb london JSON Machine-readable JSON for scripting: $ edge compute list -o json [ { "id": "vm-abc123", "name": "web-1", "status": "running", "ip": "192.0.2.10", "size": "s-2vcpu-4gb", "region": "london" }, { "id": "vm-def456", "name": "api-server", "status": "running", "ip": "192.0.2.11", "size": "s-4vcpu-8gb", "region": "london" } ] Quiet IDs only, one per line: $ edge compute list -q vm-abc123 vm-def456 Scripting Examples Combine CLI commands for automation: #!/bin/bash # Stop all VMs for vm in $(edge compute list -q); do echo "Stopping $vm..." edge compute stop "$vm" --yes done # Purge CDN and sync new assets edge cdn purge my-deployment --yes edge storage sync ./dist my-bucket/website/ # Get VM IP as variable VM_IP=$(edge compute get vm-abc123 -o json | jq -r '.ip') echo "VM IP: $VM_IP" Environment Variables Variable Description EDGE_API_KEY API key for authentication EDGE_API_URL Override API endpoint EDGE_OUTPUT Default output format EDGE_REGION Default region NO_COLOR Disable colors (standard env var) Environment variables take precedence over config file settings but are overridden by command-line flags. Exit Codes Code Meaning 0 Success 1 General error 2 Authentication error 130 Interrupted (Ctrl+C) See Also Authentication API key setup CLI Overview Getting started guide Back to Docs Need help? --- ### CLI DNS Commands URL: https://edge.network/docs/cli/dns/ Markdown: https://edge.network/docs/cli/dns.md JSON: https://edge.network/json/docs/cli/dns.json _Edge CLI DNS command reference: create zones, add and update records, set up geographic routing, import and export BIND files, and view query metrics._ CLI DNS Commands Manage DNS zones and records, including geographic routing. Zones List Zones $ edge dns list ID DOMAIN RECORDS STATUS CREATED zone-abc123 example.com 24 active 2025-01-15 zone-def456 example.org 12 active 2025-02-01 zone-ghi789 mysite.io 8 active 2025-02-10 Create a Zone $ edge dns create --domain example.com Creating zone... done ID: zone-jkl012 Domain: example.com Status: active Nameservers: ns1.edge.network, ns2.edge.network Update your domain's nameservers at your registrar to activate DNS. Get Zone Details $ edge dns get zone-abc123 ID: zone-abc123 Domain: example.com Status: active Created: 2025-01-15 10:30:00 UTC Nameservers: ns1.edge.network, ns2.edge.network Records: 24 A: 8 AAAA: 4 CNAME: 6 MX: 2 TXT: 4 Queries (24h): 1,245,678 Delete a Zone # Delete with confirmation edge dns delete zone-abc123 # Delete without confirmation edge dns delete zone-abc123 --yes Import & Export Export Zone # Export as JSON edge dns export zone-abc123 # Export as BIND zone file edge dns export zone-abc123 --format bind > example.com.zone # Export as JSON to file edge dns export zone-abc123 > example.com.json Import Zone # Import from JSON file edge dns import zone-abc123 --file records.json # Import from BIND zone file edge dns import zone-abc123 --file example.com.zone --format bind Records List Records $ edge dns records list zone-abc123 TYPE NAME DATA TTL GEO A @ 192.0.2.1 300 - A @ 192.0.2.2 300 EU A www 192.0.2.1 300 - AAAA @ 2001:db8::1 300 - CNAME cdn cdn.edge.network. 300 - MX @ mail.example.com. 3600 - TXT @ "v=spf1 include:_spf..." 3600 - Add Records # Add an A record edge dns records add zone-abc123 --type A --name www --data 192.0.2.1 --ttl 300 # Add a CNAME record edge dns records add zone-abc123 --type CNAME --name cdn --data cdn.edge.network # Add an MX record edge dns records add zone-abc123 --type MX --name @ --data mail.example.com --priority 10 # Add a TXT record edge dns records add zone-abc123 --type TXT --name @ --data "v=spf1 include:_spf.example.com ~all" Geographic Routing # Add record with geo routing edge dns records add zone-abc123 --type A --name @ --data 185.1.1.1 \ --geo EU=185.2.2.2 \ --geo NA=185.3.3.3 \ --geo US-WEST=185.4.4.4 \ --geo GB=185.5.5.5 # Geo codes follow this hierarchy: # Region: NA, EU, AS, OC, AF, ME, SA # Country: US, GB, DE, FR, JP, etc. (ISO 3166-1) # Zone: US-WEST, US-EAST, CN-NORTH, etc. Update a Record # Update record data edge dns records update zone-abc123 rec-xyz789 --data 192.0.2.2 # Update TTL edge dns records update zone-abc123 rec-xyz789 --ttl 600 # Update multiple fields edge dns records update zone-abc123 rec-xyz789 --data 192.0.2.2 --ttl 600 Delete a Record # Delete with confirmation edge dns records delete zone-abc123 rec-xyz789 # Delete without confirmation edge dns records delete zone-abc123 rec-xyz789 --yes Metrics $ edge dns metrics zone-abc123 Period: Last 24 hours Total Queries: 1,245,678 Response Time: 2.3ms avg By Record Type: A: 892,345 queries AAAA: 201,456 queries CNAME: 112,345 queries MX: 32,456 queries TXT: 7,076 queries By Country: United States: 456,789 United Kingdom: 234,567 Germany: 178,234 France: 89,012 Other: 287,076 # Specify time period edge dns metrics zone-abc123 --period 7d # Filter by record type edge dns metrics zone-abc123 --record-type A # Export as CSV edge dns metrics zone-abc123 --export csv > dns-metrics.csv Supported Record Types Type Description Geo Support A IPv4 address AAAA IPv6 address CNAME Canonical name (alias) MX Mail exchange TXT Text record NS Nameserver CAA Certificate Authority Authorization SRV Service record DNS Examiner Run AI-powered analysis of your DNS configuration. Checks email deliverability, security, nameserver delegation, and best practices. # Run examination on a zone edge dns examine <zone-id> # View the last examination result edge dns examine-last <zone-id> # Output as JSON edge dns examine <zone-id> --output json Examinations take up to 30 seconds. Results are saved and can be retrieved with examine-last . Common Flags Flag Description --domain Domain name for zone --type Record type (A, AAAA, CNAME, etc.) --name Record name (@ for root) --data Record value/data --ttl Time to live in seconds --priority Priority for MX records --geo Geographic routing (CODE=value) --format Import/export format (json, bind) See Also Storage Commands Manage buckets and objects DNS Docs Full DNS documentation Back to Docs Need help? --- ### CLI Installation URL: https://edge.network/docs/cli/installation/ Markdown: https://edge.network/docs/cli/installation.md JSON: https://edge.network/json/docs/cli/installation.json _How to install the Edge CLI on macOS, Linux, and Windows using the one-line install script or manual binary downloads, plus shell completion and updates._ CLI Installation Install the Edge CLI in seconds on any platform. Quick Install (Recommended) The fastest way to install on macOS or Linux: curl -fsSL https://edge.network/install.sh | sh This script auto-detects your OS and architecture, downloads the correct binary, and installs to /usr/local/bin . Install via npm If you already have Node.js, install the CLI from npm — the package downloads the correct native binary for your platform: npm install -g @edge-network/cli Works on macOS, Linux, and Windows. The npm package version is pinned to the CLI version. Manual Installation Linux macOS Windows Linux (amd64) # Download the binary curl -LO https://cli.edge.network/latest/edge-linux-amd64 # Make it executable chmod +x edge-linux-amd64 # Move to PATH sudo mv edge-linux-amd64 /usr/local/bin/edge # Verify installation edge version macOS # Download the binary (Apple Silicon) curl -LO https://cli.edge.network/latest/edge-darwin-arm64 # Or for Intel Macs curl -LO https://cli.edge.network/latest/edge-darwin-amd64 # Make it executable chmod +x edge-darwin-* # Move to PATH sudo mv edge-darwin-* /usr/local/bin/edge # Verify installation edge version Windows (PowerShell) # Download from PowerShell Invoke-WebRequest -Uri "https://cli.edge.network/latest/edge-windows-amd64.exe" -OutFile "edge.exe" # Move to a directory in your PATH, or add the current directory to PATH Move-Item edge.exe C:\Windows\System32\edge.exe # Verify installation edge version Available Binaries Platform Architecture Binary Linux x86_64 edge-linux-amd64 Linux ARM64 edge-linux-arm64 Linux ARM (32-bit) edge-linux-arm macOS Apple Silicon edge-darwin-arm64 macOS Intel edge-darwin-amd64 Windows x86_64 edge-windows-amd64.exe Windows ARM64 edge-windows-arm64.exe Verify Installation $ edge version edge version 1.0.0 (commit abc1234) $ edge --help Edge CLI - Manage Edge Network resources Usage: edge [command] Available Commands: auth Manage authentication compute Manage virtual machines cdn Manage CDN deployments dns Manage DNS zones and records storage Manage object storage account View account information config Manage CLI configuration version Show version information help Help about any command Flags: -h, --help help for edge -o, --output string Output format: table, json, yaml (default "table") -q, --quiet Suppress non-essential output -v, --verbose Show debug information Use "edge [command] --help" for more information about a command. Shell Completion Enable tab completion for your shell: Bash # Bash edge completion bash >> ~/.bashrc source ~/.bashrc Zsh # Zsh edge completion zsh >> ~/.zshrc source ~/.zshrc Fish # Fish edge completion fish > ~/.config/fish/completions/edge.fish Updating Update to the latest version: edge update Or re-run the install script to get the latest version. Next Steps Authentication Set up your API key Compute Commands Manage virtual machines Back to Docs Need help? --- ### CLI Shield Commands URL: https://edge.network/docs/cli/shield/ Markdown: https://edge.network/docs/cli/shield.md JSON: https://edge.network/json/docs/cli/shield.json _Manage Edge Shield bot-protection widgets from the command line._ CLI Shield Commands Create and manage Edge Shield widgets — free, privacy-first bot protection — without leaving your terminal. Widgets List Widgets $ edge shield list ID NAME SITEKEY MODE AGENTS HOSTNAMES CREATED wgt-abc123 Contact form es_6206c6fdb43e7a3cb948507e6f3e5a11 managed allow example.com 2026-03-01 wgt-def456 Signup es_9f2a1b8c7d6e5f4a3b2c1d0e9f8a7b6c invisible challenge any 2026-04-12 Create a Widget $ edge shield create --name "Contact form" --hostname example.com Creating widget... done ✓ Created widget Contact form (wgt-abc123) Sitekey: es_6206c6fdb43e7a3cb948507e6f3e5a11 Secret: ss_4f8e2a1b9c7d6e5f4a3b2c1d0e9f8a7b Mode: managed Agent Policy: allow Hostnames: example.com ! Store the secret securely — it will not be shown again. Embed on your page: <script src="https://shield.edge.network/api.js" defer></script> <div class="edge-shield" data-sitekey="es_6206c6fdb43e7a3cb948507e6f3e5a11"></div> The secret is shown only once Store it as a server-side environment variable immediately. It's needed for server-side validation and cannot be retrieved later — if it's lost, create a new widget. Get Widget Details $ edge shield get wgt-abc123 ID: wgt-abc123 Name: Contact form Sitekey: es_6206c6fdb43e7a3cb948507e6f3e5a11 Secret: ss_4f8e... Mode: managed Agent Policy: allow Hostnames: example.com Created: 2026-03-01 Update a Widget # Switch to invisible mode edge shield update wgt-abc123 --mode invisible # Replace the hostname allowlist edge shield update wgt-abc123 --hostname example.com --hostname www.example.com # Challenge verified AI agents instead of allowing them edge shield update wgt-abc123 --agent-policy challenge # Rename edge shield update wgt-abc123 --name "Contact form (prod)" Revoke a Widget # Revoke with confirmation edge shield delete wgt-abc123 # Revoke without confirmation edge shield delete wgt-abc123 --force Revocation is immediate — the sitekey and secret stop working, and any pages still embedding the widget will fail verification. Traffic Stats Challenge volume, solve rates, humanity scores, server-side verifications, and blocked replays. Defaults to the last 24 hours; use --hours for up to 30 days. $ edge shield stats wgt-abc123 --hours 168 Last 168 hours: Challenges issued: 14,382 Challenges solved: 9,041 (62.9%) Interactive shown: 412 (2.9%) Avg humanity score: 78/100 Verified submissions: 1,204 Failed verifications: 38 Replays blocked: 17 Verified agents: 93 Shield Examiner Run AI-powered analysis of a widget's aggregate traffic. Flags bot pressure, replay abuse, and calibration issues, and recommends configuration changes — the same Examiner available in the console. # Run AI-powered traffic examination edge shield examine wgt-abc123 # View the last examination result edge shield examine-last wgt-abc123 # Output as JSON edge shield examine wgt-abc123 --output json Examinations take up to 45 seconds. Results are saved and can be retrieved with examine-last . Common Flags Flag Description --name Widget name --hostname Allowed hostname (repeatable). Empty = any hostname --mode Widget mode: managed, non-interactive, invisible --agent-policy Verified-agents policy: allow, challenge, block --hours Stats window in hours (max 720) --force Skip delete confirmation See Also Shield Docs Embed the widget and validate tokens Widget Modes Managed, non-interactive, and invisible Back to Docs Need help? --- ### CLI Storage Commands URL: https://edge.network/docs/cli/storage/ Markdown: https://edge.network/docs/cli/storage.md JSON: https://edge.network/json/docs/cli/storage.json _Manage object storage buckets and files from the command line._ CLI Storage Commands Manage S3-compatible object storage with familiar commands. Buckets List Buckets $ edge storage list NAME OBJECTS SIZE CREATED my-assets 1,234 2.3 GB 2025-01-15 backups 456 45.6 GB 2025-02-01 website-static 89 123 MB 2025-02-10 Create a Bucket $ edge storage create my-new-bucket Creating bucket... done Name: my-new-bucket Region: london Delete a Bucket # Delete empty bucket edge storage delete my-bucket # Delete bucket and all contents edge storage delete my-bucket --force Bucket Info $ edge storage info my-assets Name: my-assets Region: london Objects: 1,234 Size: 2.3 GB Created: 2025-01-15 Objects List Objects $ edge storage ls my-bucket NAME SIZE MODIFIED images/ - - documents/ - - index.html 4.2 KB 2025-02-10 14:30 styles.css 12.3 KB 2025-02-10 14:30 app.js 45.6 KB 2025-02-10 14:32 # List contents of a folder $ edge storage ls my-bucket/images/ NAME SIZE MODIFIED logo.png 23.4 KB 2025-02-08 hero.jpg 1.2 MB 2025-02-08 icons/ - - # List all objects recursively (note: -R uppercase) $ edge storage ls my-bucket -R Upload Files # Upload a single file edge storage cp ./logo.png my-bucket/images/ # Upload to specific path edge storage cp ./file.pdf my-bucket/documents/report.pdf # Upload multiple files edge storage cp ./dist/* my-bucket/static/ # Recursive upload (folder, note: -R uppercase) edge storage cp -R ./public my-bucket/website/ Download Files # Download a single file edge storage cp my-bucket/images/logo.png ./downloads/ # Download to specific path edge storage cp my-bucket/report.pdf ./local-report.pdf # Recursive download (folder, note: -R uppercase) edge storage cp -R my-bucket/backups/ ./local-backups/ Delete Objects # Delete a single object edge storage rm my-bucket/old-file.txt # Delete multiple objects edge storage rm my-bucket/file1.txt my-bucket/file2.txt # Recursive delete (folder, note: -R uppercase) edge storage rm -R my-bucket/old-folder/ # Delete without confirmation edge storage rm -R my-bucket/temp/ --force Move/Rename # Rename an object edge storage mv my-bucket/old-name.txt my-bucket/new-name.txt # Move to different folder edge storage mv my-bucket/file.txt my-bucket/archive/file.txt Sync Synchronize directories between your local filesystem and storage: # Sync local folder to bucket edge storage sync ./dist my-bucket/website/ # Sync bucket to local folder edge storage sync my-bucket/backups/ ./local-backups/ # Sync with delete (remove files not in source) edge storage sync --delete ./dist my-bucket/website/ # Dry run (show what would change) edge storage sync --dry-run ./dist my-bucket/website/ Presigned URLs Generate temporary URLs for private objects: # Generate presigned URL (default 1 hour) $ edge storage presign my-bucket/private/document.pdf https://storage.edge.network/my-bucket/private/document.pdf?X-Amz-... # Custom expiry edge storage presign my-bucket/file.zip --expires 24h # Expiry options: 5m, 1h, 24h, 7d (max 7 days) Usage & Metrics Overall Usage $ edge storage usage Total Size: 48.2 GB Total Objects: 12,345 Buckets: 5 Bucket Metrics $ edge storage metrics my-bucket Bucket: my-bucket Region: london Storage Used: 2.3 GB Objects: 1,234 Created: 2025-01-15 $ edge storage metrics Overall Storage Metrics Total Storage: 48.2 GB Total Objects: 12,345 Buckets: 5 Common Flags Flag Description -R, --recursive Operate recursively on folders (uppercase R) -f, --force Force delete bucket with contents / skip confirmation --delete Delete files not in source (sync only) --dry-run Show what would change without making changes (sync only) --expires Expiry time for presigned URLs (e.g., 1h, 24h, 7d) -r, --region Global flag for region selection Note: Recursive uses uppercase -R The lowercase -r is reserved for the global --region flag. Use uppercase -R for recursive operations. Tips Quiet Mode for Scripting Use -q flag to suppress progress output in scripts. Very Large Files (1GB+) For uploading very large files, consider using S3-compatible tools like aws s3 cp or rclone which support multipart uploads with automatic retry and resumption. Upload Limits The console has a 1GB upload limit. Use the CLI or S3 API for larger files. See Also Configuration Customize CLI settings Storage Docs Full Storage documentation Back to Docs Need help? --- ### Command Palette URL: https://edge.network/docs/tooling/command-palette/ Markdown: https://edge.network/docs/tooling/command-palette.md JSON: https://edge.network/json/docs/tooling/command-palette.json _How to use the Edge console command palette: open it with / or Cmd+K, jump to any section, run contextual quick actions, and search with fuzzy matching._ Dev Tooling Command Palette Navigate anywhere and trigger actions instantly without reaching for the mouse. Opening the Command Palette The command palette can be opened from anywhere in the console using: / Forward Slash When not focused on a text input ⌘ K Cmd+K / Ctrl+K Works anywhere, even in text inputs Press Esc to close the palette at any time. Contextual Quick Actions The command palette is context-aware. Quick actions shown at the top are relevant to the section you're currently viewing: Current Section Quick Actions CDN Deploy CDN Compute Create Virtual Machine, Manage SSH Keys, Manage Firewall Rules DNS Create DNS Zone Storage Create Storage Bucket, Manage Storage Keys, Storage Connection Info Account Open Support Ticket, Manage API Keys, Manage Team, Billing, Settings, Alerts Actions from other sections are available under "Other Actions" further down the list. Navigation Jump to any section of the console instantly: → Overview → CDN → Compute → DNS → Storage → Activity → Usage → Support Search Start typing to search across all commands and actions. The search matches against: Command names — "Create Virtual Machine", "Deploy CDN", etc. Keywords — "vm", "server", "bucket", "domain", "firewall", etc. Sections — "compute", "storage", "dns", etc. When searching, all commands are shown regardless of which section you're in. This lets you quickly find actions from any page. Keyboard Navigation Navigate the command palette entirely with your keyboard: Key Action ↑ ↓ Move selection up/down Enter Execute the selected command Esc Close the command palette / Open the command palette ⌘ K Toggle the command palette (works in text inputs too) Tips Quick navigation Press / then type "cdn" and press Enter to jump straight to CDN. Fuzzy matching Search terms don't need to be exact. Typing "vm" will match "Create Virtual Machine". Mouse or keyboard You can click commands directly or navigate with arrow keys. Hovering also updates the selection. Back to Docs Need help? --- ### Dev Tooling URL: https://edge.network/docs/tooling/ Markdown: https://edge.network/docs/tooling.md JSON: https://edge.network/json/docs/tooling.json _Developer tooling for Edge Network: the console command palette for fast navigation and actions, plus the Edge CLI for managing resources from your terminal._ Dev Tooling Developer Tools Productivity features built into the Edge console for faster infrastructure management. Command Palette Navigate anywhere, trigger actions, and search across the entire console with a single keystroke. Edge CLI Full-featured command-line interface for managing all Edge resources. View CLI docs → Back to Docs Need help? --- ### Edge CLI URL: https://edge.network/docs/cli/ Markdown: https://edge.network/docs/cli.md JSON: https://edge.network/json/docs/cli.json _Overview of the Edge CLI, a single binary for macOS, Linux, and Windows that manages compute, CDN, DNS, storage, and Shield with table, JSON, or YAML output._ CLI Edge CLI Manage all Edge Network resources from your terminal. curl -fsSL https://edge.network/install.sh | sh Features Single Binary No dependencies, works on macOS, Linux, and Windows Fast Instant startup, efficient API communication Multiple Output Formats Table, JSON, YAML, or quiet mode for scripting Secure API key authentication, credentials stored locally Activity Tracking All CLI actions logged with user and source attribution Manage All Products Compute VMs, keys, groups CDN Deployments, domains DNS Zones, records Storage Buckets, objects Shield Widgets, stats Quick Examples Create a VM: edge compute create --name web-1 --size s-2vcpu-4gb --image ubuntu-24 List DNS zones: edge dns list Upload to Storage: edge storage cp ./backup.tar.gz my-bucket/backups/ Purge CDN cache: edge cdn purge my-deployment --path /images/* Add bot protection to a form: edge shield create --name "Contact form" --hostname example.com Get Started Installation Install on your system Authentication Set up API keys Back to Docs Need help? --- ## Academy & SDK Guides ### Academy URL: https://edge.network/academy/ Markdown: https://edge.network/academy.md JSON: https://edge.network/json/academy.json _Learn Edge Network. Tutorials, documentation, and guides to help you get the most from our platform._ Academy Learn Edge Get the most out of Edge Network with tutorials, guides, and best practices. Browse by Topic Find tutorials and guides organized by category. Getting Started Learn the basics of Edge Network and deploy your first resource. Console Quick Start Quick Start Guide (CLI) Terminology Account Setup CLI Installation First Deployment Video Tutorials Watch step-by-step tutorials on using Edge products. CDN Setup VM Configuration DNS Management Storage Basics Best Practices Learn how to optimize your infrastructure for performance and cost. Caching Strategies Cost Optimization High Availability How to Set Up a CDN CDN Pricing Comparison What Does Edge Infrastructure Cost? Edge Explained What edge infrastructure is, how it works, and why it matters. What is an Edge Network? What is the Edge Cloud? What is an Edge Server? What is an Edge Data Center? What is an Edge Node? What is Edge Storage? CDN vs Edge Computing Security Protect your infrastructure, your account, and your public endpoints. Security Hardening Password-Protected CDN Domains Bot Protection with Edge Shield Securing Login & Signup Flows Protecting APIs from Bot Abuse Verified AI Agents with Web Bot Auth Migrating from reCAPTCHA Assist Add AI answers to your website, drawn from your own content. Add AI Answers to Your Site Getting Started with Assist Widget & Embedding Content Ingestion API Reference Agentic Cloud Let AI agents deploy and manage your infrastructure autonomously. What is the Agentic Cloud? Agent Access Codes Discovery API Deploy an App with an Agent Deploy a Static Site with an Agent Projects API & SDK Integrate Edge services into your applications. API Reference JavaScript SDK Python SDK Go SDK Information Background information and deep dives about Edge and how the core technology works. What is Edge Network? (the company) What is a Decentralised Cloud? What is a Decentralised CDN? Decentralised Cloud Storage Explained Is DNS Centralised or Decentralised? Machine Learning at the Edge Edge Network Security Zero Egress Fees Explained What Makes Edge Better for the Environment? What is XE and how does it Power Edge? What is the EDGE Token? Featured Guides Popular tutorials to get you started quickly. What is an Edge Network? 8 min read Add AI answers to your site 6 min read Migrating from AWS to Edge 15 min read Bot protection with Edge Shield 8 min read Setting up a multi-region CDN 10 min read Deploying a Node.js app on Edge Compute 12 min read Can't find what you're looking for? Check out our documentation or reach out to support. View Documentation Contact Support --- ### Account Setup Guide URL: https://edge.network/academy/account-setup/ Markdown: https://edge.network/academy/account-setup.md JSON: https://edge.network/json/academy/account-setup.json _Complete guide to setting up your Edge Network account. Profile, payment, security, and notification configuration._ Back to Academy Getting Started 5 minutes Account Setup Guide A complete walkthrough of setting up your Edge Network account, from signup to security configuration. Get your account production-ready in 5 minutes. What you'll set up: Profile Billing Security Notifications Email Verification 01 Start Free Head to edge.network and click the "Start Free" button to begin the signup process. Visit edge.network Click "Start Free" in the top navigation You'll be taken to the account creation page 02 Create Your Account One short form — or one click with Google or GitHub. By continuing you agree to the terms of service and privacy policy. Enter your full name and email address Create a secure password (minimum 8 characters) Add your company or organisation (optional) Click "Create Account" — or sign up with Google or GitHub instead 03 Verify Your Email We send a verification link the moment you sign up. Verifying your email unlocks resource creation — starting with free DNS zones. No card is needed for this step. Check your email inbox (and spam folder) Click the verification link in the email You'll be redirected back to Edge You can now create DNS zones and other resources 04 Your Account is Ready You're all set! Your free Edge account is active and you can start deploying resources immediately. Add a card later (verified, not charged) to unlock the CDN and Storage free tiers and enable pay-as-you-go, or load a prepaid balance to run VMs. You'll be taken to your console DNS, Shield, and Assist have free tiers with no card at all Add a card to unlock the CDN & Storage free tiers and pay-as-you-go Check out the Quick Start guide to deploy your first resource 05 Complete Your Profile Your name and company come across from signup — polish the rest in Settings → Profile. Navigate to Settings → Profile Update your name or company if needed Add a profile photo Note your Customer ID — support may ask for it 06 Configure Security Secure your account with two-factor authentication. We strongly recommend enabling this. Navigate to Settings → Security Click "Enable 2FA" Scan the QR code with your authenticator app Enter the verification code to confirm 07 Set Up Notifications Choose what Edge emails you about, and add a phone number if you want SMS for critical alerts. Navigate to Settings → Communication Email notifications are on by default Toggle notification types — security alerts, product updates, usage reports, offers Add a phone number for SMS on critical alerts (optional) Account ready! Your Edge Network account is fully configured and secure. You're ready to deploy your first resource. Check out the Quick Start guide to get going. Quick Start Guide Go to Console Related guides Quick Start Guide 10 min CLI Installation 3 min First Deployment 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Add AI Answers to Your Site with Edge Assist URL: https://edge.network/academy/add-ai-answers-to-your-site/ Markdown: https://edge.network/academy/add-ai-answers-to-your-site.md JSON: https://edge.network/json/academy/add-ai-answers-to-your-site.json _Give your visitors instant, cited answers drawn from your own content. One script tag, no model keys, 250 answered questions free every month._ Back to Academy Assist 6 min read Add AI Answers to Your Site Your visitors have questions. Your site has the answers — buried across dozens of pages. Edge Assist connects the two: instant, cited answers drawn from your own content, added with one script tag. Why grounded answers beat a chatbot Most site chatbots fail in one of two directions: they either answer from a generic model and confidently invent your prices, or they're a decision tree in a trench coat that punts everything to a contact form. Assist is grounded : every answer is composed from passages retrieved out of your own ingested content, cited inline so the visitor can click through to the page a claim came from. When your content doesn't contain the answer, Assist says so and offers the closest page — or hands the conversation to a human. It never invents prices, limits, or SLAs. And because visitor questions follow a power law, answered questions are cached per site: your most-asked questions get instant, word-for-word consistent answers, and the cache invalidates itself the moment your content changes. 1. Create a site and ingest your content In the console , create an Assist site with your hostname — you'll get a public sitekey ( ea_… ). There's no secret key to protect: the API only answers for your sitekey when the request comes from your own domain. Then tell Assist what it knows. Your site build publishes a small JSON index — chunks of page text with their URLs — and Assist re-fetches it hourly, re-indexing whenever the content hash changes: { "hash": "3f9c2a71b4e8d05c", "chunks": [ { "url": "/pricing", "title": "Pricing", "section": "pricing", "text": "Storage is billed at $0.015 per GB per month. There are no egress fees within…" } ] } A site rebuild is all it takes to update what Assist knows — and any content change automatically invalidates cached answers built on the old content. The full format and chunking guidance are in the ingestion docs . 2. Add one line to your pages <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" defer></script> That's the integration. The widget is a single dependency-free script with styles isolated in a shadow root — your CSS can't break it, it can't leak into your page, and it never blocks your page load. Visitors get instant search results as they type, and a streamed, cited answer when they ask a question. How it shows up is up to you: Surface How Floating launcher The default — a pill in the corner of every page. Position, label, and colour are settings. Search shortcut Add data-hotkey="k" to the script tag and ⌘K opens site search with ask built in. Your own buttons Any element with data-edge-assist-open opens the assistant — nav icons, 404 pages, "Chat with us" links. Inline embed A <div data-edge-assist> renders the panel in the page flow, for help centres and support pages. Hosted page Zero integration: every site gets a full-page assistant at assist.edge.network you can link to. The assistant answering questions on this site right now — bottom-right corner, or press ⌘K — is this exact widget. 3. Steer it, then close the loop Everything else is a setting in Control, not code. Three are worth doing on day one: Suggested questions — up to four one-click chips shown before the first question. Seed them with the questions you most want to answer well (pricing, getting started, your differentiator). Handoff email — enables "Need a human?". The visitor leaves their address, the whole conversation lands in your inbox, and replying to the email reaches them directly. An AI answer that knows when to get out of the way is what makes visitors trust the rest. The question log — every question is logged, answered or not. Unanswered questions are a literal to-do list for your content: each one is something a real visitor wanted to know and your site didn't say. What it costs One unit: the answered question. 250 are free every month , search is free and unlimited forever, and beyond the allowance it's $0.01 per question — no plans, no seats, no per-page fees. If you never set a usage budget, the widget simply falls back to search-only at the cap and resumes next month. For scale: a docs site answering 2,000 questions a month pays $17.50. Comparable dedicated AI-answer products start at $150–500 per month before a single question is asked. Worked examples are on the pricing page . Next steps Try the live demo Ask it anything about Edge Read the docs Getting started, ingestion, widget, API Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### API Reference URL: https://edge.network/academy/api-reference/ Markdown: https://edge.network/academy/api-reference.md JSON: https://edge.network/json/academy/api-reference.json _Edge Network REST API: authentication, endpoints for Compute, CDN, DNS, Storage, and Shield, error handling, rate limiting, and pagination. Learn how to integrate Edge services into your applications._ Back to Academy API & SDK 15 min read API Reference Edge exposes a REST API for Compute, CDN, DNS, Storage, and Shield. Use it to automate deployments, manage resources, and integrate with your tooling. Base URL and architecture The Edge API is served at https://api.edge.network . All requests use REST over HTTPS. Edge does not provide a GraphQL endpoint — use the REST API for all programmatic access to Compute, CDN, and DNS. For Storage , Edge uses S3-compatible object storage. Storage is accessed via https://storage.edge.network using the AWS S3 API — not the REST API above. See the JavaScript SDK, Python SDK, or Go SDK articles for storage integration. Authentication Authenticate with a Bearer token using your API key. Pass it in the Authorization header: Authorization: Bearer ek_live_xxxxxxxxxxxxxxxxxxxxxxxx API keys follow the format ek_live_... for production. Generate keys in the Console → Settings → API Keys . Never expose API keys in client-side code or public repositories. Common headers and response format Include Content-Type: application/json for request bodies, and expect application/json in responses. Successful responses return the requested data directly or wrapped in a standard envelope. For example, a list response: { "data": [...], "meta": { "total": 42, "page": 1, "per_page": 20 } } Error handling Errors return appropriate HTTP status codes (e.g. 400 for bad request, 401 for unauthorised, 404 for not found, 429 for rate limiting) and a JSON body with an error code and message: { "error": { "code": "validation_error", "message": "Invalid VM configuration" } } Handle errors by checking the HTTP status and parsing the error object for retry logic or user-facing messages. Rate limiting and pagination The API is rate limited per account. When you exceed the limit, you receive HTTP 429. Include Retry-After in responses to indicate when to retry. Implement exponential backoff for production clients. List endpoints support pagination via page and per_page query parameters. Resource endpoints Compute /api/compute/vms GET list VMs POST create VM GET /:id get VM DELETE /:id delete VM POST /:id/power power on/off CDN /api/cdn/deployments GET list deployments POST create deployment GET /:id/domains domains POST /:id/purge purge cache DNS /api/dns/zones GET list zones POST create zone GET /:id/records list records, POST create, PUT/:recordId update, DELETE/:recordId delete Storage /api/storage/buckets GET list buckets POST create bucket GET /:bucket/objects list objects Presigned URLs generated via Storage API or S3 SDK Storage uses the S3-compatible API at https://storage.edge.network — use AWS S3 SDKs for object operations. Example requests List VMs curl -X GET "https://api.edge.network/api/compute/vms" \ -H "Authorization: Bearer ek_live_xxx" Response: { "data": [ { "id": "vm_123", "name": "web-1", "status": "running" } ], "meta": { "total": 1, "page": 1, "per_page": 20 } } Create CDN deployment curl -X POST "https://api.edge.network/api/cdn/deployments" \ -H "Authorization: Bearer ek_live_xxx" \ -H "Content-Type: application/json" \ -d '{"origin": "https://mysite.com", "name": "cdn-prod"}' Response: { "id": "cdn_456", "name": "cdn-prod", "origin": "https://mysite.com", "cname": "cdn-456.edge.network" } Create DNS record curl -X POST "https://api.edge.network/api/dns/zones/zone_789/records" \ -H "Authorization: Bearer ek_live_xxx" \ -H "Content-Type: application/json" \ -d '{"type": "A", "name": "www", "value": "203.0.113.1"}' Response: { "id": "rec_abc", "type": "A", "name": "www", "value": "203.0.113.1" } Next steps JavaScript SDK CLI Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Bot Protection with Edge Shield URL: https://edge.network/academy/bot-protection-shield/ Markdown: https://edge.network/academy/bot-protection-shield.md JSON: https://edge.network/json/academy/bot-protection-shield.json _Protect your forms, logins, and signups from bots without showing humans a CAPTCHA. Add Edge Shield in two lines, validate tokens server-side, and act on a 1–100 humanity score._ Back to Academy Security 8 min read Bot Protection with Edge Shield Stop form spam, credential stuffing, and fake signups without ever showing a human a puzzle. Two lines on the page, one HTTP call on the server — free forever. Why not just use a CAPTCHA? Traditional CAPTCHAs make humans do work that AI now does better — image puzzles cost you real conversions while modern bots solve them for fractions of a cent. And most "invisible" alternatives pay for their invisibility with tracking. Edge Shield takes a different approach: a lightweight proof-of-work runs in a background thread while the page loads, corroborated by server-side signals — solve timing, header coherence, network reputation, TLS characteristics. The result is a humanity score from 1 to 100 attached to every verification, with no cookies, no fingerprint database, and no per-visitor data stored. The score doesn't stop there. As the visitor actually uses the page — typing into your form, moving the pointer — the widget summarises that interaction into a handful of aggregate statistics (computed in the browser; raw movements and keystrokes never leave the device) and refreshes its token with a behaviour-informed score. Human motor noise raises it; machine-perfect input lowers it. By the time the form is submitted, the score reflects how the visitor behaved, not just what their browser looked like. 1. Add the widget to your form Create a widget in the console (verified email is all you need — no card), then drop the script tag and a placeholder div into any form: <script src="https://shield.edge.network/api.js" defer></script> <form action="/signup" method="POST"> <input type="email" name="email" required /> <div class="edge-shield" data-sitekey="es_your_sitekey"></div> <button type="submit">Sign up</button> </form> Verification runs while the visitor fills in the form, and the token lands in a hidden edge-shield-response input automatically. In the default managed mode , real visitors see a small "Verified" badge; only suspicious traffic gets a single-click confirmation backed by a harder challenge. 2. Validate the token server-side Client-side checks alone protect nothing — always validate the token from your server. Tokens are single-use and expire after five minutes, so replayed or scripted submissions fail even if they captured a real token. The response shape is compatible with Cloudflare Turnstile, so migrating is a URL swap. // On your server, before processing the form const res = await fetch('https://shield.edge.network/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ secret: process.env.SHIELD_SECRET, response: req.body['edge-shield-response'], }), }) const { success, score, agent } = await res.json() if (!success) return reject() // invalid, expired, or replayed if (agent?.verified) return route() // declared automation — your call if (score < 40) return stepUp() // suspicious — require confirmation 3. Act on the score, not just the verdict The score turns bot protection from a binary gate into a policy you control. Sensible starting bands: Score Meaning Suggested action 70–100 Confident human Let them straight through. 40–69 Uncertain Step up: email confirmation, or rely on managed mode’s one-click check. 1–39 Automation Block — or route verified agents to your API instead. Note the third row: "automation" doesn't have to mean "blocked". AI agents acting for real customers score low honestly — and if they sign their requests with Web Bot Auth , the siteverify response tells you exactly who they are, so you can send them to your API instead of a dead end. Where it earns its keep Signup and login forms — stop credential stuffing and fake account waves without adding friction for real users. Contact and comment forms — kill form spam at the source instead of moderating it afterwards. Checkouts — card-testing bots hammer payment forms; a score floor before the payment call cuts fraud and processor fees. Newsletter subscriptions — protect your sender reputation from bot-filled lists. Every form on this site — including the newsletter box in the footer — runs Shield in invisible mode. You've been verified several times just browsing, and never noticed. Next steps Try the live demo Watch it verify you in real time Read the docs Widget modes, JS API, migration guides Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Caching Strategies URL: https://edge.network/academy/caching-strategies/ Markdown: https://edge.network/academy/caching-strategies.md JSON: https://edge.network/json/academy/caching-strategies.json _How CDN caching works on Edge Network: cache-control headers, path-based rules, TTL configuration, cache purging, and image optimisation. Practical tips to maximise cache hit rates._ Back to Academy Best Practices 10 min read Caching Strategies Get the most from Edge CDN: how caching flows from origin to edge to user, configure cache rules, and optimise hit rates. How CDN caching works When a user requests content, the flow is: origin → edge → user . Your origin server (VM, storage bucket, or external host) delivers the response. Edge CDN nodes sit in 2,200+ locations worldwide and cache responses closer to your users. On a cache hit, the edge serves the content directly without hitting your origin — reducing latency and offloading traffic. The first request for a given URL triggers a fetch from origin. Subsequent requests for that URL (within the cache TTL) are served from the edge. Understanding this flow helps you tune cache behaviour for performance and cost. Cache-Control headers and Edge Your origin can send standard Cache-Control headers to influence caching. Edge respects max-age , s-maxage , and private / no-store . For example, Cache-Control: max-age=3600, s-maxage=86400 tells the edge to cache for 24 hours (s-maxage) even if the browser honours 1 hour (max-age). If your origin omits or sends conflicting headers, Edge applies a default TTL. You can also override origin directives via the console or API — useful when you want consistent behaviour across deployments without changing application code. Default TTLs and path-based rules Set a default TTL for your CDN deployment in the console under Configuration → Caching . This applies when the origin does not send cache directives. Path-based cache rules let you fine-tune behaviour by URL pattern. A common strategy: Long TTL for static assets — e.g. /assets/* or *.js , *.css , *.woff2 — 7–30 days or more Short TTL for HTML — e.g. /* or /*.html — 0–5 minutes for dynamic pages No cache for dynamic content — API paths, user-specific pages — bypass cache entirely In the console, add rules under Configuration → Cache Rules . The Edge CLI also supports configuring rules — run edge cdn cache-rules --help for syntax. Cache bypass for dynamic content For user dashboards, API responses, or personalised content, caching is usually wrong. Two approaches: Origin headers — Set Cache-Control: no-store or private on those responses. Edge will not cache them. Path-based bypass — Add a cache rule that matches the path (e.g. /api/* ) and sets TTL to 0 or "bypass". Use bypass sparingly — every uncached request hits your origin and increases load. Keep dynamic paths limited to what truly needs freshness. Cache purging: when and how Purge invalidates cached content before its TTL expires. Use it when you update a file, redeploy, or fix a mistake and need users to see the new version immediately. When to purge: After deploying static site updates, changing assets (JS/CSS), uploading new images, or fixing incorrect content. Avoid purging entire deployments routinely — it defeats caching. How to purge: In the console, go to your CDN deployment → Purging . You can purge by URL, path prefix, or (for deployments that support it) by tag. Via CLI: edge cdn purge <deployment-id> --url "https://yoursite.com/page" . Purging propagates across the edge network within seconds. There is no charge for purge operations within reasonable limits. Image optimisation cache behaviour Edge's image optimisation (resize, format conversion, quality) generates derived images on demand. These derived images are cached separately. Each unique URL (including query params like ?w=800 ) is cached independently. Set a long TTL for image paths — optimised images do not change unless the source changes. When you replace the source image, purge the relevant URLs or path to invalidate cached variants. Monitoring cache hit rates The console provides cache metrics per deployment: hit rate, miss rate, and bandwidth served from cache vs origin. High hit rates (e.g. 90%+) mean your origin is protected and users get fast responses. Low hit rates often mean: TTLs are too short, paths are bypassing cache, or traffic is spread across many unique URLs. Review your cache rules and consider longer TTLs for static content. Use the Edge CLI or API to pull analytics for deeper analysis. Next steps Security Hardening CDN Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### CDN Pricing Comparison URL: https://edge.network/academy/cdn-pricing-comparison/ Markdown: https://edge.network/academy/cdn-pricing-comparison.md JSON: https://edge.network/json/academy/cdn-pricing-comparison.json _Compare CDN pricing across Edge, Bunny, Cloudflare, Fastly, Akamai, and CDN77 — egress rates, minimum spend, and how each pricing model behaves at scale._ Back to Academy Best Practices 8 min read CDN Pricing Comparison CDN bills are dominated by bandwidth — but providers price it in very different ways. Here's how the major pricing models work, and how the numbers compare. The three CDN pricing models Most CDN pricing reduces to one of three models. Per-GB egress pricing charges for every gigabyte delivered to users — the traditional model used by Bunny, Fastly, Akamai, and CDN77. It ties your bill directly to traffic, which means costs spike with success: a viral post or a product launch shows up on your invoice. Request-based pricing charges per request served, regardless of size. This is Edge's model: $0.25 per million requests with bandwidth included, so a million small API responses and a million large images cost the same. It suits sites whose traffic is heavy in bytes rather than requests — media, downloads, images — because the expensive part (bandwidth) isn't metered. Flat or plan-based pricing bundles CDN into a subscription, as Cloudflare does. Predictable at small scale, but limits and enterprise features typically push growing sites into quote-based contracts where pricing is opaque. Provider pricing at a glance Published rates as compared on our CDN comparison pages — follow the links for full feature-by-feature breakdowns. Provider Egress Fees Pricing Model Minimum Spend Edge Free $0.25 per million requests None — free tier included Bunny.net $0.01–0.06/GB Per-GB egress None Cloudflare Free Plans; enterprise quote required Limited free tier Fastly $0.08–0.28/GB Per-GB egress + requests $50/month Akamai $0.10/GB+ Negotiated contracts Annual contract CDN77 $0.049/GB+ Per-GB egress None What the numbers mean in practice Per-GB rates look small until you multiply them. At Fastly's $0.08–0.28/GB, delivering 10 TB a month costs $800 or more; at Akamai's $0.10/GB+, the same traffic runs past $1,000, typically under an annual contract with quote-based pricing. Bunny and CDN77 are far cheaper per gigabyte — $0.01–0.06/GB and $0.049/GB+ respectively — but the bill still scales linearly with every byte you serve. Cloudflare and Edge both drop egress fees entirely, and differ in what you pay for instead. Cloudflare uses plan tiers, with enterprise pricing available only through sales conversations. Edge meters requests: a free tier covers 3 deployments and 500,000 requests a month, then pay-as-you-go at $0.25 per million requests, with enterprise volume pricing published from $499/month including a 99.99% SLA. There's no minimum spend and no contract. Also compare what's bundled. DDoS protection, SSL certificates, and image optimisation are add-ons or higher-tier features on some providers; Edge includes them in the free tier, and delivers from 988 edge locations — more than any of the centralised networks in the table. How to choose Match the pricing model to your traffic shape, not just the headline rate. Heavy bandwidth Video, downloads, and image-rich sites move many bytes per request. Zero-egress pricing removes the largest cost, so request-based billing wins decisively. Unpredictable traffic If traffic can spike, per-GB pricing turns success into a billing risk. Prefer models with caps, free tiers, and no bandwidth metering. Enterprise scale At high volume, insist on published pricing and an SLA. Quote-only contracts make budgeting and comparison impossible. Price your workload on Edge Free for 500k requests a month, $0.25 per million after that — and bandwidth is never a line item. View CDN Pricing All CDN Comparisons Related articles Zero Egress Fees Explained 6 min How to Set Up a CDN 7 min Cost Optimization 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### CDN vs Edge Computing: What's the Difference? URL: https://edge.network/academy/cdn-vs-edge-computing/ Markdown: https://edge.network/academy/cdn-vs-edge-computing.md JSON: https://edge.network/json/academy/cdn-vs-edge-computing.json _CDNs cache and deliver content; edge computing runs code near users. Learn how they overlap, how they differ, and when you need each._ Back to Academy Information 7 min read CDN vs Edge Computing: What's the Difference? The two terms travel together and often get used interchangeably. They're related — but they solve different problems. The short answer A CDN (content delivery network) stores copies of your content on servers near users and delivers it fast. Edge computing runs your code on those same kinds of servers, processing requests and data close to where they originate. A CDN moves content to the edge; edge computing moves computation to the edge. And yes — edge computing does include CDNs. Caching and serving content near users is the original, simplest form of computing at the edge. Edge computing is the broader category; a CDN is the most widely deployed example of it. What a CDN does A CDN is a network of edge servers that cache your content — images, video, stylesheets, scripts, downloads — and serve it from the location nearest each user. The first request from a region pulls the file from your origin; every request after that is served from the local cache. The results are lower latency for users, dramatically less traffic hitting your origin, and resilience during spikes. CDNs are largely transparent to your application: you point a domain at the CDN, set caching rules, and the network does the rest. What edge computing does Edge computing generalises the same idea from content to computation. Instead of only caching files at the edge, you run workloads there: rendering pages, personalising responses, validating requests, transforming data, running AI inference. The work happens milliseconds from the user, and only results (or nothing at all) travel back to core infrastructure. This matters for anything a cache can't answer. A cached product page is a CDN problem; a shopping basket computed per user is an edge computing problem. On Edge, this means running virtual machines and GPU workloads on the edge network itself, alongside edge storage for the data those workloads need. CDN vs edge computing at a glance CDN Edge Computing Primary job Deliver content fast Run code and process data near users What lives at the edge Cached copies of files Applications, functions, and workloads Content served Static (and cached dynamic) content Dynamic, computed responses Typical workloads Images, video, scripts, downloads, APIs Personalisation, APIs, AI inference, real-time processing State Stateless caching Can hold state and run logic Relationship to origin Shields and accelerates the origin Can replace parts of the origin entirely When you need which Most products eventually want both — a CDN for delivery, edge compute for logic. Start with the problem in front of you. Start with a CDN when… Your site or app is slow for distant users Bandwidth or egress costs are climbing with traffic You serve media, downloads, or static assets at volume Your origin struggles during traffic spikes Add edge computing when… Responses must be computed per user or per request You need to process data close to where it is produced Round trips to a central server are too slow for the experience You want to run services in regions without deploying to multiple clouds How Edge provides both Because Edge is an edge cloud rather than a single product, CDN and edge computing run on the same network of 988 nodes. The CDN handles delivery with zero egress fees and a free tier of 500k requests a month. Compute and GPUs handle the workloads, priced per resource and billed hourly. Storage and DNS complete the picture. There's no separate platform to integrate and no transfer fees between services — content, code, and data share the same edge. See pricing for the full breakdown. Delivery and compute, one network CDN with zero egress fees, plus compute at the edge. Start free — no card required. Start Free Explore the CDN Related articles What is an Edge Network? 8 min What is the Edge Cloud? 7 min What is an Edge Server? 7 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### CLI Installation URL: https://edge.network/academy/cli-installation/ Markdown: https://edge.network/academy/cli-installation.md JSON: https://edge.network/json/academy/cli-installation.json _Install the Edge CLI on macOS, Linux, or Windows and start managing your cloud infrastructure from the terminal._ Back to Academy Getting Started 5 min read CLI Installation The Edge CLI is the fastest way to manage your infrastructure. Install it in seconds, authenticate, and start deploying. Quick Install The fastest way to install the Edge CLI is with our install script. It detects your operating system and architecture automatically. # macOS and Linux curl -fsSL https://edge.network/install.sh | sh # Windows (PowerShell, run as Administrator) iwr https://edge.network/install.ps1 -useb | iex Verify it worked: edge --version edge version 1.x.x Manual Install If you prefer not to pipe to shell, download the binary directly for your platform. macOS # Apple Silicon (M1/M2/M3/M4) curl -LO https://cli.edge.network/latest/edge-darwin-arm64 chmod +x edge-darwin-arm64 sudo mv edge-darwin-arm64 /usr/local/bin/edge # Intel Macs curl -LO https://cli.edge.network/latest/edge-darwin-amd64 chmod +x edge-darwin-amd64 sudo mv edge-darwin-amd64 /usr/local/bin/edge Linux # x86_64 curl -LO https://cli.edge.network/latest/edge-linux-amd64 chmod +x edge-linux-amd64 sudo mv edge-linux-amd64 /usr/local/bin/edge # ARM64 (Raspberry Pi, AWS Graviton, etc.) curl -LO https://cli.edge.network/latest/edge-linux-arm64 chmod +x edge-linux-arm64 sudo mv edge-linux-arm64 /usr/local/bin/edge Windows # PowerShell Invoke-WebRequest -Uri "https://cli.edge.network/latest/edge-windows-amd64.exe" -OutFile "edge.exe" # Move to a directory in your PATH, or add the directory to PATH Move-Item edge.exe C:\Windows\System32\edge.exe Authenticate Once installed, log in with your API key. You can generate one in the console under API Keys . # Interactive — prompts for your key edge auth login Enter your API key: ek_live_... Authenticated as My Project (you@example.com) # Non-interactive — pass the key directly (useful for CI/CD) edge auth login --key ek_live_your_key_here # Or via environment variable export EDGE_API_KEY=ek_live_your_key_here Check your authentication status at any time: edge auth status Status: Authenticated Account: My Project User: John Smith Email: you@example.com Plan: Startup Try it out Once authenticated, try a few commands to see what you've got: # See your account overview edge account # List all your resources edge compute list edge cdn list edge dns list edge storage list # Check your usage edge account usage Configuration The CLI stores its configuration at ~/.edge/config.json . You can customise defaults to save typing: # Set default output format to JSON edge config set output json # Set a default region for new resources edge config set default_region london # View all config edge config list Output formats The CLI supports three output formats, controlled with the -o flag: table Human-readable tables (default). Best for interactive use. json JSON output. Best for scripting and piping to other tools like jq . quiet Minimal output — just IDs and essential values. Best for shell scripts. Updating The CLI checks for updates automatically and will let you know when a new version is available. To update, just run the install command again: # Re-run the install script curl -fsSL https://edge.network/install.sh | sh # Or update from within the CLI edge update Next steps First Deployment Deploy your first resource CLI Reference Full command documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Configuring DNS Failover URL: https://edge.network/academy/dns-failover/ Markdown: https://edge.network/academy/dns-failover.md JSON: https://edge.network/json/academy/dns-failover.json _Edge DNS geo-routing and multiple A records. How to configure failover, and what's not yet available — health-check-based automatic failover with workarounds._ Back to Academy Featured Guide 8 min read Configuring DNS Failover How Edge DNS handles routing and failover — what works today, what doesn't yet, and practical workarounds for high availability. What DNS failover is DNS failover means automatically switching users to a backup server when the primary goes down. In an ideal setup, a health check detects failure, DNS stops returning the failed server's IP, and clients resolve to a healthy backup. Users get continuity without manual intervention. Edge DNS geo-routing Edge DNS supports geo-routing : routing different users to different servers based on their location. This works today. You can return IP A for users in Europe and IP B for users in the Americas, for example. Useful for multi-region deployments where you want users to hit the nearest origin. Configure geo-routing in the console or via the API. Add A (or AAAA) records with geographic filters and specify which regions resolve to which IPs. Multiple A records for round-robin You can add multiple A records for the same hostname. Resolvers typically round-robin between them. This distributes load across several servers but does not provide automatic failover: if one IP is down, clients may still be directed to it. DNS does not remove unhealthy IPs automatically. Monitoring DNS with Edge metrics Edge provides DNS metrics: query volume, response times, and resolution data. Use these to monitor DNS health and spot anomalies. They complement application-level monitoring but do not replace health checks for failover logic. Health-check-based failover: not yet implemented Important: Edge DNS does not yet support health-check-based automatic failover. The system does not detect when a server is down and remove it from DNS responses. If you add multiple A records, they remain in the rotation regardless of server health. Workarounds: External monitoring + API updates — Use an external monitoring service (e.g. UptimeRobot, Pingdom) to check your endpoints. When a failure is detected, call the Edge API to update DNS records — for example, remove the failed IP or add a CNAME to a backup. Requires automation (a script or Lambda) and API access. CDN as a resilient layer — Put Edge CDN in front of your origin. The CDN caches static content and can fail over to a backup origin if configured. For dynamic content, origin health still matters, but the CDN adds redundancy for cached responses. Manual failover — The console and CLI always allow manual record updates. For planned maintenance or known outages, switch records manually. Not automated, but reliable. Next steps High Availability DNS Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Console Quick Start URL: https://edge.network/academy/dashboard-quick-start/ Markdown: https://edge.network/academy/dashboard-quick-start.md JSON: https://edge.network/json/academy/dashboard-quick-start.json _From new account to a live, globally delivered site in about ten minutes — all from your browser. No terminal, no CLI, no config files._ Back to Academy Getting Started 10 minutes Console Quick Start From new account to a live, globally delivered site in about ten minutes — all from your browser. No terminal, no config files. STEP 1 Create your account Sign up here — it takes about two minutes. Verify your email and you land in the console with the free tier already active: CDN delivery, object storage, DNS hosting, and Shield bot protection, all usable immediately. Nothing in this guide costs money. The free tiers are hard-capped by design — if you ever reach a limit, things pause rather than start billing. Paid usage only happens when you explicitly opt in. STEP 2 Get your bearings Everything lives in the left sidebar. The five you'll use most: CDN : put any site or origin behind global delivery Compute : launch virtual machines in a few clicks DNS : host domains with fast, geo-routed resolution Storage : S3-compatible buckets for files and static sites Shield : bot protection for forms and pages Billing shows your balance and usage at any time, and Support is a real human — no ticket-bot maze. STEP 3 Put a site live The fastest first win: host a static site — a portfolio, a landing page, any folder of HTML — served worldwide over HTTPS. Create a bucket. Go to Storage , click Create Bucket , give it a name. Upload your files. Open the bucket and drag your site files in — make sure there's an index.html at the top level. Connect it to the CDN. Go to CDN , open your deployment, and in the Domains tab click Add Domain . Choose Storage Bucket as the origin type and select your bucket. Use a test domain. No domain handy? Pick a test.network subdomain during setup — it works instantly, no DNS changes needed. SSL is provisioned automatically within a minute. Open your new URL — your site is being served from the nearest of 2,200+ edge locations. Sharing a work-in-progress? Click the lock icon on the domain to require a username and password — a private preview URL you can share safely. More on password protection . STEP 4 Point a real domain (optional) When you're ready to use your own domain, add it in the same Domains tab. The console shows you exactly one DNS record to create — a CNAME pointing at cdn.edge.network — and verifies it for you. If your domain's DNS is hosted on Edge, there's an Add to Edge DNS button that creates the record in one click. Hosting DNS here is free — add your domain under DNS and point your registrar at our nameservers. STEP 5 Protect a form with Shield (optional) Got a contact or signup form getting bot spam? Go to Shield , create a widget, and copy the two-line snippet into your page. Shield verifies visitors are human with a privacy-first check — free, forever, on any site. Full Shield walkthrough → Where to go from here Everything you just did in the console can also be done from the command line, the REST API, or by an AI agent — same platform, pick your interface. CLI Quick Start — the same tour, from the terminal Video: CDN Setup First Deployment — launch a virtual machine Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Cost Optimization URL: https://edge.network/academy/cost-optimization/ Markdown: https://edge.network/academy/cost-optimization.md JSON: https://edge.network/json/academy/cost-optimization.json _Get the most value from Edge Network: right-sizing VMs, monitoring usage, CDN caching, storage lifecycle, annual billing discount, and when to upgrade vs optimise._ Back to Academy Best Practices 8 min read Cost Optimization Understand Edge's pricing model and practical ways to optimise spend without sacrificing performance. Edge's pricing model Edge uses per-resource pricing : compute is billed hourly for exactly the vCPU, RAM, and disk you configure, while DNS is free and CDN and Storage have free tiers. Crucially, egress is zero — you don't pay for bandwidth between your origin and the CDN, or from the CDN to users. That removes a major variable cost found on traditional clouds. Compute runs from a prepaid balance : you top up, usage is deducted hourly, and spending can never exceed what you've added. A surprise bill is impossible by design — the cost lever is simply how much you provision. Right-sizing VMs Don't over-provision. A small static site or API may run fine on 1 vCPU / 1 GB RAM. Check your VM's actual CPU and memory usage in the console under Compute → Metrics . If utilisation is consistently low (e.g. under 20%), resize to a smaller configuration. Edge lets you resize VMs without data loss — and because billing is per resource, dropping a vCPU or halving RAM cuts your hourly cost immediately. Scaling up is just as easy when you need it. Monitoring your spend The Billing page in the console shows your prepaid balance, hourly burn rate, and a breakdown of what each resource costs. The Usage page tracks vCPU, RAM, storage, CDN requests, and bandwidth over time. Auto top-up: enable it so your balance refills automatically before it runs out — the top-up amount scales with your usage, and running VMs are stopped if the balance ever reaches zero, so it's worth keeping headroom. When to optimise: if your hourly rate feels high, right-size VMs, enable CDN caching to reduce origin load, and clean up unused storage, snapshots, and idle machines. CDN caching and storage lifecycle CDN caching reduces origin load — fewer requests hit your VM, so you use fewer compute resources. Configure cache rules for static assets (long TTL) and bypass for dynamic content. See our Caching Strategies guide. Storage lifecycle: Clean up unused files. Delete old backups, test data, and temporary uploads. Use the storage dashboard to identify large buckets or paths. If you use versioning, consider lifecycle policies to expire old versions — check the Storage docs for supported options. Stopped isn't free — but it's cheap Stopping a VM stops the vCPU and RAM charges, but its disk (and any snapshots) keep billing while they exist — you're paying for the reserved storage. For dev machines you use occasionally, stopping between sessions cuts most of the cost. For machines you're done with, delete them and their snapshots to stop the meter entirely. The Usage page Make the Usage page a regular stop. It breaks down consumption by resource type and shows trends over time. Use it to spot growth before you hit limits and to validate that optimisation changes (e.g. caching, resizing) are having the expected effect. Set up alerts if available — we notify you when you approach plan limits so you can act before overages occur. Next steps High Availability Pricing Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Decentralised Cloud Storage Explained URL: https://edge.network/academy/decentralised-cloud-storage/ Markdown: https://edge.network/academy/decentralised-cloud-storage.md JSON: https://edge.network/json/academy/decentralised-cloud-storage.json _What decentralised cloud storage is, how it works, and how decentralisation improves security and privacy for sensitive data._ Back to Academy Information 8 min read Decentralised Cloud Storage Explained Object storage doesn't have to live in one company's data centres. Here's how decentralised storage works, and why the architecture itself improves security, privacy, and cost. What is decentralised cloud storage? Decentralised cloud storage stores your files across a network of independently operated nodes rather than in data centres owned by a single provider. Your data is encrypted and distributed across the network, and retrieved from the nearest available nodes when you need it. From your application's point of view it behaves like ordinary object storage — you upload, download, and manage files through a standard API. The difference is what happens underneath: instead of one company's facilities holding everything, capacity comes from a distributed network with no single point of failure. It is the storage layer of the wider decentralised cloud . How it works When you upload an object to a decentralised storage network, it is encrypted and written to nodes in the network, with the system tracking where each object lives and verifying the nodes that hold it. When you request the object back, the network retrieves it from the nearest healthy node. Node operators are rewarded for the capacity and reliability they provide, which keeps the network well supplied with fast storage. Edge Storage applies this model with a familiar developer experience: the API is S3-compatible, so the AWS SDKs, rclone, s3cmd, and your existing tooling work by changing the endpoint and keys. Storage runs on NVMe hardware with 99.99% durability, automatic versioning, and presigned URLs — you can learn more in What is Edge Storage? How decentralisation improves security and privacy Centralised storage concentrates risk. A single provider's facilities hold enormous quantities of data, which makes them the most valuable target an attacker can pick — a honeypot. One compromised system, one misconfigured bucket policy, or one insider with broad access can expose data at massive scale, and the industry's history of large breaches reflects exactly that concentration. Decentralisation changes the shape of the problem. Data on Edge is encrypted in transit with TLS and at rest with AES-256, so the operator of any individual node cannot read the objects passing through or stored on their hardware. And because data is distributed across many independent nodes rather than pooled in one place, there is no single system whose compromise exposes everything. Availability is a security property too. A centralised region outage can lock you out of your own data for hours; a distributed network simply routes around failed nodes. Access control remains fully in your hands, with per-key permissions and signed URLs for temporary, scoped access. Security properties of decentralised storage These properties come from the architecture itself, not from bolted-on features. Encryption Throughout Data is encrypted in transit with TLS and at rest with AES-256, so no individual node operator can read the objects their hardware stores. No Central Honeypot There is no single facility holding everything, which removes the high-value target that attackers focus on with centralised providers. Resilient by Architecture Losing a node does not mean losing data or availability — the network routes around failures automatically. You Control Access Access keys, fine-grained permissions, and signed URLs put you in charge of exactly who can read or write your data. Decentralised file storage for sensitive data For sensitive workloads — backups, user uploads, documents, media that must stay private — the practical checklist is the same whatever storage you choose: encryption at rest and in transit, tight access control, and the ability to get your data back quickly when you need it. Decentralised storage meets that checklist while removing two risks that centralised providers carry: the concentration of everyone's data behind one perimeter, and egress fees that quietly penalise you for retrieving your own files. Edge Storage charges zero egress fees at any scale, so restoring a backup or serving files costs nothing beyond the $0.015 per GB-month you pay for what you store — with the first 5 GB free. Centralised vs. decentralised storage Centralised Storage Decentralised Storage All data concentrated in a few large facilities Data distributed across many independent nodes A regional outage can take your data offline Failures are isolated and routed around Egress fees make retrieving your own data expensive Edge Storage charges zero egress fees One provider is a single point of trust Encryption means no operator sees your data Try decentralised storage S3-compatible object storage on NVMe with zero egress fees — free for 2 buckets and 5 GB. Create a Bucket Explore Edge Storage Related articles What is Edge Storage? 7 min Zero Egress Fees Explained 6 min What is a Decentralised Cloud? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Deploying a Node.js App on Edge Compute URL: https://edge.network/academy/deploy-nodejs-app/ Markdown: https://edge.network/academy/deploy-nodejs-app.md JSON: https://edge.network/json/academy/deploy-nodejs-app.json _Step-by-step guide to deploying a Node.js application on Edge Compute: VM creation, Node.js setup, PM2, Nginx, CDN, DNS, and monitoring._ Back to Academy Featured Guide 12 min read Deploying a Node.js App on Edge Compute Deploy a Node.js application on an Edge VM: create the server, install Node.js, run with PM2, put Nginx and CDN in front, then point your domain. 1. Create a VM Create a VM via the console or CLI. Choose ubuntu-24.04 and a plan with at least 2 vCPU / 4 GB RAM for Node.js production workloads. Smaller plans may run simple apps but can struggle under load. edge compute create --image ubuntu-24.04 --plan standard-2 Note the VM's public IP. SSH in with the provided key. 2. Install Node.js Install Node.js via nvm (recommended for version management) or apt : Option A — nvm: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash source ~/.bashrc nvm install 20 nvm use 20 Option B — apt: curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - sudo apt-get install -y nodejs 3. Clone your repo and install dependencies Clone your repository or upload your code (e.g. via scp ), then install dependencies: git clone https://github.com/you/your-app.git cd your-app npm install --production 4. Set up PM2 for process management Install PM2 globally and start your app. PM2 keeps it running, restarts on crash, and handles logs. sudo npm install -g pm2 pm2 start server.js --name "my-app" If your entry point is different (e.g. index.js or npm start ), adjust accordingly. Enable startup on boot: pm2 startup pm2 save 5. Configure Nginx as reverse proxy Install Nginx and add a reverse proxy config. Your Node app likely runs on port 3000; Nginx listens on 80 and forwards: sudo apt install -y nginx sudo nano /etc/nginx/sites-available/default Replace the default server block with: server { listen 80; server_name your-domain.com; location / { proxy_pass http://127.0.0.1:3000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } Enable and reload Nginx: sudo ln -sf /etc/nginx/sites-available/default /etc/nginx/sites-enabled/ sudo nginx -t && sudo systemctl reload nginx 6. Set up Edge CDN and DNS Create an Edge CDN deployment with your VM's IP as origin. Add your domain; Edge handles SSL. Point your domain via Edge DNS to the CDN endpoint. Users hit the CDN, which caches static assets and forwards dynamic requests to your VM. 7. Firewall and monitoring Firewall: Allow only 80 and 443 if traffic goes through CDN, or restrict SSH to your IP. Edge VMs may include default firewall rules; verify in the console. Monitoring: Use Edge metrics to watch VM CPU, memory, and network. Set up alerts for high utilisation. PM2 provides process-level monitoring: pm2 monit for a live dashboard. Next steps Security Hardening VM Configuration video Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Edge Network Security URL: https://edge.network/academy/edge-network-security/ Markdown: https://edge.network/academy/edge-network-security.md JSON: https://edge.network/json/academy/edge-network-security.json _What edge network security means: DDoS absorption, bot mitigation, TLS everywhere, and how a distributed network shrinks the attack surface._ Back to Academy Information 8 min read Edge Network Security The network edge is where your infrastructure first meets the open internet — which makes it the best place to stop attacks. Here's what securing the edge involves. What is edge network security? Edge network security means enforcing protection at the outer boundary of a network — the distributed nodes closest to users — rather than waiting for traffic to reach a central server or data centre. Threats like DDoS floods, bot traffic, and protocol-level attacks are identified and filtered at the edge, so only legitimate requests travel onward to your origin infrastructure. The logic is simple: every request has to pass through the edge anyway, so the edge is the earliest — and therefore cheapest and safest — point at which to inspect it. The further an attack travels into your infrastructure before being stopped, the more damage and cost it causes along the way. DDoS absorption at the edge A distributed denial-of-service attack works by overwhelming a target with more traffic than it can handle. Against a single server or even a single data centre, volume wins: the pipe fills up and legitimate users are locked out alongside the attackers. A distributed network inverts that maths. Attack traffic enters the network at many different nodes — each attacking machine is routed to its nearest entry point — so no single location bears the full load. Each node filters the malicious share of what it receives, and the attack is absorbed across the network's aggregate capacity rather than concentrated on your origin. This is why Edge includes DDoS protection with CDN and DNS at no extra cost: the architecture does most of the work. Bot mitigation Not all hostile traffic is a flood. Credential stuffing, card testing, scraping, spam signups, and inventory hoarding are carried out by bots that look, individually, like ordinary requests. Stopping them requires telling humans and automation apart — ideally without forcing real users through puzzles. Edge Shield does this with invisible verification: a lightweight proof-of-work runs in a background thread while risk signals are scored, and your server receives a 1–100 humanity score with every check. You decide what to do at each threshold — allow, step up, or block — and repeat offenders face exponentially harder challenges that make abuse expensive to sustain. It's free, uses no cookies or tracking, and works as a drop-in replacement for CAPTCHA. Our guides on protecting APIs from bots and securing login and signup flows cover the practical setup. Encryption everywhere Edge security also means making encryption the default, not an option. On Edge, all traffic is encrypted in transit with TLS 1.3 and HTTPS is enforced across all endpoints. CDN domains get certificates issued and renewed automatically, so there is no window where a misconfigured or expired certificate leaves traffic exposed. Data stored on the network is encrypted at rest with AES-256. DNS deserves particular attention, because it is the step attackers subvert to redirect users wholesale. Edge DNS supports DNSSEC signing to protect zones against spoofing and cache poisoning — see Is DNS Centralised or Decentralised? for more on DNS resilience. The layers of edge security Effective edge protection combines several defences, each stopping a different class of threat before it reaches your origin. DDoS Absorption Attack traffic is filtered at the nearest node, spread across the whole network instead of funnelled at your origin. Bot Mitigation Edge Shield verifies humans invisibly and scores every visitor 1–100, stopping automated abuse before it reaches your application. TLS Everywhere TLS 1.3 in transit, HTTPS enforced across all endpoints, and automatic certificates on every CDN domain. Distributed Architecture Thousands of independent nodes mean no central chokepoint for attackers to target — the network itself is the defence. How a distributed network shrinks the attack surface It might seem that thousands of nodes mean thousands of things to attack. In practice the opposite is true, because what matters is not the number of machines but the impact of compromising or disabling any one of them. In a centralised architecture, a successful attack on the core facility affects everyone. In a distributed edge network , a compromised or failed node is simply routed around, and encryption in transit and at rest means no individual node holds readable data worth stealing. There is also no single origin IP for attackers to discover and target directly: your infrastructure sits behind the network, which presents the same hardened, distributed face everywhere in the world. Combined with platform controls — role-based access, multi-factor authentication, and continuous monitoring, detailed on our security page — the edge becomes a shield in depth rather than a wall with one gate. For hardening the resources you run on Edge itself, see the Security Hardening guide. Protect your applications at the edge DDoS protection included with CDN and DNS, and free bot protection with Edge Shield. Start Free Explore Edge Shield Related articles Security Hardening 9 min What is an Edge Network? 7 min Bot Protection with Edge Shield 6 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### First Deployment URL: https://edge.network/academy/first-deployment/ Markdown: https://edge.network/academy/first-deployment.md JSON: https://edge.network/json/academy/first-deployment.json _Deploy your first resource on Edge Network. Step-by-step tutorial covering CDN, Compute, DNS, and Storage._ Back to Academy Getting Started 12 min read First Deployment You've got an account and the CLI installed. Now let's deploy something real. Pick your product and follow along. Before you start: Account created CLI installed Authenticated ( edge auth status ) Pick your starting point Each product can be deployed independently. Pick the one that matches what you need right now — you can always add more later. CDN Cache and deliver content globally. Best for websites, APIs, and static assets. Compute Launch a virtual machine. Best for apps, databases, and backend services. DNS Manage your domains with global anycast DNS. Best when you have a domain to point. Storage Store files with S3-compatible object storage. Best for media, backups, and assets. Deploy a CDN Put your website or API behind Edge's global CDN . Content is cached across 2,200+ locations and served from the nearest point to your users. 1. Create a deployment You need a name for the deployment and your origin URL — the server where your content actually lives (e.g. your app server, S3 bucket, or any HTTP endpoint). edge cdn create --name my-site --origin https://my-origin.example.com 2. Add a custom domain Add your domain to the deployment. Edge will automatically provision an SSL certificate. edge cdn domains add <deployment-id> --domain cdn.example.com --origin https://my-origin.example.com 3. Point your DNS Create a CNAME record at your DNS provider pointing your domain to cdn.edge.network . If your DNS is already on Edge, this is done automatically. cdn.example.com CNAME cdn.edge.network 4. Verify it's working Once DNS propagates (usually within a few minutes), your content will be served through Edge's CDN. # Check deployment status edge cdn list # Test with curl curl -I https://cdn.example.com You can also do all of this from the console . Launch a VM Spin up a virtual machine with dedicated resources. Choose your OS, size, and region. 1. Create the VM Pick a name, operating system, specs, and region. The VM will be ready in about 60 seconds. edge compute create \ --name my-server \ --image ubuntu-24.04 \ --size s-2vcpu-4gb \ --region london The CLI will display the root password and IP address once the VM is provisioned. 2. Connect via SSH Use the IP address and credentials from the creation output to connect. ssh root@<your-vm-ip> 3. Deploy your app Once connected, install your dependencies and deploy. Here's a quick example with Docker: # Install Docker curl -fsSL https://get.docker.com | sh # Run your app docker run -d -p 80:8080 your-image:latest 4. Monitor Check on your VM from the CLI or the console. # View VM details edge compute get <vm-id> You can also create VMs from the console , which includes a visual OS and region picker. Set up DNS Move your domain's DNS to Edge for sub-10ms resolution with global anycast. You'll need access to your domain registrar to update nameservers. 1. Add your domain edge dns create --domain example.com Edge will assign you a pair of nameservers (e.g. ns1.edge.network and ns2.edge.network ). 2. Update nameservers at your registrar Log in to your domain registrar (Namecheap, GoDaddy, Cloudflare, etc.) and replace the existing nameservers with the ones Edge assigned. This step varies by registrar but is usually under "DNS Settings" or "Nameservers." DNS propagation can take up to 48 hours, though most registrars update within minutes. Your existing records will continue working during the transition. 3. Add your records Once the zone is created, add your DNS records. Here are the most common: # Point your domain to a server edge dns records add <zone-id> --type A --name @ --data 203.0.113.50 # Add www subdomain edge dns records add <zone-id> --type CNAME --name www --data example.com # Add email (MX record) edge dns records add <zone-id> --type MX --name @ --data "10 mail.example.com" 4. Verify # List all records edge dns records list <zone-id> # Test resolution dig example.com @ns1.edge.network Create a storage bucket S3-compatible object storage with zero egress fees. Use it for media files, backups, static assets, or anything else you need to store. 1. Create a bucket edge storage create my-bucket 2. Upload files Upload individual files or entire directories. # Upload a single file edge storage cp ./photo.jpg my-bucket/images/photo.jpg # Sync a directory edge storage sync ./dist my-bucket/website/ 3. List and manage # List files in a bucket edge storage ls my-bucket/ # Download a file edge storage cp my-bucket/images/photo.jpg ./downloaded.jpg # Generate a share link (1 hour expiry) edge storage presign my-bucket/images/photo.jpg 4. Use with S3 SDKs Edge Storage is fully S3-compatible. Use any S3 SDK or tool (like the AWS CLI) by pointing it to https://storage.edge.network . Generate access keys in the console or see the SDK guides for code examples. What's next? You've deployed your first resource. Here are some things to explore next. Caching Strategies Optimise CDN performance Security Hardening Lock down your infrastructure Agentic Cloud Let AI agents manage your infra Console Manage everything visually Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Go SDK URL: https://edge.network/academy/sdk-go/ Markdown: https://edge.network/academy/sdk-go.md JSON: https://edge.network/json/academy/sdk-go.json _Use the AWS SDK for Go v2 with Edge Storage, and net/http for Compute, CDN, and DNS. Practical deployment script example._ Back to Academy API & SDK 10 min read Go SDK Edge does not provide its own Go SDK. For Storage, use the AWS SDK for Go v2 . For Compute, CDN, and DNS, use the REST API with net/http . How it works Edge Storage is S3-compatible. Use the aws-sdk-go-v2 S3 client with Edge's endpoint and static credentials. For Compute, CDN, and DNS, call the REST API at https://api.edge.network using the standard library net/http . Storage: Installing and configuring Add the AWS SDK for Go v2: go get github.com/aws/aws-sdk-go-v2 go get github.com/aws/aws-sdk-go-v2/config go get github.com/aws/aws-sdk-go-v2/service/s3 go get github.com/aws/aws-sdk-go-v2/credentials Configure the S3 client with Edge's endpoint (region us-east-1 , path-style access): package main import ( "context" "github.com/aws/aws-sdk-go-v2/aws" "github.com/aws/aws-sdk-go-v2/credentials" "github.com/aws/aws-sdk-go-v2/service/s3" ) func newEdgeS3Client(accessKey, secretKey string) *s3.Client { return s3.NewFromConfig(aws.Config{ Region: "us-east-1", Credentials: credentials.NewStaticCredentialsProvider( accessKey, secretKey, "", ), }, func(o *s3.Options) { o.BaseEndpoint = aws.String("https://storage.edge.network") o.UsePathStyle = true }) } Storage operations Create a bucket: _, err := client.CreateBucket(ctx, &s3.CreateBucketInput{ Bucket: aws.String("my-bucket"), }) Upload a file: _, err := client.PutObject(ctx, &s3.PutObjectInput{ Bucket: aws.String("my-bucket"), Key: aws.String("deployments/app.tar.gz"), Body: bytes.NewReader(data), ContentType: aws.String("application/gzip"), }) List objects: out, err := client.ListObjectsV2(ctx, &s3.ListObjectsV2Input{ Bucket: aws.String("my-bucket"), Prefix: aws.String("deployments/"), }) for _, obj := range out.Contents { fmt.Println(*obj.Key) } Compute, CDN, DNS: REST API with net/http For non-Storage products, use net/http : req, _ := http.NewRequest("GET", "https://api.edge.network/api/compute/vms", nil) req.Header.Set("Authorization", "Bearer "+apiKey) req.Header.Set("Content-Type", "application/json") resp, err := http.DefaultClient.Do(req) // decode resp.Body to struct Use the same pattern for CDN deployments, DNS zones and records, and VM power operations. See the API Reference for endpoints. Practical example: Deployment script A simple script that builds a tarball and uploads it to Edge Storage: func deploy(ctx context.Context, dir, bucket string) error { var buf bytes.Buffer gw := gzip.NewWriter(&buf) tw := tar.NewWriter(gw) // add files from dir to tar... tw.Close() gw.Close() key := fmt.Sprintf("deployments/%s.tar.gz", time.Now().Format("20060102-150405")) _, err := s3Client.PutObject(ctx, &s3.PutObjectInput{ Bucket: aws.String(bucket), Key: aws.String(key), Body: bytes.NewReader(buf.Bytes()), ContentType: aws.String("application/gzip"), }) return err } Extend this with API calls to trigger VM restarts or CDN purges after upload. Combine Storage and REST API usage for full automation. Next steps API Reference CLI Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### High Availability URL: https://edge.network/academy/high-availability/ Markdown: https://edge.network/academy/high-availability.md JSON: https://edge.network/json/academy/high-availability.json _Design for resilience on Edge Network: built-in CDN redundancy, anycast DNS, multi-VM architecture, CDN as origin shield, backups, monitoring, and planning for failure._ Back to Academy Best Practices 10 min read High Availability Edge's built-in redundancy and how to design your applications for resilience when things fail. Edge's built-in redundancy The CDN is deployed across 2,200+ locations worldwide. When a user requests content, they're routed to the nearest edge node. If that node fails or is congested, traffic is automatically rerouted to another node — no configuration required. DNS uses anycast: the same hostname resolves to multiple IPs, and users hit the closest responder. Geo-routing directs users to optimal regions based on their location. Edge handles this at the infrastructure level. Designing for resilience with multiple VMs For critical applications, run multiple VMs behind a load balancer or use the CDN to distribute traffic. If one VM fails, the others continue serving. Ensure your application is stateless or shares state (e.g. via a database) so any VM can handle any request. Use health checks: configure your load balancer or CDN origin to probe your VMs and stop sending traffic to unhealthy instances. This accelerates failover and prevents users from hitting broken nodes. Using the CDN as a shield for your origin Put the CDN in front of your origin (VM or storage). The CDN absorbs traffic spikes, DDoS attempts, and reduces load on your origin. Even if your origin goes down briefly, cached content can still be served from the edge. Configure appropriate cache TTLs so static content is served from edge during origin outages. Dynamic content will fail, but a partially working site is better than complete downtime. See Caching Strategies for tuning. DNS failover concepts Geo-routing — Edge DNS can route users to different origins based on their geographic location. This is a real feature today: configure regional records and users are directed to the closest or preferred endpoint. Health-check-based DNS failover — Automatically switch DNS to a backup origin when the primary fails health checks. This is not yet implemented on Edge; we're working on it and will announce when it's available. For now, manual DNS changes or third-party DNS services can provide failover if you need it. Automated backups and snapshots Take regular snapshots of your VMs. In the console, use Compute → Snapshots to create point-in-time backups. Schedule them via cron or automation — daily or weekly depending on how much change you can afford to lose. For storage buckets, enable versioning where supported, and consider cross-region or off-platform backups for critical data. Test restore procedures so you know they work when needed. Monitoring and alerts Set up monitoring for your VMs, CDN, and DNS. Use the console metrics, and integrate with external tools (e.g. UptimeRobot, Pingdom) for external health checks. Configure alerts for high error rates, latency spikes, and resource utilisation. Responding quickly to degraded performance reduces impact. Review the Status page ( edge.network/status ) for platform-wide incidents. What happens during CDN node failure? If an edge node fails, traffic is automatically rerouted to the next nearest node. Users may see a brief latency increase during failover, but service continues. The CDN is designed for no single point of failure. Origin failures are different — if your VM or storage goes down, uncached requests will fail. That's why we recommend multiple origins, health checks, and good caching for cacheable content. Planning for maintenance windows When you need to update your application or VM, plan for minimal disruption. Deploy to a new VM first, then switch traffic (load balancer, DNS, or CDN origin). Alternatively, use rolling updates if your orchestration supports it. Edge publishes planned maintenance on the Status page. Schedule your own maintenance during low-traffic periods and communicate with users in advance. Next steps What is the Agentic Cloud? Status Page Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### How to Set Up a CDN URL: https://edge.network/academy/how-to-set-up-a-cdn/ Markdown: https://edge.network/academy/how-to-set-up-a-cdn.md JSON: https://edge.network/json/academy/how-to-set-up-a-cdn.json _A step-by-step guide to setting up a CDN: create a deployment, configure your origin, point DNS with a CNAME, set caching rules, and go live with SSL._ Back to Academy Best Practices 7 min read How to Set Up a CDN Putting a CDN in front of your site takes about five minutes: create a deployment, point it at your origin, and update one DNS record. Here's the full walkthrough. Before you start A CDN sits between your users and your origin server, caching content at edge locations so most requests never touch your infrastructure. To set one up you need three things: an account with a CDN provider, a domain or subdomain you want to serve through the CDN (with access to its DNS settings), and an origin — the place your content actually lives, whether that's a web server, an S3-compatible bucket, or any URL that serves your files. The steps below use Edge CDN , where the free tier covers 3 deployments and 500,000 requests a month, but the process is broadly the same on any provider. The getting started documentation covers the same flow with screenshots. Step 1: Create an account and a deployment Sign up for an account , then navigate to CDN in the sidebar and click Deploy CDN . A deployment is a container for your CDN domains — you might have one per project or per environment. Give it a name (for example "Production") and click Create Deployment . Step 2: Add your domain and origin Click Add Domain and enter the domain you want to serve through the CDN — say cdn.yoursite.com — along with your origin URL, such as https://origin.yoursite.com or an S3 bucket URL. The origin is where the CDN fetches content it doesn't yet have cached. If you're hosting a static site, you can use an Edge Storage bucket as the origin type instead: upload your files, and the CDN serves them directly — including index.html for directory paths — with no web server to run at all. Step 3: Point your DNS at the CDN At your DNS provider, add a CNAME record for your subdomain pointing to cdn.edge.network . For cdn.yoursite.com , that means a CNAME with name cdn and target cdn.edge.network . For a root domain, use your DNS provider's CNAME flattening or ALIAS record support. Propagation usually takes one to five minutes. Then click Check DNS in the console to verify the record. If you manage your zone on Edge DNS , changes propagate globally in under five seconds. Step 4: Wait for SSL — then you're live Once DNS is verified, a free SSL certificate is issued automatically via Let's Encrypt — typically within 30 to 60 seconds. When the status shows SSL: active , your domain is being served through the CDN over HTTPS. No certificate files to manage, and renewal is automatic. Step 5: Configure caching rules Out of the box the CDN caches sensibly, but path-based cache rules let you tune behaviour per content type: long TTLs (7–30 days) for static assets like /assets/* , *.js , and *.css ; long TTLs with image optimisation enabled for /images/* ; and short TTLs or a bypass for /api/* and personalised pages. Our Caching Strategies guide covers the reasoning in depth. Step 6: Test, and purge when you need to Verify everything is working with a quick header check — curl -I https://cdn.yoursite.com/path/to/file.jpg — and look for x-cache: HIT , which confirms the response came from cache. When you deploy new content, use instant cache purging from the console to invalidate stale files; on Edge, purges take effect in under a second. What a CDN gives you from day one Once traffic flows through the CDN, these benefits apply immediately. Faster loads everywhere Content is served from the node nearest each user rather than from a single origin, cutting latency worldwide. Less origin load Cached requests never reach your server, so you can run smaller infrastructure and survive traffic spikes. Built-in protection DDoS mitigation and automatic SSL are included — attack traffic is absorbed at the edge before it reaches you. Real-time analytics Traffic, cache hit rates, and geographic distribution are visible from the console as they happen. Set up your CDN now Free for 3 deployments and 500k requests a month, with automatic SSL and zero egress fees. Create a Deployment Read the Docs Related articles Video: CDN Setup 5 min Caching Strategies 8 min Setting up a Multi-Region CDN 10 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Is DNS Centralised or Decentralised? URL: https://edge.network/academy/decentralised-dns/ Markdown: https://edge.network/academy/decentralised-dns.md JSON: https://edge.network/json/academy/decentralised-dns.json _DNS was designed to be distributed, but in practice a few providers serve most zones. What that concentration risks, and what decentralised DNS means._ Back to Academy Information 7 min read Is DNS Centralised or Decentralised? DNS was designed as a distributed system — yet in practice, a handful of providers answer most of the internet's queries. That gap between design and reality matters. The short answer: both By design, DNS is decentralised: it's a federated hierarchy in which root servers, top-level-domain registries, and millions of independent authoritative nameservers each answer for their own slice of the namespace, with no single machine holding the whole map. In practice, however, DNS hosting has become heavily concentrated — a small number of large providers serve the authoritative records for an enormous share of popular domains. So the honest answer is that the protocol is decentralised but the operational reality is increasingly centralised — and it's the operational reality that determines what happens when something breaks. Why concentration is a problem DNS is the step before everything else: if name resolution fails, your site is offline for practical purposes even though your servers are healthy. When many domains share one DNS provider, that provider becomes a single point of failure for all of them at once. The pattern has played out repeatedly — most famously in the 2016 DDoS attack on the DNS provider Dyn, which took major sites including Twitter, Spotify, and Reddit offline for hours, and in subsequent outages at other large providers that each removed a visible chunk of the web. Concentration also raises subtler risks: a single provider is a bigger, more attractive target for attackers; a configuration error propagates to every zone the provider hosts; and censorship or policy decisions at one company can affect a large fraction of the namespace. What decentralised DNS means Decentralised DNS pushes the infrastructure that answers queries back out toward the edges of the network. Instead of resolving from a handful of large facilities, queries are answered by a distributed network of nodes, with Anycast routing sending each query to the nearest one. The failure of any node — or any whole region — leaves the rest of the network answering as normal, and a volumetric attack has no single chokepoint to saturate. Practical resilience follows from the same principle applied at the zone level: serving DNS from a distributed network, signing zones with DNSSEC so answers can't be forged, and using health checks with automatic failover so traffic moves away from failed origins without human intervention. How Edge DNS works Edge DNS runs on the same distributed network as the rest of the platform, with unlimited DDoS mitigation included. Global Anycast Queries are answered from the nearest of 50+ locations worldwide, with sub-10ms average resolution. Instant Propagation Record changes propagate globally in under 5 seconds — no waiting for updates to take effect. Automatic Failover Health checks are included, and traffic is routed away from unhealthy origins automatically. DNSSEC One-click zone signing protects domains from spoofing and cache poisoning. DNS resilience in practice Edge DNS is free to use — up to 50 zones with unlimited records and a million queries a month per zone included, with no per-domain fees. Health checks and geo-routing are included rather than sold as extras, and the DNS Examiner will analyse a zone's security, email deliverability, and nameserver configuration in one click. You can see how it stacks up against Cloudflare, Route 53, and DNSimple on the DNS comparison page . Whichever provider you use, the lesson of the last decade of DNS outages is the same: treat DNS as critical infrastructure, prefer providers with distributed Anycast networks and DDoS protection, enable DNSSEC, and configure failover before you need it. Our DNS Failover guide walks through the setup. Put your zones on a distributed network Fast anycast DNS with DNSSEC, health checks, and failover — free for up to 50 zones. Add Your First Zone Explore Edge DNS Related articles DNS Failover 8 min Edge Network Security 8 min What is an Edge Network? 7 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### JavaScript SDK URL: https://edge.network/academy/sdk-javascript/ Markdown: https://edge.network/academy/sdk-javascript.md JSON: https://edge.network/json/academy/sdk-javascript.json _Use the AWS S3 SDK with Edge Storage, and fetch() for Compute, CDN, and DNS. Practical examples for uploading files and generating presigned share links._ Back to Academy API & SDK 10 min read JavaScript SDK Edge does not provide its own JavaScript SDK. For Storage, use the standard AWS S3 SDK. For Compute, CDN, and DNS, use the REST API with fetch() . How it works Edge Storage is S3-compatible. Use @aws-sdk/client-s3 with Edge's endpoint and credentials. For Compute, CDN, and DNS, call the REST API at https://api.edge.network using fetch() with your API key. Storage: Installing and configuring Install the AWS S3 client and presigner (for presigned URLs): npm install @aws-sdk/client-s3 @aws-sdk/s3-request-presigner Configure the client with Edge's Storage endpoint and your access credentials (found in Console → Storage → Access Keys ): import { S3Client, CreateBucketCommand, PutObjectCommand, GetObjectCommand, ListObjectsV2Command } from '@aws-sdk/client-s3' import { getSignedUrl } from '@aws-sdk/s3-request-presigner' const s3 = new S3Client({ region: 'us-east-1', endpoint: 'https://storage.edge.network', forcePathStyle: true, credentials: { accessKeyId: process.env.EDGE_ACCESS_KEY, secretAccessKey: process.env.EDGE_SECRET_KEY } }) Use forcePathStyle: true — Edge Storage requires path-style access (e.g. storage.edge.network/bucket/key ). Storage operations Create a bucket: await s3.send(new CreateBucketCommand({ Bucket: 'my-bucket' })) Upload a file: await s3.send(new PutObjectCommand({ Bucket: 'my-bucket', Key: 'uploads/image.jpg', Body: fileBuffer, ContentType: 'image/jpeg' })) List objects: const { Contents } = await s3.send(new ListObjectsV2Command({ Bucket: 'my-bucket', Prefix: 'uploads/' })) Download a file: const { Body } = await s3.send(new GetObjectCommand({ Bucket: 'my-bucket', Key: 'uploads/image.jpg' })) const data = await Body.transformToByteArray() Generate a presigned URL: import { getSignedUrl } from '@aws-sdk/s3-request-presigner' const url = await getSignedUrl(s3, new GetObjectCommand({ Bucket: 'my-bucket', Key: 'uploads/image.jpg' }), { expiresIn: 3600 }) Compute, CDN, DNS: REST API with fetch For non-Storage products, use fetch() against the Edge API: const response = await fetch('https://api.edge.network/api/compute/vms', { headers: { 'Authorization': `Bearer ${process.env.EDGE_API_KEY}`, 'Content-Type': 'application/json' } }) const { data } = await response.json() Use the same pattern for CDN deployments, DNS zones and records, and VM power operations. See the API Reference for endpoint details. Practical example: Upload image and get share link Here's a complete example that uploads an image and returns a presigned share link: async function uploadAndShare(buffer, filename) { const key = `uploads/${Date.now()}-${filename}` await s3.send(new PutObjectCommand({ Bucket: 'my-bucket', Key: key, Body: buffer, ContentType: 'image/jpeg' })) const shareUrl = await getSignedUrl(s3, new GetObjectCommand({ Bucket: 'my-bucket', Key: key }), { expiresIn: 86400 }) // 24 hours return shareUrl } Call this from an API route or serverless function. The returned URL can be shared with users — they can view or download the file without authenticating, until the URL expires. Next steps Python SDK Storage Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Machine Learning at the Edge URL: https://edge.network/academy/machine-learning-at-the-edge/ Markdown: https://edge.network/academy/machine-learning-at-the-edge.md JSON: https://edge.network/json/academy/machine-learning-at-the-edge.json _What machine learning at the edge means, why latency matters for AI workloads, and how to deploy models on distributed GPU and compute infrastructure._ Back to Academy Information 8 min read Machine Learning at the Edge AI workloads are moving out of central data centres and closer to users. Here's what edge ML means, why latency is the driving force, and how to deploy models on distributed infrastructure. What is machine learning at the edge? Machine learning at the edge means running ML models — most often inference, the stage where a trained model makes predictions — on infrastructure located close to where the data is generated and the results are consumed, rather than in a distant central cloud region. Training usually stays in large clusters, because it needs sustained access to big datasets and lots of parallel compute. Inference is different: it happens on every user request, its output is needed immediately, and it benefits enormously from being nearby. That split — train centrally, infer at the edge — is the pattern behind most edge ML deployments, and it mirrors how CDNs and edge computing divide work more generally. Why latency matters for AI workloads An inference request's response time has two parts: the time the model spends computing, and the time the request and response spend travelling over the network. You can buy faster hardware to attack the first part, but the second is governed by distance. A user in Singapore calling a model hosted in Virginia pays a transcontinental round trip on every single request, before the model does any work at all. For interactive AI — chat interfaces, voice assistants, live translation, recommendations, fraud checks in a payment flow — that network tax is the difference between an experience that feels instant and one that feels sluggish. Streaming LLM responses makes it worse, not better: every token round trip inherits the same latency floor. Moving inference to nodes near the user removes most of the travel time. It also reduces how much raw data has to cross the internet: a computer-vision system that analyses video at the edge sends back results, not footage. GPU compute at the edge Modern models — particularly LLMs and vision models — run far faster on GPUs than CPUs, so edge ML at scale means putting GPU capacity into the distributed network itself. This is a natural fit for a decentralised platform: the same model that distributes nodes for content delivery can distribute GPU nodes for inference. Edge is bringing GPU instances to its network, with support for multiple vendors including NVIDIA, AMD, and Intel, billed hourly with no long-term commitments. In the meantime, Edge Compute VMs run CPU-based inference today, and smaller quantised models are genuinely practical on CPU. The economics matter as much as the hardware. Model serving moves a lot of data, and on traditional clouds that means egress charges on every response. Edge charges zero egress fees , so serving predictions — or shipping model weights between environments — carries no bandwidth cost. See AI & Machine Learning on Edge for the full picture. Deploying models: Ollama, vLLM, and llama.cpp You don't need a bespoke ML platform to serve models on edge infrastructure. The open source ecosystem has settled on a few excellent serving tools, each of which deploys cleanly to an Edge VM: Ollama The simplest way to run open models like Llama and Mistral on your own VM, with a clean local API. vLLM High-throughput serving for production LLM workloads, with efficient batching and an OpenAI-compatible API. llama.cpp Lightweight, CPU-friendly inference for quantised models — useful where GPU capacity is unnecessary or unavailable. The workflow is the same in each case: provision a VM sized for your model, install the serving tool, load your weights, and put the endpoint behind Edge CDN or Edge DNS for routing and TLS. Why run ML at the edge? The gains compound: faster responses, lower bills, and less data in transit. Lower Latency Inference happens close to the user, cutting the round trip that dominates response time for real-time AI features. Lower Cost Moving less data to and from a central cloud means less bandwidth spend — and on Edge, egress is free entirely. Better Privacy Data can be processed near where it is generated rather than shipped to a distant region, reducing exposure in transit. Resilience Distributed inference keeps working when any single location fails — there is no central endpoint to go down. Run your models on Edge Deploy inference on Edge Compute today, and join the waitlist for GPU instances. Get Started AI on Edge Related articles CDN vs Edge Computing 7 min What is an Edge Server? 6 min What Does Edge Infrastructure Cost? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Migrating from AWS to Edge URL: https://edge.network/academy/migrating-from-aws/ Markdown: https://edge.network/academy/migrating-from-aws.md JSON: https://edge.network/json/academy/migrating-from-aws.json _Step-by-step guide to migrating from AWS to Edge Network: DNS, storage, CDN, and compute. Zero egress fees, simpler pricing, and no vendor lock-in._ Back to Academy Featured Guide 15 min read Migrating from AWS to Edge How to migrate your infrastructure from AWS to Edge Network: DNS, storage, CDN, and compute — with zero egress fees and simpler pricing. Why migrate? Edge offers several practical advantages over AWS for many workloads: Zero egress fees — No charges for data leaving the network. AWS egress costs can add up quickly; Edge does not charge for egress. Simpler pricing — Flat, predictable rates for CDN, compute, storage, and DNS. No region-specific pricing tables or surprise billing. No vendor lock-in — Standard protocols (S3-compatible storage, HTTP origins). Move data in and out without proprietary APIs. Better performance in many regions — 2,200+ edge locations mean users often get lower latency than routing through AWS regions. Planning your migration Map your current AWS usage to Edge equivalents: EC2 → Edge Compute (VMs) CloudFront → Edge CDN Route 53 → Edge DNS S3 → Edge Storage (S3-compatible API) Assess which services you actually use. Many workloads only need CDN and storage; compute migration is more involved. Start with the lowest-risk components — typically DNS and CDN — then move storage and compute. Step-by-step migration 1. Set up your Edge account Create an account at edge.network, install the CLI, and configure your API key. See the First Deployment guide for setup. 2. Migrate DNS first (lowest risk) Create your zone in Edge DNS and replicate your records from Route 53. Lower TTLs 24–48 hours before cutover to minimise propagation delay. Switch nameservers when ready. DNS cutover is reversible — you can point back to Route 53 if needed. 3. Move storage Edge Storage is S3-compatible. Use the AWS CLI with --endpoint-url to sync buckets: aws s3 sync s3://your-aws-bucket s3://your-edge-bucket \ --endpoint-url https://storage.edge.network Update your application to use the Edge Storage endpoint. If your app already uses the S3 API, change the endpoint and credentials; the code stays the same. 4. Set up CDN Create an Edge CDN deployment pointing to your existing origin (AWS or elsewhere). Add your domain, configure SSL, and test. You can run CDN in front of AWS origin initially — a useful hybrid step — then switch the origin to Edge Storage or an Edge VM once ready. 5. Migrate compute last (most complex) Spin up Edge VMs, migrate your application code and data, configure networking, and test. Use load balancing or multiple VMs if you need redundancy. Cut over traffic gradually — e.g. by shifting a percentage of users or a subset of regions. Cost comparison and what's different Edge pricing is straightforward: no egress fees, no region-specific multipliers, no IAM complexity. You pay for usage (GB stored, requests served, compute hours) at flat rates. Compare your AWS bill — especially egress and data transfer — against Edge's pricing page . What's simpler: No IAM policies, no VPC configuration, no region-specific pricing. Deploy and scale without wrestling with AWS's organisational layers. What Edge doesn't have... yet Honesty matters. Edge does not yet offer everything AWS does: Lambda / serverless — Not available. Use Edge VMs for compute-heavy or long-running workloads. Managed databases — No RDS equivalent. Run your own database on a VM, or use an external managed service. IAM policies — Permission model is simpler; fine-grained IAM is not available. If your stack depends on Lambda, RDS, or complex IAM, a full migration may not be viable today. Consider a hybrid approach: use Edge for CDN, storage, and DNS; keep AWS for serverless or managed databases until Edge expands its offerings. Next steps Cost Optimisation First Deployment Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Migrating from reCAPTCHA to Edge Shield URL: https://edge.network/academy/migrating-from-recaptcha/ Markdown: https://edge.network/academy/migrating-from-recaptcha.md JSON: https://edge.network/json/academy/migrating-from-recaptcha.json _Replace Google reCAPTCHA with Edge Shield in under an hour: swap the script tag, update one server call, and map v3 scores to the 1–100 humanity score. Free, private, no puzzles._ Back to Academy Migration Guide 10 min read Migrating from reCAPTCHA Swap Google reCAPTCHA for Edge Shield in under an hour: one script tag, one server call, and your visitors never squint at traffic lights again. Why teams are moving Three pressures usually trigger the migration. Conversion : image challenges measurably cost signups, and AI now solves them better than humans do, so the friction buys less protection every year. Privacy : reCAPTCHA sets Google cookies and feeds behavioural data across sites, which drags your forms into GDPR consent territory. Cost : the free tier caps at 10,000 assessments a month — real traffic graduates to Enterprise pricing. Edge Shield is free without limits, collects no per-visitor data, and replaces puzzles with an invisible proof-of-work plus a 1–100 humanity score your server acts on. reCAPTCHA Edge Shield Human experience Image puzzles when suspicious (v2); silent but score-gated (v3) Invisible; at worst a single click — never a puzzle Score 0.0–1.0 (v3 only) 1–100 on every verification, all modes Privacy Google cookies and tracking across sites No cookies, no fingerprint DB, no per-visitor data Pricing Free to 10k assessments/mo, then paid (Enterprise) Free forever, unlimited Consent banners Usually required under GDPR Nothing collected, nothing to consent to AI agents Treated as attacks Cryptographically identified and routable 1. Create your Shield widget In the console , go to Shield → Create Widget . Name it, optionally pin it to your hostnames, and keep the default managed mode — it behaves like reCAPTCHA v2's "invisible" mode, escalating to a single click only for suspicious traffic. You'll get a sitekey (public) and a secret (server-side, shown once), directly replacing your reCAPTCHA key pair. 2. Swap the client-side snippet <!-- Before: reCAPTCHA --> <script src="https://www.google.com/recaptcha/api.js" async defer></script> <div class="g-recaptcha" data-sitekey="6Lc..."></div> <!-- After: Edge Shield --> <script src="https://shield.edge.network/api.js" defer></script> <div class="edge-shield" data-sitekey="es_..."></div> The token lands in a hidden edge-shield-response input on submit. If you used the JS API ( grecaptcha.render , grecaptcha.execute ), the equivalents are edgeShield.render() and edgeShield.execute() — see the JS API docs for SPA patterns. 3. Update the server-side verification Same pattern, different URL and field name. The response shape is deliberately familiar — success , hostname , challenge_ts , error-codes : // Before: reCAPTCHA siteverify const res = await fetch('https://www.google.com/recaptcha/api/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: `secret=${SECRET}&response=${req.body['g-recaptcha-response']}`, }) const { success, score } = await res.json() // score: 0.0 – 1.0 // After: Edge Shield siteverify const res = await fetch('https://shield.edge.network/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: `secret=${SECRET}&response=${req.body['edge-shield-response']}`, }) const { success, score } = await res.json() // score: 1 – 100 Score mapping: if you gate on reCAPTCHA v3 scores, multiply your thresholds by 100 — a 0.5 cutoff becomes 50 . One behavioural difference to know: Shield tokens are strictly single-use, so validate at the moment you process the form, not ahead of it. 4. Verify, then remove Google Test a real submission and watch the verification land in your widget's metrics in the console. Submit with the token replayed (or missing) and confirm your server rejects it. Remove the reCAPTCHA script tag, keys, and any google.com/recaptcha entries from your CSP. If your privacy policy or consent banner mentioned reCAPTCHA, simplify it — Shield collects nothing that needs consent. Migrating from Cloudflare Turnstile instead? That's even closer — Shield supports a drop-in compatibility mode. See the Turnstile migration guide . Next steps Try the live demo See the verification flow end to end Bot Protection with Edge Shield Score bands, verified agents, best practices Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Password-Protected CDN Domains URL: https://edge.network/academy/password-protected-cdn-domains/ Markdown: https://edge.network/academy/password-protected-cdn-domains.md JSON: https://edge.network/json/academy/password-protected-cdn-domains.json _Protect any Edge CDN domain with a username and password. Share dev builds and staging sites on a public URL without making them public — enforced at the edge, ahead of the cache._ Back to Academy Security 6 min read Password-Protected CDN Domains Ship a dev build to a Storage bucket, put it on a test domain, and share the URL without sharing it with the whole internet. Sharing without publishing Every team hits this at some point: you have a build that needs to be seen — by a client, a designer, a stakeholder — but it is not ready for the world. The usual workarounds are all bad in their own way. Obscure URLs leak. VPNs are friction for outsiders. Authentication baked into the app itself means writing code that will be thrown away. Password protection on Edge CDN solves this with the oldest, most universally supported mechanism on the web: HTTP Basic Auth . Any CDN domain can require a username and password. Visitors get their browser's native credential prompt before anything is served, and everyone with the credentials gets the full site over HTTPS at full CDN speed. No app changes, no extra infrastructure, no per-seat licences. How it works The credential check runs on the edge node itself, ahead of everything else in the request pipeline — before the cache lookup and before any origin fetch. That ordering matters: many CDN-level protections only guard origin fetches, which means content already sitting in cache can slip out unauthenticated. On Edge, protected content is never served without credentials, including cached content . Enforced at the edge, ahead of the cache — a request without valid credentials gets a 401 and the browser's login prompt. Nothing is served, cached or otherwise. Passwords stored as bcrypt hashes — the plaintext is hashed the moment you save it. Edge nodes only ever receive the hash, never the password. Verified credentials are cached at the edge — the deliberately slow bcrypt check runs once per credential, not per request, so authenticated traffic runs at full CDN speed. Failed attempts pay the full bcrypt cost every time — the hash's ~100ms work factor doubles as built-in brute-force rate limiting. SSL issuance and renewal keep working — certificate validation requests are exempt from the check, so protected domains still get automatic HTTPS. Setting it up Protection is one click from the Domains tab of any CDN deployment: Open your deployment's Domains tab in the console Click the lock icon on the domain you want to protect Enable Require a username and password and set the credentials Save — protection is live on the edge within seconds A protected domain shows a Protected badge in the domain list. To change the password, open the same modal and enter a new one; to change just the username, leave the password blank and the existing one is kept. Turning protection off is the same checkbox in reverse. The private dev preview recipe The pattern this feature was built for, end to end: Upload the build to an Edge Storage bucket — from the console, the CLI, or CI Add a domain to a CDN deployment with the bucket as its origin (a test.network subdomain works out of the box, no DNS setup needed) Enable password protection on the domain Share the URL and credentials — recipients open the link, enter the username and password once, and browse the build over HTTPS For scripted access — CI smoke tests, automated screenshots — pass credentials the standard Basic Auth way: curl -u preview:your-password https://dev.yoursite.test.network/index.html When the build goes public, flip protection off and the same domain serves the same content to everyone — nothing to migrate. When to use something else Basic Auth is a shared secret — everyone uses the same username and password, and revoking access means changing it for everyone. That is exactly right for dev previews, staging sites, and internal tools with a handful of users. It is not a substitute for real user accounts, per-user permissions, or audit trails in a production application. If what you need is protection from bots rather than from people, that is a different tool: Edge Shield verifies that visitors are human without asking anyone for a password. Next steps Domains & SSL Documentation Caching Strategies Security Hardening Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Protecting APIs from Bot Abuse URL: https://edge.network/academy/protecting-apis-from-bots/ Markdown: https://edge.network/academy/protecting-apis-from-bots.md JSON: https://edge.network/json/academy/protecting-apis-from-bots.json _Shield isn't just for forms. Attach humanity tokens to API requests, verify them with siteverify or locally against the JWKS endpoint, and identify signed AI agents with agentverify._ Back to Academy Security 10 min read Protecting APIs from Bot Abuse Scraping, enumeration, and free-tier abuse don't come through your forms — they hit your endpoints directly. Edge Shield's tokens work there too, with a verification path fast enough for API traffic. Forms are the front door. APIs are every other door. Once your web app moves logic into fetch calls — search, autocomplete, pricing lookups, content feeds — those endpoints become the cheapest way to abuse your service. A scraper doesn't render your page or fill in your form; it calls /api/search ten thousand times. Rate limiting helps but is blunt: attackers rotate IPs, and your heaviest legitimate users look exactly like abusers by request count alone. What's missing is the same question Shield answers on forms — is a human driving this? — attached to each request. 1. Attach a Shield token to API calls The widget's JavaScript API can produce tokens on demand, not just on form submit. Request one and send it in a header your server checks: // Render an invisible widget once — it verifies in the background // and keeps its token fresh automatically const widgetId = edgeShield.render(document.getElementById('shield'), { sitekey: 'es_your_sitekey', mode: 'invisible', }) // Attach the current token to each protected request await fetch('/api/search', { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-Edge-Shield-Token': edgeShield.getResponse(widgetId), }, body: JSON.stringify({ query }), }) The verification runs invisibly in a background thread — your users never see anything. See the JS API docs for the full programmatic interface. 2. Pick the right verification path For forms, one call to siteverify per submission is nothing. For an API taking hundreds of requests a second, a network round trip per request is real latency. Shield gives you a second option: tokens are Ed25519-signed JWTs , and the public key is published at a standard JWKS endpoint — so your server can verify them locally, with zero network calls. import { createRemoteJWKSet, jwtVerify } from 'jose' const JWKS = createRemoteJWKSet( new URL('https://shield.edge.network/.well-known/jwks.json') ) // Zero network calls per request — the key set is cached async function verifyOffline(token) { const { payload } = await jwtVerify(token, JWKS, { issuer: 'edge-shield', subject: process.env.SHIELD_SITEKEY, // REQUIRED — binds tokens to YOUR widget }) // Narrow the replay window: reject tokens older than 60s if (Date.now() / 1000 - payload.iat > 60) throw new Error('stale token') return payload.score // 1–100 } The trade-off: offline verification cannot enforce single-use . The ledger of spent tokens lives on Shield's servers, so a token verified offline stays valid for its full five-minute lifetime, however many times it's presented. The iat age check above narrows that window, but the rule of thumb is: Offline for high-throughput, lower-stakes endpoints — search, previews, read APIs — where latency matters more than strict single-use. siteverify for anything a replayed token shouldn't touch — signups, payments, mutations. It's the only path with a strict single-use guarantee. Full details, including key rotation behaviour, are in the offline verification docs . 3. Don't lock out the automation you want Some clients hitting your API without a widget token are exactly who you want: AI agents shopping or researching on behalf of real customers. Agents that sign their requests with Web Bot Auth can be identified without any widget at all — forward the signature headers to agentverify : // A signed agent request hit your API directly — no widget involved. // Forward its signature headers and Shield verifies the identity. const res = await fetch('https://shield.edge.network/agentverify', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ secret: process.env.SHIELD_SECRET, authority: req.headers.host, headers: { 'signature-agent': req.headers['signature-agent'], 'signature-input': req.headers['signature-input'], 'signature': req.headers['signature'], }, }), }) const { success, agent } = await res.json() if (success && agent.verified) allowFor(agent.domain) So the full policy for an API endpoint becomes: valid Shield token with a decent score → human, allow. Valid Web Bot Auth signature → known agent, allow (with its own rate tier if you like). Neither → the automation that refused to identify itself, which is the traffic you wanted to stop. Verified AI Agents with Web Bot Auth covers this in depth. Next steps Offline verification docs JWKS, claims, key rotation Verified AI Agents Web Bot Auth and agent policy Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Python SDK URL: https://edge.network/academy/sdk-python/ Markdown: https://edge.network/academy/sdk-python.md JSON: https://edge.network/json/academy/sdk-python.json _Use boto3 with Edge Storage, and the requests library for Compute, CDN, and DNS. Practical backup script example._ Back to Academy API & SDK 10 min read Python SDK Edge does not provide its own Python SDK. For Storage, use boto3 . For Compute, CDN, and DNS, use the REST API with requests . How it works Edge Storage is S3-compatible. Use boto3 (the AWS SDK for Python) with Edge's endpoint and credentials. For Compute, CDN, and DNS, call the REST API at https://api.edge.network using the requests library. Storage: Installing and configuring Install boto3 (and requests for REST API calls): pip install boto3 requests Configure the S3 client with Edge's Storage endpoint (region us-east-1 , path-style access): import boto3 import os s3 = boto3.client( 's3', endpoint_url='https://storage.edge.network', region_name='us-east-1', aws_access_key_id=os.environ['EDGE_ACCESS_KEY'], aws_secret_access_key=os.environ['EDGE_SECRET_KEY'], config=boto3.session.Config( signature_version='s3v4', s3={'addressing_style': 'path'} ) ) Create the bucket with a location constraint or omit it for Edge: s3.create_bucket(Bucket='my-bucket') Storage operations Upload a file: s3.upload_fileobj( open('local/file.txt', 'rb'), 'my-bucket', 'backups/file.txt', ExtraArgs={'ContentType': 'text/plain'} ) List objects: paginator = s3.get_paginator('list_objects_v2') for page in paginator.paginate(Bucket='my-bucket', Prefix='backups/'): for obj in page.get('Contents', []): print(obj['Key']) Download a file: s3.download_file('my-bucket', 'backups/file.txt', 'local/file.txt') Generate a presigned URL: url = s3.generate_presigned_url( 'get_object', Params={'Bucket': 'my-bucket', 'Key': 'backups/file.txt'}, ExpiresIn=3600 ) Compute, CDN, DNS: REST API with requests For non-Storage products, use requests : import requests resp = requests.get( 'https://api.edge.network/api/compute/vms', headers={ 'Authorization': f"Bearer {os.environ['EDGE_API_KEY']}", 'Content-Type': 'application/json' } ) data = resp.json() Use the same pattern for CDN, DNS, and VM operations. See the API Reference for endpoints. Practical example: Backup script This script uploads local files to Edge Storage with dated prefixes: from pathlib import Path from datetime import datetime def backup_to_edge(local_dir: str, bucket: str, prefix: str = 'backups'): """Upload directory tree to Edge Storage with timestamp prefix.""" base = Path(local_dir) timestamp = datetime.utcnow().strftime('%Y%m%d-%H%M%S') for path in base.rglob('*'): if path.is_file(): key = f"{prefix}/{timestamp}/{path.relative_to(base)}" key = key.replace('\\', '/') s3.upload_file(str(path), bucket, key) print(f"Uploaded {path} -> {key}") backup_to_edge('./data', 'my-bucket') Run it via cron for scheduled backups. You can add lifecycle rules or expiry in the console to retain only recent backups. Next steps Go SDK Storage Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Quick Start Guide URL: https://edge.network/academy/quick-start/ Markdown: https://edge.network/academy/quick-start.md JSON: https://edge.network/json/academy/quick-start.json _Get up and running with Edge Network in 10 minutes. Step-by-step guide to deploying your first resource._ Back to Academy Getting Started 10 minutes Quick Start Guide Go from zero to deployed in 10 minutes. This guide will walk you through creating an account, installing the CLI, and deploying your first resource. Prerequisites: A valid email address A credit/debit card for trial Terminal access (optional) 01 Create Your Account Sign up for Edge Network in under 2 minutes. Free — no card required. Create Account 02 Install the CLI The Edge CLI is the fastest way to manage your infrastructure. Install it with a single command. Terminal # macOS / Linux curl -fsSL https://edge.network/install.sh | sh # Windows (PowerShell) iwr https://edge.network/install.ps1 -useb | iex # Verify installation edge --version 03 Authenticate Log in to your Edge account from the command line. Terminal # Login to your account edge auth login # This will open your browser for authentication # Once complete, you're ready to deploy 04 Deploy Your First Resource Choose a product and deploy in seconds. Here's how to set up each service. CDN Add your domain and start caching content globally. # Create a new CDN deployment edge cdn create --origin https://your-origin.com # Add a custom domain edge cdn domains add mysite.com # Check deployment status edge cdn list Compute Launch a virtual machine in any of our 33 regions. # List available instance types edge compute types # Create a new VM edge compute create \ --name my-server \ --type starter \ --region eu-west-1 \ --image ubuntu-22.04 # SSH into your instance edge compute ssh my-server DNS Set up DNS for your domain with global anycast. # Add a new zone edge dns zones create example.com # Add an A record edge dns records create example.com \ --type A \ --name @ \ --value 203.0.113.50 # List all records edge dns records list example.com Storage Create an object storage bucket for your files. # Create a new bucket edge storage buckets create my-bucket # Upload a file edge storage upload ./image.png my-bucket/images/ # Make bucket public (optional) edge storage buckets update my-bucket --public Shield Add free, privacy-first bot protection to any form on your site. # Create a Shield widget edge shield create \ --name my-site \ --hostname mysite.com # The sitekey and secret are shown once — store the secret securely # Check traffic stats edge shield stats <widget-id> 05 Monitor & Manage Use the dashboard or CLI to monitor your deployments. Terminal # View all resources edge status # Check usage edge usage --period month # View logs edge logs --service cdn --follow Open Dashboard You're all set! You've deployed your first resource on Edge Network. From here, you can explore more advanced features, set up monitoring, or scale your infrastructure. More Tutorials Full Documentation Need help? If you run into any issues, we're here to help. Contact Support Join Discord Community Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Securing Login & Signup Flows URL: https://edge.network/academy/securing-login-signup-flows/ Markdown: https://edge.network/academy/securing-login-signup-flows.md JSON: https://edge.network/json/academy/securing-login-signup-flows.json _Stop credential stuffing and fake account creation without punishing real users. Layer Edge Shield's humanity score with rate limiting, step-up checks, and sensible password policy._ Back to Academy Security 10 min read Securing Login & Signup Flows Credential stuffing and fake account waves are the two most common attacks on any site with a login form. Here's how to stop both without adding friction for the humans you actually want. What you're actually defending against Credential stuffing is the replay of username/password pairs leaked from other sites. Because people reuse passwords, a list that's 0.1% effective against your login form is still a profitable attack — and it looks like thousands of individually plausible login attempts, not one obvious flood. Fake account creation feeds everything downstream: spam, referral fraud, free-tier abuse, review manipulation. By the time you notice it in your metrics, the accounts already exist and cleanup is expensive. Both attacks share one property: they're automated. That's the property to test for at the door, before a single credential is checked or a single row is written. 1. Gate the form with Edge Shield Add the Edge Shield widget to your login and signup forms, and verify the token server-side before your authentication logic runs. Tokens are single-use and expire after five minutes, so a bot can't harvest one token and replay it across a credential list. // Login route: verify the Shield token before touching credentials const res = await fetch('https://shield.edge.network/siteverify', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ secret: process.env.SHIELD_SECRET, response: req.body['edge-shield-response'], remoteip: req.ip, }), }) const { success, score } = await res.json() if (!success) return res.status(403).send('Verification failed') if (score < 40) return requireEmailConfirmation() // step up, don't hard-block // Only now check the password — bots never reach your auth logic const user = await authenticate(req.body.email, req.body.password) Two details matter here. First, pass remoteip — it lets Shield corroborate the client's network reputation. Second, the ordering: rejecting before authenticate() means stuffing attempts never touch your user table, which also keeps them out of your failed-login metrics and lockout logic. If you haven't set up a widget yet, the Bot Protection with Edge Shield guide covers it end to end — it's two lines of markup and free forever. 2. Use the score to step up, not just block Every verification returns a 1–100 humanity score . A hard pass/fail gate wastes that signal. For signups in particular, a graduated policy converts uncertain traffic instead of losing it: Signal Signup policy Score 70–100 Create the account normally. Score 40–69 Create the account, but require email confirmation before first use. Score 1–39 Reject, or hold for review. Watch for verified agents — they may be legitimate automation. For logins, treat a low score on a correct password as its own signal — that's the signature of a stuffed credential that happens to be valid. Step up to email confirmation or 2FA rather than letting the session through, and you've turned a successful account takeover into a failed one. 3. Keep the boring layers too Shield removes the bulk automation, but defence in depth still applies: Rate-limit per account, not just per IP — stuffing attacks rotate IPs cheaply; five failed attempts against one account is a better tripwire than fifty from one address. Return identical errors for "wrong password" and "no such user", on the same response timing, so the form can't be used to enumerate accounts. Check passwords against known-breach lists at signup and password change — most stuffing lists are built from exactly those breaches. Offer 2FA — it's the single strongest control against account takeover, and you should enable it on your own Edge account as well. Next steps Bot Protection with Edge Shield Full setup walkthrough Protecting APIs from Bot Abuse The same protection, beyond forms Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Security Hardening URL: https://edge.network/academy/security-hardening/ Markdown: https://edge.network/academy/security-hardening.md JSON: https://edge.network/json/academy/security-hardening.json _Secure your Edge Network infrastructure: SSH key authentication, firewall rules, 2FA, API key management, SSL/TLS, VM updates, agent access codes, and free bot protection with Edge Shield._ Back to Academy Security 12 min read Security Hardening Step-by-step practices to harden your Edge infrastructure: authentication, firewalls, API security, and agent access control. Why security hardening matters A single misconfigured VM or leaked API key can expose your infrastructure. Following these steps reduces attack surface and limits damage if credentials are compromised. Each section includes practical steps you can apply today. 1. SSH key authentication Password-based SSH is vulnerable to brute force. Use SSH keys and disable password authentication. Step-by-step: Generate an SSH key pair if you don't have one: ssh-keygen -t ed25519 -C "your@email.com" When creating a VM in the console, paste your public key or select one from your account. Edge injects it into ~/.ssh/authorized_keys . After first login, disable password auth: edit /etc/ssh/sshd_config , set PasswordAuthentication no , then restart sshd . 2. Firewall rules (security groups) Edge uses security groups to control inbound and outbound traffic to VMs. Restrict access to only what your application needs — e.g. ports 80/443 for web, 22 for SSH from your IP only. Step-by-step: In the console, go to Compute → Security Groups . Create a group with a sensible name (e.g. "web-server"). Add inbound rules: allow TCP 22 from your IP (or a VPN/jump-host IP), TCP 80/443 from 0.0.0.0/0 if the VM serves web traffic. Attach the security group to your VM(s). Avoid opening 0.0.0.0/0 for SSH unless necessary. Use edge compute security-groups in the CLI to manage rules. 3. Two-factor authentication for your Edge account Enable 2FA on your Edge account. If your password is ever leaked, an attacker still needs your authenticator device. Step-by-step: Go to Settings → Security in the console. Click Enable 2FA . Scan the QR code with an authenticator app (Google Authenticator, Authy, 1Password, etc.). Enter the verification code to confirm. Store recovery codes in a secure place. 4. API key management API keys grant full account access. Rotate them periodically and scope them when possible. Best practices: Rotation — Create a new key every few months or when a team member leaves. Revoke old keys in Settings → API Keys . Scoping — Use read-only keys for monitoring/backup workflows where write access is not needed. Storage — Never commit keys to version control. Use environment variables or a secrets manager. Prefer Agent Access Codes for AI agents and automation — they have scoped permissions and budget limits, reducing blast radius if compromised. 5. SSL/TLS When you use Edge CDN with a custom domain, SSL/TLS is handled automatically. Edge provisions and renews certificates for you. Ensure your domain is added to the CDN deployment and DNS points to Edge — HTTPS will be enabled by default. For direct VM access (e.g. SSH), connections use your client's SSH key exchange. For web apps on VMs, put the CDN in front so traffic is encrypted end-to-end via Edge's edge SSL. 6. DNS security DNSSEC adds cryptographic signing to DNS records, preventing spoofing and redirect attacks. DNSSEC support on Edge DNS is coming soon — we'll announce it when available. In the meantime, use strong, unique passwords for your domain registrar and Edge account, and enable 2FA on both where possible. 7. Keep VMs updated Unpatched systems are a common attack vector. Schedule regular updates for your VM OS and application dependencies. Step-by-step (Ubuntu/Debian): sudo apt update && sudo apt upgrade -y Reboot if the kernel was updated. Consider automating with cron or a configuration management tool. Edge provides base images that are regularly updated — recreate VMs periodically to get the latest base. 8. Agent access codes with limited permissions If you use AI agents or coding assistants to manage Edge infrastructure, do not give them your account API key. Use Agent Access Codes instead — scoped credentials with time limits and budget caps. Step-by-step: Go to Account → Agent Access in the console. Create a new code. Restrict products (e.g. only CDN and Compute, not billing). Set a budget cap so the agent cannot exceed a spend limit. Set an expiry date. Rotate codes when projects end. This limits damage if an agent’s context is leaked or misused. See Agent Access Codes for details. 9. Protect public forms and endpoints with Edge Shield Firewalls protect your VM, but your public forms — login, signup, contact, checkout — are open to the world by design. That's where credential stuffing, form spam, and fake account waves come in. Edge Shield closes that gap for free, without showing real visitors a CAPTCHA. Step-by-step: Create a widget in the console under Shield — you get a public sitekey and a server-side secret. Add the script tag and an edge-shield div to each form you want protected. Validate the submitted token from your server with one call to siteverify — tokens are signed, single-use, and expire in five minutes. Act on the 1–100 humanity score: block low scores on sensitive routes, or route verified agents to your API instead. See the full walkthrough in Bot Protection with Edge Shield . Next steps Cost Optimization Compute Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Setting up a Multi-Region CDN URL: https://edge.network/academy/multi-region-cdn/ Markdown: https://edge.network/academy/multi-region-cdn.md JSON: https://edge.network/json/academy/multi-region-cdn.json _Edge CDN is global by default — 2,200+ locations. Learn how to configure deployments, cache rules, image optimisation, and monitoring for worldwide audiences._ Back to Academy Featured Guide 10 min read Setting up a Multi-Region CDN Edge CDN is global by default — 2,200+ locations. Unlike AWS, you don't configure regions; the network routes requests to the nearest node automatically. Multi-region is built in On AWS, "multi-region" means manually provisioning CloudFront distributions, configuring origins per region, and managing replication. Edge CDN is global by default. A single deployment serves from 2,200+ locations worldwide. Every user gets routed to the nearest edge node — no region selection required. This guide walks through creating a deployment, configuring cache rules, and monitoring geo-distribution. Creating a deployment In the Edge console, create a new CDN deployment. Set your origin — a VM, storage bucket, or external URL. Add your domains; Edge provisions SSL automatically. The deployment is live across all edge locations immediately. Multiple domains: Add as many domains as you need. Each can point to the same deployment. Useful for subdomains (e.g. cdn.example.com , assets.example.com ) or multiple apex domains. How Edge routes requests When a user requests content, Edge uses DNS and Anycast to route them to the nearest node. That node checks its cache; on a hit, it serves the response. On a miss, it fetches from origin and caches the response for subsequent requests. You don't configure geography — the network handles it. Users in Tokyo, London, and São Paulo each hit the closest node automatically. Cache rules for different content types Set path-based cache rules to optimise behaviour: Static assets — /assets/* , *.js , *.css — long TTL (7–30 days) Images — /images/* — long TTL; enable image optimisation for format detection (WebP/AVIF where supported) Dynamic content — /api/* — short TTL or cache bypass HTML pages — short TTL (0–5 min) or bypass for personalised pages See Caching Strategies for detailed guidance. Monitoring per-region performance The console includes a geo distribution page for each CDN deployment. It shows traffic and cache hit rates by region or country. Use it to verify that requests are distributed globally and to identify regions where hit rates are low — a sign you may need to adjust cache rules or TTLs for that traffic pattern. Image optimisation for global audiences Edge's image optimisation automatically detects browser support for WebP and AVIF. Serve the best format for each user — smaller files, faster loads. Particularly valuable for global audiences on mixed devices and connections. Enable image optimisation in the deployment settings. Use query params (e.g. ?w=800 ) for resizing; format conversion happens automatically based on Accept headers. Dynamic content and Edge Storage as origin For dynamic content, use short TTLs or cache bypass. Path-based rules let you exempt /api/* or user-specific paths from caching. Edge Storage as CDN origin: For static sites (HTML, CSS, JS, images), use Edge Storage as the origin. You get a truly serverless setup — no VMs, no origin management. Upload files to storage; CDN serves them globally. Ideal for documentation sites, marketing pages, and SPAs with static builds. Next steps Caching Strategies CDN Documentation Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Terminology URL: https://edge.network/academy/terminology/ Markdown: https://edge.network/academy/terminology.md JSON: https://edge.network/json/academy/terminology.json _A plain-English glossary of Edge terms: products, network concepts, billing, and governance — every word you'll meet in the docs and Control, defined._ Back to Academy Getting Started 8 min read Terminology Every platform has its own vocabulary. Here's Edge's, in plain English — the words you'll meet in the docs, in Control, and around the network, each defined in a sentence or two. Products CDN Edge's content delivery network. Caches and serves your sites and assets from nodes close to your users, with zero egress fees. More → Compute Virtual machines on the Edge network. Deploy apps, containers, and full VMs to locations near your users. More → DNS Authoritative DNS hosting on a global anycast network. Free, fast, and API-first. More → Storage S3-compatible object storage with zero egress. Files live in buckets and can be served directly or through the CDN. More → Shield Privacy-first bot protection without puzzles. Scores each visitor's humanity and verifies legitimate AI agents rather than blocking everything non-human. More → Assist Conversational agents for your website. Answers questions using your own content, embedded with one line of code. More → Control The Edge customer console at /account — where you create and manage deployments, billing, and account settings. More → Agent API The machine-facing interface that lets AI agents discover, deploy, and manage Edge resources autonomously — the "agentic cloud". More → The network Node Any machine contributing capacity to the network — from a Raspberry Pi in an attic to rack hardware in a data centre — running the Edge node software. More → Relay An infrastructure node that routes traffic and coordinates work across the nodes around it, connecting them to the wider network. PoP Point of presence — a network location that serves traffic. Edge's PoPs include both strategic data-centre sites and contributed devices. More → Explorer The public view of the network: every online node on a live map, with per-node detail. More → Reputation A node's earned trust score, built through uptime and successful jobs. Higher reputation brings more and better work. Stake A refundable security deposit that unlocks trust-sensitive work for a node, or voting rights in governance. Returned when you leave; forfeited only for abuse. Billing Prepaid balance Money you've added to your account up front. Usage draws down from it before anything touches your card. Pay as you go Usage-based billing with a card on file — you pay for what you use, topped up automatically. Monthly cap An optional hard limit on monthly spend. When the cap is reached, paid usage stops rather than billing past it. Free tier The allowance included with every product before any payment is needed — e.g. 500k CDN requests or 250 Assist questions a month. Zero egress Edge doesn't charge for data transfer out, on any product, at any scale. Bills are based on what you use or store, never on bytes moved. More → Governance Governance How network changes are decided: proposals raised, debated, and voted on in the open by governance stakeholders. More → DAO The organisation that stewards the network — founders, core developers, and advisors — holding a collective veto over governance proposals. Now put the words to work Create a free account and see the terminology in its natural habitat — no card required. Start Free Quick Start Guide Related articles What is an Edge Network? 6 min Account Setup 5 min Console Quick Start 5 min --- ### Verified AI Agents with Web Bot Auth URL: https://edge.network/academy/verified-ai-agents/ Markdown: https://edge.network/academy/verified-ai-agents.md JSON: https://edge.network/json/academy/verified-ai-agents.json _More than half of web traffic is automated, and a growing share is legitimate. Learn how Edge Shield identifies AI agents that declare themselves with Web Bot Auth, and how to set a policy that blocks abuse without turning away customers' agents._ Back to Academy Security 9 min read Verified AI Agents with Web Bot Auth The bot problem changed. Some automation is your customers' AI agents trying to buy from you. Security now means telling declared automation apart from anonymous automation — and treating each accordingly. "Block all bots" is now a business decision More than half of web traffic is automated, and a growing share of it is legitimate — AI agents shopping, booking, and researching on behalf of real people. An agent filling your checkout with a customer's card is revenue; a scraper farming your catalogue is not. To a naive bot filter, they look identical: both score low on any honest humanity test, because both are automation. The distinction that matters is no longer human versus bot. It's automation that declares who it is versus automation that hides. Edge Shield is built around exactly that line. How Shield identifies agents The primary mechanism is Web Bot Auth — the emerging IETF standard (RFC 9421 HTTP Message Signatures with the web-bot-auth tag) backed by OpenAI, Google, Amazon, and Cloudflare. The agent signs each request with an Ed25519 key and points to its published key directory. Shield fetches the directory, checks the signature, and confirms exactly which agent is calling — identity that can't be spoofed by copying a user-agent string. GET /products HTTP/1.1 Host: example.com Signature-Agent: "https://agent.bot.goog" Signature-Input: sig1=("@authority" "signature-agent");created=1753100000;\ keyid="poqkLGiy...";alg="ed25519";expires=1753100300;nonce="e8N7...";tag="web-bot-auth" Signature: sig1=:jdq0SqOwHdyHr9+r5jw3iYZH6aNGKijYp/EstF4RQTQdi5N5YYKrD+mCT1HA1nZDsi6nJKuHxUi/5Syp3rLWBA==: Established crawlers that predate the standard — Googlebot, Bingbot, Applebot — are confirmed the way their operators document: reverse-DNS lookup of the calling IP, forward-confirmed back to the same address. A client merely claiming to be Googlebot from an unrelated IP gets no credit, and the lie counts against its humanity score. Verified identity is bound into the Shield response token and surfaced in the siteverify response as the agent field. Set a per-widget agent policy Each Shield widget chooses how verified agents are treated, in its settings: Policy Behaviour allow default Verified agents pass without interactive escalation. The token carries their identity — you decide what they can do. challenge No identity credit. Agents are scored like any anonymous client, and clear automation signals cap their score. block Verified agents are rejected outright with the agent-blocked error code. Whatever the policy, anonymous automation is always treated aggressively — clear automation signals with no declared identity hard-cap the humanity score. Declaring identity is the fast path; that's the incentive for agents to sign their traffic. Route on identity, not just score The score answers "is this a human?"; the agent field answers "then who is it?". Use both in your server-side check: const result = await siteverify(token) if (!result.success) reject() else if (result.agent?.verified) { // Declared automation — route it, don't fight it routeToApi(result.agent.domain) } else if (result.score >= 40) { allow() // human traffic } else { block() // automation that refused to identify itself } Note that agents don't only arrive through forms. When a signed request hits your API or a content page directly, forward its signature headers to Shield's agentverify endpoint and get the same verified identity back — no widget, no JavaScript, no challenge. See Protecting APIs from Bot Abuse for the pattern. One caution: Web Bot Auth adoption is early and uneven — Google signs its AI-browsing agent but not Googlebot indexing, and rollouts are gradual. Treat a valid signature as strong positive identity; treat its absence as neutral, not negative. The other direction: your agents on Edge If you also run AI agents — deploying infrastructure, managing DNS — the same principle applies in reverse: give automation scoped, revocable identity rather than full credentials. On Edge that means Agent Access Codes : per-agent credentials with product restrictions, budget caps, and expiry dates, so a leaked agent context never exposes your whole account. Next steps Verified Agents docs agentverify API, policies, error codes What is the Agentic Cloud? How agents use Edge itself Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Video: CDN Setup URL: https://edge.network/academy/video-cdn-setup/ Markdown: https://edge.network/academy/video-cdn-setup.md JSON: https://edge.network/json/academy/video-cdn-setup.json _Watch how to set up and configure Edge CDN from scratch. Create a deployment, add domains, configure caching, and go live._ Back to Academy Video Tutorial 8 min watch CDN Setup From zero to globally cached in under 10 minutes. Create a CDN deployment, add your domain, configure caching rules, and go live. Video coming soon Follow the written guide below in the meantime What this tutorial covers Follow along with the video or use this written guide to set up your CDN. Creating a CDN Deployment A CDN deployment is a container for one or more domains. When you create one, Edge provisions cache space across 2,200+ global locations for your content. In the console, navigate to CDN and click Create Deployment . Give it a name that identifies your project (e.g. "marketing-site" or "api-cache"). Adding a Domain Each deployment can have multiple domains. Add your domain and specify the origin — the server where your content lives. Edge fetches from your origin on cache miss and serves from cache on hit. You'll need to create a CNAME record pointing your domain to cdn.edge.network . Once DNS propagates, Edge automatically provisions a free SSL certificate via Let's Encrypt. Configuring Cache Rules By default, Edge caches everything for 1 year. You can customise this per path: Static assets (images, CSS, JS) — cache for 1 year, they rarely change HTML pages — cache for 1 hour or less if content updates frequently API responses — short TTL (minutes) or bypass cache entirely Configure these in the deployment's Configuration tab under Cache Rules. Image Optimisation Edge CDN includes automatic image optimisation. When enabled, images are converted to WebP or AVIF based on the visitor's browser support, and resized on-the-fly via URL parameters. This is enabled by default on new deployments. Purging Cache When you update content, you can purge individual URLs or the entire cache. Purges propagate globally within seconds. # Purge a specific URL edge cdn purge <deployment-id> --url https://cdn.example.com/style.css # Purge everything edge cdn purge <deployment-id> Next: VM Configuration Set up and manage virtual machines CDN Documentation Full reference docs Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Video: DNS Management URL: https://edge.network/academy/video-dns-management/ Markdown: https://edge.network/academy/video-dns-management.md JSON: https://edge.network/json/academy/video-dns-management.json _Learn how to manage DNS zones and records on Edge. Create zones, update nameservers, add A, AAAA, CNAME, MX, and TXT records, understand TTL, and use geo-routing._ Back to Academy Video Tutorial 7 min watch DNS Management Manage DNS zones and records on Edge. Create a zone, point your domain, add records, and take advantage of geo-routing and built-in monitoring. Video coming soon Follow the written guide below in the meantime What this tutorial covers Follow along with the video or use this written guide to manage your DNS on Edge. Creating a Zone A zone represents a domain you want to manage. In the console, go to DNS → Create Zone and enter your domain (e.g. example.com ). Edge will generate nameservers for you — you'll need these in the next step. You can create multiple zones for different domains or subdomains. Each zone is independent with its own set of records. Updating Nameservers at Your Registrar For Edge to serve DNS for your domain, point it at our nameservers. At your domain registrar (where you bought the domain), find the DNS or nameserver settings and replace the current nameservers with Edge's. Edge provides two nameservers, e.g. ns1.edge.network and ns2.edge.network . Propagation can take up to 48 hours, though it's often much faster. Adding A, AAAA, CNAME, MX, and TXT Records A records map a hostname to an IPv4 address. Use them for your main domain or subdomains pointing to servers. AAAA records map to IPv6 addresses. Add both A and AAAA for dual-stack support. CNAME records alias one hostname to another. Use them for www pointing to your root domain, or for CDN origins. MX records define mail servers. Add these when using external email providers (e.g. Google Workspace, Fastmail). TXT records store text — commonly used for domain verification, SPF, DKIM, and other authentication. Understanding TTL TTL (Time to Live) controls how long resolvers cache your records. A low TTL (e.g. 60 seconds) means changes propagate quickly but increases DNS query load. A high TTL (e.g. 3600) reduces queries but slows propagation. Use low TTL before migrations; use higher TTL for stable production records. Geo-routing Edge DNS supports geo-routing — serving different answers based on the requester's location. Use this to direct users to the nearest region or to comply with data residency requirements. In the record editor, enable geo-routing and add region-specific values. For example, EU users might get a different IP than US users. Monitoring DNS Metrics Each zone has a metrics dashboard showing query volume, response times, and record hit rates. Use these to understand traffic patterns and identify anomalies. Access metrics from the zone detail page. Set up alerts for unusual spikes or errors. Next: Storage Basics S3-compatible object storage DNS Documentation Full reference docs Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Video: Storage Basics URL: https://edge.network/academy/video-storage-basics/ Markdown: https://edge.network/academy/video-storage-basics.md JSON: https://edge.network/json/academy/video-storage-basics.json _Learn Edge Object Storage — S3-compatible, zero egress. Create buckets, upload files, generate access keys, use S3 SDKs, create presigned URLs, and connect to CDN._ Back to Academy Video Tutorial 8 min watch Storage Basics Edge Object Storage is S3-compatible with zero egress fees. Create buckets, upload files, integrate with your apps, and serve content via CDN. Video coming soon Follow the written guide below in the meantime What this tutorial covers Follow along with the video or use this written guide to get started with Edge Object Storage . Creating a Bucket Buckets are containers for your objects. In the console, go to Storage → Create Bucket . Give it a unique name — bucket names must be globally unique across Edge and follow S3 naming rules. Choose a region for your bucket. Content is stored and served from that region, though you can connect it to CDN for global distribution. Uploading Files (CLI and Console) Console: Open your bucket and drag-and-drop files or use the upload button. You can create folders for organisation — they're logical prefixes in object keys. CLI: Use the AWS CLI with the Edge endpoint. Configure your credentials first: # Upload a file aws s3 cp ./my-file.jpg s3://my-bucket/ --endpoint-url https://storage.edge.network # Sync a directory aws s3 sync ./dist/ s3://my-bucket/ --endpoint-url https://storage.edge.network Generating Access Keys For programmatic access, create access keys in Storage → Access Keys . You'll get an Access Key ID and Secret Access Key — store the secret securely; it's only shown once. Use these with any S3-compatible client. The endpoint is https://storage.edge.network . Using with S3 SDKs Edge Storage works with the AWS SDK and other S3-compatible libraries. Point the client at https://storage.edge.network and use your access keys. // JavaScript example with @aws-sdk/client-s3 const { S3Client, PutObjectCommand } = require('@aws-sdk/client-s3'); const client = new S3Client({ endpoint: 'https://storage.edge.network', region: 'us-east-1', credentials: { accessKeyId: '...', secretAccessKey: '...' } }); await client.send(new PutObjectCommand({ Bucket: 'my-bucket', Key: 'file.jpg', Body: buffer })); Presigned URLs for Sharing Generate temporary URLs that allow download or upload without exposing your credentials. Presigned URLs expire after a set duration (e.g. 1 hour, 24 hours). Use the SDK's getSignedUrl or GetObjectCommand with presigning. Share the URL with clients for time-limited access to private objects. Connecting to CDN as an Origin Serve your bucket contents through Edge CDN for fast global delivery and zero egress. In the CDN deployment, add a custom origin and set the origin URL to your bucket's endpoint. The format is typically https://<bucket>.storage.edge.network . Configure cache rules to optimise TTLs for your content type. Monitoring Usage The Storage dashboard shows bucket size, object count, and request metrics. Use these to track growth and identify usage patterns. Billing is based on storage used and requests — egress to Edge CDN is free. The first 5 GB is free; beyond that, monitor your usage to keep costs predictable. Next: Caching Strategies Best practices for CDN caching Storage Documentation Full reference docs Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Video: VM Configuration URL: https://edge.network/academy/video-vm-configuration/ Markdown: https://edge.network/academy/video-vm-configuration.md JSON: https://edge.network/json/academy/video-vm-configuration.json _Learn how to set up and manage Edge Compute virtual machines. Choose an OS, create a VM, connect via SSH, configure firewall rules, resize instances, and manage backups._ Back to Academy Video Tutorial 10 min watch VM Configuration Set up and manage Edge Compute virtual machines. Choose your OS and size, create VMs, connect via SSH, add firewall rules, resize instances, and manage backups and snapshots. Video coming soon Follow the written guide below in the meantime What this tutorial covers Follow along with the video or use this written guide to get your virtual machines up and running. Choosing an OS and Size Edge Compute supports Ubuntu, Debian, and other popular Linux distributions. Pick an OS that matches your stack. For size, start small — you can resize anytime without downtime. The smallest instances are ideal for development and low-traffic apps. Navigate to Compute → Create VM and select your preferred image and instance size. Each size shows vCPU count, RAM, and estimated monthly cost. Creating a VM Give your VM a name, select a region (choose one close to your users), and optionally add SSH keys during creation. Click Create and Edge provisions your machine in under a minute. You'll receive the VM's public IP and root credentials via email unless you used SSH keys. Store these securely — you'll need them for your first login. Connecting via SSH From your local terminal, connect using the VM's public IP: # Connect as root ssh root@<vm-ip> # Or with a specific key ssh -i ~/.ssh/my-key root@<vm-ip> Adding SSH Keys For key-based authentication, add your public key before creating the VM, or add it later via the console. Go to Compute → SSH Keys , paste your public key, and associate it with existing VMs or new ones. Key-based auth is more secure than passwords — we recommend disabling password login once keys are set up. Firewall Rules Edge Compute includes a built-in firewall. By default, only SSH (22) is open. Add rules to allow inbound traffic for web servers (80, 443), databases, or custom ports. Configure firewall rules in the VM's Networking tab. Rules apply immediately — no VM reboot required. Resizing Instances Need more CPU or RAM? Resize your VM from the console. Select a larger size and apply. The VM reboots briefly during the resize — plan for a few seconds of downtime. You can downsize as well if you over-provisioned. Backups and Snapshots Create snapshots before major changes or on a schedule. Snapshots are stored separately and can be used to restore a VM or spin up a clone. Enable automatic backups in Settings to protect production workloads. Manual snapshots are useful for one-off captures before risky updates. Monitoring Metrics Each VM has a metrics dashboard showing CPU, memory, disk I/O, and network traffic. Use these to identify bottlenecks before resizing, and to set up alerts when utilisation exceeds thresholds. Access metrics from the VM detail page. Historical data is retained for 30 days. Next: DNS Management Manage zones and records Compute Documentation Full reference docs Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What Does Edge Infrastructure Cost? URL: https://edge.network/academy/edge-infrastructure-costs/ Markdown: https://edge.network/academy/edge-infrastructure-costs.md JSON: https://edge.network/json/academy/edge-infrastructure-costs.json _The real cost components of edge infrastructure — hardware, colocation, bandwidth, and operations — and when it makes more sense to buy than build._ Back to Academy Best Practices 8 min read What Does Edge Infrastructure Cost? Whether you build your own edge presence or use a platform, the cost drivers are the same four things. Here's how to think about them — and when buying beats building. The short answer The cost of edge infrastructure depends entirely on whether you build or buy. Building your own edge sites means paying for hardware, colocation, bandwidth, and operations at every location — costs that multiply with each site and typically run from thousands of dollars per site per year for a modest deployment to far more at scale. Using an edge platform turns all of that into usage-based pricing: on Edge, a small virtual machine costs a few dollars a month and CDN, DNS, and bot protection start free. There is no single "average cost per edge server" because the term spans everything from a mini PC in a branch office to GPU racks in regional data centres. What is consistent is the cost structure — so that's the useful thing to understand. The four cost components of DIY edge infrastructure Every self-built edge deployment pays for these, at every site, for as long as it runs. Hardware Servers, storage, and networking gear for every site — plus spares, refresh cycles every few years, and capacity you must size for peak load rather than average. Colocation & Power Rack space, power, and cooling at each location, billed monthly per site. Costs multiply with every region you add. Bandwidth & Connectivity Transit and peering at every site, often with committed minimums. Distributed sites mean many separate contracts and providers. Operations Monitoring, patching, hardware replacement, and on-call cover across time zones — typically the largest long-term cost, and the hardest to scale. Why edge costs multiply rather than add The defining feature of edge infrastructure is that it is distributed — and distribution is exactly what makes DIY expensive. A single well-run data centre amortises its costs across thousands of servers. An edge deployment inverts that: many small sites, each needing its own hardware, its own connectivity contract, its own remote-hands arrangement, and its own share of monitoring and maintenance. Ten sites don't cost ten times one site; they cost more, because coordination overhead grows with count. Utilisation makes it worse. Each site must be provisioned for its local peak, but most sites sit well below peak most of the time. You pay for capacity around the clock that serves traffic for a few hours a day. This is the core inefficiency that decentralised networks exist to solve: pooling many operators' spare capacity means nobody has to over-provision alone. Why most teams should buy, not build Building your own edge makes sense in a narrow set of cases: hard data-residency requirements, specialised hardware at specific sites, or workloads physically tied to a location, such as factory-floor processing. For everything else — serving content and applications to users with low latency — a platform that already operates hundreds or thousands of edge locations delivers the same outcome with zero capital outlay and no operations burden. The comparison isn't close on smaller scales. The hardware budget for a single self-hosted site exceeds years of platform fees for an equivalent workload, before counting bandwidth contracts or the engineer-hours to keep it healthy. Platforms also fix the utilisation problem: you pay for what you use, not for idle peak capacity. What edge infrastructure costs on Edge Edge prices per resource, billed hourly from a prepaid balance: $0.004 per vCPU-hour (about $2.92 a month), $0.00256 per GiB of RAM per hour, and $0.074 per GiB-month for NVMe disk. A starter VM with 1 vCPU, 2 GB RAM, and 40 GB of disk comes to roughly $10 a month — and because spending is deducted from a balance you top up, a surprise bill is impossible by design. The rest of the platform starts free: DNS is free for up to 50 zones, Shield bot protection is free forever, the CDN includes 500,000 requests a month with zero egress fees , and Storage includes 5 GB. That combination — no hardware, no colocation contracts, no bandwidth line item — is what edge infrastructure costs when the network already exists and you simply deploy onto it. For squeezing the most from a deployment once it's running, see Cost Optimization . Skip the buildout Deploy on an existing global edge network — per-resource pricing, free tiers, and no hardware to own. Start Free View Pricing Related articles Cost Optimization 8 min What is an Edge Data Center? 7 min CDN Pricing Comparison 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is a Decentralised CDN? URL: https://edge.network/academy/what-is-a-decentralised-cdn/ Markdown: https://edge.network/academy/what-is-a-decentralised-cdn.md JSON: https://edge.network/json/academy/what-is-a-decentralised-cdn.json _A decentralised CDN delivers content from a network of independent nodes rather than data centres owned by one company. Learn how it works and why it matters._ Back to Academy Information 7 min read What is a Decentralised CDN? Content delivery networks have traditionally been built from data centres owned by a single company. A decentralised CDN takes a different approach — and it changes the economics and resilience of content delivery. The short answer A decentralised CDN is a content delivery network built on nodes run by independent operators rather than on data centres owned by one company. Content is cached and served from whichever participating node is closest to the user, and the network as a whole — not any single facility — provides the capacity and redundancy. The result is the same job a traditional CDN does — caching content close to users so it loads quickly — delivered by a fundamentally different architecture. It is the CDN expression of the broader decentralised cloud model. How centralised CDNs work — and where they fall short A conventional CDN operates a fleet of points of presence (PoPs): racks of servers in data centres, placed in cities the provider has chosen to invest in. When a user requests a file, DNS or Anycast routing directs them to the nearest PoP, which serves the content from cache or fetches it from your origin server. This model works, but its constraints are structural. Coverage only extends to locations that justify the cost of a data centre presence, so users far from major hubs see higher latency. The provider's network is a single administrative domain — a bad configuration push or a core outage can affect every PoP at once, as several high-profile CDN outages have shown. And because the provider must recover the cost of building and running those facilities, bandwidth is metered and charged, usually per gigabyte of egress. The decentralised approach A decentralised CDN replaces the company-owned PoP fleet with a network of independent nodes. Anyone with suitable hardware and connectivity can contribute capacity, and the network's software handles the hard parts: verifying node performance, routing each request to the best available node, and moving traffic away from nodes that go offline. On Edge, node operators are rewarded in the network's native token for the capacity they contribute, which gives them a direct economic stake in keeping their nodes fast and reliable. You can read more about how that works in What is the Edge Token? Because the network grows wherever operators join rather than where a company builds, coverage extends into regions and smaller cities that centralised CDNs skip. Edge's network currently spans 988 nodes — more edge locations than any traditional CDN operates. Centralised vs. decentralised CDN Centralised CDN Decentralised CDN PoPs owned and operated by a single company Nodes run by independent operators worldwide Coverage limited to commercially viable cities Presence wherever operators run nodes One outage can affect the whole network Failures are isolated to individual nodes Capacity requires new data centre buildout Capacity grows as operators join the network Bandwidth priced to recover facility costs Uses spare capacity, enabling zero egress fees Why decentralisation matters for content delivery Resilience, coverage, and economics all improve when delivery capacity is distributed rather than concentrated. Broader Coverage Independent operators bring nodes to places centralised providers never build, putting content closer to more users. No Single Point of Failure If a node goes offline, requests are routed to the next nearest node automatically. There is no central facility to take the network down. Better Economics The network runs on spare capacity rather than purpose-built data centres, which is how Edge can serve traffic with zero egress fees. Lower Environmental Impact Using hardware that already exists means fewer new data centres and less wasted capacity. Edge CDN in practice Edge CDN is a working decentralised CDN, not a research project. You create a deployment, point it at your origin, and content is served from the nearest node with automatic SSL, instant cache purging, image optimisation, and DDoS protection included. Crucially, the economics follow the architecture. Because the network runs on contributed capacity rather than company-owned data centres, Edge charges zero egress fees — you pay $0.25 per million requests beyond a free tier of 500,000 requests a month, and nothing for bandwidth. On a traditional CDN, bandwidth is usually the largest line on the bill. To users, none of this is visible: they simply get content from a nearby node over a standard HTTPS connection. The decentralisation is an implementation detail that shows up as better coverage, better resilience, and a smaller bill. Try a decentralised CDN Serve your first site from Edge's network free — 3 deployments and 500k requests a month, with zero egress fees. Start Free Explore Edge CDN Related articles What is a Decentralised Cloud? 8 min CDN vs Edge Computing 7 min CDN Pricing Comparison 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is a Decentralised Cloud? URL: https://edge.network/academy/what-is-a-decentralised-cloud/ Markdown: https://edge.network/academy/what-is-a-decentralised-cloud.md JSON: https://edge.network/json/academy/what-is-a-decentralised-cloud.json _Learn how decentralised cloud infrastructure works and why it offers advantages over traditional centralised providers._ Back to Academy Information 8 min read What is a Decentralised Cloud? The cloud as you know it is changing. Decentralised cloud infrastructure represents a fundamental shift in how we think about computing resources, moving away from monolithic data centres toward a distributed, community-powered model. The Traditional Cloud Model When most people think of "the cloud," they picture massive data centres owned and operated by tech giants like Amazon, Google, and Microsoft. These facilities house thousands of servers, consume enormous amounts of energy, and are concentrated in a relatively small number of locations around the world. While this model has enabled incredible innovation, it comes with significant drawbacks: high costs, vendor lock-in, environmental concerns, and a concentration of power in the hands of a few large corporations. A New Approach: Decentralisation A decentralised cloud distributes computing resources across a network of independent operators rather than concentrating them in a few large facilities. Think of it like the difference between a single power plant and a network of solar panels on rooftops across a city. At Edge, our network is powered by thousands of node operators worldwide. These operators contribute their computing resources to the network and are rewarded for their participation. This creates a more resilient, efficient, and democratic infrastructure. Traditional vs. Decentralised Traditional Cloud Decentralised Cloud Centralised data centres owned by one company Distributed network of independent node operators Single points of failure Redundancy built into the architecture Limited geographic coverage Global presence through community nodes Opaque infrastructure Transparent and verifiable operations Vendor lock-in Open standards and portability Benefits of Decentralisation The decentralised model offers advantages that are impossible to achieve with traditional infrastructure. Lower Latency Data is processed closer to end users, reducing round-trip times and improving performance. Greater Resilience No single point of failure. If one node goes down, traffic is automatically routed to others. Environmental Benefits Utilises existing infrastructure and spare capacity, reducing the need for new data centres. Community Powered A global network of operators who are invested in the success of the platform. How Edge's Network Works Edge's decentralised cloud is built on a global network of nodes operated by independent participants. When you deploy a resource on Edge—whether it's a CDN distribution, a virtual machine, or a DNS zone—your workload is distributed across this network. Our intelligent routing ensures that requests are always handled by the nearest available node, minimising latency and maximising reliability. If a node becomes unavailable, traffic is seamlessly rerouted to alternatives. Node operators are rewarded with XE, Edge's native token, creating an economic incentive for maintaining high-quality infrastructure. This alignment of interests ensures that the network remains robust and performant. Experience the Decentralised Cloud Ready to see the difference? Try Edge's infrastructure free — no card required. Start Free Explore Our Network Related articles What is XE and how does it Power Edge? 6 min What Makes Edge Better for the Environment? 5 min Quick Start Guide 10 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is an Edge Data Center? URL: https://edge.network/academy/what-is-an-edge-data-center/ Markdown: https://edge.network/academy/what-is-an-edge-data-center.md JSON: https://edge.network/json/academy/what-is-an-edge-data-center.json _An edge data center is a small facility located close to end users. Learn how edge data centers differ from hyperscale facilities and why proximity matters._ Back to Academy Information 6 min read What is an Edge Data Center? For two decades data centres got bigger and further away. Edge data centres reverse the trend: smaller facilities, closer to the people they serve. Edge data centre, defined An edge data centre is a small data centre located close to the end users it serves — typically in or near a city — rather than in a remote hyperscale campus. Edge data centres bring computing, caching, and storage capacity to the local level, cutting the distance data has to travel and therefore the latency users experience. They range from container-sized micro data centres at the base of mobile towers, to a few racks in a regional colocation facility, to purpose-built sites serving a metropolitan area. What defines them isn't size — it's purpose. An edge data centre exists to be near users, and it usually works as part of a wider edge network rather than standing alone. Edge data centres vs hyperscale data centres Hyperscale Data Centre Edge Data Centre Enormous campuses in remote, low-cost regions Compact facilities in or near population centres Tens of thousands of servers per site A few racks to a few hundred servers per site Optimised for cheap land, power, and cooling Optimised for proximity to users A handful of sites serve a continent Many sites, each serving its local area Users may be thousands of kilometres away Users are milliseconds away Hyperscale facilities excel at bulk work: training models, running databases, batch processing. Edge data centres excel at delivery and interaction. Modern infrastructure uses both. Why proximity matters Every kilometre between a user and a server adds latency, and no amount of engineering can remove it — data cannot travel faster than light through fibre. A round trip across a continent costs tens of milliseconds; across an ocean, over a hundred. For a web page assembled from dozens of requests, or an application that feels "live", those milliseconds accumulate into something users can feel. Proximity also changes the economics. Traffic served locally never touches expensive long-haul routes, and origin infrastructure can be sized for a fraction of peak load because edge servers absorb the rest. This is the same logic behind CDNs — moved from caching alone to the whole facility. What's driving the edge data centre trend Several forces are pushing infrastructure out of central facilities and toward the edge. Latency-sensitive applications Video calls, gaming, and real-time apps degrade noticeably when servers are far away. Proximity is the only fix physics allows. Growth in video and rich media Streaming from local facilities avoids hauling the same bytes across the backbone millions of times. Edge computing workloads Processing data near its source — devices, sensors, users — needs compute capacity distributed to match. Coverage beyond major hubs Users outside the big internet cities deserve the same experience. Small local facilities make that possible. The logical endpoint: a decentralised network Follow the edge data centre trend to its conclusion and you arrive somewhere interesting. If smaller facilities closer to users are better, the ideal infrastructure isn't a few hundred company-owned sites — it's capacity everywhere, contributed by many independent operators, coordinated as one network. That's how Edge is built. Rather than leasing space in edge data centres one city at a time, the Edge network is made up of 988 nodes run by independent operators, from modest hardware behind home routers to powerful machines in data centres. A core-team-managed backbone, housed with data centre partners worldwide, guarantees baseline capacity, while community nodes extend coverage far beyond what any single company could build. The result is the edge data centre idea taken to its limit: a decentralised cloud where the "facility" is the network itself, powering CDN , storage , compute , and DNS from wherever users happen to be. Infrastructure that lives at the edge Deploy on a network of 988 nodes. Try Edge free — no card required. Start Free Explore Our Network Related articles What is an Edge Server? 7 min What is an Edge Network? 8 min What is the Edge Cloud? 7 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is an Edge Network? URL: https://edge.network/academy/what-is-an-edge-network/ Markdown: https://edge.network/academy/what-is-an-edge-network.md JSON: https://edge.network/json/academy/what-is-an-edge-network.json _An edge network is a distributed network of servers placed close to end users. Learn how it works, how it differs from centralised cloud, and why it matters._ Back to Academy Information 8 min read What is an Edge Network? Edge networking moves computing power out of distant data centres and puts it close to the people using it. Here's how edge networks work, and why the internet is being rebuilt around them. Edge network definition An edge network is a distributed network of servers positioned close to end users — at the "edge" of the internet — rather than concentrated in a handful of central data centres. Because requests are handled by the nearest server instead of travelling to a distant facility, edge networks deliver lower latency, higher reliability, and lower bandwidth costs than centralised infrastructure. The idea is simple: the speed of light is a hard limit. A request from London to a data centre in Virginia and back takes tens of milliseconds before any work is even done. Multiply that by every asset on a page, or every frame of a video call, and distance becomes the dominant cost. Edge networking removes the distance. The network edge vs the network core In networking terms, the core is the high-capacity backbone — the long-haul fibre routes and interconnection points that carry traffic between regions. The edge is where that backbone meets the real world: the last-mile networks, exchange points, and servers nearest to homes, offices, and devices. Traditional cloud hosting lives deep in the core. Your application runs in one or two large facilities, and every user, wherever they are, has to reach those facilities across the backbone. An edge network inverts this: it stations edge servers at many points near users, so most requests never need to cross the core at all. The two aren't in competition — the core still carries traffic between edge locations and back to origin systems. But the more work the edge absorbs, the faster and cheaper everything gets. Edge networks vs centralised hosting Centralised Hosting Edge Network All requests travel to one central location Requests are handled by the nearest server Latency grows with distance from the data centre Low latency for users everywhere A single outage can take everything down Traffic reroutes around failed servers automatically Capacity is fixed to one facility Capacity is spread across many locations Bandwidth is billed as metered egress Delivery costs fall as content is served locally How CDNs relate to edge networks A content delivery network (CDN) was the first mainstream use of edge networking. A CDN caches copies of static content — images, video, scripts, downloads — on edge servers around the world, so each user fetches files from a nearby cache instead of a distant origin. Modern edge networks go further. Beyond caching, they run compute workloads , store data in object storage , and answer DNS queries at the edge. A CDN is one service an edge network can offer; the network itself is the underlying infrastructure. We cover the distinction in detail in CDN vs Edge Computing . Why edge networks matter The advantages of moving work to the edge compound: every request handled locally is faster for the user and cheaper for the operator. Lower Latency Requests are answered by a server physically near the user, cutting round-trip times dramatically. Resilience With many servers sharing the load, no single failure can take the network offline. Global Reach Users in every region get the same fast experience, without you deploying to multiple clouds. Lower Costs Serving content close to users reduces long-haul bandwidth and takes pressure off origin infrastructure. How Edge builds its edge network differently Most edge networks are built the traditional way: one company leases rack space in data centres around the world and fills it with its own hardware. That works, but coverage is limited by how many facilities one company can afford to run. Edge takes a decentralised approach. Our network is made up of 988 nodes contributed by independent operators worldwide, who stake tokens to participate and earn rewards for the capacity they provide. Because anyone can add a node, the network grows where demand exists rather than where leases are cheapest — and there is no single company data centre whose failure can take it down. On top of this network Edge runs a full set of services: a CDN with zero egress fees, object storage , compute and GPUs , and DNS — the components of what we call the edge cloud . You can read more about the decentralised model in What is a Decentralised Cloud? Put your app on the edge Deploy on a network of 988 nodes. Try Edge free — no card required. Start Free Explore Our Network Related articles What is the Edge Cloud? 7 min What is an Edge Server? 7 min What is a Decentralised Cloud? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is an Edge Node? URL: https://edge.network/academy/what-is-an-edge-node/ Markdown: https://edge.network/academy/what-is-an-edge-node.md JSON: https://edge.network/json/academy/what-is-an-edge-node.json _An edge node is a device at the network edge that serves content and runs workloads close to users. Learn what edge nodes do and how to run one._ Back to Academy Information 7 min read What is an Edge Node? Edge nodes are the building blocks of distributed networks — the machines that put content and compute close to users. Here's what they do, and how Edge's node types fit together. The short answer An edge node is a computing device located at the edge of a network — close to end users — that serves content, processes data, or runs workloads locally instead of passing every request back to a distant central data centre. In a CDN, edge nodes cache and serve files from nearby; in edge computing more broadly, they run applications and process data near its source. On the Edge Network specifically, an edge node is a device connected to the network to contribute its spare capacity. Together, 988 nodes make up a decentralised cloud that powers CDN, DNS, compute, and storage services. What edge nodes do in a network The job of an edge node is proximity. When a user requests a web page, an image, or an API response, the network routes that request to the nearest node rather than to a central server that might be thousands of kilometres away. If the node has the content cached, it responds immediately; if not, it fetches it once from the origin and caches it for everyone nearby. The same principle extends beyond caching. Edge nodes answer DNS queries from nearby resolvers, terminate TLS connections close to the user, absorb and filter attack traffic at the point it enters the network, and — increasingly — run compute workloads such as machine learning inference . Every one of these tasks benefits from shaving the physical distance between the user and the machine doing the work. The three node types in the Edge Network Edge organises its network into three roles, each with different responsibilities and hardware requirements. Host Processing and storage capacity Hosts provide the processing and storage capacity in the network. Designed for mixed device types with varying capability, they can run behind a home router with no special configuration. 15 Mbit/s+ bandwidth · quad-core 1.2 GHz+ CPU · 1 GB+ RAM · 50 GB+ disk Gateway Entry point and job routing Gateways are the entry point to the network, aggregating Host capacity. They manage job queues and route requests to the Hosts most likely to complete each task quickly, based on rolling performance scores. 250 Mbit/s+ bandwidth · 99% availability · quad-core 2.5 GHz+ CPU · 64 GB+ RAM · 1 TB+ SSD Stargate Network coordination and security Stargates are the masternodes of the network. They run the XE blockchain, provide the naming system that makes Gateway and Host resources addressable, monitor resources, and control device yields. 1 Gbit/s+ bandwidth · 99.9999% availability · 2x quad-core 2.8 GHz+ CPU · 128 GB+ RAM · 2 TB+ SSD How the node types work together A request entering the Edge Network arrives at a Gateway, which acts as the aggregate point for the Host capacity behind it. The Gateway maintains a rolling score for each Host and hands the job to the Host most likely to complete it quickly at that moment. Hosts do the heavy lifting — serving cached content, storing objects, running workloads — while Stargates sit above the whole system, running the XE blockchain, providing the naming system that makes resources addressable, and monitoring the network's health. Alongside community-run nodes, the Edge core team operates a network backbone — Stargates, Gateways, and Hosts housed with data centre partners around the world — to guarantee baseline capacity as the network grows. How to run an edge node Anyone with suitable hardware can contribute to the network. The most accessible entry point is a Host: the minimum specification is a quad-core CPU, 1 GB of RAM, 50 GB of disk, and a 15 Mbit/s connection, and it runs happily behind a home router. Gateways and Stargates demand progressively more bandwidth, hardware, and availability. Node operators stake XE and earn rewards for the capacity and reliability they provide — the economic engine described in What is the Edge Token? If you'd rather not supply hardware yourself, nodes in the network backbone are made available for staking, with yields split between the staker and the network's development fund. Full setup instructions live in the network nodes wiki , and you can watch the live network at edge.network/network . See the network in action Explore the live map of nodes powering Edge, or deploy your first resource on them. Explore the Network Start Free Related articles What is an Edge Server? 6 min What is the Edge Token? 6 min What is a Decentralised Cloud? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is an Edge Server? URL: https://edge.network/academy/what-is-an-edge-server/ Markdown: https://edge.network/academy/what-is-an-edge-server.md JSON: https://edge.network/json/academy/what-is-an-edge-server.json _An edge server is a server near end users that handles requests locally. Learn how edge servers work in a CDN and how they differ from origin servers._ Back to Academy Information 7 min read What is an Edge Server? Edge servers are the workhorses of the modern internet — the machines that make websites feel instant by answering requests from just down the road instead of across an ocean. Edge server definition An edge server is a server located near end users — at the "edge" of a network — that handles requests locally instead of passing them back to a central data centre. Edge servers cache content, terminate connections, and increasingly run application code, so that most requests are answered within a few milliseconds of the user rather than travelling to a distant origin. Together, many edge servers form an edge network . Each individual server is ordinary hardware; the value comes from where the servers are, and from the routing intelligence that sends every user to the nearest one. How edge servers work in a CDN In a content delivery network , edge servers act as caches. The first time a user near a given location requests a file, the edge server fetches it from the origin, serves it, and keeps a copy. Every subsequent request for that file from the same area is served straight from the cache — no round trip to origin at all. This does two things at once. Users get content from a server that might be ten milliseconds away instead of two hundred. And the origin server sees only a trickle of traffic — cache misses and updates — instead of every request from every user. During a traffic spike, the edge absorbs the load. Modern edge servers do more than cache: they terminate TLS connections close to the user (which speeds up connection setup), optimise images, filter malicious traffic, and answer DNS queries . The step beyond that — running your own code on edge servers — is covered in CDN vs Edge Computing . Edge server vs origin server Origin Server Edge Server Single source of truth for your application Many copies distributed near users Usually one location (or a few regions) Hundreds or thousands of locations Handles every request if unprotected Absorbs most requests before they reach origin Distance to users determines latency Positioned specifically to minimise latency Failure means downtime Failure means traffic shifts to a neighbour The two work together: the origin remains the authoritative source of your application and data, while edge servers handle the volume. Most requests should never reach origin. Where edge servers are located Traditional CDN operators place edge servers in internet exchange points and carrier data centres in major cities — wherever many networks meet. The economics of leasing space limit how many locations one company can cover, so most centralised CDNs operate somewhere between a few dozen and a few hundred points of presence, and increasingly in smaller edge data centres nearer to users. Edge takes this further. Because our network is built from nodes contributed by independent operators, edge servers exist wherever operators run them — 988 nodes today, spread across cities, towns, and regions that centralised providers don't reach. The network routes each request to the nearest node with capacity. What running an edge server involves On Edge, anyone can run an edge server. Operators stake tokens, contribute capacity, and earn rewards for the traffic they serve. The network has three node types: Host Provides processing and storage capacity. Designed for mixed devices, and can run behind a home router with no special configuration. Gateway The entry point to the network. Gateways aggregate Host capacity and route each job to the Hosts best placed to complete it quickly. Stargate The masternodes of the network. Stargates run the XE blockchain, provide DNS for network resources, and oversee secure operation. A Host can run on modest hardware — the minimum specification starts at a quad-core CPU, 1 GB of RAM, and 50 GB of disk. See the network nodes wiki and the Host setup guide for details, or read about the network . Use the edge, or become part of it Deploy on 988 edge servers, or run a node and earn rewards for the capacity you contribute. Start Free Run a Node Related articles What is an Edge Network? 8 min What is an Edge Data Center? 6 min What is a Decentralised Cloud? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is Edge Network? URL: https://edge.network/academy/what-is-edge-network/ Markdown: https://edge.network/academy/what-is-edge-network.md JSON: https://edge.network/json/academy/what-is-edge-network.json _Edge Network is a cloud platform — CDN, compute, storage, DNS, bot protection, and AI site assistants — running on a distributed network of nodes, with zero egress fees and generous free tiers. The company, the products, and how it works._ Back to Academy Information 6 min read What is Edge Network? Not the concept — the company. Who we are, what we run, and why the platform is built the way it is. Edge Network, in one paragraph Edge Network (often just "Edge") is a cloud platform offering CDN, compute, object storage, DNS, bot protection, and AI site assistants. Instead of running everything from centralised data centres, it operates a distributed network of nodes — including hardware contributed by independent operators — placing capacity closer to the people using it. The commercial result of that architecture: zero egress fees on every product, genuinely useful free tiers, and billing designed so a surprise bill can't happen. A note on names: "edge network" is also a generic term for infrastructure placed near users — the concept this company is named after and built on. This page is about Edge Network the platform, found at edge.network. What Edge offers Six products on one account, one console, and one prepaid balance. Full rates on the pricing page . CDN Global content delivery with zero egress fees. Free tier: 3 deployments and 500k requests a month, then $0.25 per million requests. Compute Virtual machines priced per resource — vCPU, RAM, disk — billed hourly from a prepaid balance. Storage S3-compatible object storage on NVMe. Free to 5 GB, then $0.015/GB-month, with free egress at any scale. DNS Authoritative anycast DNS, free for everyone — up to 50 zones with unlimited records. Shield Bot protection without puzzles: invisible checks, a 1–100 humanity score, and verified AI-agent access. Free forever. Assist Conversational AI for any website, grounded in your own content. 250 answered questions a month free, then $0.01 per question. How it's different A distributed network, not data centres Edge runs on a global network of contributed and strategically placed nodes rather than a handful of centralised data centres. Capacity lives closer to users, and bandwidth isn't a scarce, capitalised resource. Zero egress fees No Edge product charges for data transfer out, at any volume, in any region. Bills are based on what you use or store — never on bytes moved. No surprise bills, by design Free tiers hard-cap instead of silently billing. Paid usage draws from a prepaid balance against budgets you set. A surprise bill is structurally impossible. Built for AI agents A first-class Agent API and MCP server let coding agents discover, deploy, and manage Edge resources autonomously — including self-signup with no human in the loop. A short history Edge has been building the distributed network since 2018 — first the network layer itself, run with independent node operators, then the products on top of it. The network settles node earnings and governance on XE, its own fast, feeless ledger , and network changes are decided through public governance proposals . 2018 Edge founded, with a vision for decentralised cloud infrastructure 2020 Mainnet launch with the first independent node operators 2022–2025 CDN, DNS, Compute, and Storage launched to the public 2026 Shield (bot protection) and Assist (AI site assistants) launched The fuller story, including the team, is on the about page . See it for yourself Free account, no card required — DNS and Shield free forever, free tiers on everything else. Start Free View Pricing Related articles What is an Edge Network? (the concept) 8 min Terminology 8 min Zero Egress Fees Explained 6 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is Edge Storage? URL: https://edge.network/academy/what-is-edge-storage/ Markdown: https://edge.network/academy/what-is-edge-storage.md JSON: https://edge.network/json/academy/what-is-edge-storage.json _Edge storage keeps data on servers close to end users. Learn how edge object storage works, what it costs, and why zero egress fees change the economics._ Back to Academy Information 7 min read What is Edge Storage? Storing data centrally and serving it globally means every download pays a distance tax. Edge storage removes it — and, done right, removes the egress bill too. Edge storage, defined Edge storage is data storage distributed across servers close to end users — the edge of the network — rather than held in a single central data centre. When a user requests a file, it is served from a nearby location instead of crossing continents, which means faster downloads, lower latency, and less load on core infrastructure. In practice, edge storage usually means object storage — the model popularised by Amazon S3, where files are stored as objects in buckets and accessed over HTTP — combined with edge delivery, so reads are answered from the location nearest the requester. How edge storage works You upload objects through an API — with Edge, an S3-compatible one — and the platform handles placement and replication across the edge network . When the data is requested, it's cached and served from the edge server nearest to the user, so a photo uploaded in London is served to a user in Singapore from Singapore's side of the world, not from London. This pairs naturally with a CDN : the storage layer is the durable source of truth, and the delivery layer keeps hot content at the edge. On Edge the two are part of the same platform, so buckets work as CDN origins without extra configuration or transfer fees between services. Edge object storage solutions Edge Storage is scalable object storage built for edge deployments: S3-compatible, backed entirely by NVMe, and delivered from the network's edge locations with 99.99% durability. It's designed for the workloads object storage does best — static assets, media files, user uploads, backups, CDN origins, data lakes, and logs. S3-Compatible API Works with existing S3 tooling and SDKs, so migrating is a config change rather than a rewrite. All NVMe Every object lives on NVMe storage. No cold tiers, no retrieval delays — data is instantly accessible. Encrypted at Rest AES-256 encryption for all stored data, with signed URLs and fine-grained access control. Versioning Built In Automatic version history for all objects, so previous versions can be restored at any time. What does edge storage cost? Edge Storage is free for the first 5 GB, then $0.015 per GB-month — with no egress fees and no per-request charges at any volume. Storage is the only line item. Paid usage is opt-in: you set a monthly budget, and usage is billed hourly from a prepaid balance, so a surprise bill is impossible by design. Here's how the published standard rates compare: Provider Storage Egress Requests Edge Storage $0.015/GB-month Free Free AWS S3 $0.023/GB-month $0.09/GB $0.40/M reads, $5.00/M writes Google Cloud Storage $0.020/GB-month $0.12/GB $0.40/M reads, $5.00/M writes Cloudflare R2 $0.015/GB-month Free $0.36/M reads, $4.50/M writes Published standard on-demand rates. See storage pricing for a calculator that models your exact workload. Why zero egress fees matter With traditional cloud storage, keeping data is cheap — serving it is expensive. At $0.09–0.12 per GB of egress, a product that stores 250 GB but serves 500 GB a month pays far more for downloads than for storage itself. The more successful your product, the worse the bill. Edge charges nothing for egress or requests, at any volume. The economics flip: costs track how much you store, not how popular you are. For media-heavy products, user-generated content, and anything that pairs storage with a CDN, this is usually the single biggest line-item saving of moving to edge storage. Store at the edge 5 GB free, S3-compatible, zero egress fees. No card required to start. Start Free See Storage Pricing Related articles What is the Edge Cloud? 7 min What is an Edge Server? 7 min CDN vs Edge Computing: What's the Difference? 7 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is the Agentic Cloud? URL: https://edge.network/academy/what-is-the-agentic-cloud/ Markdown: https://edge.network/academy/what-is-the-agentic-cloud.md JSON: https://edge.network/json/academy/what-is-the-agentic-cloud.json _How AI agents are replacing manual cloud operations — and how Edge Network is built from the ground up for autonomous infrastructure management._ Back to Academy Agentic Cloud 6 min read What is the Agentic Cloud? The shift from human-operated infrastructure to AI-managed infrastructure — and why it matters for every developer, founder, and enterprise. The cloud is changing For the last two decades, cloud computing has required humans to do the heavy lifting. You learn the platform, read the docs, write the config files, set up the pipelines, and monitor the dashboards. Whether it's AWS, GCP, or Azure, the pattern is the same: the cloud provides the tools, and you figure out how to use them. The agentic cloud flips this model. Instead of you operating the cloud, an AI agent does it for you. You describe what you need — "deploy my app with a CDN, database, and custom domain" — and the agent handles provisioning, configuration, DNS, SSL, and monitoring. Autonomously. This isn't a future concept. It's happening now. Coding assistants like Cursor, Windsurf, and Claude can already deploy infrastructure when given the right APIs. The question isn't whether agents will manage cloud infrastructure — it's whether your cloud platform is ready for them. Traditional vs. Agentic The operational model is fundamentally different. Traditional Cloud Agentic Cloud Read documentation, learn CLI, configure manually Agent discovers capabilities, deploys via natural language Copy-paste API keys, manage secrets, configure SDKs Single access code with scoped permissions and budget limits Write scripts for scaling, monitoring, alerting Agent monitors, scales, and resolves issues autonomously Separate dashboards for billing, resources, logs Agent sees everything in one discovery call Requires DevOps expertise and certifications Anyone can deploy — describe what you want, the agent builds it How it works on Edge Edge Network is designed from the ground up for agents. The workflow is straightforward: 1. Generate an Agent Access Code In the console under Agent Access, create a code with the permissions and budget your agent needs. This is a scoped credential — not your account API key. 2. Give your agent the URL and code Pass your coding assistant the Edge agent endpoint and the access code. The agent calls the discovery API and immediately understands what it can do. 3. Describe what you need "Deploy my Next.js app with a CDN and custom domain" or "Set up a staging environment that mirrors production." Natural language, not YAML. 4. The agent handles the rest Provisioning, configuration, DNS, SSL, and deployment — all handled autonomously. The agent reports back what it did, what it cost, and how to access your resources. Built for agents Every part of the Edge API is designed with autonomous agents in mind. Discovery API One endpoint returns everything an agent needs — available products, current usage, plan limits, and budget. No documentation crawling. Agent Access Codes Scoped, time-limited credentials designed for agents. Set budget caps, restrict products, and control permissions without sharing your account keys. Project-Based Resources Group VMs, CDN deployments, DNS zones, and storage buckets into a project. Health check, scale, or tear down an entire app in one call. Dry Run Mode Preview any action before committing. Your agent can show you exactly what would happen and what it would cost before making changes. Budget-Aware Operations Every API response includes cost context. Hard and soft caps prevent runaway spending. Your agent operates within limits you define. Human-Readable Responses Every response includes a tell_user field — a plain English summary your agent can relay directly to you without interpretation. Who is the agentic cloud for? Developers Stop context-switching between your IDE and cloud dashboards. Your coding assistant deploys while you keep building. Founders & vibe coders No AWS certifications needed. Describe what you want and ship. The agent handles the infrastructure complexity you shouldn't need to learn. Agencies Deploy client projects faster. Give each project its own agent access code with budget limits. Scale without scaling your ops team. Enterprises Your DevOps team becomes a platform team. Define policies and budgets, let agents handle execution. Humans focus on strategy, not tickets. Ready to try it? Create an agent access code and let your coding assistant deploy something. It takes about 30 seconds. Create Access Code Read the Agent Docs State of the Cloud 2026 Report Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is the Edge Cloud? URL: https://edge.network/academy/what-is-the-edge-cloud/ Markdown: https://edge.network/academy/what-is-the-edge-cloud.md JSON: https://edge.network/json/academy/what-is-the-edge-cloud.json _The edge cloud delivers cloud services — CDN, compute, storage, DNS — from servers near your users instead of central data centres. Learn how it works._ Back to Academy Information 7 min read What is the Edge Cloud? The cloud gave us on-demand infrastructure. The edge cloud puts that infrastructure where it actually belongs: next to your users. Edge cloud, defined The edge cloud is cloud computing delivered from servers distributed close to end users, rather than from a small number of centralised data centres. It offers the same on-demand services as traditional cloud — compute, storage, content delivery, DNS — but runs them across an edge network of many smaller locations, so every user is served from nearby. You still get the things that made the cloud attractive in the first place: no hardware to buy, pay for what you use, scale on demand. What changes is the geography. Instead of choosing "us-east-1" and accepting that users in Sydney will have a slower experience, your workload lives everywhere your users are. Edge cloud vs traditional cloud Traditional Cloud Edge Cloud Services run in a few large regions Services run at many locations near users You pick a region and hope your users are near it The network routes every user to the closest capacity Latency varies wildly by geography Consistently low latency worldwide Egress fees penalise serving your own data Delivery from the edge, without the bandwidth bill Scaling means bigger machines in the same place Scaling means more locations closer to demand The two models are complementary in practice: many teams keep databases and heavy back-office systems in a central cloud while moving delivery, caching, and latency-sensitive work to the edge cloud. What makes up an edge cloud platform An edge cloud platform is more than a cache. To replace centralised infrastructure for real workloads, it needs the full set of cloud services, each running at the edge: CDN Static content cached and served from the nearest edge location, with zero egress fees. Compute & GPUs Virtual machines and GPU capacity running on the network, priced per resource and billed hourly. Object Storage S3-compatible storage on NVMe, delivered from the edge with no egress or per-request charges. DNS Authoritative DNS answered from edge locations worldwide, so lookups resolve fast everywhere. Edge cloud use cases Any workload where distance to the user shows up in the experience — or the bill — is a candidate for the edge cloud. Media & content delivery Websites, video, downloads, and APIs served from the nearest location, without egress fees eating the margin. Latency-sensitive applications Gaming, real-time collaboration, and interactive apps where tens of milliseconds are the difference between fluid and frustrating. Storage-heavy products User uploads, backups, and media libraries in edge storage that's fast to write and free to serve. Globally distributed audiences Products with users on several continents get consistent performance without multi-region cloud architecture. How Edge delivers the edge cloud Edge runs its edge cloud on a decentralised network of 988 nodes contributed by independent operators around the world. Rather than one company leasing data centre space, capacity comes from many participants who stake tokens to join the network and earn rewards for the traffic they serve. The practical result is an edge cloud with far more locations than a company could build alone, no single point of failure, and structurally lower costs — which is why Edge can offer pricing with zero egress fees across CDN, storage, and compute. Free tiers are available for every service, so you can try the edge cloud without a card. Try the edge cloud CDN, storage, compute, and DNS on one edge network. Start free — no card required. Start Free See Pricing Related articles What is an Edge Network? 8 min What is Edge Storage? 7 min CDN vs Edge Computing: What's the Difference? 7 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is the EDGE Token? URL: https://edge.network/academy/what-is-the-edge-token/ Markdown: https://edge.network/academy/what-is-the-edge-token.md JSON: https://edge.network/json/academy/what-is-the-edge-token.json _EDGE is the utility token of the Edge Network, used to pay for cloud services, stake nodes, and take part in governance. A factual guide to how it works._ Back to Academy Information 6 min read What is the EDGE Token? EDGE is the utility token behind the Edge Network — the mechanism that pays for services, secures nodes, and coordinates a decentralised cloud. EDGE, defined EDGE (often written $EDGE) is the utility token of the Edge Network , a decentralised cloud platform powered by independent node operators. It is used to purchase Edge services, to stake nodes into the network, for governance, and for node rewards. EDGE is also available as an ERC-20 token on Ethereum, bridged 1:1 with the token on Edge's own blockchain. Unlike tokens whose only function is to be traded, EDGE is tied to working infrastructure: a network of 988 nodes delivering CDN , storage , compute , and DNS services to real customers. EDGE and XE: how they fit together Edge runs its own Layer 1 blockchain, known as XE — a chain designed for fast, fee-free transactions mapped to resource usage within the network. XE is the economic and coordination layer: it records staking, node activity, governance, and rewards. EDGE is the tradable utility token, available as an ERC-20 on Ethereum and bridged 1:1 in and out of the Edge chain via the network bridge. In practice: node operators stake and earn on the XE chain, and the bridge connects that internal economy to Ethereum, where EDGE can be held in any wallet that supports ERC-20 tokens. When services are purchased in EDGE, the tokens are automatically bridged into the network. For the full picture of the chain itself, read What is XE and how does it Power Edge? What the EDGE token is used for EDGE has four core functions within the network: Paying for Services Cloud services on Edge — CDN, compute, storage, DNS — can be purchased directly in EDGE. Card payments are also supported. Node Staking Edge is a proof-of-stake network. Contributing a node requires a stake, locked for the duration the node is online. Bad actors have their stake penalised and burned. Governance Holding a stake in the network allows participation in governance: proposals covering protocol parameters, funds, and network upgrades. Node Rewards Operators earn rewards for the capacity they contribute, drawn from a dedicated node reward pool released gradually over time. Supply and tokenomics A total of 50 million EDGE were minted and distributed at genesis, with a further 10 million locked in the network to be released as node rewards. Rewards are emitted on a declining curve — a maximum of 10% of the remaining reward pool per year — so emissions decrease every year. The network also has deflationary mechanics: 25% of network revenue is burned monthly, sent to the chain's zero address, and stakes reclaimed from misbehaving nodes are burned too. Changes to tokenomics run through project governance. The full breakdown — initial distribution, emission schedules, the bridge, and supply endpoints for verification — is maintained in the Edge tokenomics wiki . A token backed by working infrastructure The distinguishing feature of EDGE is that demand comes from usage. Developers and organisations pay for cloud services; operators stake to contribute nodes and earn rewards for serving traffic. Every part of the token's design maps to a function of the decentralised cloud it supports. Edge deliberately avoids price talk. The token exists to make the network work — aligning the interests of the people who provide capacity with the people who use it — not as a speculative instrument. Where EDGE is available EDGE has been available to trade on Uniswap since September 2021, via a single $EDGE:$WETH pairing on a Uniswap V3 pool. As an ERC-20 token it can be held in any Ethereum wallet that supports custom tokens, and bridged into the Edge Network 1:1 using the network bridge. Details, contract addresses, and token tracking links are listed in the wiki . You don't need to hold EDGE to use the platform — services can be paid for by card as well, with free tiers across CDN, storage, and DNS to get started. See the network EDGE powers Explore the infrastructure behind the token, or try the platform free — no card required. Explore Our Network Start Free Related articles What is XE and how does it Power Edge? 7 min What is a Decentralised Cloud? 8 min What is an Edge Network? 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What is XE and how does it Power Edge? URL: https://edge.network/academy/what-is-xe/ Markdown: https://edge.network/academy/what-is-xe.md JSON: https://edge.network/json/academy/what-is-xe.json _XE is Edge Network's Layer 1 blockchain: the economic and coordination layer for the network. Learn how XE enables staking, governance, rewards, and service payments on Edge._ Back to Academy Information 7 min read What is XE and how does it Power Edge? XE is the blockchain that underpins Edge Network — the economic and coordination layer for node operators, governance, and payments. What is XE? XE is Edge Network's own Layer 1 blockchain. It is not Ethereum-based — it is a separate chain designed specifically to serve the Edge Network. It functions as the economic and coordination layer: the mechanism by which node operators participate, stake, earn, and govern. Node operators stake XE tokens to join the network. Staking signals commitment and enables reputation tracking. Nodes that perform well earn rewards; those that misbehave or go offline risk penalties. The blockchain records this activity transparently. What XE is used for XE serves several distinct purposes within the Edge ecosystem: Node staking and reputation — Operators lock XE to run nodes . Stake size and performance history affect reputation and workload assignment. Governance — Token holders can participate in decisions about protocol parameters, feature prioritisation, and network upgrades. Rewards for providing capacity — Node operators earn XE (or EDGE) for serving compute, storage, CDN, or DNS traffic. Paying for services — On the Edge platform, users pay for cloud services using EDGE tokens. EDGE is the platform token; XE underpins the chain that records and settles activity. The relationship: XE is the chain and its native token; EDGE is the token used for platform payments (CDN, compute, storage, DNS). The two work together — XE secures and coordinates the network; EDGE facilitates usage and payments. The community node network Today, Edge runs on 2,200+ nodes globally. These are community-operated — individuals and small operators who run hardware, stake XE, and earn rewards for serving traffic. The blockchain enables trustless coordination: no central authority assigns work; the protocol does it based on stake, reputation, and availability. This is not a typical crypto project. Edge is infrastructure-backed utility. The token has real demand from actual cloud services: developers pay in EDGE for CDN, compute, storage, and DNS. That creates genuine economic activity flowing through the network, not speculation alone. Summary XE is the Layer 1 blockchain that powers Edge Network. It coordinates node participation, staking, governance, and rewards. EDGE is the token used to pay for platform services. Together they enable a decentralised cloud that runs on community nodes, with real demand from developers and organisations using the infrastructure. Next steps What is a Decentralised Cloud? Community Nodes concept Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### What Makes Edge Better for the Environment? URL: https://edge.network/academy/edge-and-the-environment/ Markdown: https://edge.network/academy/edge-and-the-environment.md JSON: https://edge.network/json/academy/edge-and-the-environment.json _How Edge Network's distributed model reduces environmental impact: utilising existing spare capacity, shorter data journeys, 50% less energy than hyperscale providers, and zero new data centres built._ Back to Academy Information 6 min read What Makes Edge Better for the Environment? How Edge Network's distributed architecture reduces carbon footprint, energy use, and environmental impact compared to traditional cloud infrastructure. The environmental problem with traditional cloud Traditional hyperscale cloud providers rely on massive centralised data centres. These facilities consume enormous amounts of energy for compute, storage, and — critically — cooling. Data centres account for roughly 1–2% of global electricity use, and that figure is growing. Beyond energy, traditional cloud has significant environmental costs: land use for sprawling campuses, concrete and steel for construction, water for cooling systems, and the embodied carbon of building new facilities. Each new data centre represents years of emissions before it even serves a single request. How Edge is different Edge Network does not build data centres. Instead, it utilises existing spare capacity across 2,200+ locations worldwide. These are community-run nodes — servers that are already running, already powered, and already connected. The network harnesses underused resources rather than constructing new infrastructure. Shorter data journeys: Edge processing means data travels less. When compute happens at the edge, closer to users, transmission energy drops. Less distance means fewer hops, fewer routers, and less energy spent moving bits around the internet. Efficiency gains: Independent analysis indicates Edge can achieve roughly 50% less energy consumption per request than hyperscale providers. This stems from the distributed model: no idle servers burning energy in cavernous halls, no over-provisioned cooling, and utilisation of hardware that would otherwise run under capacity. 100% renewable where available: Node operators can run on renewable energy. Many community nodes are in homes or small offices powered by solar, wind, or grid mixes with high renewable penetration. The network inherits that flexibility. What this means in practice For developers and organisations using Edge, the environmental benefits translate into practical outcomes: Less carbon per request — Each API call, page load, or asset delivery can have a lower footprint than equivalent traffic through traditional cloud. Less water for cooling — No monolithic cooling systems; distributed nodes use ambient cooling or local HVAC where appropriate. Less concrete — Zero new data centres built. No additional land clearing, no embodied carbon in new construction. Edge is not a silver bullet — all computing has an environmental cost. But for workloads suited to distributed edge infrastructure, the model offers a materially different and often lower-impact alternative to centralised hyperscale cloud. Learn more For detailed environmental metrics, methodology, and ongoing research, see our environment page . Next steps What is XE? What is a Decentralised Cloud? Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ### Zero Egress Fees Explained URL: https://edge.network/academy/zero-egress-explained/ Markdown: https://edge.network/academy/zero-egress-explained.md JSON: https://edge.network/json/academy/zero-egress-explained.json _What egress fees are, why cloud providers charge them, and what zero egress means in practice for CDN and object storage bills._ Back to Academy Information 6 min read Zero Egress Fees Explained Egress fees are where cloud bills hide most of their cost. Here's what they are, why providers charge them, and what "zero egress" actually means. What are egress fees? Egress fees are charges for data leaving a provider's network — every gigabyte transferred out to users, to another cloud, or back to your own systems. Zero egress means exactly what it says: data transfer out is free, at any volume, so your bill is based on what you use or store rather than on how much you move. The asymmetry is the tell: uploading data into a cloud (ingress) is almost always free, while getting it back out is metered. Once your data and traffic are inside, every download, restore, and page view has a price attached. Why do cloud providers charge for egress? Part of the answer is genuine cost: centralised providers build and operate enormous data centres and the network capacity connecting them, and metering bandwidth is one way to recover that investment. But egress pricing has long outgrown its cost basis — the per-gigabyte rates charged by major clouds are many multiples of what wholesale bandwidth actually costs. The other part is strategic. Free ingress and expensive egress makes it cheap to move in and costly to leave. Egress fees act as a switching cost: migrating a large dataset to a competitor, or even serving your own content from elsewhere, incurs a bill sized to discourage the attempt. That's why egress charges attract regulatory attention as a form of vendor lock-in. They also make bills unpredictable. Storage and compute are things you provision deliberately; egress is driven by your users' behaviour. A traffic spike — the best thing that can happen to your product — becomes the worst thing that can happen to your invoice. What zero egress means at Edge Edge doesn't charge for bandwidth anywhere in its platform — a position explained in Zero Egress: Why We Don't Charge for Bandwidth . Because the network runs on the distributed spare capacity of independent nodes rather than on centralised data centres, bandwidth isn't the scarce, capitalised resource it is for traditional clouds — so it isn't a line item. In practice, on the CDN you pay $0.25 per million requests beyond a free tier of 500,000 requests a month, and nothing for the gigabytes delivered — the same price in every region, with no premium routes. On Storage you pay $0.015 per GB-month for what you store (the first 5 GB free), and retrieving your own data — a backup restore, a data migration, public file serving — costs nothing at any scale. Zero egress also changes behaviour, not just bills. You can serve media-heavy sites without fearing success, restore backups without a penalty, and move data freely between providers — the lock-in mechanism simply isn't there. CDN egress rates compared Published per-GB egress rates from our CDN comparison pages . Provider Egress Fees Edge Free — at every scale, in every region Bunny.net $0.01–0.06/GB CDN77 $0.049/GB+ Fastly $0.08–0.28/GB Akamai $0.10/GB+ Where zero egress pays off The more bytes you move relative to what you store or serve, the bigger the difference. Media delivery Video, audio, and image-heavy sites move terabytes per month. On per-GB pricing, bandwidth dwarfs every other cost; on zero egress, it disappears. Backups & recovery Egress fees mean paying to retrieve your own data exactly when you need it most. Zero egress makes restores free, however large. Portability Without an exit toll, multi-cloud setups and provider migrations become engineering decisions rather than financial ones. Stop paying for bandwidth CDN and object storage with zero egress fees — free tiers included, never a surprise bill. Start Free Explore Edge Storage Related articles CDN Pricing Comparison 8 min Decentralised Cloud Storage Explained 8 min Cost Optimization 8 min Coming soon Edge Accreditation Become a certified Edge practitioner. A structured programme covering the whole platform, with a verifiable certificate at the end. Sign up now for updates. Sign up for updates Learn more about accreditation --- ## Products ### Assist Examiner | How Answerable Is Your Content? URL: https://edge.network/assist/examiner/ Markdown: https://edge.network/assist/examiner.md JSON: https://edge.network/json/assist/examiner.json _An AI review of your content through your visitors' questions: coverage score, unanswered questions, dead pages, stale answers, and suggested fixes — free on every site._ Assist Assist The Examiner An AI review of your content through the lens of your visitors' real questions — what's covered, what's missing, what's contradicting itself — with specific fixes. Free on every site. Add Assist to Your Site Try the Live Demo What the Examiner reviews Your visitors' questions are the most honest audit your content will ever get. The Examiner reads both sides — the questions and the content — and tells you where they don't meet. Coverage Score How much of what your visitors ask can your content actually answer? A single 0–100 score, tracked over time, so you can see whether your content is keeping up with your audience. Unanswered Questions The questions Assist couldn't answer, clustered by topic and ranked by how often they're asked. This is your content roadmap, written by your visitors. Dead Weight Pages that never get cited in any answer. Either nobody asks about them — or they're written in a way retrieval can't use. Both are worth knowing. Stale & Conflicting Content Pages that contradict each other or contradict your pinned facts — the raw material of wrong answers, caught before a visitor sees one. Suggested Overrides Where a pinned fact would fix a cluster of shaky answers, the Examiner drafts it for you. Accept it in one click and it takes precedence in every answer. Prioritised Findings Every review produces a plain-English report with prioritised fixes — edit this page, add that fact, retire those three. No dashboards to decode. Plain English, specific fixes No analytics safari. The Examiner writes what a good content strategist would tell you after reading a month of your visitors' questions — and hands you the one-click fixes. Findings ranked by how many visitors each one affects Suggested pinned facts, pre-drafted — accept in one click Coverage score tracked review over review, so you can see improvement // Examiner review — last 30 days Coverage score: 78/100 (up from 71) ⚠ 24 visitors asked about refunds — no page covers your refund policy ⚠ /pricing and /faq disagree on the free tier limit → Suggested pinned fact: "The free tier includes…" [Accept] → 3 pages never cited in any answer — review or retire ✓ Top 20 questions all answered with strong citations How it works Three steps, under a minute, no configuration. 1 Open the Examiner tab Every Assist site has an Examiner tab in the console. 2 Run a review The analysis covers your content and your last 30 days of visitor questions, and takes under a minute. 3 Apply the fixes Findings come with specific recommendations — fix the content at source, or accept a suggested pinned fact in one click. Your last ten reviews are saved. Find out what your content can't answer Add Assist, let it field real questions for a few weeks, and the Examiner will tell you exactly where your content falls short. Free on every site. Start Free --- ### Assist Help | Expert Setup for AI Answers URL: https://edge.network/assist/help/ Markdown: https://edge.network/assist/help.md JSON: https://edge.network/json/assist/help.json _Get hands-on help from Edge experts: content ingestion, answer quality tuning, white-label setup, and large knowledge base deployments._ Assist Expert Services Need a hand? Let our team get Assist answering brilliantly on your content — ingestion, answer tuning, branding, and knowledge bases of any size. We run it on our own site every day. How we can help Whether you're adding AI answers for the first time or replacing an expensive tool, our team makes it painless. Content & Ingestion Setup We'll wire Assist into your site build or storage bucket, tune the chunking, and make sure every page and document you care about is in the index. Answer Quality Tuning We'll review your visitors' real questions, pin the facts that matter, curate answers for high-stakes topics, and close the gaps your content leaves open. White-Label & Multi-Site Rolling Assist out across several sites, or under your own assistant brand? We'll set up the theming, naming, and per-site configuration for you. Large Knowledge Bases More than 10,000 documents? Our Expert Services team designs custom deployments — private knowledge bases, access controls, and retrieval tuned to your corpus. Learn more about Expert Services Sound familiar? These are the kinds of challenges Assist — and our team — solve every day. Our site search is useless and visitors can't find answers Support keeps answering the same twenty questions We're quoted $500+/month for an AI answer widget Our docs are good but nobody reads them We have thousands of PDFs and reports nobody can search We want AI on our site but it must not make things up We need the assistant under our own brand, not a vendor's We want to know what our visitors are actually asking We tried a chatbot before and it embarrassed us Get in touch Tell us about your site and what you'd like Assist to answer, and we'll get back to you within 24 hours with a plan. First Name Last Name Work Email Website Content Size Roughly how much content? Under 100 pages 100 – 1,000 pages 1,000 – 10,000 documents More than 10,000 documents Not sure How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 An expert will look at your content and map out the ingestion approach. 3 We'll set up Assist on your site, tune the answers, and configure your branding. 4 Assist is live. We'll review the first weeks of real questions with you and refine. Typical setup time Under 48 hours From first call to answers live on your site --- ### Assist Interface URL: https://edge.network/assist/interface/ Markdown: https://edge.network/assist/interface.md JSON: https://edge.network/json/assist/interface.json _A close look at the Edge Assist widget: instant search and streamed, cited AI answers in one interface — annotated, component by component._ Assist Interface One widget. Every answer. Assist is one interface with two modes: instant search as visitors type, and a conversation the moment they ask. Here's the whole thing, component by component — then press ⌘K and try the real one. The Search View What visitors see first: results before they finish typing, and a standing offer to turn the query into a question. 1 storage pricing 2 Ask Edge Assist: "storage pricing" 3 Storage Pricing /storage/pricing Edge Storage — S3-compatible object storage /storage Platform Pricing /pricing 4 Edge Assist · answers come from edge.network content Powered by Edge Assist esc to close 1 One box, two jobs Search and ask share a single input. It opens from the launcher, a search icon, or ⌘K — and it replaces your site search outright. 2 One keypress from search to answer The top row always offers the question form of what was typed. Hit return and the same words become a grounded AI answer instead of a list of links. 3 Instant results, free forever Full-text results over your ingested content appear as visitors type — no AI call, no charge, unlimited. Snippets and titles come straight from your pages. 4 Your brand, if you want Any paid usage removes the badge; white-label goes further with your own assistant name and icon everywhere visitors see it. The Conversation View One return-key later. Streamed answers grounded in your content, cited as they're made — with a human one click away. 1 Conversation memory Follow-ups like "how fast?" resolve against the thread so far. Each surface keeps its own session, and visitors can reopen recent conversations or start fresh. 2 Grounded, streamed answers Answers stream token by token over SSE and are composed only from your ingested content and pinned facts — no invented prices, no off-site tangents. 3 Citations built in Claims link inline to the pages they came from, with source chips underneath. Visitors verify in one click — and you see which pages carry your answers. 4 Follow-ups where you expect them Once a conversation starts, the input docks below the thread with a send button — chat-style. New conversations open with configurable suggested questions; cached answers return instantly. 5 Human handoff When Assist can't answer — or a visitor wants a person — they leave an email and the whole transcript lands in your inbox. Answers and leads from one widget. 1 Edge Assist New conversation How much does storage cost? 2 Storage is $0.015 per GB per month on all-NVMe hardware, and the first 5 GB are free. There are no egress or per-request fees at any volume — see storage pricing for worked examples. Storage Pricing Platform Pricing 3 4 Ask a follow-up… 5 Edge Assist · answers come from edge.network content Powered by Edge Assist Need a human? Leave your email And Everything Around It The panel is half the story — the other half is how invisibly it fits into your site. Expanded mode On desktop the panel expands to full screen with a citations rail: every source from the conversation, plus your "Keep exploring" links. Made for mobile Below tablet width the panel fills the viewport — a native-feeling assistant, not a floating card. A hosted page covers apps and link-outs. Matches your site Accent colour, launcher position and copy, welcome message, and placeholder are all yours. Styles are isolated in a shadow root — your CSS never leaks in, ours never leaks out. One line of code A single script tag, a few kilobytes of dependency-free JavaScript, loaded lazily. No framework, no iframe jank, no impact on your page speed. Don't take the mockup's word for it Everything on this page is live on this site right now — the search icon above and the launcher in the corner are the exact widget you'd ship. Press ⌘K and ask it something hard. See the full demo Add it to your site --- ### Bot Weather Report | Edge Shield URL: https://edge.network/shield/weather/ Markdown: https://edge.network/shield/weather.md JSON: https://edge.network/json/shield/weather.json _Live, anonymous bot pressure across the Edge Shield network over the last 24 hours: challenge volume, escalation rates, humanity scores, and replay attempts. No customer or visitor data — just the weather._ Shield BOT WEATHER REPORT What the Bots Are Doing Right Now Live bot pressure across the whole Edge Shield network over the last 24 hours, computed from the same hourly aggregates that power every widget's analytics. No customer data, no visitor data — just the weather. Updated every 5 minutes. Reading the instruments… The weather station isn't answering right now. Try again shortly. — — Challenges issued — Avg humanity score — Interactive escalations — Replay attempts caught — Tarpit challenges served — Verified agents Last 24 Hours Challenges Escalations How the Pressure Index Works The bot pressure index is a 0–100 blend of four network-wide rates over the last 24 hours: the share of solved traffic scoring in the bottom three humanity-score deciles, the rate of background attempts escalated to an interactive challenge, the siteverify failure rate, and the replay-attempt rate. Everything is computed from hourly aggregate counters — Shield keeps no per-visitor data, so there is nothing more granular to leak even if we wanted to. Honeypot widgets (which exist to attract bots on purpose) are excluded so they don't skew the picture. The raw data behind this page is public: GET shield.edge.network/weather — build your own dashboard, status widget, or terminal toy with it. Your Forms Deserve Better Weather Two lines of code, free forever, and no puzzles for the humans caught in the storm. Create Free Account --- ### CDN Comparison: Edge vs AWS, Cloudflare, Akamai & More URL: https://edge.network/cdn/compare/ Markdown: https://edge.network/cdn/compare.md JSON: https://edge.network/json/cdn/compare.json _Compare CDN providers on features and pricing. See how Edge CDN stacks up against AWS CloudFront, Cloudflare, Akamai, Bunny, Fastly, and CDN77._ CDN CDN How Edge Compares See how Edge CDN stacks up against the competition. Feature Comparison A detailed breakdown of how we compare to other CDN providers. Feature Edge AWS Cloudflare Akamai Egress Fees Free $0.085/GB Free $0.10/GB Edge Locations 988 30+ 300+ 350+ Instant Purge 5-10 min 5-10 min Real-time Analytics Free SSL DDoS Protection Included Extra cost Included Extra cost HTTP/3 Edge Rules Lambda@Edge Password Protection Included Lambda@Edge Paid add-on Extra cost Decentralized Transparent Pricing No Vendor Lock-in Price Comparison Most CDN bills are mostly bandwidth. Edge charges per request with zero egress fees — so costs stay flat as traffic grows. See our full CDN pricing comparison guide for a deeper breakdown. Edge AWS Cloudflare Akamai Pricing model $0.25/M requests Per GB + per request Free (plans for features) Per GB (contract) Egress / bandwidth Free $0.085/GB Free $0.10/GB Bandwidth cost, 500 GB/mo $0 $42.50 $0 $50 Free tier 3 deployments, 500k req/mo Limited Surprise-bill protection Hard caps by default Contract-based Bandwidth example assumes 500 GB/month of data transfer out at each provider's published standard rate. Edge pricing: $0.25 per million requests beyond the free tier, with zero egress fees at every scale — see CDN pricing . Detailed Comparisons Pros and cons of each provider compared to Edge. Edge vs AWS CloudFront AWS CloudFront Pros Large network Deep AWS integration Feature-rich AWS CloudFront Cons Complex pricing Egress fees add up Slow purge times Full comparison → Edge vs Cloudflare Cloudflare Pros Free tier available Large network Good security Cloudflare Cons Limited customization on free Vendor lock-in Enterprise pricing opaque Full comparison → Edge vs Akamai Akamai Pros Largest network Enterprise features Proven reliability Akamai Cons Expensive Complex setup Long contracts Full comparison → Edge vs CDN77 CDN77 Pros Competitive pricing Video streaming focus Private backbone CDN77 Cons Smaller network (50+ PoPs) Per-GB egress fees Centralized architecture Full comparison → Edge vs Bunny.net Bunny.net Pros Very affordable Developer-friendly Good feature set Bunny.net Cons Smaller network (123 PoPs) Per-GB pricing Basic DDoS protection Full comparison → Edge vs Fastly Fastly Pros Fast purge times Edge compute (VCL) Developer tools Fastly Cons Expensive egress $50/mo minimum VCL learning curve Full comparison → Why choose Edge? The key advantages that set us apart. $0 Egress fees 100% Transparent pricing 0 Lock-in Get Started with Edge CDN --- ### CDN Features URL: https://edge.network/cdn/features/ Markdown: https://edge.network/cdn/features.md JSON: https://edge.network/json/cdn/features.json _Global edge network, instant cache purge, real-time analytics, and DDoS protection. Explore all Edge CDN features._ CDN CDN CDN Features Everything you need for lightning-fast content delivery, built into one powerful platform. Core Features Enterprise-grade CDN capabilities available to every account. Global Edge Network 988 strategically placed points of presence across 6 continents ensure your content is always served from the closest location to your users. Lightning Fast Sub-20ms latency globally with our optimized network routing and edge caching technology. Instant Purge Invalidate cached content globally in under 500ms. API and dashboard support for single URLs or full purges. Smart Caching Intelligent caching algorithms that automatically optimize based on content type and access patterns. Edge Rules Create powerful rules to customize caching, redirects, headers, and request/response transformations. DDoS Protection Built-in protection against volumetric attacks at no extra cost. Your origin stays protected. Image Watermarking Automatically overlay your logo on every image served — position, size, and opacity under your control, applied at the edge with no origin changes. Password Protection Protect any domain or dev build with a username and password. Enforced at the edge before the cache — nothing is served without credentials, and authenticated traffic runs at full speed. Free SSL/TLS Automatic SSL certificate provisioning and renewal. Support for custom certificates. Real-Time Analytics Monitor traffic, bandwidth, cache hit rates, and errors in real-time with detailed dashboards. Powerful API Full-featured REST API for automation, integration, and programmatic control of your CDN. And so much more Every feature you need, included as standard. HTTP/2 & HTTP/3 Support Brotli & Gzip Compression WebSocket Support Custom Error Pages Geo-blocking Token Authentication Query String Caching Origin Shield IPv6 Support Range Requests Vary Header Support Stale-While-Revalidate Ready to get started? Deploy your first CDN distribution in under 2 minutes. Start Free Today --- ### CDN Help | Expert Services URL: https://edge.network/cdn/help/ Markdown: https://edge.network/cdn/help.md JSON: https://edge.network/json/cdn/help.json _Get hands-on help from Edge experts to overhaul your media delivery platform. Migration support, performance optimisation, and custom configuration._ CDN Expert Services Need a hand? Let our team of CDN experts help you overhaul your media delivery platform. From migration to optimisation, we've got you covered. How we can help Our expert services team has helped hundreds of companies transform their content delivery. Whatever your challenge, we've probably solved it before. Performance Optimisation We'll analyse your current setup and implement optimisations that dramatically improve load times and reduce latency. Migration Support Moving from another CDN? Our team handles the entire migration, ensuring zero downtime and seamless transition. Custom Configuration Complex caching rules, edge logic, or security requirements? We'll build a bespoke solution tailored to your needs. Rapid Deployment Get up and running fast. Our experts can have your CDN configured and optimised within days, not weeks. Learn more about Expert Services Sound familiar? These are the kinds of challenges we help solve every day. Our CDN costs are spiralling out of control We're experiencing cache miss issues Our videos buffer for users in certain regions We need to migrate off CloudFront / Akamai / Cloudflare Our current setup can't handle traffic spikes We need custom edge logic but don't know where to start Our Time to First Byte is too high We want to serve different content by region Our images and assets load slowly on mobile Get in touch Tell us about your project and we'll get back to you within 24 hours with a plan of action. First Name Last Name Work Email Company Current CDN Provider Select your current provider AWS CloudFront Cloudflare Akamai Fastly Bunny CDN CDN77 KeyCDN Other None / Self-hosted How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 A CDN expert will schedule a call to understand your requirements in detail. 3 We'll provide a tailored proposal with timeline and pricing. 4 Once approved, our team gets to work immediately. Trusted by --- ### CDN Performance: Benchmarks & Comparison URL: https://edge.network/cdn/performance/ Markdown: https://edge.network/cdn/performance.md JSON: https://edge.network/json/cdn/performance.json _Live CDN performance comparison. Independent PerfOps benchmarking measures Edge CDN median latency against major providers in real time._ CDN CDN CDN Performance Independent benchmarking shows Edge CDN consistently delivering fast response times. Real-time data from PerfOps measuring median latency. Live Performance Real-time comparison against major CDN providers over the last hour. Loading performance data... Why Edge CDN is fast Our architecture is built from the ground up for speed, not retrofitted onto legacy infrastructure. Global Edge Network Content is cached at edge locations worldwide. Users are served from the nearest PoP, minimizing latency. Optimized Caching Multi-tier caching with memory and disk storage. Hot content stays in RAM for sub-millisecond access. Rust-Powered Core Built in Rust for maximum throughput and minimal overhead. Zero-copy data handling and async I/O throughout. Independent benchmarking Performance data is collected by PerfOps, a leading independent monitoring provider. We don't mark our own homework. Real User Monitoring (RUM) from actual browsers Median algorithm reduces outlier influence Per-minute granularity for accurate trends Geographic filtering by country/region Powered by PerfOps Independent CDN monitoring PerfOps provides enterprise-grade RUM benchmarking for DNS, CDN, and cloud providers. Their methodology is trusted by thousands of companies worldwide. Learn more about PerfOps Ready for faster content delivery? Start with 100GB free bandwidth per month. No credit card required. Get Started Free Contact Sales --- ### CDN Pricing URL: https://edge.network/cdn/pricing/ Markdown: https://edge.network/cdn/pricing.md JSON: https://edge.network/json/cdn/pricing.json _A genuinely useful free tier — 3 deployments and 500k requests a month with zero egress fees — then $0.25 per million requests pay-as-you-go. Never a surprise bill._ CDN CDN Pricing A free tier that's the full product, hard-capped so it can never silently start billing — and zero egress fees at every scale. Evaluate with a real workload The free tier isn't a demo — it's the full CDN with every feature enabled, capped by volume. Custom domains, automatic SSL, image optimization, purging, and analytics are all included. Without a card on file, exceeding the cap pauses delivery rather than charging you — there's no way to accidentally run up a bill. With one, pay-as-you-go takes over seamlessly. Beyond the free tier $0.25 per million requests With a card on file, pay-as-you-go keeps you serving past 500k requests automatically. Overage bills hourly from your prepaid balance — add an optional monthly cap if you want a hard ceiling — and delivery pauses when the headroom is spent, never a surprise bill. Egress stays free. Free tier CDN Free Tier $0 /mo — billed only beyond the free tier 3 deployments 500,000 requests per month Zero egress fees Custom domains with automatic SSL Image optimization Instant cache purging Real-time analytics Create a Deployment CDN pricing at a glance Item Price Detail Free tier $0 3 deployments, 500,000 requests/month, every feature included Requests beyond free tier $0.25 per million Pay-as-you-go, billed hourly from prepaid balance Bandwidth / egress $0 Free at every scale, in every region Custom domains, SSL, image optimization, purging, analytics Included No add-on charges Enterprise volume From $499/month Volume request pricing, 99.99% SLA, account manager All prices in USD, identical in every region. What would your bill be? Slide in your traffic. Bandwidth is where CDN bills hide — and where Edge charges nothing. Requests per month Every file served counts as one request million Bandwidth per month Data delivered to visitors (egress) GB Optimized images per month Requests served through image optimization million Edge CDN $2.38 /mo 500k requests free, then 9.5M × $0.25/million. Bandwidth and image optimization are free at any volume. Paid usage is opt-in: set a monthly budget on the billing page, billed hourly from prepaid balance. The same traffic elsewhere Amazon CloudFront $83 bandwidth + $0 requests + $10 images (est.) $93 /mo Fastly $240 bandwidth + $7.50 requests + $145 images $393 /mo Bunny.net $20 bandwidth + $0 requests + $9.50 images $30 /mo $91 /month saved vs Amazon CloudFront — 97 % less. Still not counted — included free with Edge Password protection, instant purging, and real-time analytics are part of every Edge deployment, and plan-gated or DIY elsewhere. Published standard North America / Europe rates for delivery and HTTPS requests. Permanent free allowances are credited (CloudFront's always-free 1 TB and 10M requests/month, Fastly's 100k free image requests); time-limited trials are not. Image optimization uses Fastly's published Image Optimizer tiers and Bunny's $9.50/mo Optimizer; CloudFront has no native product, so its figure estimates the usual DIY route (Lambda resizing on cache misses at AWS's published rates). Flat-plan providers like Cloudflare aren't usage-comparable and are excluded. Edge charges nothing for bandwidth or image optimization. Zero egress. That's the pricing model. Most CDN bills are mostly bandwidth. Ours isn't a line item at all — data transfer out is included at every scale, in every region. Same price everywhere No regional bandwidth tiers or premium routes. Traffic served from São Paulo costs the same as traffic served from London: nothing. Hard caps by default Free tiers pause at their limits instead of billing. The only way to spend money is to explicitly set a budget first. Volume pricing at scale Enterprise volume pay-as-you-go from $499/month with volume request pricing, a 99.99% SLA, and an account manager. View full Edge pricing Pricing FAQ Everything you need to know about how CDN billing works. Is the free tier really free? Yes. A card on file is required (it's how we keep abuse out), but the free tier itself never charges. It's sized to evaluate the CDN with a real workload — 3 deployments and 500k requests a month. What happens if I exceed the free tier? Nothing silent. With a card on file, pay-as-you-go keeps you serving at $0.25 per million requests — billed from your prepaid balance (with an optional monthly cap), pausing again only if the headroom runs out. Prefer a hard stop? Turn paid usage off on the billing page and exceeding the cap pauses delivery instead of billing. Are there really no egress fees? Really. Bandwidth is included at every scale, in every region. You pay nothing for data transfer out — which is where traditional CDN and cloud bills hide most of their cost. What about high-traffic sites? Enterprise volume pay-as-you-go starts at $499/month, with volume request pricing, a 99.99% SLA, and an account manager. Talk to us and we'll price your workload precisely. Do I need a plan to use custom domains or SSL? No. Custom domains, automatic SSL, image optimization, purging, and analytics are all included in the free tier — the free tier is the product, just capped by volume. Deploy your first site free Full-featured CDN with zero egress fees — free for 3 deployments and 500k requests a month. Get Started Talk to Us About Scale --- ### CDN Regions URL: https://edge.network/cdn/regions/ Markdown: https://edge.network/cdn/regions.md JSON: https://edge.network/json/cdn/regions.json _Browse Edge Network CDN locations across Europe, the Americas, Asia Pacific, the Middle East and Africa: 6 continents with sub-20ms latency for 95% of users._ CDN CDN Global Edge Network 988+ points of presence across 6 continents, delivering sub-20ms latency to 95% of the world's internet users. Regions Edge locations strategically placed for optimal coverage. Europe 18 locations <10ms avg latency Amsterdam London Frankfurt Paris Stockholm Madrid Milan Warsaw Dublin Brussels Vienna Zurich Copenhagen Oslo Helsinki Prague Bucharest Athens North America 24 locations <15ms avg latency New York Los Angeles Chicago Dallas Miami Seattle Denver Atlanta Phoenix Toronto Montreal Vancouver San Francisco Boston Washington DC Minneapolis Houston Detroit Philadelphia San Jose Las Vegas Salt Lake City Mexico City Guadalajara Asia Pacific 12 locations <20ms avg latency Singapore Tokyo Hong Kong Sydney Seoul Mumbai Jakarta Bangkok Manila Taipei Auckland Melbourne Latin America 6 locations <25ms avg latency São Paulo Buenos Aires Santiago Bogotá Lima Quito Middle East 3 locations <20ms avg latency Dubai Tel Aviv Bahrain Africa 2 locations <30ms avg latency Johannesburg Cape Town 988+ Edge Locations 6 Continents 95% Global Coverage <20ms Avg Latency Deploy globally in minutes Your content, cached at every edge location, automatically. Start Free Today --- ### Compare CAPTCHA Alternatives | Edge Shield URL: https://edge.network/shield/compare/ Markdown: https://edge.network/shield/compare.md JSON: https://edge.network/json/shield/compare.json _Compare Edge Shield to Cloudflare Turnstile, Google reCAPTCHA, hCaptcha, and Friendly Captcha. Free, privacy-first bot protection with a humanity score._ Shield Shield How Shield Compares Free like Turnstile, scored like reCAPTCHA v3, private like nothing else. See how Shield stacks up against every alternative. Feature Comparison A detailed breakdown of Shield vs the most popular verification providers. Feature Edge Shield Turnstile reCAPTCHA hCaptcha Friendly Captcha Price Free, unlimited Free Free to 10k/mo Free tier Paid (free for non-commercial) Confidence score 1–100, every call ✗ 0.0–1.0 (v3) Enterprise only ✗ Visual puzzles Never Never v2 fallback Yes Never Invisible mode ✓ ✓ ✓ (v3) Paid ✓ Proof-of-work challenges ✓ Partial ✗ ✗ ✓ No ad-tech tracking ✓ ✓ ✗ ✓ ✓ No per-visitor data stored ✓ ✗ ✗ ✗ ✓ Offline token verification (JWKS) ✓ ✗ ✗ ✗ ✗ Report-only (shadow) mode ✓ ✗ ✗ ✗ ✗ Test keys for CI ✓ ✓ ✗ Test mode ✗ Open-source widget ✓ ✗ ✗ ✗ ✓ Independent of big-cloud ecosystem ✓ ✗ ✗ ✓ ✓ Turnstile-compatible siteverify ✓ — ✗ Partial ✗ Works without account lock-in ✓ Cloudflare account Google account ✓ ✓ Competitor capabilities and pricing based on publicly available information and may change. What actually sets Shield apart Four differences that matter more than any feature checkbox. A score, not just a verdict Every other free option gives you pass/fail at best. Shield returns a 1–100 humanity score on every verification, so your application can make graduated decisions — auto-approve humans, step up uncertain traffic, redirect legitimate AI agents to your API, or block abuse. Built for a web where automation isn't automatically the enemy. Nothing to leak Turnstile, reCAPTCHA, and hCaptcha all store per-visitor data somewhere. Shield architecturally cannot: signals are scored in memory and discarded, and only hourly aggregates are persisted. Privacy compliance becomes a non-event. No ecosystem lock-in Shield is a standalone service. It doesn't require routing traffic through our network, doesn't deepen a cloud dependency, and its siteverify format is Turnstile-compatible — so leaving is as easy as arriving. We'd rather keep you with quality than with switching costs. Built to be unnoticeable A dependency-free widget under 15KB that does its work in a Web Worker. No layout shift, no main-thread jank, no Core Web Vitals penalty — lighter than every mainstream alternative. Provider by provider Every provider has strengths. Here's an honest look at each — and where Shield wins. Shield vs Cloudflare Turnstile The CAPTCHA alternative that popularised invisible verification, free within the Cloudflare ecosystem. Strengths Free No visual puzzles Mature bot detection Managed/non-interactive/invisible modes Limitations No confidence score exposed Requires a Cloudflare account Closed-source widget Stores per-visitor data Deepens Cloudflare lock-in The Shield advantage: Shield matches Turnstile's modes and siteverify format exactly — then adds a 1–100 humanity score, an open-source widget, and zero per-visitor data. Migration is a URL and key swap. Shield vs Google reCAPTCHA The incumbent. v2 shows image puzzles; v3 scores traffic invisibly — with Google's tracking along for the ride. Strengths Huge training dataset v3 exposes a score Familiar to every developer Limitations Ad-tech tracking concerns Image puzzles frustrate users (v2) Free tier capped at 10,000 assessments/month GDPR compliance burden Accessibility problems The Shield advantage: Shield gives you what v3's score offers without the tracking, the puzzles, or the assessment cap — and without wiring Google into every page of your site. Shield vs hCaptcha A privacy-focused reCAPTCHA alternative, but one that still leans on visual puzzles for verification. Strengths Privacy-friendlier than reCAPTCHA Drop-in reCAPTCHA compatibility Established enterprise product Limitations Shows image puzzles to real users Invisible mode is a paid feature Score gated behind enterprise plans Closed-source widget The Shield advantage: Shield never shows a puzzle — verification is proof-of-work plus signals, not human labelling labour. Invisible mode and the humanity score are free for everyone. Shield vs Friendly Captcha A European privacy-first CAPTCHA built on proof-of-work, philosophically closest to Shield. Strengths Genuinely privacy-first Proof-of-work based No puzzles EU-hosted Limitations Paid for commercial use No confidence score No adaptive managed mode Smaller detection surface The Shield advantage: Shield takes the same privacy-first, proof-of-work approach and makes it free for commercial use — with adaptive risk scoring and a humanity score on top. Migrating takes minutes. Staying is optional. If you're on Turnstile, the siteverify response is identical — swap a URL and two keys. If you're on reCAPTCHA or hCaptcha, the widget drops into the same place on your forms. Start Migration Free --- ### Compare Compute Providers URL: https://edge.network/compute/compare/ Markdown: https://edge.network/compute/compare.md JSON: https://edge.network/json/compute/compare.json _Compare Edge Compute to AWS EC2, DigitalOcean, and Vultr. Better performance, zero egress fees, and simpler pricing._ Compute Compute How Edge Compares See how Edge Compute stacks up against other cloud providers. Feature Comparison A detailed breakdown of how we compare to other compute providers. Feature Edge AWS EC2 DigitalOcean Vultr Egress Fees Free $0.09/GB $0.01/GB Free (limited) Deploy Time <60s 2-5 min <60s <60s NVMe Storage Extra cost DDoS Protection Included Extra cost Basic Basic Private Networking IPv6 Snapshots Free Per GB $0.05/GB Free GPU Instances Hourly Billing Transparent Pricing Price Comparison Monthly pricing for comparable instance sizes. Instance Specs Edge AWS DigitalOcean Vultr 1 vCPU / 1 GB / 25 GB $6.57 $8.50 $6 $5 2 vCPU / 4 GB / 80 GB $19.04 $34 $24 $20 4 vCPU / 8 GB / 160 GB $38.08 $68 $48 $40 8 vCPU / 16 GB / 320 GB $76.16 $136 $96 $80 * AWS prices based on t3 instances in us-east-1. Prices may vary by region. Detailed Comparisons Pros and cons of each provider compared to Edge. Edge vs DigitalOcean DigitalOcean Pros Developer-friendly Mature managed products Great documentation DigitalOcean Cons Fixed Droplet sizes Card required at signup Egress overage fees Full comparison → Edge vs Hetzner Cloud Hetzner Cloud Pros Very low plan prices Green data centres Solid EU performance Hetzner Cloud Cons Regions centred on Europe Fixed server plans Signup identity checks Full comparison → Edge vs Vultr Vultr Pros Many locations Bare metal available Competitive entry pricing Vultr Cons Fixed plan sizes DDoS protection costs extra Egress overage fees Full comparison → Edge vs AWS EC2 AWS EC2 Pros Huge service ecosystem Enterprise tooling Every instance type imaginable AWS EC2 Cons Complex pricing $0.09/GB egress Surprise bills common Full comparison → Why choose Edge? The key advantages that set us apart. $0 Egress fees 60s Deploy time 50% Greener by design Get Started with Edge Compute --- ### Compare DNS Providers URL: https://edge.network/dns/compare/ Markdown: https://edge.network/dns/compare.md JSON: https://edge.network/json/dns/compare.json _Compare Edge DNS to Cloudflare, AWS Route 53, and DNSimple. Faster propagation, unlimited domains, and simpler pricing._ DNS DNS How Edge DNS Compares See how Edge stacks up against other DNS providers. Feature Comparison A detailed breakdown of how we compare to other DNS providers. Feature Edge Cloudflare Route 53 DNSimple Price Free Free $0.50/zone + usage From $5/zone Domains Up to 50 zones Unlimited Unlimited Per domain Anycast PoPs 50+ 300+ 50+ 30+ Propagation Time <5 seconds <5 seconds 60 seconds <5 seconds DNSSEC Health Checks Included Extra cost $0.50/check Included Geo-routing Enterprise ALIAS Records API Access DDoS Protection Unlimited Unlimited Limited Basic Query Pricing 1M/zone/mo included Free $0.40/million Included Per-Domain Fee None None $0.50/zone $5/zone AI DNS Examiner Price Comparison Monthly pricing for common usage scenarios. Scenario Edge Cloudflare Route 53 DNSimple 10 domains, 10M queries/mo Free Free $9 $50 50 domains, 50M queries/mo Free Free $45 $250 100 domains, 500M queries/mo Contact us Enterprise $250 $500 500 domains, 1B queries/mo Contact us Enterprise $650 $2,500 Detailed Comparisons In-depth, provider-by-provider breakdowns of features, pricing, and when each option makes sense. Edge DNS vs Cloudflare DNS Health checks, geo-routing, and the AI DNS Examiner — what each free tier actually includes. Read the comparison Edge DNS vs AWS Route 53 Per-zone fees, query metering, and propagation speed — free DNS against AWS's pay-per-everything model. Read the comparison Why choose Edge DNS? The key advantages that set us apart. Free Up to 50 zones, no card required <5s Propagation time ∞ Unlimited records Get Started with Edge DNS --- ### Compare Monitoring Providers | Edge Pulse URL: https://edge.network/pulse/compare/ Markdown: https://edge.network/pulse/compare.md JSON: https://edge.network/json/pulse/compare.json _Compare Edge Pulse to Pingdom, UptimeRobot, Datadog Synthetic, and Better Uptime. See why residential monitoring changes everything._ Pulse Pulse How Pulse Compares The only monitoring platform that tests from real residential connections. See how we stack up against every alternative. Feature Comparison A detailed breakdown of Pulse vs the most popular monitoring tools. Feature Pulse Pingdom UptimeRobot Datadog Better Uptime Probe Locations 2,000+ residential ~120 data centres ~30 data centres ~70 data centres ~30 data centres Residential IPs Check Frequency 30s 1 min 30s (paid) 1 min 30s (paid) HTTP/HTTPS Checks DNS Monitoring SSL Monitoring Multi-step API Page Speed Status Pages Free shared, $2/mo custom $29/mo extra $7/mo extra Included Starting Price $0 (150k runs/mo free) $15/mo $0 (5 min) $5/check/mo $0 (5 monitors) Usage-based Pricing Multi-location Confirmation Slack Integration PagerDuty Integration What makes Pulse different It's not just more locations. It's a fundamentally different approach to monitoring. Residential vs data centre Every competitor runs probes from data centres — the same networks that CDNs, cloud providers, and infrastructure companies use. Pulse runs from real homes on real ISPs. If your users can't reach your site but AWS can, only Pulse will catch it. See what your users see Data centre probes benefit from direct peering, cloud allowlists, and optimised routing. Your users don't. Pulse tests from the same residential resolvers, ISP routes, and network conditions your actual visitors experience. 2,000+ locations, not 30 Competitors offer 30–120 probe locations in major cities. Pulse has 2,000+ locations in cities, suburbs, and rural areas worldwide — because Edge Hosts are community-contributed machines on real broadband connections. Pay per run, not per monitor No plans and no per-monitor fees. Every account gets 150,000 standard check runs free each month; beyond that, usage is deducted hourly from the same prepaid balance as Edge compute. Tune checks, frequency, and locations freely. Detailed Comparisons How Pulse stacks up against each competitor, head to head. Pulse vs Pingdom One of the original uptime monitoring services, now owned by SolarWinds. Pingdom Pros Well-established brand Good feature set Reliable infrastructure Pingdom Cons Data centre probes only Status pages cost $29/mo extra Starting at $15/mo Owned by SolarWinds (enterprise pricing) Edge Advantage Pulse offers 16x more probe locations on residential networks, a free shared status page, and 150,000 free check runs every month — no plan required. Pulse vs UptimeRobot Popular for its generous free tier and simplicity. UptimeRobot Pros Free tier (50 monitors) Simple interface Affordable paid plans UptimeRobot Cons Only ~30 probe locations No DNS or SSL monitoring on free No multi-step API checks No page speed monitoring Edge Advantage Pulse provides residential probes, DNS/SSL/API/Page Speed monitoring, and status pages — all from 2,000+ locations. Pulse vs Datadog Synthetic Enterprise-grade synthetic monitoring as part of the Datadog observability platform. Datadog Synthetic Pros Deep APM integration Browser testing Comprehensive dashboards Datadog Synthetic Cons $5 per API test/month $12 per browser test/month Complex pricing Data centre probes only Edge Advantage With per-run pricing, Pulse works out around 70x cheaper than Datadog synthetics at scale — and uniquely offers residential probe locations no enterprise tool can match. Pulse vs Better Uptime Modern uptime monitoring with a focus on incident management. Better Uptime Pros Clean interface Incident management built in Free status pages Better Uptime Cons Only ~30 data centre probes Limited check types No API workflow monitoring No page speed monitoring Edge Advantage Pulse offers 60x more probe locations, all on residential networks, with full DNS, SSL, API, and page speed monitoring. Why choose Pulse? The numbers speak for themselves. 2,000+ Residential probe locations 150,000 Free check runs every month Free Shared status page on every account Start Monitoring Free --- ### Compare Storage Providers URL: https://edge.network/storage/compare/ Markdown: https://edge.network/storage/compare.md JSON: https://edge.network/json/storage/compare.json _Compare Edge Storage to AWS S3, Google Cloud Storage, and Cloudflare R2. Lower costs, zero egress fees._ Storage Storage How Edge Storage Compares See how Edge stacks up against other object storage providers. Feature Comparison A detailed breakdown of how we compare to other storage providers. Feature Edge AWS S3 Google Cloud Cloudflare R2 Storage Cost $0.013/GB $0.023/GB $0.02/GB $0.015/GB Egress Cost $0 $0.09/GB $0.12/GB $0 PUT/POST $0.004/1K $0.005/1K $0.005/1K $0.0045/1K GET/HEAD Free $0.0004/1K $0.0004/1K Free Delete Free Free $0.005/1K Free Simple API Limited Edge Caching Included Extra (CloudFront) Extra Via CF Versioning Encryption Included Included Included Included Multi-Region Included Extra cost Extra cost Auto Image Optimization Included Extra Extra Via CF Monthly Cost Comparison Real-world scenarios with typical usage patterns. Scenario Edge AWS S3 Google Cloud Cloudflare R2 100 GB storage, 1 TB egress/mo $1.30/mo $92/mo $122/mo $1.50/mo 1 TB storage, 10 TB egress/mo $13/mo $923/mo $1,220/mo $15/mo 10 TB storage, 100 TB egress/mo $130/mo $9,230/mo $12,200/mo $150/mo * Estimates based on standard pricing. Actual costs may vary. Detailed Comparisons Pros and cons of each provider compared to Edge. Edge vs AWS S3 AWS S3 Pros Industry standard Deep AWS integration Every storage class imaginable AWS S3 Cons $0.09/GB egress Per-request billing Complex tiering decisions Full comparison → Edge vs Backblaze B2 Backblaze B2 Pros Very cheap storage S3-compatible API Great for backups Backblaze B2 Cons Egress free only to 3x stored Optimised for cold data Storage only — no platform Full comparison → Why choose Edge Storage? The key advantages that set us apart. $0 Egress Fees Simple Modern API 50+ Edge Locations Get Started with Edge Storage --- ### Compute Features URL: https://edge.network/compute/features/ Markdown: https://edge.network/compute/features.md JSON: https://edge.network/json/compute/features.json _Instant provisioning, NVMe storage, DDoS protection, and full root access. Explore all Edge Compute features._ Compute Compute Compute Features Everything you need to run production workloads at the edge. Core Features Enterprise-grade compute capabilities available to every account. Instant Provisioning Deploy virtual machines in under 60 seconds. No waiting for hardware allocation or manual setup. Global Deployment 20+ regions across 6 continents. Deploy close to your users for optimal performance. NVMe Storage All instances include high-performance NVMe SSDs with up to 100,000 IOPS. DDoS Protection Built-in protection against volumetric attacks. No configuration required. Console Access Browser-based VNC console for direct access. Debug boot issues or recover from SSH lockouts. Dedicated Resources No noisy neighbors. Your CPU and RAM are dedicated to your workloads. Private Networking Create isolated VxLAN networks between your VMs. Automatic IP assignment with secure customer isolation. Real-Time Monitoring Built-in metrics for CPU, memory, disk, and network. Live bandwidth monitoring with auto-scaling units. Live Resize Scale vCPU, RAM, and disk on running VMs. No downtime required for most operations. Firewall Rules Granular inbound and outbound rules. Manage per-VM or use shared security groups. Suspend & Resume Pause VMs preserving memory state. Resume instantly without boot sequence – perfect for dev workflows. Recovery Tools Rescue mode, OS reinstall, and automated backups. Recover from any situation. And so much more Every feature you need, included as standard. Automated Backups Manual Backups Backup Restore Activity Log SSH Key Management Additional IPs IPv6 Support Full Root Access Rescue Mode OS Reinstall VM Rename API Access Ready to get started? Deploy your first VM in under 60 seconds. Start Free Today --- ### Compute Help | Expert Services URL: https://edge.network/compute/help/ Markdown: https://edge.network/compute/help.md JSON: https://edge.network/json/compute/help.json _Get hands-on help from Edge experts to build and optimise your compute infrastructure. Migration support, architecture design, and custom configuration._ Compute Expert Services Need a hand? Let our team of infrastructure experts help you design, build, and optimise your compute environment. From migration to scaling, we've got you covered. How we can help Our expert services team has helped hundreds of companies transform their infrastructure. Whatever your challenge, we've probably solved it before. Infrastructure Design We'll architect a compute solution tailored to your workload—whether it's high-availability clusters, GPU-intensive AI, or cost-optimised batch processing. Migration Support Moving from AWS, GCP, or Azure? Our team handles the entire migration, ensuring minimal downtime and a smooth transition. Custom Configuration Complex networking, security requirements, or specialised setups? We'll build a bespoke solution that fits your exact needs. Rapid Deployment Get your infrastructure up and running fast. Our experts can have your compute environment configured and optimised within days. Learn more about Expert Services Sound familiar? These are the kinds of challenges we help solve every day. Our cloud costs are spiralling out of control We need to migrate off AWS / GCP / Azure Our current setup can't handle traffic spikes We need GPU instances for AI/ML workloads Our infrastructure isn't scaling properly We want to move to a more sustainable provider Our deployments are slow and unreliable We need high-availability across regions Our team is stretched thin managing infrastructure Get in touch Tell us about your project and we'll get back to you within 24 hours with a plan of action. First Name Last Name Work Email Company Current Cloud Provider Select your current provider AWS Google Cloud Microsoft Azure DigitalOcean Linode Vultr Hetzner Other None / On-premise How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 An infrastructure expert will schedule a call to understand your requirements in detail. 3 We'll provide a tailored proposal with timeline and pricing. 4 Once approved, our team gets to work immediately. Trusted by --- ### Compute Instances URL: https://edge.network/compute/instances/ Markdown: https://edge.network/compute/instances.md JSON: https://edge.network/json/compute/instances.json _Flexible VM configurations from 1-32 vCPUs, 1-64GB RAM, and up to 2TB NVMe storage. Pay only for what you use._ Compute Compute Server Configuration Configure servers exactly how you need them. Pick the vCPU, RAM, and disk per server and pay hourly, per resource — no fixed instance sizes. Configuration Options Size each server independently within these ranges. Mix and match across your infrastructure. vCPUs 1 – 32 Scale processing power as needed RAM 1 – 64 GB Memory for any workload NVMe Storage 1 GB – 2 TB High-performance SSD storage Bandwidth Unlimited No transfer limits or throttling Example Configurations Common configurations for different workloads. Use these as starting points – you can adjust resources anytime. Development Environment Lightweight servers for dev and testing 2 vCPU • 4 GB RAM • 50 GB storage Perfect for CI/CD runners, staging environments, and personal projects. Web Application Balanced for web servers and APIs 4 vCPU • 8 GB RAM • 100 GB storage Run Node.js, Python, PHP, or any web framework with room to grow. Database Server Memory-optimized for data workloads 8 vCPU • 32 GB RAM • 500 GB storage PostgreSQL, MySQL, MongoDB, Redis – optimized for data-intensive applications. Production Backend High-performance application servers 16 vCPU • 32 GB RAM • 250 GB storage Handle high traffic with consistent performance for production workloads. Compute-Intensive CPU-heavy processing tasks 32 vCPU • 64 GB RAM • 500 GB storage Video encoding, data processing, scientific computing, and batch jobs. AI & ML Inference GPU-accelerated for machine learning 8 vCPU • 32 GB RAM • 320 GB storage + GPU Run inference workloads with NVIDIA GPUs. See GPU options for details. Learn more Included with every server Enterprise features at no extra cost. No hidden fees, no surprises. NVMe SSD Storage Unlimited Bandwidth DDoS Protection Private Networking IPv6 Support Full Root Access Cloud-Init Support Zero Egress Fees Priced per resource, billed hourly Every server is priced by exactly what you configure — vCPU, RAM, and disk — and billed hourly from your prepaid balance. Resize any time; your cost changes immediately. Need serious scale? Contact us for enterprise options. View Plans Contact Sales --- ### Compute Pricing URL: https://edge.network/compute/pricing/ Markdown: https://edge.network/compute/pricing.md JSON: https://edge.network/json/compute/pricing.json _Pay per resource, billed hourly from a prepaid balance. vCPU from $0.004/hr, RAM from $0.00256/GiB-hr, NVMe disk at $0.074/GiB-month. No plans, no egress fees, no surprise bills._ Compute Compute Pricing No plans and no instance types to decode. Pick exactly the vCPU, RAM, and disk you need, pay per resource by the hour from a prepaid balance, and stop any time. The rate card Three resources make up a VM. Everything else is a flat add-on or free. Resource Price Notes vCPU Dedicated virtual CPU core $0.004 per hour ≈ $2.92/month per core, billed only while running RAM Memory, per GiB $0.00256 per GiB-hour ≈ $1.87/month per GiB, billed only while running Disk NVMe SSD storage $0.074 per GiB-month Billed for allocated storage, running or stopped Additional IPv4 Extra public address $2.00 per month, each First public IP included Snapshots & backups Point-in-time copies $0.05 per GiB-month Billed for stored snapshot size Bandwidth All traffic in and out Free Zero egress fees, every region Try the VM configurator on the pricing page What it actually costs Monthly cost = vCPU + RAM billed per hour (730 hours/month) plus disk. Here are three common builds. Build vCPU RAM NVMe Disk Monthly cost Starter Small sites & side projects 1 2 GiB 40 GB $9.62 /mo Standard Apps & databases 2 4 GiB 80 GB $19.24 /mo Performance Production workloads 4 8 GiB 160 GB $38.47 /mo Prices include bandwidth — there are no egress fees on any build, in any region. VMs bill by the hour, so a Standard build run for a weekend costs about $1.27, not $19.24. No surprise bills. By design. Compute is prepaid: you load a balance and usage is deducted hourly. It's structurally impossible to wake up to a runaway bill. Prepaid balance Top up when it suits you, or enable auto top-up. A one-time $5 starter credit is available once your card is on file. Balance out, VMs pause At zero balance, running VMs stop — nothing is deleted. Top up and the VMs we stopped start again automatically. Exact price up front The configurator shows the precise hourly and monthly cost of your build before you deploy. No egress math, no fine print. Pricing FAQ Everything you need to know about how compute billing works. How does billing work? Usage is metered and deducted hourly from a prepaid balance. You load credit, run what you need, and stop any time. There is no subscription to commit to and nothing to cancel — a one-time $5 starter credit is available once your card is on file. What happens when my balance runs out? Running VMs are stopped — never deleted. Your data, configuration, and IPs stay in place, and VMs we stopped are started again automatically when you top up. Enable auto top-up to avoid interruptions. Do stopped VMs cost anything? A stopped VM stops accruing vCPU and RAM charges immediately. Disk keeps billing at $0.074/GiB-month while the VM exists, because the storage is still allocated to you. Are there egress fees? No. Bandwidth in and out is included at every size, in every region. The price you configure is the price you pay. Can I see the cost before I deploy? Yes — the configurator on the pricing page and in the console shows the exact hourly and monthly total for your vCPU, RAM, and disk selection before you create anything. What about high-volume workloads? Enterprise volume pay-as-you-go starts at $499/month with volume discounts, a 99.99% SLA, and an account manager. Talk to us if you're running at scale. Deploy your first VM in seconds Configure exactly what you need, see the exact price, and pay only while it runs. Get Started Explore Configurations --- ### Compute Regions URL: https://edge.network/compute/regions/ Markdown: https://edge.network/compute/regions.md JSON: https://edge.network/json/compute/regions.json _Deploy VMs across 33 global regions on 5 continents. Sub-50ms latency from anywhere in the world._ Compute Compute Global Compute Regions 33 regions across 5 continents. Deploy your VMs close to your users for the best possible performance. Available Regions Deploy in any region or across multiple for redundancy. North America 10 regions <30ms avg latency New York Los Angeles Chicago Dallas Miami Seattle Denver Atlanta Toronto San Francisco Europe 9 regions <25ms avg latency London Frankfurt Amsterdam Paris Stockholm Dublin Milan Warsaw Madrid Asia Pacific 8 regions <40ms avg latency Singapore Tokyo Sydney Mumbai Seoul Hong Kong Jakarta Melbourne Latin America 3 regions <45ms avg latency São Paulo Mexico City Buenos Aires Middle East & Africa 3 regions <50ms avg latency Dubai Tel Aviv Johannesburg 33 Regions 5 Continents 99.99% Uptime SLA <50ms Avg Latency Deploy globally in minutes Choose any region or deploy across multiple for redundancy. Start Free Today --- ### DNS URL: https://edge.network/dns/ Markdown: https://edge.network/dns.md JSON: https://edge.network/json/dns.json _Global DNS with sub-10ms resolution times. Anycast network, DNSSEC support, and simple per-query pricing._ DNS DNS Lightning-fast DNS at the edge Global anycast DNS with sub-10ms resolution . Intelligent routing, automatic failover, and enterprise-grade security built in. Add Your Domain DNS is free — up to 50 zones per account, no card required. 50+ Global PoPs <10ms Avg Resolution 100% Uptime SLA ∞ DDoS Protection DNS built for modern infrastructure Everything you need to manage DNS at scale, with the performance your users expect. Global Anycast DNS queries are answered from the nearest of 50+ locations worldwide. Sub-10ms resolution everywhere. Instant Propagation Changes propagate globally in under 5 seconds. No more waiting for DNS to update. DDoS Protected Unlimited DDoS mitigation included. Your DNS stays online no matter what. Automatic Failover Health checks and automatic failover. Route traffic away from unhealthy origins instantly. Real-Time Analytics Query logs, geographic distribution, and response time metrics in real-time. DNSSEC One-click DNSSEC signing. Protect your domains from spoofing and cache poisoning. DNS Examiner AI-powered zone analysis. Checks email deliverability, security, nameservers, and best practices in one click. DNS is free for everyone No plans, no card required — just a verified email. Point your nameservers at Edge and go. Free $0 /mo Up to 50 zones Unlimited records 1M queries/month per zone included All record types & geo-routing Global anycast network Add-ons From $1 /mo Zone backups — $1/zone/month Managed test.network subdomains — $1/month Managed ed.ge subdomains — $5/month Billed hourly from your prepaid balance High volume Talk to us Sustained traffic beyond the included queries Volume pricing 99.99% SLA available Contact us View full pricing Perfect for Enterprise-grade DNS for every use case. Web Applications API Endpoints Email Routing Load Balancing CDN Origins Microservices SaaS Products Global Apps Guides & resources Set up fast, resilient DNS on Edge. Getting started Create a zone, add records, and point your nameservers at Edge. DNS failover Automatic failover between origins with health checks and low-TTL records. DNS security Why distributed nameservers are harder to attack — and what that means for uptime. Ready to speed up your DNS? Add your first domain in under 2 minutes. Free — no card required. Get Started Free --- ### DNS Examiner URL: https://edge.network/dns/examine/ Markdown: https://edge.network/dns/examine.md JSON: https://edge.network/json/dns/examine.json _AI-powered DNS zone analysis. Check email deliverability, security configuration, nameserver delegation, and best practices in one click._ DNS DNS DNS Examiner AI-powered zone analysis that checks your DNS configuration for issues, misconfigurations, and missed best practices — then tells you exactly how to fix them. Try DNS Examiner How it works One click. Full analysis. Actionable fixes. 1 Click Examine Navigate to any zone in your Edge DNS dashboard and open the Examiner tab. Hit "Run Examination". 2 Live Analysis We run live DNS lookups against your domain and compare them with your configured records. AI analyses everything in seconds. 3 Fix Issues Get a health score, a prioritised list of issues by severity, and specific record values to add or change — right in your dashboard. What it checks A comprehensive audit across six categories, every time you run it. Email Deliverability Validates SPF, DKIM, and DMARC records. Checks MX configuration and flags missing or misconfigured email authentication that could land your messages in spam. Security Configuration Reviews CAA records for certificate authority restrictions, checks for overly permissive wildcards, and verifies DNSSEC readiness. Nameserver Delegation Compares live NS lookups against your assigned Edge nameservers. Identifies delegation mismatches at your registrar before they cause downtime. Web Accessibility Confirms A/AAAA records resolve correctly, checks for CNAME-at-apex conflicts, and verifies www subdomain configuration. Best Practices Audits TTL values, flags duplicate or conflicting records, checks MX priority spread, and identifies orphaned entries. Live Verification Performs real DNS lookups alongside your configured records to catch propagation issues and discrepancies between intent and reality. Only on Edge DNS No other DNS provider offers built-in AI analysis. Cloudflare, Route 53, and DNSimple don't have it. AI-powered analysis Live DNS verification Email auth checks Security audit Health scoring Actionable fixes Persisted results No extra cost Try DNS Examiner Add your domain and run your first examination in under a minute. Included free with every Edge account. Get Started --- ### DNS Features URL: https://edge.network/dns/features/ Markdown: https://edge.network/dns/features.md JSON: https://edge.network/json/dns/features.json _Global anycast network, instant propagation, DNSSEC, and real-time analytics. Explore all Edge DNS features._ DNS DNS DNS Features Enterprise-grade DNS with the simplicity you expect from modern infrastructure. Core Features Enterprise-grade DNS capabilities available to every account. Global Anycast Network 50+ points of presence worldwide. DNS queries are answered from the nearest location for sub-10ms resolution. Instant Propagation Changes propagate globally in under 5 seconds. Update records and see changes immediately. DDoS Protection Unlimited DDoS mitigation at no extra cost. Your DNS infrastructure stays online during attacks. Health Checks & Failover Monitor endpoint health and automatically route traffic away from unhealthy origins. Real-Time Analytics Query logs, geographic distribution, response times, and error rates in real-time dashboards. DNSSEC One-click DNSSEC signing and key management. Protect against spoofing and cache poisoning. Flexible TTLs Set TTLs as low as 30 seconds for dynamic records or longer for stable entries. Secondary DNS Use Edge as primary or secondary. AXFR/IXFR zone transfers supported. Full API Access REST API for complete automation. Terraform provider and CLI available. DNS Examiner AI-powered zone analysis that checks email deliverability, security configuration, nameserver delegation, and best practices. One click, actionable results. And so much more Every feature you need, included as standard. Geo-routing Weighted routing Latency-based routing Wildcard records ALIAS records CAA records DNS Examiner Bulk record updates Version history Audit logs Team permissions API rate limits Ready to get started? Add your first domain in under 2 minutes. Start Free --- ### DNS Help | Expert Services URL: https://edge.network/dns/help/ Markdown: https://edge.network/dns/help.md JSON: https://edge.network/json/dns/help.json _Get hands-on help from Edge experts to set up and optimise your DNS infrastructure. Migration support, architecture design, and custom configuration._ DNS Expert Services Need a hand? Let our team of DNS experts help you design, migrate, and optimise your DNS infrastructure. From simple setups to complex global configurations, we've got you covered. How we can help Our expert services team has helped hundreds of companies set up bulletproof DNS. Whatever your challenge, we've probably solved it before. DNS Architecture We'll design a DNS strategy optimised for your needs—whether it's global load balancing, failover, or complex routing rules. Migration Support Moving from another DNS provider? Our team handles the entire migration with zero downtime and full verification. Custom Configuration Complex record setups, DNSSEC, or advanced routing? We'll configure everything to your exact specifications. Rapid Deployment Get your DNS running fast. Our experts can have your zones configured and propagating globally within hours. Learn more about Expert Services Sound familiar? These are the kinds of challenges we help solve every day. We need to migrate our DNS without any downtime Our current DNS provider is too slow We need geographic load balancing Our DNS configuration is a mess We need help setting up DNSSEC We want failover between providers Our propagation times are too long We need to consolidate multiple domains We want better visibility into DNS queries Get in touch Tell us about your project and we'll get back to you within 24 hours with a plan of action. First Name Last Name Work Email Company Current DNS Provider Select your current provider Cloudflare AWS Route 53 Google Cloud DNS Azure DNS GoDaddy Namecheap DNSimple NS1 Other How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 A DNS expert will schedule a call to understand your requirements in detail. 3 We'll provide a tailored proposal with timeline and pricing. 4 Once approved, our team gets to work immediately. Trusted by --- ### DNS Performance URL: https://edge.network/dns/performance/ Markdown: https://edge.network/dns/performance.md JSON: https://edge.network/json/dns/performance.json _Independent benchmarking shows Edge DNS consistently outperforming major providers. Real-time data from PerfOps measuring median resolution times._ DNS DNS DNS Performance Independent benchmarking shows Edge DNS consistently outperforming major providers. Real-time data from PerfOps measuring median resolution times. Live Performance Real-time comparison against major DNS providers over the last hour. Loading performance data... Why Edge DNS is so fast Our architecture is built from the ground up for speed, not retrofitted onto legacy infrastructure. 50+ PoPs Worldwide Anycast routing ensures queries are answered by the nearest server. Most users are within 10ms of an Edge PoP. In-Memory Resolution Zones are compiled into optimized in-memory structures. No disk I/O, no database queries—just pure speed. Rust-Powered Core Written in Rust for maximum performance and reliability. Zero-copy parsing, minimal allocations, and predictable latency. Independent benchmarking Performance data is collected by PerfOps, a leading independent monitoring provider. We don't mark our own homework. Real User Monitoring (RUM) from actual browsers Median algorithm reduces outlier influence Per-minute granularity for accurate trends Geographic filtering by country/region Powered by PerfOps Independent DNS monitoring PerfOps provides enterprise-grade RUM benchmarking for DNS, CDN, and cloud providers. Their methodology is trusted by thousands of companies worldwide. Learn more about PerfOps Ready for faster DNS? Start with 1 million free queries per month. No credit card required. Get Started Free Contact Sales --- ### DNS Pricing URL: https://edge.network/dns/pricing/ Markdown: https://edge.network/dns/pricing.md JSON: https://edge.network/json/dns/pricing.json _Fast anycast DNS, free for everyone — up to 50 zones, unlimited records, 1M queries per zone each month. Optional add-ons: test.network domains from $1/month and zone backups at $1/month._ DNS DNS Pricing Free for everyone. Fast anycast DNS with up to 50 zones and unlimited records — no card required. Pay only for optional add-ons like managed domains and zone backups. The core product is free. Full stop. Point your nameservers at Edge and manage all your domains from one place — on the same global anycast network our paying customers use, with DNSSEC, geo-routing, and instant propagation included. Each zone includes a million queries a month, and the limit is soft: we warn, we never block resolution. Your domains stay up. Free forever Edge DNS $0 /mo — verified email, no card Up to 50 zones Unlimited records 1M queries per zone, per month Global anycast network DNSSEC support Geographic routing Instant propagation Add Your First Zone Optional add-ons Everything below is opt-in, billed hourly from your prepaid balance, and droppable at any time. The core DNS product never costs anything. Add-on Price Notes test.network domain Managed development subdomain $1.00 per month, each Instant setup, full DNS control, no registrar ed.ge domain Managed premium short domain $5.00 per month, each Your name on the shortest domain around Zone backups Automatic versioned backups $1.00 per zone, per month Point-in-time restore for a whole zone Learn about test.network domains Pricing FAQ Everything you need to know about how DNS billing works. Is DNS really free? Yes — free for everyone with a verified email, no card required. Up to 50 zones with unlimited records on a global anycast network. It's the same infrastructure paying customers use, not a limited tier. What happens if a zone exceeds 1M queries in a month? The limit is soft: we'll warn you, but we never block resolution or drop your queries. If you're consistently over, we'll talk about a volume arrangement — your domains stay up regardless. How are add-ons billed? Managed domains and zone backups are billed hourly from the same prepaid balance as Edge compute — a $1/month add-on costs about $0.0014 per hour while active, and you can drop it at any time. Do I need to transfer my domain to Edge? No. Keep your registrar and simply point your nameservers at Edge. If you want a domain without a registrar at all, test.network and ed.ge subdomains are available as managed add-ons. What about very high query volumes? Enterprise volume pay-as-you-go covers DNS at scale with volume query pricing, a 99.99% SLA, and an account manager. Talk to us if you're serving hundreds of millions of queries. Free, fast DNS in minutes Add a zone, point your nameservers, done. Up to 50 zones with unlimited records — no card required. Get Started Free See the Performance --- ### DNS Record Types URL: https://edge.network/dns/records/ Markdown: https://edge.network/dns/records.md JSON: https://edge.network/json/dns/records.json _Full support for A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, and more. Manage all your DNS records in one place._ DNS DNS Supported Record Types Full support for all standard DNS record types, plus Edge-specific extensions. Record Types All standard record types plus Edge-specific extensions for modern infrastructure. A Address Record Maps a domain to an IPv4 address. example.com → 192.0.2.1 AAAA IPv6 Address Record Maps a domain to an IPv6 address. example.com → 2001:db8::1 CNAME Canonical Name Creates an alias pointing to another domain. www.example.com → example.com ALIAS ALIAS Record Like CNAME but works at the zone apex. Edge-specific. example.com → cdn.edge.network MX Mail Exchange Specifies mail servers for the domain. example.com → mail.example.com (priority 10) TXT Text Record Stores text data, commonly used for verification and SPF. v=spf1 include:_spf.google.com ~all NS Name Server Delegates a zone to specific name servers. example.com → ns1.edge.network SRV Service Record Specifies host and port for services. _sip._tcp.example.com → 5060 sip.example.com CAA Certification Authority Authorization Specifies which CAs can issue certificates for the domain. example.com CAA 0 issue "letsencrypt.org" PTR Pointer Record Reverse DNS lookup, maps IP to domain. 1.2.0.192.in-addr.arpa → example.com SOA Start of Authority Contains zone information and settings. Managed automatically by Edge NAPTR Naming Authority Pointer Used for ENUM and SIP routing. Advanced telephony routing Advanced Capabilities Powerful features for complex DNS requirements. Wildcard records (*.example.com) ALIAS records at zone apex Unlimited records per zone Bulk import/export TTL as low as 30 seconds DNSSEC signing API and Terraform support Version history for all changes Start managing your DNS Import your existing records or start fresh. Setup takes under 2 minutes. Add Your Domain --- ### DNS Regions URL: https://edge.network/dns/regions/ Markdown: https://edge.network/dns/regions.md JSON: https://edge.network/json/dns/regions.json _DNS resolution from 50+ global points of presence. Sub-10ms query resolution worldwide._ DNS DNS Global Anycast Network 50+ points of presence across 5 continents. DNS queries are automatically routed to the nearest location for the fastest possible resolution. Complete Coverage DNS resolution from locations strategically placed worldwide. North America 11 PoPs <5ms avg resolution New York Los Angeles Chicago Dallas Seattle Atlanta Miami Toronto Mexico City Silicon Valley Honolulu Europe 8 PoPs <8ms avg resolution London Frankfurt Amsterdam Paris Madrid Stockholm Warsaw Manchester Asia Pacific 9 PoPs <12ms avg resolution Singapore Tokyo Sydney Mumbai Seoul Bangalore Delhi Osaka Melbourne Latin America 2 PoPs <15ms avg resolution São Paulo Santiago Middle East & Africa 2 PoPs <18ms avg resolution Tel Aviv Johannesburg How Anycast DNS Works Your queries are automatically routed to the nearest location. 1 User Makes Query A user's device requests your domain's DNS records. 2 Nearest PoP Responds BGP routing directs the query to the closest Edge location. 3 Instant Resolution Response is returned in milliseconds from local cache. 50+ Global PoPs 5 Continents 100% Uptime SLA <10ms Avg Resolution Experience global DNS Your domains, resolved from 50+ locations worldwide. Start Free --- ### Edge Assist | Chatty Agents for Your Website URL: https://edge.network/assist/ Markdown: https://edge.network/assist.md JSON: https://edge.network/json/assist.json _Add a conversational agent to your website, app, wiki, or CRM with one line of code. Edge Assist reads your content and answers your visitors' questions instantly — with citations, on your pages, in your brand._ Assist Assist Chatty agents for your website Your visitors have questions. Your site has the answers — buried across dozens of pages. Edge Assist connects the two: instant, cited answers drawn from your own content , added with a single line of code. Add Assist to Your Site Free to start — 250 answered questions every month, no credit card required. Ask a follow-up… New conversation Do you ship to New Zealand? Yes — we ship worldwide, including New Zealand. International orders are dispatched within 2 working days, and delivery typically takes 5–10 days. Shipping is free on orders over $75. See shipping & delivery for the full rates. Shipping & Delivery International Orders Edge Assist · answers come from this site's content esc to close 1 Line of Code 250 Free Questions / Month 1¢ Per Question After 10k Documents per Site How it works From your content to answered questions in three steps. No training, no tuning, no prompt engineering. 01 Point Assist at your content Publish a content index from your site build, or drop documents into an Edge Storage bucket. Assist ingests it automatically and stays in sync — update your site and Assist knows within the hour. 02 Drop in the widget One line of code adds a search-and-ask box to your site. Use the floating launcher, bind it to your own search icon or ⌘K, embed it inline in a help centre — or skip integration entirely and share your site's hosted assistant page. 03 Visitors ask, Assist answers Answers stream in word by word, grounded in your content, with citations linking back to your pages. Questions Assist can't answer from your content are politely declined — no making things up. Built to answer, not to impress Assist is deliberately conservative: it answers from your content, cites its sources, and hands you the controls. Grounded answers, cited Every answer is drawn from your content and cites the pages it came from. Assist never invents facts or numbers — if your site doesn't say it, Assist doesn't either. Search and chat in one box Instant search results as visitors type, and a full conversational answer when they ask a question. One widget replaces your site search and adds AI on top. Streaming, cached, fast Answers stream word by word. Repeat questions are answered instantly from a per-site cache that invalidates itself whenever your content changes — and paid sites can pre-warm it, answering hundreds of likely questions before the first visitor asks. Real conversations Follow-up questions work — "why?", "how much?", "on this page?". Conversations survive closing the box, and visitors can pick up where they left off or start fresh. You have the final word Pin authoritative facts and curate exact answers for high-stakes questions. Browse every question visitors ask and correct any answer in one click. Your brand, your rules Theme it, position it, turn features on or off. Paid sites can remove Edge branding entirely — or white-label Assist under their own assistant name. Replaces your chatbot A "How can we help?" launcher opens straight into a chat — set the message yourself, rotate several, or seed questions that start the conversation pre-asked. We binned our own chatbot for it. A human when it matters If Assist can't answer or a visitor asks for a person, it collects their email and hands the whole conversation to your support inbox — transcript attached, reply goes straight to them. It's running on this site right now We don't sell anything we don't run ourselves. The search icon in the navigation above and the launcher in the bottom corner are Edge Assist — the exact widget you'd be adding to your site, served from the same script tag. Press ⌘K and ask it something. Answers every question about Edge products, pricing, and how-tos Re-ingests the whole site automatically on every deploy Serves repeat questions instantly from cache, site-wide — and "is there a limit on this page?" is answered against the page you're reading // Add Assist to any site <script src="https://assist.edge.network/widget.js" data-sitekey="ea_1a2b3c4d5e6f"></script> // That's it. Content already ingested: ✓ 214 pages indexed from yoursite.com ✓ Widget live — search + ask enabled → First question answered in 0.4s (cached) Find out what your visitors actually want Every question a visitor asks is a signal you've never had before. Assist turns your site into a listening post: see what people are looking for, what your content fails to answer, and fix it — in your content or with a one-click override. Every question visitors ask, logged and searchable Full conversation threads, replayable in your dashboard Top unanswered questions — your content gap list Most-cited pages and answer rates over time Correct any answer directly from the question log Top unanswered questions "Do you offer student discounts?" 31 asks "Can I pause my subscription?" 18 asks "Is there an API?" Corrected Each one is a content gap — or a one-click override Your content already has the answers Add AI answers to your site in two minutes. 250 answered questions free every month — no credit card needed. Start Free --- ### Edge Assist Demo | Ask It Something URL: https://edge.network/assist/demo/ Markdown: https://edge.network/assist/demo.md JSON: https://edge.network/json/assist/demo.json _A live Edge Assist demo: ask a real question, watch retrieval find the sources, and see the answer stream in — grounded in this site's content, with citations._ Assist Assist Ask it something This page runs a real Assist conversation against this site's live content. Ask a question below and watch retrieval, citations, and the streamed answer happen for real — nothing is staged. 1 The question Type anything a visitor might ask, or pick a suggestion. This is the same input your visitors would see — in the widget, a docs sidebar, or your help centre. Live demo, politely rate limited — a handful of questions per visitor. Ask How much does storage cost? What makes the CDN fast? How do I stop bots without annoying users? Can I deploy a VM from the CLI? 2 The sources Before a word of the answer is written, Assist retrieves the most relevant passages from this site's index. These are the pages the answer will be grounded in — and the citations your visitor can check. Waiting for a question… 3 The answer Streamed word by word as it's composed, with the sources linked inline. Assist answers only from your content — ask it something this site doesn't cover and it will say so rather than make something up. The answer will stream in here. 4 The integration Everything you just watched is what your visitors get from one line of code. Point Assist at your content, paste the snippet, done. Prefer no integration at all? Every site also gets a hosted assistant page you can simply link to. <script src="https://assist.edge.network/widget.js" data-sitekey="ea_your_sitekey" defer></script> Now imagine it on your content Everything on this page ran against edge.network's pages. Point Assist at yours and it answers just as well — 250 questions free every month. Start Free --- ### Edge Assist Features | AI Answers, Search, Insight & Control URL: https://edge.network/assist/features/ Markdown: https://edge.network/assist/features.md JSON: https://edge.network/json/assist/features.json _Everything Edge Assist does: grounded AI answers with citations, instant search, conversations, human handoff, content ingestion, overrides, cache pre-warming, analytics, white-labelling, and mobile support._ Assist Assist Features Everything Assist does, from the answer your visitor sees to the controls you hold behind it. Answering What your visitors experience. Grounded in your content Answers are built from your pages and documents, retrieved fresh for every question. If your content doesn't cover it, Assist says so politely — it never fabricates facts, numbers, or policies. Citations on every answer Each answer links to the pages it was drawn from, as inline links and source chips. Visitors can verify anything in one click — and every citation is a visit to your content. Streaming answers Answers stream word by word, with the first words appearing in under a second. Repeat questions hit a per-site answer cache — shared across every page of your site — and return instantly. Page-aware context Assist knows which page the visitor is on. Questions that point at it — "is there a limit on this page?", "how do I set this product up?" — are answered against the page they're reading, not the site in general. Real conversations Follow-ups work naturally, conversations survive closing the widget, and visitors can pick up where they left off or start fresh. Idle threads expire so stale context never pollutes a fresh question. Extended conversations A paid per-site setting for longer threads with a deeper memory — for products where visitors genuinely work through something with the assistant. Deep turns meter at 2× the question rate. Instant search built in Results appear as visitors type, before any AI is involved. One box covers both "find me the page" and "answer my question" — replacing your site search outright. Human handoff built in When Assist can't answer — or a visitor simply wants a person — it offers to hand over: they leave an email, the whole conversation lands in your support inbox with the transcript attached, and your reply goes straight to them. Answers and leads from one widget. Content ingestion How Assist learns what it knows. Content index from your build Publish a small JSON index from your site build — the format is a single page of JSON, fully specified in the docs, and most builds emit it in a few dozen lines. Assist polls it hourly and re-ingests automatically whenever your content changes. You control exactly what Assist knows. Bucket ingestion Point Assist at an Edge Storage bucket and drop documents in — markdown, plain text, HTML, PDF. Additions, updates, and deletions are picked up incrementally. Perfect for knowledge bases that don't live on a website. By URL No build step, no bucket — give Assist your URL and it crawls your site itself, following your sitemap and links, re-crawling on a schedule to stay current. The zero-integration way in. Always in sync Ingestion is automatic and continuous. Rebuild your site or update a document, and Assist answers from the new content — the answer cache invalidates itself on every re-ingest. Up to 10,000 documents Every site supports up to 10k documents with fast, predictable retrieval. Bigger knowledge base? Our Expert Services team builds custom deployments beyond the cap. Private knowledge bases Bucket-backed sites are private by default: anonymous requests are rejected, and access comes from per-site API keys and short-lived visitor tokens your server mints behind your own login. An internal handbook assistant only your team can reach. Insight & control You own the answers. Pinned facts Short authoritative statements that take precedence over site content — "We ship worldwide except X", "Support hours are Y". One pinned fact fixes every phrasing of a question. Curated Q&As For high-stakes questions, write the exact answer yourself. Strong matches return your words verbatim — instantly, without an AI call. Question log & correction loop Browse every question visitors ask, see the answer given, and correct it in one click — the correction becomes an override. Your assistant gets better every week you use it. Metrics & conversations Questions per day, answer rates, latency, top questions, top unanswered questions, most-cited pages — plus a full conversations explorer to replay any thread. Answer cache purge Clear your site's cached answers whenever you need — the whole site or a single question — just like purging a CDN. Free and instant. Cache pre-warming Assist reads your content, works out the hundreds of questions visitors are likely to ask, and answers them all ahead of time — so your most-asked questions are instant from the very first visitor. Review the generated list before it runs, and re-warm automatically when your content changes. A paid feature, metered at the normal question rate. Budgets & caps Free tier is hard-capped and can never bill you. Paid usage draws from a prepaid budget you set — when it's exhausted the widget falls back to plain search, never to a surprise invoice. The widget Fits your site, carries your brand. Chat launcher A "How can we help?" bubble that opens straight into a chat with a greeting — everything visitors expect from a chatbot, answered by your content instead of a script. It even inverts its colours automatically over dark page sections. Modal or embedded Prefer no bubble? Bind Assist to your own search icon or Cmd+K, open it from any button on your page, or embed it inline in a help centre, docs sidebar, or 404 page. Run several at once — each surface keeps its own conversation. Launcher prompts Set the launcher message yourself — or a rotating series: "How can we help?", "Ask about pricing…", "Looking for docs?". Configured per site from your dashboard, applied to live widgets in minutes. Suggested questions Show your own starter questions inside the opened panel. One click begins a chat with that question — guide visitors to the answers you know land well. Full-screen mode On desktop, visitors can expand the widget to cover the page — chat on the left, a citations rail on the right, including "keep exploring" links you curate per site. On mobile the widget always uses the full screen. Hosted assistant page Every site gets a full-page assistant hosted at assist.edge.network — link to it from an email signature, a social bio, or a support menu before you've touched your site's code. Zero integration. Themable Colours, position, placeholder text, welcome message — configured from your dashboard, applied instantly, no code changes. Configuration is server-side, so it can't be tampered with in the page. White-label Paid sites can remove Edge branding. The white-label add-on goes further: your own assistant name and icon throughout — your visitors meet your assistant, not ours. Mobile apps A hosted widget page drops into any in-app browser sheet today. Native SDKs for Swift, Kotlin, React Native, and Flutter follow — same content, same customisation, fully native UI. Protected by design Your sitekey is public but origin-locked: the API only answers for it from your own domain, so a lifted key is useless anywhere else. Per-visitor rate limits and hard monthly caps mean bots can't burn your question budget. Try it before you add it Assist runs on this site right now — press ⌘K and ask it anything. Then add the same thing to yours, free. Start Free See Pricing --- ### Edge Assist Pricing | AI Answers for a Penny a Question URL: https://edge.network/assist/pricing/ Markdown: https://edge.network/assist/pricing.md JSON: https://edge.network/json/assist/pricing.json _Add AI answers to your site: 250 answered questions free every month, then $0.01 per question. No plans, no seats, no per-page fees._ Assist Assist Pricing A penny a question. No plans, no seats, no per-page fees — and the first 250 answered questions every month are free. Start free. Stay free if you're small. Every account gets 250 answered questions free each month — plenty for a personal site, a blog, or a small product's docs. Search is unlimited and free on every tier, forever. No credit card required to sign up. When you need more, usage is deducted hourly from the same prepaid balance as other Edge services, against a budget you set. The free tier is hard-capped: when it's used up the widget falls back to search — it never bills you. Free every month Assist Free Allowance $0 /mo — no card required 250 answered questions every month Up to 500 pages of content per site Instant search included — unlimited, always free Citations, conversations & streaming answers Human handoff — conversations land in your inbox Widget, hosted assistant page & suggested questions Question log & metrics in your dashboard "Powered by Edge Assist" badge Start Free The rate card An answered question is the only unit you pay for. Everything else is a flat add-on or free. Resource Price Notes Answered questions AI answers, grounded in your content $0.01 per question First 250/month free. $10 per 1,000. Search Instant type-ahead results Free Unlimited on every tier Content ingestion Site index or storage bucket, up to 10k documents Free Automatic re-ingestion included. Bucket ingestion & private access require pay-as-you-go Extended conversations Longer threads with a deeper memory 2× question rate Optional per-site setting — deeper context costs more to produce Cache pre-warming Answer the questions visitors are likely to ask, ahead of time $0.01 per question Paid feature — you choose the scale per run (e.g. 250 or 1,000 questions) White-label Your assistant name & icon, no Edge branding $29 per site / month Badge removal alone is included with any paid usage Overrides & answer cache Pinned facts, curated Q&As, cache purge Free Included on every tier View full Edge pricing What it actually costs You pay for answered questions, nothing else. Here's what real sites cost. Site Content Questions Monthly cost Personal site / blog 60 pages 180 / month $0.00 Within free allowance SaaS docs site 400 pages 2,000 / month $17.50/mo After 250 free questions Help centre at scale 3,000 documents 20,000 / month $197.50/mo After 250 free questions The first 250 answered questions each month are free; the rest are billed at $0.01 each. For example, the SaaS docs site: 2,000 − 250 = 1,750 billable questions = $17.50. Comparable dedicated AI-answer products start at $150–500+ per month before a single question is asked. Pricing FAQ Everything you need to know about how Assist billing works. What counts as a question? One AI-generated answer. Searches are free and unlimited — you only pay when Assist composes an answer. Follow-ups in a conversation each count as one question. What about repeat questions? Repeat questions are answered instantly from your site's answer cache. Cached answers still count as questions — the cache is a speed win for your visitors, and it means answer quality is consistent for your most-asked questions. What is cache pre-warming? A paid feature that reads your ingested content, generates the hundreds of questions visitors are likely to ask, and answers them all into your cache ahead of time — so your most-asked questions are instant from the first visitor. You review the generated list before it runs, each answered question meters at the normal rate, and it can re-warm automatically whenever your content changes. What happens when I hit my free allowance? The widget falls back to instant search — it keeps working, it just stops composing AI answers until the month resets. With a card on file, pay-as-you-go covers questions past the free tier automatically at $0.01 each; without one, the free tier can never bill you. How does billing work? Usage is metered and deducted hourly from the same prepaid balance you use for other Edge services, against a budget you set. No subscriptions, no seats, nothing to cancel. Can Assist power a private, internal knowledge base? Yes. Bucket-backed sites are private by default: anonymous requests are rejected, and access comes from per-site API keys and short-lived visitor tokens your server mints behind your own login. It's included with pay-as-you-go — no separate plan. What if I have more than 10,000 documents? Talk to our Expert Services team. Deployments beyond the self-serve cap get a dedicated design — access controls per prefix, and retrieval tuned to your corpus. Can I remove the Edge Assist branding? Any paid usage removes the "Powered by Edge Assist" badge. The white-label add-on ($29/site/month) goes further: your own assistant name and icon everywhere your visitors see it. How Assist compares Dedicated AI-answer products charge hundreds per month before a single question. Assist starts at zero and charges a penny a question. Feature Edge Assist Kapa.ai Inkeep Intercom Fin Pricing model Per question Annual contract Plan tiers Per resolution Starting price $0 (250 q/mo free) ~$500+/mo ~$150+/mo $0.99/resolution Free tier Search included Citations on answers White-label option Self-serve setup AI answers for a penny a question 250 answered questions free every month, unlimited search, and citations on everything. No credit card required. Start Free Explore Features --- ### Edge Assist vs Chatbase, Kapa, Inkeep & Intercom Fin | Compare URL: https://edge.network/assist/compare/ Markdown: https://edge.network/assist/compare.md JSON: https://edge.network/json/assist/compare.json _How Edge Assist compares to Chatbase, Kapa.ai, Inkeep, and Intercom Fin: usage-based pricing from $0, citations, white-labelling, and two-minute setup._ Assist Assist Compare The AI-answer market prices like enterprise software. We price like infrastructure — and undercut it by 10–100×. Where Assist is different Same category as Chatbase, Kapa, Inkeep, and Intercom Fin. A very different set of decisions. Priced like infrastructure, not software Kapa and Inkeep sell contracts and tiers — you pay whether visitors ask questions or not. Assist is metered like the rest of Edge: a penny per answered question, from a prepaid balance, with a hard-capped free tier. A quiet month costs you nothing. Live in minutes, not meetings No sales call, no onboarding project. Point Assist at your content, paste one line of code, and it's answering. The same widget that runs on this site — press ⌘K to try it. Search and answers in one Most AI-answer products bolt onto your existing search or replace part of it. Assist is both: instant results as visitors type, AI answers when they ask. One box, one integration, one bill. Part of a platform Assist composes with Edge: ingest documents from a Storage bucket, protect the ask endpoint with Shield, bill from the balance you already hold. One dashboard, one invoice, five products that work together. Feature by feature Published pricing and features as of writing — check vendors for current terms. Feature Edge Assist Chatbase Kapa.ai Inkeep Intercom Fin Pricing model Per question ($0.01) Credit-based tiers Annual contract Plan tiers $0.99/resolution Starting price $0 (250 q/mo free) $40+/mo ~$500+/mo ~$150+/mo Intercom plan + usage Free tier Trial-sized Self-serve setup 1 line of code Self-serve Sales call Self-serve Intercom required Instant search included Citations on answers Limited Streaming answers Pinned facts & curated answers Question & conversation analytics Answer cache (instant repeats) Human handoff & lead capture Via integrations White-label / rename $29/mo add-on Paid add-on Enterprise Document ingestion (bucket) Standalone (no helpdesk required) The maths, on a real site A docs site answering 2,000 questions a month — a healthy, well-used assistant. Edge Assist: 1,750 billable questions after the free 250 = $17.50/month Chatbase: $40–150/month in credit-based tiers — 2–9× more, and credits to ration Kapa.ai: ~$500+/month on an annual contract — ~29× more Inkeep: ~$150+/month on a plan tier — ~9× more Intercom Fin: $0.99 per resolution — 99× the per-answer price, plus the Intercom plan // Monthly cost, 2,000 answered questions Edge Assist $17.50 Chatbase $40–150 Inkeep $150+ Kapa.ai $500+ Intercom Fin $1,980 + plan Same job. Assist is 10–100× cheaper. Try the cheaper one first It's free to start and takes two minutes to add. If it doesn't answer well on your content, you've lost nothing. Start Free --- ### Edge Cache | Edge CDN URL: https://edge.network/cdn/edge-cache/ Markdown: https://edge.network/cdn/edge-cache.md JSON: https://edge.network/json/cdn/edge-cache.json _Edge Cache stores content permanently at every edge location for 100% cache hit rates, zero origin load, and origin failover. Included free with all CDN plans._ CDN CDN Edge Cache Permanently store your most critical content at the edge. Reduce origin load and ensure lightning-fast delivery, always. How Edge Cache Works Three simple steps to permanent edge caching. 1 Upload Once Push your static assets to Edge Cache via API or dashboard. 2 Replicate Globally Content is permanently stored across all 988 edge locations. 3 Serve Forever Content is served directly from the edge, even if your origin is down. Benefits Why Edge Cache is essential for high-performance delivery. 100% Cache Hit Rate Permanently cached content means every request is served from the edge. Zero Origin Load Your origin server is never touched for cached content. Origin Failover Content remains available even if your origin goes down. Unlimited Storage No limits on how much content you can permanently cache. Perfect For Ideal use cases for permanent edge caching. Static Websites JavaScript Libraries CSS Frameworks Media Assets Software Downloads Game Assets Documentation Fonts & Icons Enable Edge Cache today Included with all CDN plans at no extra cost. Get Started --- ### Edge CDN | Global Content Delivery Network URL: https://edge.network/cdn/ Markdown: https://edge.network/cdn.md JSON: https://edge.network/json/cdn.json _Ultra-fast content delivery network spanning thousands of locations worldwide. Zero egress fees, intelligent routing, and real-time analytics._ CDN CDN Performance like never before Join our lightning fast global content delivery network and supercharge your web presence. Deliver consistent experience to everyone, no matter where they are. Start Now Free to sign up. Complete setup in 2 minutes. Never make your users wait again Supercharge your content delivery via a global distribution network with unparalleled speed, security, and stability. Deliver exceptional performance. For every request. Every time. 24/7 Support Advanced Caching Edge Rules Real-Time Monitoring DDoS Protection Zero Egress Fees Global Edge Network 988 strategically placed edge locations ensure your content is always delivered from the nearest point to your users. Smart Caching Intelligent caching algorithms automatically optimize content delivery based on real-time traffic patterns. Image Optimization & Watermarking Resize, convert, and compress images on the fly — and automatically overlay your logo on every image served, with no origin changes. Real-Time Analytics Monitor your traffic, bandwidth, cache hit rates, and performance metrics in real-time with detailed dashboards. Edge Rules Create powerful rules to customize caching behavior, redirects, headers, and more at the edge. Instant Purge Invalidate cached content globally in under 500ms. Full control over what stays and what goes. Password Protection Protect any domain with a username and password, enforced at the edge before the cache. Perfect for sharing dev builds and staging sites privately. Automatic SSL Free SSL certificates issued in under a minute and renewed automatically for every domain you add. TLS 1.3 and HTTP/3 included. 988 Edge Locations <15ms Global Latency 99.99% Uptime SLA $0 Egress Fees Super responsive. Around the clock. No more waiting around for the support you need right now. We are here for you 24 hours a day, 7 days a week, 365 days a year. 5 min First Response 3 hrs Avg. Solve Time Super attentive. Working on a bigger project? Take advantage of a dedicated support team that is available to you 24/7. Get direct help and never wait again. Meet Our Support Team What our customers say Don't just take our word for it. "Edge CDN is truly exceptional. It outperforms major CDN providers in speed, and it's cheaper with zero egress fees." Alex M. CTO, TechStart "Great price. Great service. Great support. Migrated all our assets from AWS and it works better and costs less." Laurent B. Lead Engineer "The best-kept secret in the CDN marketplace. Edge Rules, zero egress, and incredible performance at any scale." Brian J. Founder, MediaFlow Guides & resources Learn how to get the most out of the Edge CDN. Multi-region CDN setup Serve users from the nearest edge node with regional distribution and smart routing. Caching strategies Cache keys, TTLs, and purging patterns that maximise hit rates without stale content. The future CDN, today Why a decentralised delivery network outperforms traditional datacentre CDNs. Start free Deploy to our global network of 2,200+ PoPs with zero egress fees and sub-20ms latency worldwide. Start Now Free to sign up. Complete setup in 2 minutes. --- ### Edge CDN vs Akamai URL: https://edge.network/cdn/compare/akamai/ Markdown: https://edge.network/cdn/compare/akamai.md JSON: https://edge.network/json/cdn/compare/akamai.json _Compare Edge CDN to Akamai. Instant cache purge, zero egress fees, and simpler setup without enterprise complexity._ CDN CDN Comparison Edge vs Akamai A detailed comparison of Edge CDN and Akamai for content delivery. The enterprise CDN alternative Akamai pioneered the CDN industry and remains a giant in enterprise content delivery. They offer a comprehensive suite of solutions with proven reliability at massive scale. However, Akamai's enterprise focus comes with enterprise complexity: long contracts, opaque pricing, slow onboarding, and significant costs that make them prohibitive for many organizations. Edge delivers enterprise-grade performance without the enterprise overhead. Self-service setup in minutes, transparent pricing, and no long-term commitments. Key Differences Zero egress fees – Akamai charges $0.10+/GB 6x more edge locations – 988 vs 350+ Instant cache purge – Akamai takes 5-10 minutes No contracts – Monthly billing, cancel anytime Feature Comparison How Edge and Akamai compare feature by feature. Feature Edge Akamai Egress Fees Free $0.10/GB+ Edge Locations 988 350+ Instant Purge < 1 second 5-10 minutes Setup Time Minutes Weeks Contract Length Monthly Annual minimum DDoS Protection Included Kona (extra) HTTP/3 Real-time Analytics Free SSL Transparent Pricing Decentralized Self-Service Limited Price Comparison Estimated monthly costs. Akamai pricing varies significantly by contract. Scenario Edge Akamai 1 TB egress/month $48 $100+ 10 TB egress/month $480 $1,000+ 100 TB egress/month $4,800 $10,000+ * Akamai pricing is negotiated and varies. Estimates based on industry averages. Migrating from Akamai Switching from Akamai to Edge is straightforward. Our team can help you migrate without downtime, and you'll start saving from day one. 1 Sign up for Edge Create your account and configure your CDN in minutes. 2 Test in parallel Run Edge alongside Akamai to verify performance. 3 Update DNS Point your traffic to Edge and cancel your Akamai contract. Ready to leave enterprise complexity behind? Get enterprise-grade CDN performance without the enterprise overhead. Get Started with Edge CDN View All Comparisons --- ### Edge CDN vs AWS CloudFront URL: https://edge.network/cdn/compare/aws/ Markdown: https://edge.network/cdn/compare/aws.md JSON: https://edge.network/json/cdn/compare/aws.json _Compare Edge CDN to AWS CloudFront. Zero egress fees, instant cache purge, and simple setup vs AWS complexity._ CDN CDN Comparison Edge vs AWS CloudFront A detailed comparison of Edge CDN and Amazon CloudFront for content delivery. Why teams switch from CloudFront AWS CloudFront is a capable CDN deeply integrated into the AWS ecosystem. However, many teams find themselves frustrated by complex pricing, slow cache invalidation, and significant egress costs that grow with success. Edge offers a simpler, more transparent alternative with zero egress fees, instant cache purging, and a decentralized architecture that provides resilience against single points of failure. Key Differences Zero egress fees – CloudFront charges $0.085/GB Instant purge – CloudFront takes 5-10 minutes Simple pricing – No calculator required HTTP/3 support – CloudFront doesn't support it Feature Comparison How Edge and AWS CloudFront compare feature by feature. Feature Edge AWS CloudFront Egress Fees Free $0.085/GB Edge Locations 988 30+ Instant Purge < 1 second 5-10 minutes Setup Complexity Simple Complex DDoS Protection Included AWS Shield (extra) HTTP/3 Real-time Analytics Free SSL Edge Compute Coming soon Lambda@Edge Transparent Pricing Decentralized Vendor Lock-in None High Price Comparison Monthly costs for typical CDN usage scenarios. Edge pricing based on $0.048/GB traffic. Scenario Edge AWS CloudFront 1 TB egress/month $48 $85 10 TB egress/month $480 $850 100 TB egress/month $4,800 $8,500 * AWS pricing based on standard CloudFront rates. Actual costs may vary by region and usage patterns. Ready to switch from CloudFront? Migration is simple. Get started with Edge CDN today and see the difference. Get Started with Edge CDN View All Comparisons --- ### Edge CDN vs BunnyCDN URL: https://edge.network/cdn/compare/bunny/ Markdown: https://edge.network/cdn/compare/bunny.md JSON: https://edge.network/json/cdn/compare/bunny.json _Compare Edge CDN to BunnyCDN. More edge locations, zero egress fees, and enterprise-grade DDoS protection._ CDN CDN Comparison Edge vs Bunny.net A detailed comparison of Edge CDN and Bunny.net for content delivery. How we compare to Bunny.net Bunny.net has made a name for itself with extremely competitive pricing, a developer-friendly approach, and a suite of products including CDN, storage, and video streaming. They're known for transparent, affordable rates. Edge offers a fundamentally different architecture: a decentralized network with 18x more edge locations, zero egress fees, and resilience that centralized providers can't match. While Bunny.net's per-GB pricing is attractive at lower volumes, Edge's zero-egress model and massive edge presence provide unique advantages for businesses that value coverage and predictability. Key Differences 18x more edge locations – 988 vs 123 Zero egress fees – Bunny charges per GB Decentralized architecture – True resilience Enterprise DDoS protection – Included at no extra cost Feature Comparison How Edge and Bunny.net compare feature by feature. Feature Edge Bunny.net Egress Fees Free $0.01-0.06/GB Edge Locations 988 123 Instant Purge DDoS Protection Included Basic HTTP/3 Real-time Analytics Free SSL Image Optimization ✓ (Bunny Optimizer) Video Streaming ✓ (Stream) Edge Storage Transparent Pricing Decentralized When to Choose Edge Both are excellent choices. Here's when Edge makes more sense. You need global coverage With 988 edge locations vs 123, Edge delivers content closer to more users worldwide. You want predictable costs Zero egress fees mean your costs don't spike with traffic. Budget with confidence. You value resilience Edge's decentralized architecture means no single point of failure—ever. Ready to try Edge? Create a free account and experience the difference. Get Started with Edge CDN View All Comparisons --- ### Edge CDN vs CDN77 URL: https://edge.network/cdn/compare/cdn77/ Markdown: https://edge.network/cdn/compare/cdn77.md JSON: https://edge.network/json/cdn/compare/cdn77.json _Compare Edge CDN to CDN77. More global coverage, zero egress fees, and better performance at scale._ CDN CDN Comparison Edge vs CDN77 A detailed comparison of Edge CDN and CDN77 for content delivery. How we compare to CDN77 CDN77 is a respected European CDN provider known for competitive pricing, video streaming capabilities, and a strong private backbone network. They offer transparent pay-as-you-go pricing that appeals to media companies. Edge differentiates with a massively larger edge network (988 vs 50+ locations), zero egress fees, and a decentralized architecture that provides unmatched resilience. While CDN77 offers volume discounts at scale, Edge's zero-egress model becomes increasingly advantageous as traffic grows. Key Differences 44x more edge locations – 988 vs 50+ Zero egress fees – CDN77 charges per GB Decentralized architecture – No single point of failure Predictable costs – No surprises as traffic scales Feature Comparison How Edge and CDN77 compare feature by feature. Feature Edge CDN77 Egress Fees Free $0.049/GB+ Edge Locations 988 50+ Instant Purge DDoS Protection Included Included HTTP/3 Real-time Analytics Free SSL Video Streaming Transparent Pricing Decentralized Pay-as-you-go Private Backbone Ready to try Edge? Create a free account and experience the difference. Get Started with Edge CDN View All Comparisons --- ### Edge CDN vs Cloudflare URL: https://edge.network/cdn/compare/cloudflare/ Markdown: https://edge.network/cdn/compare/cloudflare.md JSON: https://edge.network/json/cdn/compare/cloudflare.json _Compare Edge CDN to Cloudflare. More edge locations, dedicated CDN infrastructure, and no vendor lock-in._ CDN CDN Comparison Edge vs Cloudflare A detailed comparison of Edge CDN and Cloudflare for content delivery. How we compare to Cloudflare Cloudflare is a well-established CDN with a generous free tier and strong security features. They've built a massive centralized network and offer many services beyond CDN. Edge takes a different approach: a decentralized architecture that provides true resilience, fully transparent pricing at all tiers, and a focus on performance without vendor lock-in. While Cloudflare's free tier is attractive, their enterprise pricing is opaque and requires sales conversations. Edge publishes all pricing upfront. Key Differences 7x more edge locations – 988 vs 300+ Decentralized architecture – No single point of failure Transparent enterprise pricing – No sales calls required No vendor lock-in – Standard APIs, easy migration Feature Comparison How Edge and Cloudflare compare feature by feature. Feature Edge Cloudflare Egress Fees Free Free Edge Locations 988 300+ Instant Purge Free Tier Free tier included Limited free DDoS Protection Included Included HTTP/3 Real-time Analytics Free SSL Transparent Pricing Partially Decentralized Enterprise Pricing Published Quote required Vendor Lock-in None Moderate When to Choose Edge Both are solid choices, but here's when Edge makes more sense. You need maximum coverage With 988 edge locations vs Cloudflare's 300+, Edge delivers content closer to more users globally. You want transparent pricing Cloudflare's enterprise pricing requires sales conversations. Edge publishes everything upfront. You value resilience Edge's decentralized architecture means no single point of failure, unlike centralized providers. Ready to try Edge? Create a free account and experience the difference. Get Started with Edge CDN View All Comparisons --- ### Edge CDN vs Fastly URL: https://edge.network/cdn/compare/fastly/ Markdown: https://edge.network/cdn/compare/fastly.md JSON: https://edge.network/json/cdn/compare/fastly.json _Compare Edge CDN to Fastly. Zero egress fees, 988+ edge locations, and better value for high-traffic sites._ CDN CDN Comparison Edge vs Fastly A detailed comparison of Edge CDN and Fastly for content delivery. How we compare to Fastly Fastly has built a reputation for developer-friendly edge computing with their Compute@Edge platform and powerful VCL configuration language. They're favored by engineering teams who need granular control. Edge offers a simpler approach with a much larger network (988 vs 90+ locations), zero egress fees, and no minimum spend. Our decentralized architecture provides resilience that traditional CDNs can't match. For teams who value simplicity, cost predictability, and global coverage over complex edge logic, Edge is the clear choice. Key Differences 24x more edge locations – 988 vs 90+ Zero egress fees – Fastly charges $0.08-0.28/GB No minimum spend – Fastly requires $50/mo Simple configuration – No VCL learning curve Feature Comparison How Edge and Fastly compare feature by feature. Feature Edge Fastly Egress Fees Free $0.08-0.28/GB Edge Locations 988 90+ Instant Purge ✓ (150ms) Edge Compute Coming soon Compute@Edge DDoS Protection Included Included HTTP/3 Real-time Analytics Free SSL VCL/Config Language Simple rules VCL (complex) Transparent Pricing Partially Decentralized Minimum Spend None $50/mo Price Comparison Monthly costs for typical CDN usage scenarios. Scenario Edge Fastly 1 TB egress/month $48 $80+ 10 TB egress/month $480 $800+ 100 TB egress/month $4,800 Custom * Fastly pricing varies by region. Enterprise pricing requires custom quote. Ready to try Edge? Create a free account and experience the difference. Get Started with Edge CDN View All Comparisons --- ### Edge Compute - Global Virtual Machines URL: https://edge.network/compute/ Markdown: https://edge.network/compute.md JSON: https://edge.network/json/compute.json _Powerful virtual machines across 33 global regions. Flexible configurations, unlimited bandwidth, and predictable pricing._ Compute Compute Virtual machines at the edge Deploy powerful virtual machines globally in seconds. From small development instances to GPU-accelerated workloads, scale your infrastructure without limits. Deploy Your First VM Free to sign up. Complete setup in 2 minutes. Flexible resources, your way No fixed instance sizes — pick the exact vCPU, RAM, and disk for each server, across one machine or many, and pay hourly for what you configure. vCPUs 1 – 32 Per server, scale as needed RAM 1 – 64 GB Per server, scale as needed NVMe Storage 1 GB – 2 TB Per server, scale as needed Pay only for what you configure Unlike fixed instance sizes, Edge prices each resource separately — choose exactly the vCPU, RAM, and storage you need and pay hourly. Spin up multiple small servers or consolidate into fewer powerful ones, resize live as your needs change. View Pricing Configuration Options Built for performance Enterprise-grade infrastructure with the tools you need to build and scale. Instant Provisioning Deploy VMs in under 60 seconds. No waiting, no queues. Your infrastructure ready when you need it. Global Regions Deploy close to your users across 20+ regions worldwide. Reduce latency and improve performance. Console Access Browser-based VNC console for direct access. Debug issues or recover from SSH lockouts instantly. Live Resize Scale vCPU, RAM, and disk on running VMs without downtime. Grow as your needs change. Private Networks Isolated VxLAN networks between your VMs. Automatic IP assignment with secure customer isolation. Recovery Tools Rescue mode, automated backups, and OS reinstall. Recover from any situation with confidence. 20+ Global Regions <60s Deploy Time 99.99% Uptime SLA $0 Egress Fees Your favorite operating systems Deploy with one-click images or bring your own ISO. Alma Linux CentOS Debian Ubuntu FreeBSD Oracle Linux Alpine ISO Custom ISO Guides & resources Everything you need to plan, deploy, and run production workloads on Edge Compute. Migrating from AWS Map EC2 instance types to per-resource configurations and move workloads without surprises. Deploy a Node.js app From VM creation to a production process manager and reverse proxy, step by step. High availability patterns Multi-region designs, DNS failover, and load balancing on decentralised infrastructure. Ready to deploy? Start free today — pay per resource, billed hourly. Get Started Free --- ### Edge Compute vs AWS EC2 URL: https://edge.network/compute/compare/aws/ Markdown: https://edge.network/compute/compare/aws.md JSON: https://edge.network/json/compute/compare/aws.json _Compare Edge Compute to AWS EC2. Per-resource pricing without instance-type complexity, zero egress fees, and prepaid billing with no surprise bills._ Compute Compute Comparison Edge vs AWS EC2 A detailed comparison of Edge Compute and Amazon EC2 for cloud virtual machines. How we compare to AWS EC2 AWS EC2 is the industry default, with unmatched breadth: hundreds of instance types, every conceivable integration, and deep enterprise tooling. If your architecture depends on the wider AWS ecosystem — RDS, Lambda, SQS, IAM — EC2 is the natural home for your compute. That breadth comes at a cost: pricing complexity, separate charges for storage and bandwidth, and bills that are hard to predict. Edge Compute has three published per-resource rates — vCPU, RAM, and NVMe disk — billed hourly from a prepaid balance, with zero egress fees and no separate storage line items. For teams running VMs, object storage, DNS, and a CDN, Edge Compute delivers the essentials at a fraction of the cost and complexity. See the compute docs to get started. Key Differences Three published rates – vCPU, RAM, disk — no instance-type matrix Zero egress fees – EC2 charges $0.09/GB to serve your users Prepaid billing – A surprise bill is impossible by design Free signup, no card – Deploy without an enterprise procurement process Feature Comparison How Edge and AWS EC2 compare feature by feature. Feature Edge AWS EC2 Pricing Model Per resource 750+ instance types Custom vCPU / RAM / Disk Egress Fees Free $0.09/GB Billing Hourly, prepaid Per second, postpaid Surprise Bills Possible Storage Included NVMe included EBS billed separately DDoS Protection Included Extra cost (Shield Advanced) Deploy Time <60s 2-5 min Pricing Complexity 3 rates Requires a calculator GPU Instances Decentralized Sustainable by Design Price Comparison Monthly pricing for comparable VM configurations. Edge prices are calculated from our published per-resource rates . VM Specs Edge AWS EC2 2 vCPU / 4 GB / 80 GB $19.24 ~$36 2 vCPU / 8 GB / 160 GB $32.63 ~$70 4 vCPU / 16 GB / 320 GB $65.26 ~$140 8 vCPU / 32 GB / 640 GB $130.52 ~$280 * AWS estimates based on comparable t3/m-family on-demand instances in us-east-1 plus gp3 EBS storage, as published at the time of writing. Excludes egress, which AWS bills separately at ~$0.09/GB. Prices vary by region — check AWS's current pricing. When to Choose Edge AWS has unmatched breadth. Here's when Edge makes more sense. You serve real traffic EC2 egress at $0.09/GB means 10 TB out costs around $900 on top of your instances. Edge includes transfer at no charge. You want a bill you can predict AWS bills arrive after the fact and famously surprise people. Edge Compute is prepaid — when your balance runs out, VMs stop and data is retained. You don't need 200+ AWS services If your workload is VMs, storage, DNS, and a CDN, Edge covers it without IAM policies, VPC wizards, or a pricing calculator. Ready to try Edge? Create a free account — no card required — and deploy your first VM in under a minute. Get Started with Edge Compute View All Comparisons --- ### Edge Compute vs DigitalOcean Droplets URL: https://edge.network/compute/compare/digitalocean/ Markdown: https://edge.network/compute/compare/digitalocean.md JSON: https://edge.network/json/compute/compare/digitalocean.json _Compare Edge Compute to DigitalOcean Droplets. Per-resource pricing instead of fixed sizes, zero egress fees, and prepaid billing with no surprise bills._ Compute Compute Comparison Edge vs DigitalOcean A detailed comparison of Edge Compute and DigitalOcean Droplets for cloud virtual machines. How we compare to DigitalOcean DigitalOcean is one of the best-known developer clouds, with a mature product line, extensive tutorials, and a large community. Droplets are simple to deploy and come in a wide range of fixed sizes. Edge takes a different approach: instead of fixed instance sizes, you pay per resource — vCPU, RAM, and NVMe disk are each priced independently and billed hourly from a prepaid balance. You can deploy a VM with exactly the resources you need, and signup is free with no card required. If you rely heavily on DigitalOcean's managed products — managed databases, App Platform, or managed Kubernetes — their ecosystem may be a better fit. For raw virtual machines with flexible sizing and predictable costs, Edge is hard to beat. See the compute docs to get started. Key Differences Per-resource pricing – Pick exact vCPU, RAM, and disk — no fixed sizes Free signup, no card – DigitalOcean requires payment details upfront Prepaid billing – A surprise bill is impossible by design Zero egress fees – No per-GB transfer overage charges Feature Comparison How Edge and DigitalOcean compare feature by feature. Feature Edge DigitalOcean Pricing Model Per resource Fixed Droplet sizes Custom vCPU / RAM / Disk Sign Up Without Card Egress Fees Free Pooled allowance, then per GB Billing Hourly, prepaid Hourly, postpaid Surprise Bills Possible NVMe Storage Deploy Time <60s <60s DDoS Protection Included Basic GPU Instances Decentralized Sustainable by Design Price Comparison Monthly pricing for comparable VM configurations. Edge prices are calculated from our published per-resource rates . VM Specs Edge DigitalOcean 1 vCPU / 1 GB / 25 GB $6.64 $6 1 vCPU / 2 GB / 50 GB $10.36 $12 2 vCPU / 4 GB / 80 GB $19.24 $24 4 vCPU / 8 GB / 160 GB $38.47 $48 8 vCPU / 16 GB / 320 GB $76.94 $96 * DigitalOcean prices are published list prices for Basic (shared CPU) Droplets at the time of writing. Check DigitalOcean's current pricing. When to Choose Edge Both are solid choices, but here's when Edge makes more sense. You want to size VMs exactly Droplets come in fixed tiers, so you often pay for RAM or disk you don't need. Edge lets you configure each resource independently. You want a hard spending cap Edge Compute bills hourly from a prepaid balance. When it runs out, VMs stop and your data is retained — no runaway bills. You value sustainability Edge's decentralized network uses existing capacity instead of new data centres, making it around 50% greener by design. Ready to try Edge? Create a free account — no card required — and deploy your first VM in under a minute. Get Started with Edge Compute View All Comparisons --- ### Edge Compute vs Hetzner Cloud URL: https://edge.network/compute/compare/hetzner/ Markdown: https://edge.network/compute/compare/hetzner.md JSON: https://edge.network/json/compute/compare/hetzner.json _Compare Edge Compute to Hetzner Cloud. Per-resource pricing, free signup with no card, global decentralised regions, and prepaid billing with no surprise bills._ Compute Compute Comparison Edge vs Hetzner Cloud A detailed comparison of Edge Compute and Hetzner Cloud for cloud virtual machines. How we compare to Hetzner Hetzner Cloud has earned a strong reputation for aggressive pricing — its shared vCPU plans start at just a few euros a month, and on raw price per plan it's one of the cheapest providers anywhere. If your workload fits neatly into one of its fixed plans and its European-centred regions, it's genuinely hard to beat on cost. Edge competes on a different axis. Instead of fixed plans, you pay per resource — vCPU, RAM, and NVMe disk are priced independently and billed hourly from a prepaid balance, so you never pay for capacity you don't use and a surprise bill is impossible by design. Signup is free with no card and no identity checks. Edge's decentralised network also offers global coverage where Hetzner is concentrated in Germany and Finland, plus GPU instances that Hetzner Cloud doesn't offer. See the compute docs to get started. Key Differences Per-resource pricing – Pick exact vCPU, RAM, and disk — no fixed plans Free signup, no card – No payment details or ID checks to get started Global coverage – Hetzner locations are concentrated in Europe Prepaid billing – A surprise bill is impossible by design Feature Comparison How Edge and Hetzner Cloud compare feature by feature. Feature Edge Hetzner Cloud Pricing Model Per resource Fixed server plans Custom vCPU / RAM / Disk Sign Up Without Card Billing Hourly, prepaid Hourly, postpaid Surprise Bills Possible Region Coverage Global EU, US, Singapore Egress Fees Free Allowance, then per TB NVMe Storage GPU Instances Identity Checks at Signup None Sometimes required Decentralized Sustainable by Design Green energy DCs How the Pricing Models Differ Hetzner sells fixed plans priced in euros; Edge prices each resource independently. Rather than compare plan-for-plan, here's what each model means for you. Hetzner: fixed plans Hetzner's shared vCPU plans start at a few euros per month and scale in fixed steps of vCPU, RAM, and disk. Prices are quoted in euros excluding VAT, with a bandwidth allowance included and per-TB charges beyond it. Check Hetzner's current pricing for exact figures. On raw price per plan, Hetzner is often the cheapest option — but if your workload needs, say, lots of RAM and little disk, you still pay for the whole bundle. Edge: per resource vCPU is $0.004/hr (~$2.92/mo), RAM is $0.00256/GiB-hr (~$1.87/mo), and NVMe disk is $0.074/GiB-mo. Combine them however you like and pay hourly from a prepaid balance. 1 vCPU · 2 GB RAM · 40 GB NVMe $9.62/mo 2 vCPU · 4 GB RAM · 80 GB NVMe $19.24/mo 4 vCPU · 8 GB RAM · 160 GB NVMe $38.47/mo * Edge prices are calculated from our published per-resource rates . Hetzner pricing as published at the time of writing — check Hetzner's site for current figures. When to Choose Edge Hetzner is a great budget choice for European workloads. Here's when Edge makes more sense. You need regions beyond Europe Hetzner's locations are concentrated in Germany and Finland, with limited US and Singapore presence. Edge's decentralised network spans the globe. You want to size VMs exactly Hetzner's plans are fixed bundles, so you pay for resources you may not use. Edge prices vCPU, RAM, and disk independently. You want zero-friction signup Hetzner requires payment details and sometimes identity verification before you can deploy. Edge signup is free with no card required. Ready to try Edge? Create a free account — no card required — and deploy your first VM in under a minute. Get Started with Edge Compute View All Comparisons --- ### Edge Compute vs Vultr URL: https://edge.network/compute/compare/vultr/ Markdown: https://edge.network/compute/compare/vultr.md JSON: https://edge.network/json/compute/compare/vultr.json _Compare Edge Compute to Vultr. Per-resource pricing instead of fixed plans, free signup with no card, and prepaid billing with no surprise bills._ Compute Compute Comparison Edge vs Vultr A detailed comparison of Edge Compute and Vultr for cloud virtual machines. How we compare to Vultr Vultr is a well-regarded independent cloud with competitive pricing, a wide choice of locations, and a broad product range including bare metal and GPU instances. Its fixed plans are simple and its entry-level pricing is aggressive. Edge takes a different approach: instead of fixed plans, you pay per resource — vCPU, RAM, and NVMe disk are each priced independently and billed hourly from a prepaid balance. Signup is free with no card required, and DDoS protection is included rather than an add-on. If you need bare metal or Vultr's specific managed products, they may be a better fit. For flexible, exactly-sized VMs with predictable costs on a decentralised network , Edge is the stronger choice. See the compute docs to get started. Key Differences Per-resource pricing – Pick exact vCPU, RAM, and disk — no fixed plans Free signup, no card – Vultr requires payment details upfront Prepaid billing – A surprise bill is impossible by design DDoS protection included – Vultr charges extra per instance Feature Comparison How Edge and Vultr compare feature by feature. Feature Edge Vultr Pricing Model Per resource Fixed plans Custom vCPU / RAM / Disk Sign Up Without Card Egress Fees Free Allowance, then per GB Billing Hourly, prepaid Hourly, postpaid Surprise Bills Possible NVMe Storage Deploy Time <60s <60s DDoS Protection Included Extra cost GPU Instances Decentralized Sustainable by Design Price Comparison Monthly pricing for comparable VM configurations. Edge prices are calculated from our published per-resource rates . VM Specs Edge Vultr 1 vCPU / 1 GB / 25 GB $6.64 $5 1 vCPU / 2 GB / 55 GB $10.73 $10 2 vCPU / 4 GB / 80 GB $19.24 $20 4 vCPU / 8 GB / 160 GB $38.47 $40 8 vCPU / 16 GB / 320 GB $76.94 $80 * Vultr prices are published list prices for Regular Cloud Compute plans at the time of writing. Check Vultr's current pricing. When to Choose Edge Both are solid choices, but here's when Edge makes more sense. You want to size VMs exactly Vultr's plans come in fixed steps, so you often pay for RAM or disk you don't need. Edge prices each resource independently. You want a hard spending cap Edge Compute bills hourly from a prepaid balance. When it runs out, VMs stop and your data is retained — no runaway bills. You value sustainability Edge's decentralized network uses existing capacity instead of building new data centres, making it around 50% greener by design. Ready to try Edge? Create a free account — no card required — and deploy your first VM in under a minute. Get Started with Edge Compute View All Comparisons --- ### Edge DNS vs AWS Route 53 URL: https://edge.network/dns/compare/route53/ Markdown: https://edge.network/dns/compare/route53.md JSON: https://edge.network/json/dns/compare/route53.json _Compare Edge DNS to AWS Route 53: no per-zone fees, sub-5-second propagation, and health checks included. Simpler pricing for DNS at any scale._ DNS DNS Comparison Edge DNS vs AWS Route 53 A detailed comparison of Edge DNS and Amazon Route 53 for authoritative DNS hosting. How we compare to Route 53 Route 53 is AWS's DNS service: mature, reliable, and deeply integrated with the rest of the AWS ecosystem. If your infrastructure lives entirely inside AWS, that integration is a real convenience. The trade-off is pricing complexity and speed. Route 53 charges $0.50 per hosted zone per month before you've answered a single query, $0.40 per million queries after that, and $0.50 per health check on top. Record changes take around 60 seconds to propagate. Edge DNS is free — up to 50 zones with unlimited records and a million queries a month per zone — with health checks included and propagation in under 5 seconds. Edge also includes the AI DNS Examiner, which analyses your zone configuration automatically — something Route 53 has no equivalent for. Key Differences Free DNS hosting – Route 53 charges $0.50 per hosted zone, every month Faster propagation – <5 seconds vs 60 seconds Health checks included – $0.50 per check on Route 53 No query metering – 1M queries/month per zone included vs $0.40 per million Feature Comparison How Edge DNS and Route 53 compare feature by feature. Feature Edge Route 53 Price Free $0.50/zone + usage Zones Included Up to 50 Pay per zone Records Unlimited Unlimited Query Pricing 1M/zone/month included $0.40/million Anycast PoPs 50+ 50+ Propagation Time <5 seconds 60 seconds DNSSEC Health Checks Included $0.50/check Geo-routing ALIAS Records API Access DDoS Protection Unlimited Limited AI DNS Examiner Price Comparison Monthly pricing for common usage scenarios. Route 53's per-zone and per-check fees compound as your footprint grows; Edge's single query rate doesn't. Scenario Edge Route 53 10 domains, 10M queries/mo Free $9 50 domains, 50M queries/mo Free $45 10 health checks Included $5/mo Geo-routing Included Per-query premium When to Choose Edge Both are capable DNS providers. Here's when Edge makes more sense. You manage many domains Route 53's $0.50 monthly fee per hosted zone adds up fast across a portfolio. Edge DNS is free for up to 50 zones — you pay nothing per domain. You need changes to land quickly Edge propagates record changes in under 5 seconds, against 60 seconds on Route 53. For failover and rapid rollouts, that gap matters. You want predictable, simple pricing Free — with unlimited records, a million queries a month per zone, and health checks included. No per-zone fees, no per-check fees, no bill-shaped surprises. Also considering Cloudflare? See how Edge DNS compares to Cloudflare DNS . Ready to try Edge DNS? Create a free account and add your first zone in minutes. Get Started with Edge DNS View All Comparisons --- ### Edge DNS vs Cloudflare DNS URL: https://edge.network/dns/compare/cloudflare/ Markdown: https://edge.network/dns/compare/cloudflare.md JSON: https://edge.network/json/dns/compare/cloudflare.json _Compare Edge DNS to Cloudflare DNS: health checks included, geo-routing without an enterprise tier, and the AI DNS Examiner. A fair, detailed comparison._ DNS DNS Comparison Edge DNS vs Cloudflare DNS A detailed, fair comparison of Edge DNS and Cloudflare DNS for authoritative DNS hosting. How we compare to Cloudflare Cloudflare runs one of the largest DNS platforms in the world, with over 300 anycast PoPs and free authoritative DNS for unlimited domains. Edge DNS is also free — up to 50 zones with unlimited records and a million queries a month per zone, no card required — so for most teams the price of both providers is the same: nothing. Where the picture changes is when you need more than the basics. Health checks cost extra on Cloudflare, and geo-routing is reserved for the Enterprise tier. On Edge, both are included on every account, alongside the AI DNS Examiner — automated analysis of your zone configuration that no other provider in this comparison offers. Edge DNS is also a genuinely standalone service. It works with any CDN, any host, and any cloud, so choosing it for DNS never becomes a decision about the rest of your stack. Key Differences Health checks included – an extra cost on Cloudflare Geo-routing on every account – Enterprise-only on Cloudflare AI DNS Examiner – automated analysis of your zone configuration Standalone DNS – use Edge DNS with any CDN, host, or provider Feature Comparison How Edge DNS and Cloudflare DNS compare feature by feature. Feature Edge Cloudflare Price Free Free Zones Included Up to 50 Unlimited Records Unlimited Unlimited Queries Included 1M/zone/month Unlimited Anycast PoPs 50+ 300+ Propagation Time <5 seconds <5 seconds DNSSEC Health Checks Included Extra cost Geo-routing Enterprise ALIAS Records API Access DDoS Protection Unlimited Unlimited AI DNS Examiner What's Included Free Both providers offer free authoritative DNS. The difference is what sits inside the free tier: on Cloudflare, advanced features become a paid or Enterprise conversation; on Edge, they're included. Feature Edge Cloudflare Authoritative DNS hosting Free Free Health checks Included Extra cost Geo-routing Included Enterprise tier AI zone analysis (DNS Examiner) Included Not available When to Choose Edge Both are excellent DNS providers. Here's when Edge makes more sense. You need health checks Edge includes health checks as standard, so you can route around failing endpoints without buying an add-on. You want geo-routing without an enterprise contract On Cloudflare, geo-routing is reserved for the Enterprise tier. On Edge, every account gets it. You want DNS that stands alone Edge DNS works with whatever sits behind it — any CDN, any host, any cloud. There's no pull towards adopting the rest of a proprietary stack. Also weighing up AWS? See how Edge DNS compares to Route 53 . Ready to try Edge DNS? Create a free account and add your first zone in minutes. Get Started with Edge DNS View All Comparisons --- ### Edge Pulse | Synthetic Monitoring from Real User Locations URL: https://edge.network/pulse/ Markdown: https://edge.network/pulse.md JSON: https://edge.network/json/pulse.json _Monitor your infrastructure from 2,000+ residential locations worldwide. See what your actual users see — not what data centres see. Status pages included._ Pulse Pulse Monitor from real user locations Your CDN says it's working. Your users say it isn't. Pulse monitors from 2,000+ residential connections worldwide — so you see exactly what your users see. Start Monitoring Free to start — 150,000 check runs every month, no credit card required. 2,000+ Probe Locations 30s Check Frequency 6 Probe Types 150k Free Check Runs / Month How it works From configuration to incident response in three simple steps. 01 Configure your checks Set up HTTP, DNS, SSL, TCP, API, or Page Speed checks in seconds. Choose your probe locations, frequency, and alert rules. 02 Probes run from Edge Hosts Your checks execute from real residential connections worldwide — the same networks your users are on. Not from data centres. 03 Get alerts & dashboards Instant alerts via email, Slack, webhook, or PagerDuty. Real-time dashboards with uptime grids, response time charts, and incident timelines. Six probe types. One platform. Monitor every layer of your stack from the networks your users are actually on. HTTP / HTTPS Monitor URLs with GET/POST requests. Validate status codes, response times, and body content matches. As fast as every 30 seconds. DNS Resolve domains from residential resolvers worldwide. Verify records match expected values and track propagation times. SSL Certificate Track certificate validity, expiry dates, and chain completeness. Get warned before certificates expire — not after. TCP / UDP Port connectivity checks from real user networks. Verify your services are reachable where your users actually are. API Workflow Multi-step API monitoring: authenticate, make requests, validate responses. Test entire workflows, not just endpoints. Page Speed Full page load timing from residential connections. Measure TTFB, DOM ready, and complete load — real-world performance. The real world advantage Every competitor runs probes from data centres. We run them from the same residential and business connections that your users are on. That changes everything. Real residential networks Probes run from home broadband connections on real ISPs — the same path your users take. Data centre probes miss ISP-level issues entirely. Catch what others miss Residential IPs aren't on cloud provider allowlists. If a CDN is accidentally blocking residential traffic, Pulse catches it. Competitors can't. Real DNS resolution paths Your users resolve DNS through residential resolvers, not cloud DNS. Pulse tests the same resolution path and catches propagation issues others miss. Genuine network conditions Real-world latency, packet loss, and ISP routing — not the pristine connections between data centres. See true end-user performance. Smart incident detection A single probe failure doesn't mean your site is down. Pulse confirms incidents across multiple locations before alerting you — eliminating false positives without sacrificing speed. Probe fails from one location — immediately re-probed from 2 more hosts in the same region 2 of 3 probes fail in one region — confirmed regional failure 3+ regions report failure — global incident triggered Alerts delivered in seconds via email, Slack, webhook, or PagerDuty // Probe fails from London → Re-probing from 2 more London hosts... ✗ London host-2: timeout (3.2s) ✗ London host-3: 503 Service Unavailable → Confirmed failure in London. Checking other regions... ✗ Paris: 503 Service Unavailable ✗ Frankfurt: timeout (4.1s) ✓ New York: 200 OK (142ms) ✓ Tokyo: 200 OK (198ms) ⚠ Regional incident: EU regions affected → Alert sent to #ops-alerts (Slack) → Status page updated automatically Status pages, from free Every competitor charges $29–79/month extra for status pages. With Pulse, a shared status page is free on every account, and a custom branded page on your own domain is just $2/month. Give your users a professional page they can trust. Custom domain (status.yourdomain.com) Branded with your logo and colours Real-time uptime for each service Full incident history with timeline Email and RSS subscriptions Powered by Edge CDN + DNS status.yourapp.com Website Operational API Operational Dashboard Degraded CDN Operational Last updated 12 seconds ago Stop guessing. Start monitoring. See what your users see with monitoring from 2,000+ real residential locations. 150,000 free check runs every month — no credit card needed. Start Monitoring Free --- ### Edge Shield | The Lightweight CAPTCHA Alternative URL: https://edge.network/shield/ Markdown: https://edge.network/shield.md JSON: https://edge.network/json/shield.json _Free, privacy-first verification for the agentic web. Welcome humans invisibly, route legitimate AI agents, and stop abuse — with a 1–100 humanity score on every check. No puzzles, no tracking, no lock-in._ Shield Shield Stop abuse. Not automation. Free, privacy-first verification without puzzles or tracking. Shield scores every visitor invisibly from 1–100 — so you can welcome humans, route legitimate AI agents to the right endpoints, and stop abuse before it reaches your forms. Get Your Sitekey Free forever for core protection — unlimited widgets, no credit card required. Verified Sign up // siteverify response { "success" : true, "score" : 96 } <15KB JavaScript Bundle 1–100 Humanity Score 0 Cookies & Trackers Free Forever How it works From script tag to verified traffic in under five minutes. 01 Add the snippet One script tag and one div with your sitekey. Works with plain HTML, React, Vue, or any framework — under five minutes to integrate. 02 Visitors verify invisibly A lightweight proof-of-work runs in a background thread while risk signals are scored — and the score keeps refining as the visitor interacts. Real humans almost never see a challenge. 03 Validate server-side Your server checks the response token with one API call and gets a pass/fail verdict plus a 1–100 humanity score. Tokens are single-use and expire in five minutes. Everything Turnstile does. Less of what it costs you. Bot protection shouldn't mean puzzles for your users, tracking scripts on your pages, or routing your traffic through someone else's network. Invisible verification No traffic lights, no crosswalks, no fire hydrants. Managed mode only shows a single "I am human" click to genuinely suspicious traffic. Humanity score Every verification returns a 1–100 score — 1 is confirmed automation, 100 a confirmed human. Allow, step up, redirect, or block: your rules, not a binary verdict. Privacy by design No cookies, no fingerprint database, no per-visitor storage — only hourly aggregate counters. GDPR and CCPA friendly by default, not by configuration. Genuinely lightweight A dependency-free widget under 15KB that solves challenges in a Web Worker. Your Core Web Vitals won't notice it exists. Drop-in Turnstile migration The siteverify response matches Turnstile's exactly, and compatibility mode populates the same form field. Migrate by swapping a URL and two keys. Edge accelerated Challenges are stateless and cryptographically signed, built to be served from Edge Network PoPs closest to your visitors. Shadow mode & test keys Trial Shield in report-only mode on live traffic — nothing ever blocked — and run CI against fixed test sitekeys that never touch real state. Offline verification Tokens are Ed25519-signed JWTs with a public JWKS endpoint. Verify them on your own server with zero network calls. The tarpit Repeat offenders get exponentially harder proof-of-work. Bots can keep trying — they just pay for it in electricity. Two snippets. That's the integration. A script tag and a div on the client, one HTTP call on your server. If you're on Turnstile today, the response format is identical — swap the URL and your keys, and you're migrated. Sitekey + secret key model — familiar from Turnstile and reCAPTCHA Works with SPAs, mobile web, and any backend language Single-use tokens with short expiry, cryptographically signed Embeddable on any site — your traffic never routes through our network <!-- 1. On your page --> <script src= "https://shield.edge.network/api.js" defer></script> <div class= "edge-shield" data-sitekey= "es_your_sitekey" ></div> // 2. On your server POST https://shield.edge.network/siteverify // Response { "success" : true , "score" : 96 , "hostname" : "example.com" } Three modes. Zero puzzles. Choose how visible verification is — from a subtle badge to nothing at all. Recommended Managed Adapts automatically. Verification is invisible for real users; only suspicious traffic gets a one-click confirmation with a harder challenge. Non-Interactive Background verification with a small status badge. No user action, ever — traffic that fails simply doesn't get a token. Invisible No visible widget at all. Verification runs silently behind your forms and login pages, triggered on load or on demand. Built for the agentic web A growing share of legitimate traffic isn't human — shopping assistants, booking agents, and research tools acting on behalf of real people. Binary CAPTCHAs treat them all as attacks. Shield treats automation as a signal, not a verdict — you decide what happens next. Verified agent identity Agents that sign their requests with Web Bot Auth — the IETF standard backed by OpenAI, Google, and Amazon — are cryptographically identified, not guessed at. Confirmed crawlers like Googlebot are verified too. Route, don't dead-end The siteverify response tells you exactly who a verified agent is, so you can send it to your API or agent endpoints instead of a puzzle. Per-widget policies — allow, challenge, or block — put you in control. Aggressive with the anonymous Automation that refuses to identify itself is, by definition, the traffic you can be hard on. Clear automation signals with no declared identity floor the humanity score — declaring identity is the fast path. Live now: Web Bot Auth verification on every challenge, reverse-DNS crawler confirmation, per-widget agent policies, and a server-side agentverify API — no widget required. Privacy isn't a setting. It's the architecture. Shield never stores per-visitor data — not anonymised, not aggregated per user, not at all. Verification signals are scored in memory and discarded; the only thing persisted is hourly counters. There's nothing to consent to, because there's nothing collected. No cookies or local storage No behavioural profiling or ad tracking No fingerprint database Only hourly aggregate counters stored Open-source client widget WCAG 2.2 AA accessible What Shield stores Hourly challenge counts Stored Average humanity score Stored Visitor IP addresses Never Browsing history / fingerprints Never Cookies Never Shield Examiner Your AI traffic analyst Charts tell you what happened; the Examiner tells you what it means. One click turns 30 days of metrics into a plain-English review — how much bot pressure you're under, whether escalation is calibrated for your audience, what abuse signals look like, and the exact score thresholds to use in your own verification handling. It reads hourly aggregates only. Shield holds no per-visitor data, so your visitors are never part of the analysis — there's nothing about them to analyse. Read the Examiner docs Shield Examiner Powered by Grok 92 / 100 Healthy traffic with no abuse signals — humans score well, replay protection has nothing to catch, and bot pressure is low. Escalation rate above typical range warning 25% of background attempts were escalated to a click — consistent with a VPN-heavy audience rather than an attack. Fix: If VPN users matter to you, treat scores 30–40 as acceptable at siteverify rather than blocking. Common Questions Including the one everyone asks: why deploy bot protection before you have a bot problem? We don't have a bot problem. Why add Shield now? Because "no bot problem" is usually an assumption, not a measurement — automated traffic doesn't announce itself. It shows up as inflated visitor counts, odd conversion rates, and email lists that decay faster than they should. Shield in invisible mode is a measurement instrument first: every visitor gets a 1–100 humanity score in the background, and your dashboard shows the real mix of humans, declared AI agents, and undeclared automation — without a single challenge shown. Most sites are surprised by what they see in the first fortnight. Is Shield just a CAPTCHA replacement for once abuse starts? That's part of it — but the reason CAPTCHAs are added reactively is that they cost conversion, so nobody wants one until they must. Shield is invisible and free, so that trade-off disappears. Running it... --- ### Edge Shield Demo | Try It Live URL: https://edge.network/shield/demo/ Markdown: https://edge.network/shield/demo.md JSON: https://edge.network/json/shield/demo.json _Watch Edge Shield verify you in real time — invisible challenge, humanity score, and a live server-side siteverify call. No puzzles, no tracking._ Shield Shield Watch it verify you This page runs a real Shield widget. By the time you read this sentence, you have probably already been verified — no puzzle, no clicking, no data collected. 1 The widget A managed-mode widget in a typical signup form. The proof-of-work solved in a background thread while the page loaded — the badge is all a real visitor sees. Reset and verify again Email Sign up This form does not submit anywhere — it is here to show the widget in context. 2 The token Verification produced a signed, single-use token and placed it in a hidden form input, ready to travel with the form submission. It expires after five minutes and refreshes automatically. Waiting for verification… 3 Your humanity score Decoded from the token payload — 1 is confirmed automation, 100 a confirmed human. Your application chooses what each range means: allow, step up, redirect, or block. Keep moving your mouse or typing and watch it update: the first score is computed at page load, then refined once with a summary of how you actually interact. Human motor noise raises it — scripted precision lowers it. Refresh the page and you're back at the baseline. That's not a bug — it's the privacy guarantee. Shield keeps no profile of you, so every visit starts as a fresh, anonymous assessment. A remembered "trusted visitor" would be a cookie to track you with and a credential for bots to farm; forgetting you is what makes the score honest. — 4 Server-side validation Your server POSTs the token to siteverify and gets the verdict plus the score. Try it — then press the button again to watch the single-use protection reject the replay with timeout-or-duplicate . Run siteverify Managed mode When traffic looks suspicious You scored as a human, so verification stayed invisible. When a background attempt scores low, managed mode doesn't just block it — it asks for a single click and runs a harder proof-of-work behind it. Legitimate users tap once; scripted abuse pays a much steeper compute cost. Press the button to see exactly what that escalation looks like — a real, harder challenge is issued and solved on your click. Simulate suspicious traffic Email Verification appears here once triggered. Sign up Verified agents When automation introduces itself Not all automation is abuse — AI agents shop, book, and research for real people. Agents that sign their requests with Web Bot Auth (the IETF standard backed by OpenAI, Google, and Amazon) are cryptographically identified, so you can route them instead of fighting them. Automation that stays anonymous gets the aggressive treatment. Press the button and Shield plays both sides for real: it signs a genuine agent request with an Ed25519 key published in its own key directory, then verifies that signature through the agentverify API — the exact flow a signed agent triggers on your site. Send a signed agent request The signed request — three headers, verifiable identity POST /agentverify — the verdict Shield fetched the agent's public key from its published directory, checked the Ed25519 signature over the request, and confirmed who's calling — no user-agent trust, no IP allowlists. Run it again and a fresh single-use nonce is signed. The entire integration Everything you just saw took two lines on the page and one HTTP call on the server. Your page <script src="https://shield.edge.network/api.js" defer></script> <div class="edge-shield" data-sitekey="es_your_sitekey"></div> Your server POST https://shield.edge.network/siteverify secret=es_secret_...&response=<token> Get Your Sitekey — Free Read the Docs --- ### Edge Storage vs AWS S3 URL: https://edge.network/storage/compare/aws-s3/ Markdown: https://edge.network/storage/compare/aws-s3.md JSON: https://edge.network/json/storage/compare/aws-s3.json _Compare Edge Storage to AWS S3. S3-compatible API, lower storage costs, free reads, and zero egress fees — no data transfer bill, ever._ Storage Storage Comparison Edge vs AWS S3 A detailed comparison of Edge Storage and Amazon S3 for object storage. How we compare to AWS S3 Amazon S3 defined object storage. It's extremely durable, deeply integrated with the AWS ecosystem, and offers specialised storage classes for every access pattern — if you're willing to manage them. The catch is the bill. S3 charges for storage, for every request, and — most painfully — for egress at around $0.09/GB. The more your data is used, the more you pay. Edge Storage is S3-compatible with a simpler model: $0.013/GB stored, free reads, and zero egress fees. If you depend on tight integrations with other AWS services or need archive tiers like Glacier, S3 may still fit better. For everything else, the same API costs a fraction as much on Edge — see our pricing and the getting started guide . Key Differences Zero egress fees – S3 charges ~$0.09/GB to serve your data 43% cheaper storage – $0.013/GB vs $0.023/GB standard Free reads – S3 bills every GET request One storage class – No tiering decisions or retrieval fees Feature Comparison How Edge Storage and AWS S3 compare feature by feature. Feature Edge AWS S3 Storage Cost $0.013/GB $0.023/GB Egress Cost $0 $0.09/GB PUT/POST Requests $0.004/1K $0.005/1K GET/HEAD Requests Free $0.0004/1K S3-Compatible API Native Free Tier 5 GB, 2 buckets 12-month trial only Sign Up Without Card Edge Caching Included Extra (CloudFront) NVMe Storage Varies by class Storage Classes to Manage One 8+ Multi-Region Included Extra cost Decentralized * AWS S3 figures are Standard-class list prices in us-east-1 at the time of writing. Prices vary by region and storage class — check AWS's current pricing. Monthly Cost Comparison Real-world scenarios with typical usage patterns. Egress is where the difference explodes. Scenario Edge AWS S3 100 GB storage, 1 TB egress/mo $1.30/mo ~$92/mo 1 TB storage, 10 TB egress/mo $13/mo ~$923/mo 10 TB storage, 100 TB egress/mo $130/mo ~$9,230/mo * Estimates based on standard published pricing. Actual costs may vary. When to Choose Edge S3 is the incumbent for a reason. Here's when Edge makes more sense. You serve data to users S3's egress fee means costs scale with your success. Edge serves data at no charge — 100 TB out costs $0, not ~$9,000. You want simple pricing S3 has 8+ storage classes, retrieval fees, and per-request billing. Edge has one price for storage, one for writes, and reads are free. You already use S3 tools Edge Storage is S3-compatible, so the AWS CLI, SDKs, and existing integrations work with a change of endpoint. Migration is low-risk. Ready to try Edge? Create a free account — no card required — and get 5 GB of S3-compatible storage free. Get Started with Edge Storage View All Comparisons --- ### Edge Storage vs Backblaze B2 URL: https://edge.network/storage/compare/backblaze/ Markdown: https://edge.network/storage/compare/backblaze.md JSON: https://edge.network/json/storage/compare/backblaze.json _Compare Edge Storage to Backblaze B2. Unconditionally free egress, free reads, NVMe performance, and integrated edge caching with an S3-compatible API._ Storage Storage Comparison Edge vs Backblaze B2 A detailed comparison of Edge Storage and Backblaze B2 for object storage. How we compare to Backblaze B2 Backblaze B2 is one of the best-value object stores around. At roughly $6 per TB per month it undercuts almost everyone on raw storage cost, and it's a superb choice for backups, archives, and cold data. Credit where it's due: if you're storing a lot and downloading a little, B2 is very hard to beat. Edge Storage is built for a different job: hot data that gets served. Egress is free without conditions — B2's free egress is capped at 3x your stored data, after which per-GB charges apply. Reads are always free on Edge, storage is all-NVMe, and edge caching is included rather than routed through partner CDNs. Both offer S3-compatible APIs, so tooling works either way. Choose based on workload: B2 for cold archives, Edge for data your users actually download. See our pricing and the getting started guide . Key Differences Unconditionally free egress – B2 caps free egress at 3x your stored data Free reads, always – No transaction classes or daily allowances to track All-NVMe performance – Built for serving, not just archiving Integrated platform – CDN, compute, and DNS alongside your buckets Feature Comparison How Edge Storage and Backblaze B2 compare feature by feature. Feature Edge Backblaze B2 Storage Cost $0.013/GB $0.006/GB Egress Cost $0, unconditional Free to 3x stored, then per GB PUT/POST Requests $0.004/1K Free GET/HEAD Requests Free Free allowance, then per 10K S3-Compatible API Sign Up Without Card All-NVMe Storage Edge Caching Included Via partner CDNs Multi-Region Included Region chosen at signup Compute + CDN + DNS Platform Decentralized * Backblaze B2 figures are published list prices at the time of writing — check Backblaze's current pricing. An Honest Look at the Pricing Which is cheaper depends entirely on how your data is used. B2 wins on cold data At roughly $0.006/GB stored, B2 is less than half Edge's $0.013/GB. If you're storing backups or archives that are rarely downloaded, B2 will likely cost less overall. We'd rather tell you that than have you find out later. Edge wins on hot data Once downloads exceed 3x your stored data, B2 starts charging per GB — and content, media, and app assets routinely blow past that ratio. On Edge, egress is $0 no matter how much you serve, reads are free, and edge caching is built in. The busier your data, the further ahead Edge pulls. When to Choose Edge B2 is excellent for archives. Here's when Edge makes more sense. Your data is downloaded heavily B2's free egress stops at 3x your stored data — a problem for small datasets served often. Edge egress is free without conditions. You serve users, not archives Edge Storage runs on NVMe with integrated edge caching, built for hot data. B2 is optimised for backup and archival workloads. You want one platform B2 is storage only. Edge pairs buckets with VMs, a global CDN, and DNS under one account and one bill. Ready to try Edge? Create a free account — no card required — and get 5 GB of S3-compatible storage free. Get Started with Edge Storage View All Comparisons --- ### GPU Compute URL: https://edge.network/compute/gpus/ Markdown: https://edge.network/compute/gpus.md JSON: https://edge.network/json/compute/gpus.json _GPU-accelerated virtual machines for AI/ML, LLM inference, 3D rendering, and video transcoding. Coming soon._ Compute Compute GPU Compute Coming Soon High-performance GPU instances for machine learning, rendering, and compute-intensive workloads. Multi-vendor support coming to Edge. GPU compute is on the way We're bringing GPU instances to Edge with support for multiple vendors including NVIDIA, AMD, and Intel. Whether you need GPUs for AI inference, model training, or high-performance computing, we'll have options to fit your workload. Join the waitlist to be notified when GPU compute launches and get early access. Join the Waitlist NVIDIA GPUs AMD GPUs Intel GPUs What to Expect GPU compute on Edge will include these features. Multiple Vendors Access GPUs from NVIDIA, AMD, and Intel – choose the right hardware for your workload. Flexible Billing Pay only for what you use with hourly billing. No long-term commitments required. Edge Deployment Run GPU workloads at the edge for lower latency inference and processing. Use Cases GPU-accelerated workloads for every industry. Machine Learning Train and deploy ML models at scale LLM Inference Run large language models with low latency 3D Rendering GPU-accelerated rendering for creative workloads Video Transcoding Hardware-accelerated video processing Scientific Computing CUDA-accelerated simulations and analysis AI at the Edge Low-latency inference close to your users Need GPU compute now? Contact our team to discuss your requirements. We may be able to arrange early access or help you find an interim solution. Contact Us --- ### Private Clusters URL: https://edge.network/compute/private-clusters/ Markdown: https://edge.network/compute/private-clusters.md JSON: https://edge.network/json/compute/private-clusters.json _Dedicated compute clusters for your enterprise. Full fine-grained control via the Edge interface, CLI, and agentic API._ Compute Compute Private Clusters Dedicated compute clusters for your enterprise. Full fine-grained control via the Edge interface, CLI, and agentic API. Talk to Sales Your infrastructure, our platform A private cluster is a set of dedicated hypervisors reserved exclusively for your organisation. You get bare-metal performance with the convenience of managed cloud. 1 We provision your cluster Dedicated hypervisors deployed in your chosen location. IP pools assigned. Cluster configured and ready. 2 You deploy via Edge Create VMs from the console, CLI, or API — exactly like shared compute. Your cluster is selected automatically. 3 We manage the hardware Hardware maintenance, network uplinks, power, and cooling are all handled by Edge. You focus on your workloads. What you get Everything in shared compute, plus dedicated hardware and full isolation. Dedicated Hardware Your own hypervisors, not shared with anyone else. Full isolation for compliance, performance, and security requirements. Complete Isolation Your cluster is invisible to other customers. VMs deploy only to your hardware. No noisy neighbours, no contention. Same Interface Manage your private cluster through the same Edge console, CLI, and API. No separate tools, no learning curve. CLI & API Access Full automation via the Edge CLI and REST API. Deploy, scale, and manage infrastructure programmatically. Agentic API Let AI agents manage your infrastructure. The agentic API provides self-describing endpoints with natural language summaries. Shared IP Pools IP pools can be shared across clusters or dedicated to yours. Flexible networking to match your architecture. Built for Regulated industries Financial services, healthcare, and government workloads that require dedicated infrastructure. High-performance computing Consistent performance without contention. No noisy neighbours affecting your workloads. Data sovereignty Keep your data on hardware in a specific jurisdiction. Full control over where your VMs run. Enterprise SaaS Run your SaaS platform on dedicated infrastructure with guaranteed resources and isolation. Get a private cluster Tell us about your requirements and we'll configure a cluster for you. Most clusters are ready within 48 hours. Talk to Sales --- ### Pulse Features URL: https://edge.network/pulse/features/ Markdown: https://edge.network/pulse/features.md JSON: https://edge.network/json/pulse/features.json _HTTP, DNS, SSL, API, and Page Speed monitoring from 2,000+ residential locations. Multi-step API workflows, smart alerting, branded status pages, and real-time dashboards._ Pulse Pulse Features Six probe types, smart multi-location alerting, branded status pages, and real-time dashboards — all from residential connections your users actually use. HTTP / HTTPS Monitoring The backbone of uptime monitoring. Pulse checks your URLs from real residential connections every 30 seconds, validating not just that your server responds — but that it responds correctly. Unlike data centre probes that bypass CDN geo-restrictions and ISP-level issues, Pulse sees what a real user on a home broadband connection would see. If Cloudflare is serving a stale page to residential users in Brazil, you'll know. Capabilities GET, POST, PUT, DELETE methods Status code validation Response body content matching Custom headers and authentication Response time thresholds Redirect chain following HTTP/2 and HTTP/3 support Cookie and session handling DNS Monitoring Has your DNS change propagated to residential resolvers worldwide? Don't guess — know. Pulse resolves your domains from the same recursive resolvers your users hit, not from cloud DNS. Track propagation times, verify record accuracy, and get alerted when DNS resolution fails or returns unexpected values from any residential location. Capabilities A, AAAA, CNAME, MX, TXT, NS records Expected value validation Propagation time measurement Residential resolver testing DNSSEC validation Multi-provider comparison SSL Certificate Monitoring Expired certificates are the most preventable cause of outages. Pulse monitors your SSL certificates continuously and alerts you 30, 14, and 7 days before expiry — so renewal never catches you off guard. Beyond expiry, Pulse validates the full certificate chain, checks protocol versions, and verifies that the correct certificate is being served from every location. Capabilities Certificate expiry monitoring Chain completeness validation Issuer and subject verification Protocol version checking (TLS 1.2/1.3) Alerts 30, 14, and 7 days before expiry Wildcard and SAN certificate support API Workflow Monitoring Real APIs aren't single requests. Pulse runs multi-step workflows — authenticate, make requests, validate responses, chain data between steps — all from residential connections. Test your entire API flow the way a real client would: login, fetch data, submit a form, verify the response. If any step fails from any location, you'll know immediately. Example workflow 01 POST /auth/login → Extract token from response 02 GET /api/users/me → Validate status: 200, body contains "id" 03 POST /api/orders → Validate status: 201, response < 500ms Page Speed Monitoring Lab tests from data centres don't reflect real-world performance. Pulse measures full page load times from actual residential connections — with all the latency, DNS resolution, and ISP routing your users experience. Track TTFB, DOM ready, and full page load across every location. Spot performance regressions by ISP, region, or time of day. 142ms TTFB 0.8s DOM Ready 1.4s Full Load Measured from a residential connection in São Paulo Not from an AWS data centre Alerts that matter Multi-location confirmation eliminates false positives. When Pulse alerts you, it's real. Deliver alerts to the tools your team already uses. Email Instant email alerts with full incident context, response time data, and affected locations. Webhook POST incident data to any URL. Perfect for custom integrations, internal dashboards, or automation. Slack Rich Slack notifications with status changes, response charts, and one-click acknowledgement. PagerDuty Trigger PagerDuty incidents automatically with full context. Resolve when the check recovers. Branded status pages Give your users a professional status page at status.yourdomain.com . Branded with your logo and powered by Edge CDN + DNS, for $2/month — or use the free shared page at pulse.edge.network/yourname . Public-facing A professional, always-updated page your users can check anytime. No more "is it just me?" support tickets. Subscribable Users subscribe via email or RSS to get notified automatically when status changes. Proactive communication, zero effort. Incident history Full timeline of past incidents with duration, affected services, and resolution notes. Built-in SLA transparency. Dashboard & reporting Real-time visibility into every check, every location, every metric. Everything you need for operational awareness and SLA reporting. Uptime grid 30 and 90-day views per check, colour-coded green/amber/red. See your uptime history at a glance. Response time charts Line charts per location with p50, p95, and p99 percentiles. Spot degradation before it becomes an outage. Incident timeline Full incident history with duration, affected locations, and resolution. Exportable for SLA reporting. Global map view See probe locations and their current status on an interactive world map. Regional health at a glance. Ready to see what your users see? Start monitoring from real residential locations in under 2 minutes. 150,000 check runs free every month — no card required. Start Monitoring Free --- ### Pulse Help | Expert Monitoring Setup URL: https://edge.network/pulse/help/ Markdown: https://edge.network/pulse/help.md JSON: https://edge.network/json/pulse/help.json _Get hands-on help from Edge monitoring experts. Migration from Pingdom or Datadog, check configuration, alerting setup, and status page deployment._ Pulse Expert Services Need a hand? Let our monitoring experts set up your checks, migrate from other tools, and configure alerting that actually works. We've done this hundreds of times. How we can help Whether you're setting up monitoring for the first time or migrating from an expensive tool, our team makes it painless. Check Configuration We'll analyse your infrastructure and configure optimal checks — the right probe types, frequencies, locations, and alert thresholds for your stack. Migration from Other Tools Moving from Pingdom, Datadog, or UptimeRobot? We'll migrate all your checks, alerting rules, and status pages with zero monitoring gaps. Custom Alerting & Integrations Complex alerting requirements? We'll build custom webhook integrations, escalation policies, and notification workflows tailored to your team. Status Page Setup Get a branded, professional status page deployed on your domain in hours. Custom design, service grouping, and subscriber management included. Learn more about Expert Services Sound familiar? These are the kinds of monitoring challenges we help solve every day. We're paying too much for Pingdom / Datadog monitoring Our monitoring missed a real outage that users reported first We need to monitor APIs with multi-step authentication flows Our status page is on a separate tool and costs us extra every month We want to monitor from residential networks, not just data centres We need regional alerting — know which countries are affected Our SSL certificate expired and nobody was alerted We want to consolidate monitoring, CDN, and DNS under one provider We need monitoring but don't want per-monitor fees or plan tiers Get in touch Tell us about your monitoring needs and we'll get back to you within 24 hours with a plan. First Name Last Name Work Email Company Current Monitoring Tool Select your current tool Pingdom UptimeRobot Datadog Better Uptime StatusCake New Relic Checkly Other None / No monitoring yet How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 A monitoring expert will schedule a call to understand your requirements. 3 We'll configure your checks, alerting, and status pages — or migrate your existing setup. 4 Your monitoring is live. We'll stay on hand to fine-tune thresholds and alerting. Typical setup time Under 48 hours From first call to fully configured monitoring --- ### Pulse Pricing URL: https://edge.network/pulse/pricing/ Markdown: https://edge.network/pulse/pricing.md JSON: https://edge.network/json/pulse/pricing.json _Synthetic monitoring from 2,000+ residential locations. Pay per check run — $0.01 per 1,000 standard runs, with 150,000 free every month. No plans, no per-monitor fees._ Pulse Pulse Pricing No plans. No per-monitor fees. Pay per check run from a prepaid balance — with 150,000 standard runs free every month. Tune checks, frequency, and locations freely. Start free. Stay free if you're small. Every account gets 150,000 standard check runs free each month — enough for 3 checks at a 5-minute interval from 3 locations, with room to spare. No credit card required to sign up. When you need more, usage is deducted hourly from the same prepaid balance as Edge compute. Top up when it suits you, or enable auto top-up and forget about it. There's nothing to subscribe to and nothing to cancel. Free every month Pulse Free Allowance $0 /mo — no card required 150,000 standard check runs every month HTTP/HTTPS, TCP, ping & DNS checks Choose any probe locations Email, Slack & webhook alerts Shared status page (pulse.edge.network/yourname) 7-day data retention Start Free The rate card A check run is one probe executed from one location. That's the only unit you pay for — everything else is a flat, tiny add-on or free. Resource Price Notes Standard check runs HTTP/HTTPS, TCP, ping & DNS probes $0.01 per 1,000 runs First 150,000 runs/month free Browser check runs Headless full-page loads $1.00 per 1,000 runs Real page loads from residential connections Custom status page Your domain, your branding $2.00 per month, each Billed hourly like other add-ons Shared status page pulse.edge.network/yourname Free Included with every account Alerts Email, Slack & webhook Free Unlimited on every account Data retention: 7 days on free usage, 90 days once your account has any paid usage. View full Edge pricing What it actually costs Runs per month = checks × locations × runs per check. Here's what real setups cost with standard checks. Setup Checks Interval Locations Runs / month Monthly cost Side project 3 checks 5 min 3 77,760 $0.00 Within free allowance Startup 10 checks 1 min 3 1,296,000 ~$11.46/mo After 150k free runs Scale 30 checks 30s 5 12,960,000 ~$128.10/mo After 150k free runs Based on a 30-day month: a check runs 8,640 times at a 5-minute interval, 43,200 times at 1 minute, and 86,400 times at 30 seconds — per location. The first 150,000 standard runs each month are free; the rest are billed at $0.01 per 1,000. For example, the Startup setup: 1,296,000 − 150,000 = 1,146,000 billable runs ≈ $11.46. At this scale, comparable Datadog synthetics run roughly 70x the price. Pricing FAQ Everything you need to know about how Pulse billing works. What is a check run? One probe executed from one location. A check on a 5-minute interval running from 3 locations executes 3 runs every 5 minutes — 25,920 runs per month. Your monthly total is simply checks × locations × runs per check (8,640 per month at a 5-minute interval). What happens when my balance runs out? Your checks pause. Nothing is deleted — your configuration, history, and status pages stay in place, and checks resume automatically as soon as you top up. Enable auto top-up to avoid monitoring gaps. How does this compare to per-monitor pricing? Traditional tools charge a flat fee per monitor, regardless of how often it runs or from how many locations. Pulse only charges for the runs you actually execute, so you can tune checks, frequency, and locations freely. At scale, it works out around 70x cheaper than Datadog synthetics. How does billing work? Usage is metered and deducted hourly from the same prepaid balance you use for Edge compute and other services. There are no subscriptions to commit to — top up when you need to, with auto top-up supported. You don't need a card to start. How long is monitoring data retained? Data is retained for 7 days on free usage. Once your account has any paid usage, retention extends to 90 days. How Pulse compares The only monitoring platform that probes from real residential connections. See how we stack up. Feature Edge Pulse Pingdom UptimeRobot Datadog Probe locations 2,000+ residential ~120 data centres ~30 data centres ~70 data centres Residential IPs Check frequency 30s 1 min 30s (paid) 1 min Pricing model Per check run Plan tiers Per monitor Per test/mo Status pages Free shared, $2/mo custom $29/mo extra $7/mo extra Not included Starting price $0 (150k runs/mo free) $15/mo $0 (5 min) $5/check/mo Usage-based pricing Real user conditions Start monitoring for free 150,000 standard check runs from residential locations, unlimited alerts, and a shared status page — free every month. No credit card required. Start Free Explore Features --- ### Shield Examiner URL: https://edge.network/shield/examiner/ Markdown: https://edge.network/shield/examiner.md JSON: https://edge.network/json/shield/examiner.json _An AI review of your Shield widget's traffic: bot pressure, escalation calibration, abuse signals, and recommended thresholds — from aggregate data only, free on every widget._ Shield Shield The Examiner An AI review of your widget's traffic that turns 30 days of metrics into a plain-English assessment — what's healthy, what's under attack, what to tune — with specific fixes. Free on every widget. Run a Review Read the Docs Your security analyst, on tap Analytics tell you what happened. The Examiner tells you what it means — and what to do about it. Traffic Health Challenge volumes, solve rates, and verification patterns — explained in terms of what they mean for your site, not raw numbers. Bot Pressure How much automation is hitting the widget, whether it's declared (verified agents) or anonymous, and whether it's trending up. Escalation Calibration Whether your interactive-confirmation rate suggests genuine suspicious traffic or an over-challenged audience — VPNs, privacy browsers — and what to do about it. Abuse Signals Token replays, verification failures, score collapses, and drift anomalies — the traces real attacks leave in aggregate data. Configuration Fit Whether your widget mode, verified-agents policy, and hostname allowlist match the traffic you're actually receiving — plus recommended siteverify score thresholds. Health Score Every review produces a 0–100 health score with prioritised findings, so you can see at a glance whether anything needs attention. Three steps, a few seconds No setup, no configuration. If your widget has traffic, the Examiner has opinions. 1 Open the Examiner tab Every Shield widget has an Examiner tab in the console. 2 Run a review The analysis covers your last 30 days of traffic and takes a few seconds. 3 Apply the fixes Findings come with specific recommendations — apply them in Settings or your siteverify handling. Your last ten reviews are saved. Aggregates only. By architecture. The Examiner analyses hourly aggregate counters — challenge volumes, solve rates, score averages, abuse counts — plus your widget's configuration. Nothing else exists to analyse. Shield holds no per-visitor data, so none can be reviewed or shared. That's not a policy decision; it's how the system is built. Hourly aggregate counters Widget configuration Individual visitor data IP addresses or fingerprints Browsing history Free with every widget Run reviews as often as you like, on every widget. Like all of Shield, the Examiner is free. Get Started Examiner Docs --- ### Shield Features URL: https://edge.network/shield/features/ Markdown: https://edge.network/shield/features.md JSON: https://edge.network/json/shield/features.json _Invisible verification, a 1–100 humanity score, proof-of-work challenges in a Web Worker, and privacy by architecture. Every Edge Shield feature in detail._ Shield Shield Features Invisible verification, a humanity score your server can act on, and privacy guaranteed by architecture rather than policy — with none of the puzzles. Three widget modes Managed mode adapts to the traffic: real users verify invisibly, while suspicious traffic gets a single "I am human" click backed by a harder challenge. Non-interactive and invisible modes never ask for anything. Whatever the mode, no visitor ever labels traffic lights, transcribes text, or slides a puzzle piece. The interactive fallback is one click — and most of your users will never see it. Capabilities Managed: invisible for humans, one-click confirm for suspicious traffic Non-Interactive: background verification with a subtle status badge Invisible: no visible widget at all — verify on load or on demand Per-widget mode configuration from the dashboard Automatic token refresh before expiry Explicit JavaScript API for SPAs (render, execute, reset) Proof-of-work, not proof-of-patience Shield issues a cryptographically signed challenge that the browser solves in a background Web Worker — tens of milliseconds on a phone, invisible to the user, and free of any impact on your Core Web Vitals. Difficulty adapts to risk. A clean browser gets a trivial challenge; automation gets exponentially more expensive work. Bots pay in compute, humans pay nothing. Capabilities SHA-256 proof-of-work solved in a Web Worker Adaptive difficulty driven by risk signals The tarpit: repeat offenders get exponentially harder work — persistent bots pay in electricity Stateless, HMAC-signed challenges — built for edge delivery Headless browser and automation-framework detection Behavioural motor-noise analysis — aggregates computed in the browser, raw input never leaves the device Solve-time plausibility analysis Rotating challenges with anti-replay enforcement The humanity score Turnstile tells you pass or fail. Shield tells you how confident it is: every verification carries a 1–100 score, where 1 is confirmed automation and 100 a confirmed human. That granularity is yours to use. Auto-approve signups above 80, require email confirmation between 40 and 80, and below 40 choose what fits: block outright, or redirect legitimate automation to your API or agent endpoint. In a world where AI agents act for real customers, "not human" and "not welcome" are different things — thresholds and outcomes are tuned to your traffic, not ours. Returned on every successful siteverify call 1 = confirmed automation, 100 = confirmed human Refines as the visitor interacts — the token is re-minted with a behaviour-informed score before your server sees it Act on it: allow, step up, redirect to your API, review, or block Automation is a signal, not a verdict — good agents can be routed, not refused Average score tracked per widget in analytics Versioned feature schema — scoring improves without integration changes // siteverify response { "success" : true , "score" : 96 , "challenge_ts" : "2026-07-19T13:00:00Z" , "hostname" : "example.com" , "error-codes" : [] } 96 / 100 Confident human — auto-approve 55 / 100 Uncertain — step up to email confirmation 8 / 100 Automation — block, or redirect to your API Privacy by architecture Most verification products promise not to misuse the data they collect. Shield doesn't collect it. Signals are scored in memory during the request and discarded; the only thing that touches a disk is hourly counters. That means no cookie banners triggered by your bot protection, no data processing agreements for visitor data we don't hold, and no fingerprint database to breach. Guarantees No cookies or local storage No fingerprint database No per-visitor records — only hourly aggregate counters Signals scored in memory, then discarded Open-source client widget GDPR / CCPA friendly by default Integration & migration Built to slot into your existing stack — and to make leaving your current CAPTCHA provider a one-line change. One snippet, any stack A script tag and a div. The widget auto-renders, appends a hidden form field, and works with plain HTML, React, Vue, or any SPA. Turnstile-compatible siteverify The response body matches Turnstile's exactly — success, challenge_ts, hostname, error-codes — plus our score field. Existing server code just works. Sitekey + secret model The key model you already know from Turnstile and reCAPTCHA. Secrets are hashed at rest and shown exactly once. Hostname allowlists Lock each widget to specific hostnames. Tokens minted elsewhere fail validation automatically. WCAG 2.2 AA No puzzles means no accessibility trade-off. The rare interactive confirmation is a real button with full ARIA support and keyboard navigation. Isolated infrastructure Shield runs on dedicated infrastructure at shield.edge.network. Your verification traffic never mixes with — or depends on — anything else. Test sitekeys for CI Fixed keys that always pass, always fail, or always escalate — deterministic, network-state-free, and invisible to your analytics. Run your whole suite without a real key. Shadow (report-only) mode Trial Shield on live traffic with zero risk: nothing is ever blocked, and analytics show exactly what enforcement would have rejected or escalated. Offline verification (JWKS) Tokens are Ed25519-signed JWTs with a public key endpoint. Verify them locally with zero network calls — nobody else in the CAPTCHA space offers this. Analytics dashboard Everything you need to understand your traffic — and nothing that would compromise your visitors. Challenge metrics Issuance and solve rates per widget, hour by hour. See exactly how much traffic Shield is processing. Score distribution Average humanity score over time. A sudden drop is your early warning of a bot campaign. Block & escalation insight How often traffic was escalated to an interactive confirmation, failed verification, or attempted token replay. Shield Examiner An AI review of your traffic: bot pressure, escalation calibration, abuse signals, and recommended score thresholds — in plain English, with specific fixes. Privacy-safe by construction All analytics are hourly aggregates. There is no per-visitor drill-down because there is no per-visitor data. Bot weather report A public, anonymous view of bot pressure across the whole Shield network — see what the bots are doing right now at /shield/weather. Protection your users will never notice Add Shield to your site in under five minutes. Free forever, no credit card required. Get Your Sitekey --- ### Shield Help | Expert Integration Support URL: https://edge.network/shield/help/ Markdown: https://edge.network/shield/help.md JSON: https://edge.network/json/shield/help.json _Get hands-on help from Edge experts. Migration from Turnstile, reCAPTCHA, or hCaptcha, widget integration, humanity score tuning, and framework support._ Shield Expert Services Need a hand? Let our experts handle your migration from Turnstile, reCAPTCHA, or hCaptcha, integrate Shield into your stack, and tune the humanity score for your traffic. How we can help Whether you're adding bot protection for the first time or escaping a provider that no longer fits, our team makes it painless. Migration from Other Providers Moving from Turnstile, reCAPTCHA, or hCaptcha? We'll swap the widgets, update your server-side validation, and verify every form — with zero protection gaps. Integration Support SPAs, SSR frameworks, mobile web, multi-step forms, or custom render flows — we'll get the widget working cleanly in your stack, whatever it is. Humanity Score Tuning Not sure where to set your thresholds? We'll analyse your traffic patterns and recommend score cutoffs for auto-approve, step-up, and block that fit your risk profile. Custom Rules & Hardening Hostname allowlists, widget-per-environment setups, rate limiting strategy, and integration with your existing fraud or WAF tooling. Learn more about Expert Services Sound familiar? These are the kinds of problems that bring people to Shield. reCAPTCHA is hurting our conversion rate with image puzzles We're worried about what our CAPTCHA provider does with visitor data reCAPTCHA's 10,000 free assessments stopped being enough We want out of the Cloudflare ecosystem without losing bot protection Bots are signing up faster than we can clean them out Our accessibility audit flagged our CAPTCHA We need bot protection on a Core Web Vitals budget AI agents are legitimate customers for us — we need to route them, not block them Our privacy policy shouldn't need a section about our bot protection Get in touch Tell us about your setup and we'll get back to you within 24 hours with a plan. First Name Last Name Work Email Company Current Provider Select your current provider Cloudflare Turnstile Google reCAPTCHA hCaptcha Friendly Captcha GeeTest Custom / in-house Other None / no bot protection yet How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 An engineer will schedule a call to understand your forms, stack, and traffic. 3 We'll integrate Shield or migrate your existing provider, form by form. 4 Protection is live. We'll stay on hand to tune score thresholds as real traffic arrives. Typical migration time Under 48 hours From first call to fully protected forms --- ### Shield Pricing URL: https://edge.network/shield/pricing/ Markdown: https://edge.network/shield/pricing.md JSON: https://edge.network/json/shield/pricing.json _Edge Shield is free forever. Unlimited widgets, unlimited verifications, humanity scores, and basic analytics — no plans, no assessment caps, no credit card._ Shield Shield Pricing This is the shortest pricing page we have: Shield is free. No verification caps, no widget limits, no plans, no card. Forever. Free forever. Not free-until-you-grow. reCAPTCHA charges once you pass 10,000 assessments a month. hCaptcha holds its best detection back for enterprise. Shield's core protection — verifications, scores, all widget modes — has no caps and no paid gate, at any scale. Why? Shield is how we introduce developers to Edge. If it wins your trust for bot protection, we'd love to earn your CDN, DNS, or compute workloads too — but that's entirely optional, and Shield never requires it. Optional paid extras (advanced analytics, enterprise support) come later; the protection itself stays free. Everything included Shield Free $0 /mo — forever, no card required Unlimited widgets and sitekeys Unlimited verifications and siteverify calls 1–100 humanity score on every verification All three widget modes (managed, non-interactive, invisible) Shadow (report-only) mode for risk-free trials The tarpit — escalating proof-of-work for repeat offenders Offline token verification via public JWKS Test sitekeys for CI and local development Hostname allowlists and anti-replay protection Basic analytics dashboard (hourly aggregates) Turnstile-compatible migration Get Your Sitekey The rate card Nothing you need to protect your site costs anything. The only paid items are optional extras — and they don't exist yet. Resource Price Notes Verifications Challenges, solves & siteverify calls Free unlimited Fair-use protected against abuse of the service itself Widgets & sitekeys Per account Free unlimited Create one per site, form, or environment Humanity score 1–100 on every siteverify response Free Included — not an enterprise upsell Basic analytics Hourly challenge, solve & score metrics Free Included with every widget Advanced analytics Extended retention, exports, alerting Coming later Optional paid add-on — core protection stays free Enterprise support & SLA Dedicated support, custom rules, WAF integration Coming later Optional — contact us if you need this now View full Edge pricing Free, compared "Free" means different things to different providers. Here's what it means for each. Feature Edge Shield Turnstile reCAPTCHA hCaptcha Price Free, unlimited Free (10 widgets) Free to 10k/mo, then paid Free tier, paid pro Confidence score 1–100 on every call 0.0–1.0 (v3) Enterprise only Visual puzzles Never Never Yes (v2 fallback) Yes Ad-tech tracking Per-visitor data stored Open-source widget Competitor details based on publicly listed plans and may change — see the full comparison . Pricing FAQ The questions everyone asks about a free product. Is it really free? What's the catch? Core protection is free forever, with no verification caps. Shield exists to introduce developers to Edge — we monetise optional extras later (advanced analytics, enterprise support, WAF integration), never the protection itself. Do I need a credit card? No. Create an account, create a widget, and you have a sitekey and secret. There is nothing to subscribe to and nothing that expires. Are there rate limits? Only abuse protection on the service itself — generous per-IP limits that legitimate websites will never encounter. There are no monthly assessment quotas like reCAPTCHA's 10,000-call cap. How does this compare to Turnstile? Turnstile is also free, but it doesn't expose a confidence score and it ties you into the Cloudflare ecosystem. Shield gives you a 1–100 humanity score on every verification, runs on independent infrastructure, and is a drop-in replacement — same siteverify response shape. What happens if my site gets a traffic spike? Nothing — that's the point. Shield runs on dedicated Edge infrastructure built for unbounded public traffic, and challenges are stateless so they scale horizontally. Your bill stays at zero either way. The price is zero. The setup is five minutes. Unlimited bot protection with a humanity score on every verification. No card, no caps, no catch. Get Started Free Explore Features --- ### Smart Routing | Edge CDN URL: https://edge.network/cdn/smart-routing/ Markdown: https://edge.network/cdn/smart-routing.md JSON: https://edge.network/json/cdn/smart-routing.json _Intelligent traffic routing optimises every request. Global optimization, real-time health monitoring, and automatic failover._ CDN CDN Smart Routing Intelligent request routing that finds the fastest path to your origin, bypassing Internet congestion and failures automatically. Faster than the Internet The public Internet is unpredictable. Packets get lost, routes get congested, and latency spikes happen constantly. Smart Routing uses our optimized network to bypass these issues. ✓ Real-time network monitoring across all paths ✓ Automatic failover in under 1 second ✓ 30% average latency reduction to origin Key Capabilities Intelligent routing features that optimize every request. Global Optimization Optimized routes between all 988 edge locations and your origin. Instant Failover Automatic rerouting when network issues are detected. Origin Protection Reduced load on your origin with optimized connection pooling. The Difference See how Smart Routing transforms your origin connectivity. Without Smart Routing ✗ Unpredictable latency ✗ Packet loss during congestion ✗ Slow failover on network issues ✗ Higher origin load With Smart Routing ✓ Consistent sub-50ms origin fetches ✓ Zero packet loss on our network ✓ Instant failover (<1 second) ✓ Connection pooling reduces origin load Enable Smart Routing Included with all CDN plans at no extra cost. Get Started --- ### Storage URL: https://edge.network/storage/ Markdown: https://edge.network/storage.md JSON: https://edge.network/json/storage.json _Simple object storage without egress fees. Global distribution, high durability, and straightforward pricing._ Storage Storage Object storage without egress fees Store and serve unlimited data from the edge. A clean, modern API that just works – no complexity, no bandwidth surprises. Create Your First Bucket Free to sign up. Complete setup in 2 minutes. $0 egress fees. Forever. We never charge for bandwidth out. Store your data and serve it globally without worrying about surprise bills. $0 Egress Fees 99.99% Durability 50+ Edge Locations <50ms Global Latency Storage built for the modern web Everything you need to store, manage, and deliver content at scale. Dead Simple API A clean REST API that makes sense. Great SDKs for every language. No 200-page spec required. Edge Delivery Content is automatically cached and served from the nearest edge location. Instant Access No cold storage tiers or retrieval delays. All data is instantly accessible. Encrypted at Rest AES-256 encryption for all stored data. Your content is always protected. Versioning Automatic version history for all objects. Restore previous versions anytime. Access Control Fine-grained permissions with signed URLs and simple access rules. Simple, predictable pricing Pay only for what you store. Egress is always free. Storage $0.02 /GB/mo 5 GB free tier included No minimum commitment Pay as you go Egress $0 /GB Unlimited bandwidth No hidden fees Serve globally free Operations $0.004 /1K requests PUT, COPY, POST, LIST GET/HEAD free DELETE free View full pricing Perfect for Scalable object storage for any workload. Static Assets Media Files Backups Data Lakes User Uploads CDN Origins Archives Logs Guides & resources Get started with S3-compatible object storage on Edge. Getting started Create your first bucket, generate access keys, and upload objects in minutes. Video: storage basics A walkthrough of buckets, keys, and the S3-compatible API on Edge. Storage security How decentralisation changes the security model for cloud storage. Ready to store without limits? Create your first bucket in seconds. Free tier included — no charge, ever, without your explicit opt-in. Get Started Free --- ### Storage Features URL: https://edge.network/storage/features/ Markdown: https://edge.network/storage/features.md JSON: https://edge.network/json/storage/features.json _Simple API, global replication, image transformations, and zero egress fees. Explore all Edge Storage features._ Storage Storage Storage Features Enterprise object storage with the simplicity you expect from modern cloud infrastructure. Core Features Everything you need for enterprise-grade object storage. Simple API A clean, modern API that's easy to use. Works with popular SDKs, CLI tools, and applications. Global Edge Delivery Objects are automatically replicated and served from the nearest edge location for minimal latency. Instant Access No storage classes or retrieval delays. All your data is hot and instantly accessible. AES-256 Encryption All data encrypted at rest with AES-256. Optional client-side encryption for additional security. Object Versioning Enable versioning to keep a history of all object versions. Restore or delete any version. Signed URLs Generate time-limited signed URLs for secure, temporary access to private objects. Image Optimization On-the-fly image resizing, format conversion, and optimization. Serve WebP automatically. Static Site Hosting Host static websites directly from buckets. Custom domains and SSL included. Terraform & CLI Full Terraform provider and dedicated CLI for infrastructure as code workflows. Lifecycle Rules Automate object transitions and expiration with configurable lifecycle policies. Usage Analytics Real-time dashboards for storage usage, requests, and bandwidth consumption. Multipart Uploads Efficient uploads for large files. Resume interrupted uploads automatically. Compatible Tools Works with all your favorite tools and libraries. AWS CLI boto3 s3cmd rclone Cyberduck MinIO Client Terraform CloudBerry And so much more Every feature you need, included as standard. CORS configuration Custom metadata Object tagging Pre-signed POST Cross-region replication Event notifications Webhooks Access logs Immutable buckets Legal holds Retention policies Access controls Ready to get started? Create your first bucket in under a minute. Start Free Today --- ### Storage Help | Expert Services URL: https://edge.network/storage/help/ Markdown: https://edge.network/storage/help.md JSON: https://edge.network/json/storage/help.json _Get hands-on help from Edge experts to set up and optimise your object storage. Migration support, architecture design, and custom configuration._ Storage Expert Services Need a hand? Let our team of storage experts help you design, migrate, and optimise your object storage. From simple buckets to complex multi-region setups, we've got you covered. How we can help Our expert services team has helped hundreds of companies optimise their storage infrastructure. Whatever your challenge, we've probably solved it before. Storage Architecture We'll design a storage solution optimised for your workload—whether it's high-throughput media, backup and archival, or real-time data access. Migration Support Moving from S3, GCS, or Azure Blob? Our team handles the entire migration, preserving your data integrity and access patterns. Custom Configuration Complex access policies, lifecycle rules, or replication requirements? We'll configure everything to your exact specifications. Rapid Deployment Get your storage running fast. Our experts can have your buckets configured and data migrating within hours. Learn more about Expert Services Sound familiar? These are the kinds of challenges we help solve every day. Our S3 bills are out of control We need to migrate terabytes of data safely Our storage access is too slow for users We need multi-region replication Our backup strategy needs an overhaul We want to reduce egress costs We need better access control policies Our media assets need faster delivery We want to consolidate storage providers Get in touch Tell us about your project and we'll get back to you within 24 hours with a plan of action. First Name Last Name Work Email Company Current Storage Provider Select your current provider AWS S3 Google Cloud Storage Azure Blob Storage DigitalOcean Spaces Backblaze B2 Wasabi Cloudflare R2 Other None / Self-hosted How can we help? Request Assistance Prefer a quick chat? Email us directly at experts@edge.network What happens next? 1 We'll review your submission and get back to you within 24 hours. 2 A storage expert will schedule a call to understand your requirements in detail. 3 We'll provide a tailored proposal with timeline and pricing. 4 Once approved, our team gets to work immediately. Trusted by --- ### Storage Pricing URL: https://edge.network/storage/pricing/ Markdown: https://edge.network/storage/pricing.md JSON: https://edge.network/json/storage/pricing.json _S3-compatible object storage on NVMe with a free tier — 2 buckets and 5 GB — then $0.015/GB-month pay-as-you-go. Zero egress fees at every scale, never billed silently._ Storage Storage Pricing S3-compatible object storage on NVMe with a free tier to start and zero egress fees at every scale. Hard-capped by default — it never silently starts billing. Start free, on real hardware The free tier runs on the same all-NVMe infrastructure as everything else — the full S3-compatible API with presigned URLs, multipart uploads, and access keys included. Without a card on file, hitting the 5 GB cap blocks writes rather than starting a bill — your existing objects stay readable. Paid usage only ever happens once you've added a card. Beyond the free tier $0.015 per GB per month With a card on file, pay-as-you-go keeps you writing past 5 GB automatically. Overage is prorated hourly from your prepaid balance — add an optional monthly cap if you want a hard ceiling — and writes pause again if the headroom runs out, never a surprise bill. Egress stays free. Free tier Storage Free Tier $0 /mo — billed only beyond the free tier 2 buckets 5 GB storage S3-compatible API Zero egress fees All NVMe hardware Presigned URLs Any S3 SDK you already use Create a Bucket Storage pricing at a glance Item Price Detail Free tier $0 2 buckets, 5 GB on NVMe, full S3-compatible API Storage beyond free tier $0.015 per GB-month Prorated hourly from prepaid balance Egress / downloads $0 Free at every scale API requests $0 No per-request charges Enterprise volume Custom Per-GB volume pricing, 99.99% SLA, account manager All prices in USD, identical in every region. What would your bill be? Slide in your workload. Downloads are where storage bills hide — and where Edge charges nothing. Storage Total data stored GB Downloads per month Data served or retrieved (egress) GB Reads per month GET requests million Writes per month PUT / POST requests million Edge Storage $3.67 /mo 5 GB free, then 245 GB × $0.015/GB. Downloads and requests are free at any volume. Paid usage is opt-in: set a monthly budget on the billing page, billed hourly from prepaid balance. The same workload elsewhere AWS S3 $5.75 storage + $36 egress + $9.00 requests $51 /mo Google Cloud Storage $5.00 storage + $60 egress + $9.00 requests $74 /mo Cloudflare R2 $3.60 storage + $0 egress + $0 requests $3.60 /mo $47 /month saved vs AWS S3 — 93 % less. Published standard on-demand rates: storage, egress, and per-request operations. Permanent free allowances are credited (AWS 100 GB/month transfer; R2 10 GB storage, 10M reads and 1M writes/month); time-limited promotional tiers are not. Edge charges nothing for egress or requests. Your data. Free to leave. Egress is where object storage bills hide their cost — retrieving a terabyte from S3 costs around $90. From Edge Storage it costs nothing, at any scale. Zero egress fees Serve public files, restore backups, or migrate away entirely — data transfer out is always included. All NVMe No spinning disks and no archive-tier retrieval delays. Every object is on NVMe and served at full speed. Volume pricing at scale Enterprise volume pay-as-you-go from $499/month with per-GB volume pricing, a 99.99% SLA, and an account manager. See how we compare to S3 Pricing FAQ Everything you need to know about how storage billing works. How does the free tier work? Every account gets 2 buckets and 5 GB of NVMe-backed, S3-compatible storage. A card on file is required, but the free tier never charges — it's sized to evaluate with a real workload. What happens at the 5 GB cap? With a card on file, pay-as-you-go covers it automatically: writes continue at $0.015/GB-month, prorated hourly from your prepaid balance (add an optional monthly cap for a hard ceiling). Without a card, writes are blocked — never billed silently — and your existing objects stay readable and served. Are downloads really free? Yes. There are no egress fees at any scale, which is where S3 bills hurt most — retrieving your own data from Edge Storage costs nothing, whether it's a backup restore or public file serving. Is it actually S3-compatible? Yes — the API speaks S3, so the AWS SDKs, rclone, s3cmd, and existing tooling work by changing the endpoint and keys. Presigned URLs and multipart uploads are supported. What if I need more than the free tier? Enterprise volume pay-as-you-go covers storage at scale with per-GB volume pricing, a 99.99% SLA, and an account manager. Talk to us about your workload and we'll price it precisely. Create your first bucket free S3-compatible, all NVMe, zero egress. Point your existing SDK at Edge and go. Get Started View SDK Examples --- ### Storage Regions URL: https://edge.network/storage/regions/ Markdown: https://edge.network/storage/regions.md JSON: https://edge.network/json/storage/regions.json _Store data across 20 global regions with automatic replication. High durability and low latency worldwide._ Storage Storage Global Storage Regions Store your data close to your users. 20 regions across 5 continents with automatic edge caching worldwide. How Edge Storage Works Simple, powerful, globally distributed. 1 Choose Primary Region Select the region closest to your application or users for writes. 2 Automatic Replication Data is automatically replicated for durability and availability. 3 Edge Caching Frequently accessed objects cached at 50+ edge locations globally. Available Regions Choose from 20 regions across 5 continents. North America 6 regions <30ms avg latency New York us-east-1 Los Angeles us-west-1 Chicago us-central-1 Dallas us-south-1 Toronto ca-east-1 Seattle us-west-2 Europe 5 regions <35ms avg latency London eu-west-1 Frankfurt eu-central-1 Amsterdam eu-west-2 Paris eu-west-3 Stockholm eu-north-1 Asia Pacific 5 regions <40ms avg latency Singapore ap-southeast-1 Tokyo ap-northeast-1 Sydney ap-southeast-2 Mumbai ap-south-1 Seoul ap-northeast-2 Latin America 2 regions <45ms avg latency São Paulo sa-east-1 Mexico City mx-central-1 Middle East & Africa 2 regions <50ms avg latency Dubai me-south-1 Johannesburg af-south-1 Global Durability & Availability Enterprise-grade reliability built in. 99.99% durability across all regions Automatic cross-region replication 99.9% availability SLA Geographic redundancy included No additional replication costs Instant failover between regions Edge caching at 50+ locations Data residency controls Store globally, serve instantly Pick your region and start storing. Global delivery included. Get Started Free --- ## Solutions ### Agentic Development URL: https://edge.network/solutions/agentic-development/ Markdown: https://edge.network/solutions/agentic-development.md JSON: https://edge.network/json/solutions/agentic-development.json _The first cloud platform built for AI agents. Give your coding assistant one access code and it deploys, manages, and monitors your infrastructure — free to start, no card required._ Agentic Development Your AI agent deploys your app The first cloud platform with an API designed for AI agents. Give your coding assistant one access code and let it handle deployment, DNS, SSL, and monitoring — while you keep building. Start Free — No Card Required Explore the Agent API Free account, $5 starter credit, and an agent code in under two minutes — or skip signup entirely with the one-line MCP setup . Cursor Agent # You say: "Deploy my React app to portfolio.example.com" # Agent connects to Edge GET /agent → 5 products, $47.20 remaining # Agent deploys ✓ Storage bucket created ✓ 12 files uploaded ✓ CDN deployment configured ✓ DNS CNAME added ✓ SSL certificate issued ✓ Contact form protected with Edge Shield # Agent reports back: "Your portfolio is live at https://portfolio.example.com with CDN, automatic SSL, and bot protection on the contact form. Estimated cost: ~$2.80/month." Deployment shouldn't break your flow You build an app with your AI assistant in minutes. Then deployment kills your momentum. Without Edge Agent API 0:00 App built. Time to deploy. 0:05 Leave editor. Open hosting provider dashboard. 0:12 Create project, configure build settings, upload files. 0:20 Switch to DNS provider. Add CNAME record. Wait for propagation. 0:30 SSL not working. Debug certificate issuance. Retry. 0:45 Finally live. Context completely lost. What were you building? With Edge Agent API 0:00 App built. "Deploy this to portfolio.example.com" 0:03 Agent creates storage bucket, uploads files. 0:08 Agent configures CDN, adds DNS record, triggers SSL. 0:15 "Your site is live at https://portfolio.example.com with CDN and SSL. ~$2.80/month." 0:16 You keep building. Flow unbroken. 45 minutes → 15 seconds. Never leave your editor. One paste to production Deploy without leaving your editor No SDK to install, no dashboard to learn. Create a free account, generate a scoped agent code, and hand it to Cursor, Claude Code, Windsurf — whatever you already use. Paste this, and your agent discovers the platform and ships your app. Get Your Agent Code — Free See the API Paste into your AI assistant Copy You can deploy to Edge Network. Here's my agent access code: ea_live_YOUR_CODE Read https://edge.network/agent to discover what you can do, then deploy this app: put static assets on Edge Storage, front them with the CDN, add the DNS record for app.mysite.com, and issue SSL. Report the live URL and the estimated monthly cost when you're done. Official MCP server One line of config. 22 tools in your editor. Prefer MCP over raw HTTP? Add one entry to your tool's config and Cursor, Windsurf, Claude Desktop, or Continue gets native Edge tools — deploy a site, provision a VM, manage DNS, check project health — with no SDK and nothing else to install. Zero-friction start — no access code? The server self-signs-up for a free explore account. No card, no dashboard visit. Remote option — hosted agents can skip npx and POST straight to https://edge.network/mcp Framework wrappers — LangChain, LlamaIndex, CrewAI, and Vercel AI SDK packages for agents you build yourself Connect Your Tool .cursor/mcp.json Copy { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"] } } } # That's it. Then just ask: "Deploy this folder to Edge and give me the URL." Built for How Agents Think Not a standard API with agent wrappers. Designed from the ground up for LLM interaction patterns. Discovery-First API Your agent calls one endpoint and learns everything — available products, current limits, existing resources, and budget. No documentation crawling needed. Budget-Aware by Default Every response includes cost context. Set soft or hard monthly caps so your agent operates within your limits without surprises. Human-Readable Responses Every API response includes a tell_user field — a plain English summary your agent can relay directly to you. Dry Run Everything Preview any action before committing. Your agent can show you exactly what would happen and what it would cost. Project-Based Resources Group VM + CDN + Storage + DNS into a project. Health check, scale, or teardown everything for an app in one call. Errors as Guidance When something goes wrong, the API tells your agent exactly what to do — and what to tell you. How It Works From access code to live app in five steps. 1 Create your free account Sign up in under two minutes — no card required, with a $5 starter credit to deploy against. 2 Generate a scoped agent code Choose the products, permissions, and budget the agent can use. Revoke it any time. 3 Give it to your agent Add the one-line MCP config to Cursor, Windsurf, Claude Desktop, or Continue — or just hand the code and the URL https://edge.network/agent to any assistant. No SDK to install. 4 Agent discovers and deploys One API call reveals everything it can do; then it creates storage, configures CDN, sets up DNS, issues SSL, and reports the live URL. 5 Agent monitors and reports Ask how things are going. It checks health, tracks spend against your cap, and suggests optimisations. Works with Any AI Coding Tool The Agent API is a standard REST API. Any tool that can make HTTP requests — AI assistant, CI/CD pipeline, custom script — can use it. No SDK required, no vendor lock-in. AI Coding Assistants Cursor, Windsurf, Cline, Aider, Claude Code — one-line MCP setup, or any agent that can make API calls CI/CD Pipelines GitHub Actions, GitLab CI, Jenkins — automate deployments with agent codes in your pipeline Custom Agents, MCP & Scripts Official MCP server (local via npx or hosted at edge.network/mcp), LangChain / LlamaIndex / CrewAI wrappers, or a simple curl command — if it speaks HTTP, it works # curl $ curl https://edge.network/agent \ -H "Authorization: Bearer ea_live_..." # Python requests.get("https://edge.network/agent", headers={"Authorization": "Bearer ea_live_..."}) # JavaScript fetch("https://edge.network/agent", { headers: { Authorization: "Bearer ea_live_..." } }) # Or just tell your AI assistant: "Here's my Edge agent code: ea_live_... Deploy my app to mysite.com" You Stay in Control Agent access codes give you fine-grained control over what your agent can do. Set it and forget it — or adjust permissions as your project evolves. Scoped Permissions Choose which products and actions each agent can access Budget Caps Soft caps warn, hard caps block — you choose the enforcement level Full Audit Trail Every action taken by every agent is logged and traceable Instant Revocation Revoke any agent code immediately — access stops instantly Agent Code Configuration Name Cursor - Personal Projects Products Compute CDN Storage DNS Shield Permissions Deploy Manage Delete Budget Cap $50/month Soft cap Ready to let your agent build? Create a free account, generate an agent code, and start deploying in seconds. No card required. Start Free Read the Docs --- ### AI & Machine Learning Infrastructure URL: https://edge.network/solutions/ai/ Markdown: https://edge.network/solutions/ai.md JSON: https://edge.network/json/solutions/ai.json _Machine learning infrastructure at the edge. GPU compute for training and low-latency inference — run LLMs on distributed GPUs with zero egress fees._ AI & Machine Learning Inference is better at the edge Run LLMs and SLMs on distributed GPU infrastructure. Low-latency inference, cost-effective training, and global scale. Get Started View GPU Pricing Purpose-Built for AI Workloads Infrastructure designed from the ground up for machine learning. GPU Compute at the Edge NVIDIA GPUs deployed globally for low-latency inference. Run models closer to your users. Model Hosting Deploy and scale ML models with automatic load balancing and version management. Sub-100ms Inference Edge deployment means faster responses. Critical for real-time AI applications. Global Distribution Serve AI workloads from 60+ locations. Automatic routing to the nearest GPU cluster. Flexible Infrastructure From shared GPUs to dedicated clusters. Scale compute up or down as demand changes. Cost-Effective Training Access GPU compute at a fraction of hyperscaler prices. No egress fees for model deployment. Built for Every AI Use Case Real-Time Inference Deploy models for instant predictions – image recognition, NLP, recommendations. LLM Applications Host and serve large language models with low latency and high throughput. Computer Vision Process video and images at the edge for surveillance, quality control, and more. Training Workloads Access affordable GPU compute for model training and fine-tuning. Why Edge for AI? Traditional cloud providers charge premium prices for GPU compute and add steep egress fees. Edge offers a better way. Up to 60% lower GPU costs vs. hyperscalers Zero egress fees for model deployment Global edge locations for low-latency inference Simple, predictable pricing No long-term commitments required Example Savings A100 GPU Instance AWS p4d.24xlarge $32.77/hr Google Cloud a2-highgpu-8g $29.39/hr Edge GPU Compute $12.00/hr View full GPU pricing Machine learning infrastructure, without the hyperscaler premium Most ML infrastructure lives in a handful of centralised regions. That works for batch training, but it breaks down for inference: every request pays a round trip to a distant data centre, and every response pays egress fees on the way out. Running models at the edge — on GPU compute distributed close to your users — cuts both the latency and the bill. Edge provides the full stack: GPU instances for training and fine-tuning, low-latency inference close to users, S3-compatible object storage for models and datasets with zero egress fees, and a global CDN for serving results. Deploy open models in minutes with our ready-made stacks for Ollama , vLLM , llama.cpp and ComfyUI . New to the topic? Start with our guide to machine learning at the edge . Ready to deploy AI at the edge? Get started with GPU compute today. No commitment, pay only for what you use. Get Started Talk to an Expert --- ### Craft CMS Hosting URL: https://edge.network/solutions/craft/ Markdown: https://edge.network/solutions/craft.md JSON: https://edge.network/json/solutions/craft.json _Craft CMS hosting on Edge — production VMs with PHP-FPM, S3-compatible asset volumes via the AWS adapter, on-the-fly image transforms and a global CDN with zero egress fees._ For Craft CMS Craft CMS hosting, production-grade and predictable Hosting for the premium PHP CMS, built for design-led teams: real VMs with S3-compatible asset volumes and a global CDN. Servd-class infrastructure at a fraction of the cost. Start free For agencies # config/filesystems.php — S3 volume return [ [ 'type' => craft\awss3\Fs::class, 'handle' => 'edgeAssets', 'name' => 'Edge Assets', 'settings' => [ 'endpoint' => '$EDGE_ENDPOINT', 'bucket' => 'craft-assets', ], ], ]; # Provision and apply $ edge compute create --plan small ... $ php craft up Why Craft teams pick Edge Pixel & Tonic-recommended hosting characteristics, at agency-friendly prices. Real PHP, real performance Dedicated CPU, NVMe storage, OPCache tuned for Yii — the hosting story Pixel & Tonic actually recommend, on infrastructure that doesn't bill per page-view. S3 asset volumes Use the official `craftcms/aws-s3` adapter pointing at Edge Storage. Local volumes for dev, S3-backed volumes for production — same Craft setup either way. Image transforms, two ways Craft's native transforms work great. For high-traffic sites, point your asset URLs at Edge Image Optimization for AVIF/WebP at the CDN. Global CDN, zero egress Front the front-end through the Edge CDN. Logged-in editors hit origin; the world reads from cache. No egress fees on any of it. MySQL or Postgres Run on the same VM for cost, separate VMs for scale, or your existing managed provider. Craft is happy with all three. Project Config + Composer flow Standard Craft deploy: pull, `composer install`, `php craft up`, restart. Wrap it in a CI step or Envoyer/Forge — both work pointed at an Edge VM. Reference architecture How Craft maps to Edge Standard LEMP stack with S3-backed asset volumes and the global CDN out front. Boring, fast, predictable. Compute Runs Craft + Nginx + PHP-FPM on a VM, with MySQL or Postgres Storage S3-compatible bucket for asset volumes CDN Caches the front-end and asset URLs globally Image Optimization On-the-fly variants from Craft asset URLs DNS Anycast DNS for the apex, www and any subsite domains Shield Protects contact and entry forms from spam without hurting UX — free Assist Answers visitor questions from your entries — one script tag, on brand # Twig template — Craft asset → Edge Image URL <img src="https://cdn.example.com/{{ asset.path }}?w=1200&fm=webp" srcset="https://cdn.example.com/{{ asset.path }}?w=800&fm=webp 800w, https://cdn.example.com/{{ asset.path }}?w=1600&fm=webp 1600w" alt="{{ asset.title }}" > # Or use native transforms {{ asset.getUrl({ width: 1200, format: 'webp' }) }} Common questions Craft 4 or Craft 5? Both work. Craft 5 (PHP 8.2+) is a clean fit for a fresh Edge VM. The bootstrap script installs Composer, the right PHP version and `php craft up` runs migrations on first boot. Can I keep using Forge or Envoyer? Yes — both can target an Edge VM by IP. We provision the box, they handle the deploy pipeline. Or use the Edge CLI to script the same workflow if you'd rather skip the third party. How does this compare to Servd / Cloudways? Cheaper, faster, you keep root. The trade-off is a bootstrap script (or Forge/Envoyer) to manage the OS — or our Expert Services team can run it for you. What about Craft Commerce? Runs identically — same PHP/MySQL stack, same S3 asset volumes for product imagery. The CDN handles catalogue traffic; checkout falls through to your origin VM. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Protects contact and entry forms from spam without hurting a design-led UX. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers visitor questions from your entries — on brand, one script tag. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Strapi The leading open-source headless CMS Directus Instant API over any SQL database Payload TypeScript-first headless CMS, Next.js-ready WooCommerce Self-host the world's most popular store Ship Craft on Edge Start free. Bring an existing Craft site or scaffold a new one — agency-friendly pricing all the way up. Start free Talk to an engineer --- ### Deploy Astro on Edge | Content-first sites at the edge URL: https://edge.network/solutions/astro/ Markdown: https://edge.network/solutions/astro.md JSON: https://edge.network/json/solutions/astro.json _Deploy Astro static and SSR sites to Edge — global CDN with zero egress, S3-compatible storage for assets and on-the-fly image optimisation._ For Astro Astro sites, edge-delivered Build with Astro, serve from Edge. A global CDN with zero egress fees, S3-compatible storage for assets and a small VM for SSR when you need it. (We use this stack ourselves.) Start free Read the deploy guide # Build the site $ astro build # Sync to Edge Storage $ aws s3 sync ./dist s3://my-site \ --endpoint https://storage.edge.run # Front it with the CDN $ edge cdn create example.com \ --origin s3://my-site # Purge on every deploy $ edge cdn purge example.com ✓ Live, globally cached Why Astro teams pick Edge We built our own marketing site with this exact stack — so we know the deploy story works at speed and at scale. Static-first delivery Build to `dist/`, push to Edge Storage, front it with the global CDN. Most pages never touch a server — and they fly. SSR when you need it Run Astro's Node adapter on a small VM for dynamic routes. Static pages stay on the CDN, dynamic ones fall through to your origin. Image optimisation, included Use Astro's `<Image />` with our URL-based optimiser. Resize, crop, AVIF/WebP — at the CDN, no per-image fees. Asset storage that scales S3-compatible Edge Storage for media, downloads and content imports. The same bucket the CDN serves from. CI-friendly deploys Build in GitHub Actions, sync to Storage with the AWS CLI, purge the CDN. A handful of YAML, no platform lock-in. Built on Astro ourselves edge.network runs on Astro, hosted on Edge. We test our docs, blog and marketing on the same stack we sell. Reference architecture How Astro maps to Edge For a static-only site you don't even need a VM — just a bucket and a CDN deployment. Add Compute later if and when you need SSR. Storage Holds the built `dist/` bundle and any uploaded media CDN Serves the entire static build with zero egress fees Compute Optional: runs Astro's Node adapter for SSR routes Image Optimization Powers `<Image />` with on-the-fly transforms DNS Anycast DNS for the apex, www and preview branches Shield Guards newsletter and contact forms without a CAPTCHA bundle — free Assist AI answers drawn from your content-first pages — one script tag # .github/workflows/deploy.yml - run: npm ci && npm run build - run: | aws s3 sync dist s3://$BUCKET \ --endpoint $EDGE_ENDPOINT \ --delete --cache-control max-age=31536000 - run: | curl -X POST $EDGE_API/cdn/deployments/$ID/purge \ -H "Authorization: Bearer $TOKEN" Common questions Static-only or SSR? Either. Pure static sites need only a Storage bucket and a CDN deployment. SSR sites add a small VM running Astro's Node adapter — the CDN still handles all the static work. How do I deploy from CI? Build in your CI of choice, then `aws s3 sync ./dist s3://your-bucket --endpoint https://...` and trigger a CDN purge via the Edge API. We have ready-made GitHub Actions snippets. Does Astro's `<Image />` work? Yes — point Astro at our image optimisation service via a custom service / loader. You get the same component API, with transforms happening at the CDN. Can I host previews per branch? Yes. Push each branch build to a `branch-name/` prefix in Storage, alias a `branch.preview.example.com` subdomain to it via DNS + CDN. Tear it down on PR close. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Guard newsletter and contact forms without shipping a CAPTCHA bundle to your content-first pages. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Content-first sites are Assist’s home turf: it answers from the pages Astro already renders. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Laravel Production VMs, S3 storage and CDN Django Python web apps, no surprise bills Rails Classic VPS workflow, modern network The site you're reading runs on this Astro on Edge — built, deployed and delivered with the exact stack on this page. Try it. Start free Talk to an engineer --- ### Deploy Django on Edge | Python web apps without surprise bills URL: https://edge.network/solutions/django/ Markdown: https://edge.network/solutions/django.md JSON: https://edge.network/json/solutions/django.json _Run Django on Edge — Gunicorn or Uvicorn on real VMs, S3-compatible storage for static and media, global CDN with zero egress fees._ For Django Django hosting, done properly Real VMs for Gunicorn or Uvicorn, S3-compatible storage for media, global CDN with zero egress fees. The classic Django deployment — wired up the way you'd wire it yourself, but quicker. Start free Read the deploy guide # settings.py DEFAULT_FILE_STORAGE = 'storages.backends.s3.S3Storage' STATICFILES_STORAGE = 'storages.backends.s3.S3Storage' AWS_S3_ENDPOINT_URL = 'https://storage.edge.run' AWS_STORAGE_BUCKET_NAME = 'media' # Provision the VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-django.sh # CDN out front $ edge cdn create app.example.com \ --origin https://<vm-ip> Why Django teams pick Edge PaaS-style simplicity, VPS-style price, no proprietary buildpacks. Gunicorn / Uvicorn on real VMs Run any WSGI or ASGI server (Gunicorn, Uvicorn, Granian, Daphne) on a sized-to-fit VM. Predictable RAM and CPU. S3 storage backend Wire `django-storages` to Edge Storage and use it as the default for `MEDIA_ROOT` and `STATIC_ROOT`. Works exactly like AWS S3. PostgreSQL on the same network Run Postgres on the same VM, a separate VM, or your existing managed provider. Low-latency, no egress fees between Edge resources. On-the-fly image transforms Skip the `sorl-thumbnail` queues — generate responsive variants from a URL via Edge Image Optimization. Global CDN, zero egress Front collected static and media files through the CDN. Massive cache hit rates on the things your users actually load. Agentic deployments Tell the Edge agent to deploy your Django app to a domain — it provisions the VM, sets up DNS and adds the CDN. Reference architecture How Django maps to Edge Standard WSGI/ASGI on a VM, media in object storage, CDN out front. Compute Runs Gunicorn (WSGI) or Uvicorn (ASGI) behind Nginx/Caddy Storage Backs `django-storages` for `STATICFILES_STORAGE` and `DEFAULT_FILE_STORAGE` CDN Caches `/static/` and `/media/` URLs globally Image Optimization On-the-fly thumbnails, AVIF/WebP, smart cropping DNS Anycast DNS for the apex, www and admin subdomains Shield Free bot protection for auth and contact forms — validated with one HTTP call Assist AI answers from your site content — one template include # /etc/systemd/system/django.service [Service] WorkingDirectory=/srv/app ExecStart=/srv/app/.venv/bin/gunicorn \ myproject.wsgi:application \ --workers 4 --bind 127.0.0.1:8000 Restart=always [Install] WantedBy=multi-user.target Common questions WSGI or ASGI? Either. Gunicorn for classic Django, Uvicorn or Daphne for ASGI/Channels. Both run as standard Python processes on an Edge VM behind a reverse proxy. Where does Postgres go? For small to medium loads, run it on the same VM. For larger loads, give it its own VM (private network keeps the latency low) — or point Django at your existing managed Postgres provider. How do I deploy? Standard `git pull` + `pip install` + `manage.py migrate` + `manage.py collectstatic` + restart. Wrap it in a CI step or systemd path unit. How does this compare to PaaS like Heroku? Cheaper, faster (real CPU and disk), and you keep control of the full Python environment. The trade-off is one bootstrap script — and we provide a sensible starter. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Validate the humanity score in a form view with one requests call. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers One template include gives your site an AI answer box grounded in your content. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Rails Classic VPS workflow, modern network Node.js Express, Fastify, Hono — your runtime WordPress Fast, cheap and zero egress fees Drupal Enterprise PHP CMS, predictable bills Ship Django on Edge Start free. Bring an existing project or start fresh. Start free Talk to an engineer --- ### Deploy Drupal on Edge | Enterprise PHP CMS, predictable bills URL: https://edge.network/solutions/drupal/ Markdown: https://edge.network/solutions/drupal.md JSON: https://edge.network/json/solutions/drupal.json _Run Drupal 10 / 11 on Edge — production VMs with PHP-FPM, S3 File System for media, global CDN with zero egress fees. Acquia and Pantheon-grade infrastructure without the price tag._ For Drupal Drupal on Edge, enterprise without the bill Acquia and Pantheon-grade infrastructure on real VMs you control. S3 File System for media, global CDN with zero egress fees, multi-site ready out the box. Start free Have us manage it # settings.php — Edge Storage via s3fs $settings['s3fs.access_key'] = getenv('EDGE_KEY'); $settings['s3fs.secret_key'] = getenv('EDGE_SECRET'); $config['s3fs.settings']['bucket'] = 'drupal-files'; $config['s3fs.settings']['endpoint'] = 'https://storage.edge.run'; $config['s3fs.settings']['use_https'] = TRUE; # Provision the VM with Drush $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-drupal.sh # Front it with the CDN $ edge cdn create example.com ... Why Drupal teams pick Edge All the platform features of the big managed Drupal hosts, on infrastructure that doesn't bill per page-view. Real VMs for PHP-FPM Dedicated CPU and NVMe storage, sized to fit. None of the noisy-neighbour problems that plague shared Drupal hosting. S3 File System for media Use the well-trodden `s3fs` Drupal module pointing at Edge Storage. Files survive any VM restore and are served straight from the CDN. Image styles, edge-accelerated Pair Drupal's image styles with Edge Image Optimization for AVIF/WebP and responsive variants — generated on demand, cached at the CDN. Global CDN, zero egress Front anonymous Drupal traffic through the Edge CDN. Authenticated users hit your origin VM as usual; everyone else gets cached pages. MySQL, MariaDB or Postgres Run the database on the same VM, a separate VM via private networking, or your existing managed provider. Drupal's happy with all three. Multi-site friendly Drupal multi-site setups work cleanly on a single VM with multiple databases, or one VM per site. The CDN handles per-domain routing transparently. Reference architecture How Drupal maps to Edge Standard LEMP + Drupal stack on a VM, public/private files in object storage, CDN out front. Compute Runs Drupal + Nginx + PHP-FPM (and a database) on a sized-to-fit VM Storage S3 File System (`s3fs`) for the public and private file systems CDN Caches anonymous-user HTML and all `/sites/default/files` URLs Image Optimization On-the-fly responsive variants, smart cropping and modern formats DNS Anycast DNS for the apex, www and any subsites Shield Replaces CAPTCHA modules on webforms, comments and registration — free Assist AI answers grounded in your published content — one script tag in the theme Indicative cost Mid-sized Drupal site ~1M monthly page views, 500GB image bandwidth, multi-site (3 sites) Acquia Cloud Professional ~$500–1,500 Pantheon Performance ~$300–800 Edge (VM + CDN + Storage) ~$50–120 Indicative figures. Add Expert Services for a fully managed equivalent. Common questions Drupal 10 or Drupal 11? Both run cleanly on Edge — they're standard PHP/MySQL stacks. Bootstrap script handles Composer, Drush, and the relevant PHP extensions. How does this compare to Acquia / Pantheon? Cheaper, faster (real CPU and IO), and you keep root and database access. The trade-off is one bootstrap script and you handle module updates yourself — or our Expert Services team can manage it. Can I do blue/green deploys? Yes — provision a second VM, deploy the new build, switch the CDN origin to the new VM, decommission the old. Zero downtime, no platform-specific machinery required. What about the Memcache / Redis cache backends? Run Memcached or Redis on the same VM (cheapest), a separate VM via private networking (most scalable), or your existing managed provider. Drupal core supports all three. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Replaces CAPTCHA modules on webforms, comments and registration. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Turns your published content into instant visitor answers — one script tag in the theme. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Ghost Modern publishing, self-hosted Statamic Flat-file Laravel CMS, zero database drama Craft CMS Premium PHP CMS for design-led teams Strapi The leading open-source headless CMS Move Drupal to Edge Start free. Migrate a single site or a whole multi-site estate — Expert Services can plan and run it. Start free Have us migrate it --- ### Deploy Laravel on Edge | Production VMs, S3 storage and CDN URL: https://edge.network/solutions/laravel/ Markdown: https://edge.network/solutions/laravel.md JSON: https://edge.network/json/solutions/laravel.json _Run Laravel apps on Edge — production-grade VMs, S3-compatible storage for filesystems, queues and caching, and a global CDN with zero egress fees._ For Laravel Laravel hosting without the markup Production VMs with proper CPU, S3-compatible storage for the filesystem driver, and a global CDN with zero egress fees. The full Laravel stack, on infrastructure you actually control. Start free Read the deploy guide # Provision a VM and bootstrap PHP/Nginx $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-laravel.sh # Configure the s3 disk in config/filesystems.php 'edge' => [ 'driver' => 's3', 'endpoint' => env('EDGE_ENDPOINT'), 'bucket' => env('EDGE_BUCKET'), ], # Front it with the CDN $ edge cdn create app.example.com \ --origin https://<vm-ip> Why Laravel teams pick Edge The DigitalOcean-style simplicity you love, with the global edge network and storage you'd otherwise glue together yourself. Real VMs, not shared hosting Dedicated vCPU, NVMe storage and 10Gbps networking. Sized from a small VM up to multi-core monsters as you grow. S3-compatible Filesystem Plug Edge Storage into Laravel's `s3` filesystem driver. Uploads, exports and backups offloaded to durable object storage. Global CDN, zero egress Front public/ assets, Mix/Vite output and Storage URLs through the Edge CDN. No egress fees, no per-request gotchas. Bring your DB Run MySQL, MariaDB, PostgreSQL or Redis on the same VM, a separate VM, or your existing managed provider. Your call. On-the-fly image transforms Skip Intervention/Image queues — point Edge Image Optimization at your bucket and resize/convert via URL. Forge-style automation Use the Edge CLI or agentic API to provision VMs, set firewall rules, and roll out releases — scriptable end-to-end. Reference architecture How Laravel maps to Edge A typical Laravel app maps cleanly onto our four core products. Same mental model as your dev box, but with global delivery and zero egress for everything users actually download. Compute Runs PHP-FPM + Nginx (or Octane) on a sized-to-fit VM Storage S3-compatible bucket for the `public` and `s3` Laravel disks CDN Caches static assets, Vite output, and public Storage URLs Image Optimization On-the-fly resize, crop and AVIF/WebP conversion of media DNS Anycast DNS for your apex, subdomains and email records Shield Free bot protection for login, register and contact routes — one middleware Assist AI answers from your public pages — one line in the Blade layout # app/Http/Controllers/UploadController.php $path = $request->file('avatar') ->store('avatars', 'edge'); # Generate a CDN-fronted URL $url = 'https://cdn.example.com/' . $path; # Resize on the fly $thumb = $url . '?w=300&fit=cover&fm=webp' ; Common questions Does Laravel Octane work? Yes. Run Octane with Swoole or RoadRunner on an Edge VM exactly as you would on any other Linux box. We have no Lambda-style cold starts to worry about. Can I use Forge-style provisioning? You can keep using Forge if you want — point it at an Edge VM by IP. Or use the Edge CLI / agentic API to bootstrap an equivalent stack with a single script. How do queues and scheduled tasks work? Run `queue:work` and `schedule:run` as systemd services on the same VM, or split workers onto a dedicated VM. Use Redis on the same VM for cheap, fast queues. Where do I store user uploads? Use the standard `s3` filesystem driver pointing at an Edge Storage bucket. The AWS SDK works unchanged — just set the endpoint to the Edge Storage endpoint. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection One middleware guards login, register and contact routes against bots. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers One line in your Blade layout — answers come from your public pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Django Python web apps, no surprise bills Rails Classic VPS workflow, modern network Node.js Express, Fastify, Hono — your runtime WordPress Fast, cheap and zero egress fees Move your Laravel app today Free to sign up — full platform access. Bring an existing site or start fresh — we'll help you size the VM and migrate the storage. Start free Talk to an engineer --- ### Deploy Magento Open Source on Edge | Enterprise PHP commerce URL: https://edge.network/solutions/magento/ Markdown: https://edge.network/solutions/magento.md JSON: https://edge.network/json/solutions/magento.json _Run Magento Open Source on Edge — production VMs with PHP-FPM, MySQL/Postgres, Redis and Elasticsearch, S3-compatible media via the official adapter, global CDN with zero egress fees._ For Magento Magento on Edge, enterprise without Adobe pricing Magento Open Source on real VMs with the full data tier on private networking, S3-compatible media and a global CDN. Adobe Commerce-class hosting at a fraction of the cost. Start free Have us manage it # Provision a Magento-ready VM $ edge compute create \ --image ubuntu-24-04 --plan medium \ --script ./bootstrap-magento.sh # env.php — S3 media adapter 'media_storage_configuration' => [ 'media_storage' => 2, // S3 'endpoint' => 'https://storage.edge.run', 'bucket' => 'magento-media', ], # CDN out front $ edge cdn create shop.example.com \ --origin https://<vm-ip> Why Magento merchants move to Edge Adobe Commerce-grade hosting characteristics, agency-friendly bills. Tuned for Magento's appetite Magento needs real CPU, fast disk and plenty of RAM. Edge VMs with NVMe and dedicated cores keep page generation snappy at scale. Full data tier on private networking Run MySQL, Redis and Elasticsearch on the same or adjacent VMs. No cross-region latency, no per-query egress fees. S3 media adapter Use the official Magento S3 adapter (or community Flysystem alternatives) pointing at Edge Storage. Catalogue media survives VM restores. Image transforms at the CDN Magento generates thumbnails for every product variant. Hand them off to Edge Image Optimization for AVIF/WebP at the CDN. Global CDN, zero egress Cache catalogue HTML for guests, all static assets, JS bundles and product images. Your origin VM only sees logged-in / cart traffic. B2B and multi-store Magento's multi-website / multi-store features work cleanly on a single VM with multiple URLs, or split across VMs as the catalogue grows. Reference architecture How Magento maps to Edge Magento + LEMP + the full data tier, all wired together over Edge's private networking. Compute Runs Magento + Nginx + PHP-FPM, with MySQL, Redis and Elasticsearch on the same or private VMs Storage S3-compatible bucket for the `pub/media` directory CDN Caches catalogue HTML for guests, plus all static and media URLs Image Optimization AVIF/WebP and responsive variants from Magento media URLs DNS Anycast DNS for stores, admin and email subdomains Shield Stops carding bots and fake account creation on checkout and login — free Assist Deflects pre-sales questions using your catalogue and policy pages Indicative cost Mid-sized Magento store ~500k monthly visits, 5,000 SKUs, B2B + B2C, 1TB image bandwidth Adobe Commerce Cloud $$$$+ Magento-specialist host ~$300–800 Edge (VMs + CDN + Storage) ~$80–180 Indicative figures. Add Expert Services for a fully managed equivalent. Common questions Magento Open Source or Adobe Commerce? Open Source runs cleanly on Edge — same PHP/MySQL stack, fewer licensing constraints. Adobe Commerce (the paid version) also runs technically, but most teams who pay for Adobe Commerce stay on Adobe Commerce Cloud for the bundled support. What about Magento's page cache? Built-in Varnish-style FPC works fine on a Magento VM. Pair it with the Edge CDN for a two-tier cache (CDN for the world, Magento FPC for warm origin pages). How do I run Elasticsearch / OpenSearch? On the same VM for small catalogues, on a dedicated VM via private networking for serious ones. We have customers running 500k+ SKUs against a single dedicated search VM. How does this compare to Magento hosting providers? Cheaper and faster than most Magento-specific hosts (you're not paying for branded support tier you may not need), and you keep root. Trade-off: bootstrap script for the OS — or our Expert Services team can run it. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Stops carding bots and fake account creation on checkout and login. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Deflects pre-sales questions using your catalogue and policy pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront PostgreSQL Self-hosted Postgres on dedicated NVMe MySQL MySQL or MariaDB on real VMs Move Magento to Edge Start free. Migrate one store or a whole estate — Expert Services can plan and execute. Start free Have us migrate it --- ### Deploy Next.js on Edge | A self-hosted Next.js platform URL: https://edge.network/solutions/nextjs/ Markdown: https://edge.network/solutions/nextjs.md JSON: https://edge.network/json/solutions/nextjs.json _Run Next.js on Edge — production VMs, S3-compatible storage, global CDN with zero egress fees. The self-hosted alternative to Vercel._ For Next.js Self-host Next.js without the lock-in Run Next.js on production VMs with global CDN, zero egress fees, S3-compatible storage and on-the-fly image optimisation. Everything you'd want from Vercel — without the bill or the lock-in. Start free Read the deploy guide # Build a standalone Next.js app $ next build # Spin up a VM with the Edge CLI $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-nextjs.sh # Front it with the CDN $ edge cdn create app.example.com \ --origin https://<vm-ip> ✓ Live at https://app.example.com ✓ SSL provisioned, CDN warming Why developers move Next.js to Edge Predictable VM pricing, real CPU and memory limits, and no surprise function invocations on your bill. Standalone or Node server Build with `next build` (standalone or default) and run on any Edge VM. No proprietary runtime, no vendor wrappers. next/image without the bill Point next/image at our URL-based image optimisation. Resize, crop, convert to AVIF/WebP on the fly with no per-image fees. S3-compatible storage Use Edge Storage as the backing bucket for uploads, ISR cache, or static assets. AWS SDK works unchanged. Global CDN, zero egress Front your app with a CDN spread across thousands of edge locations. Stop worrying about bandwidth bills on launch day. Your CI, your way Deploy with GitHub Actions, GitLab CI, or a single SSH command. Use the Edge CLI to script everything. Agent-deployable Tell an AI agent "deploy my Next.js app to example.com" — the agentic API provisions the VM, DNS, CDN and SSL for you. Reference architecture How Next.js maps to Edge A typical Next.js app maps cleanly onto our four core products. No glue services, no proprietary primitives — just standard infrastructure you can move at any time. Compute Runs `next start` (or your standalone build) on a VM near your users Storage S3-compatible bucket for uploads, ISR snapshots, and static asset overflow CDN Caches `_next/static`, public assets, and edge-cacheable API routes globally Image Optimization Drop-in loader for next/image — resize, AVIF/WebP, smart cropping DNS Anycast DNS with instant propagation for your apex and previews Shield Free bot protection for forms and API routes, with a 1–100 humanity score Assist AI answer box grounded in your rendered pages — one script tag in the layout # next.config.js — image loader module.exports = { images: { loader: 'custom' , loaderFile: './edge-loader.js' , }, } # edge-loader.js export default function loader({ src, width, quality }) { return `https://cdn.example.com/${src}?w=${width}&q=${quality||75}` } The Vercel maths, without the surprises A medium-traffic Next.js app on Vercel routinely runs into four-figure monthly bills once you cross a million page views. The same app on Edge runs from a small VM and a CDN deployment — fixed costs, no per-invocation fees, no per-image transforms. Predictable VM pricing — no per-invocation surprises Zero egress fees for CDN traffic Image optimisation included with the CDN Move providers any time — vanilla Node, vanilla S3 Indicative monthly cost Medium-traffic Next.js app ~3M page views, 500GB image bandwidth, ISR Vercel Pro + overages ~$300–800 AWS (EC2 + CloudFront + S3) ~$120–250 Edge (VM + CDN + Storage) ~$30–60 Indicative figures based on public pricing. Run your own numbers in the trial. Common questions Do server components and server actions work? Yes. Next.js runs as a normal Node process on an Edge VM, so the full feature set — server components, server actions, middleware, route handlers — works exactly as documented. What about ISR and on-demand revalidation? Built-in ISR works out of the box. For multi-VM setups you can persist the cache to Edge Storage with a custom cache handler, or call your `/revalidate` endpoint from any CI step. Can I use next/image without paying per-transform? Yes — configure a custom loader pointing at Edge Image Optimization. You get the same `<Image />` component with on-the-fly resizing and modern format conversion at CDN prices. How do previews / branch deploys work? Spin up a small VM per branch from your CI, point a `*.test.network` subdomain at it, tear it down on PR close. The Edge CLI and agentic API both make this a few lines of YAML. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Score signups and API-route submissions with one fetch from a route handler — no CAPTCHA widget to ship. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers One script tag in the root layout gives every page an answer box grounded in your rendered content. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Nuxt Vue-powered SSR on global VMs SvelteKit Tiny, fast, and Node-friendly Astro Content-first sites at the edge Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Ship Next.js on your terms Free to sign up — full platform access. Bring an existing app or start from scratch — we'll match your current performance and slash your bill. Start free Talk to an engineer --- ### Deploy Node.js on Edge | Express, Fastify, Hono — your runtime URL: https://edge.network/solutions/nodejs/ Markdown: https://edge.network/solutions/nodejs.md JSON: https://edge.network/json/solutions/nodejs.json _Run any Node.js app on Edge — Express, Fastify, Hono, NestJS, Koa. Real VMs, S3-compatible storage, global CDN with zero egress fees._ For Node.js Node.js apps, properly hosted Express, Fastify, Hono, NestJS — any Node app, on a real VM, fronted by a global CDN. No serverless gotchas, no per-invocation pricing, no platform-specific build steps. Start free Read the deploy guide # bootstrap-node.sh curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash - sudo apt-get install -y nodejs git clone git@github.com:me/api . npm ci && npm run build sudo systemctl enable --now api # Provision the VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-node.sh # CDN out front $ edge cdn create api.example.com ... Why Node teams pick Edge A long-running Node process is still the fastest, simplest, cheapest deployment for most apps. Any Node framework, any runtime Express, Fastify, Hono, NestJS, Koa, Adonis, plain http — if it runs on Node, it runs on an Edge VM. Bun and Deno work too. Long-running process, no cold starts A real Node process on a real VM. Consistent latency, no per-invocation pricing, no surprise cold-start spikes. S3-compatible storage Use the AWS SDK or any S3 client to push uploads and downloads through Edge Storage. Same code in dev and prod. Image transforms via URL Hand off resizing, cropping and format conversion to Edge Image Optimization. Your Node process stays small and fast. Global CDN, zero egress Front static assets and cacheable routes through the Edge CDN. Your Node app only sees the dynamic traffic that needs it. Plain Linux deploys systemd, pm2, Docker, Kamal — pick your poison. The Edge CLI provisions the VM, you decide how to ship to it. Reference architecture How a Node app maps to Edge Node process on a VM, optional state in Postgres or Redis, S3 for blobs, CDN for everything cacheable. Compute Runs your Node process under systemd, pm2 or Docker Storage S3-compatible bucket for uploads, exports, and snapshot backups CDN Caches static files and edge-cacheable API responses Image Optimization Resize, crop and AVIF/WebP convert via URL DNS Anycast DNS for production, staging and previews Shield Score any POST with one fetch — Express, Fastify or Hono, free Assist AI answer box grounded in your pages — one script tag in the layout # Hono on Node, with Edge Storage SDK import { Hono } from 'hono' import { S3Client } from '@aws-sdk/client-s3' const s3 = new S3Client({ endpoint: 'https://storage.edge.run' , region: 'us-east-1' , }) const app = new Hono() app.get( '/' , c => c.text( 'Hello, Edge' )) serve({ fetch: app.fetch, port: 3000 }) Common questions Express, Fastify, Hono, NestJS — which is best? All of them work. We have no opinion on your framework choice; the deployment story is identical because they're all Node processes behind a reverse proxy on a VM. Can I use TypeScript? Yes — compile in CI, run the JS output on the VM. Or run `tsx` / `ts-node` directly if you prefer (with the obvious startup-time trade-off). What about Bun or Deno? Both work. Install the runtime in your bootstrap script, set up the systemd service to invoke it, deploy as normal. The rest of the stack (Storage, CDN, DNS) is runtime-agnostic. How do I scale horizontally? Provision more VMs and front them with the CDN, or with a small Caddy/Nginx load balancer on a separate VM. Your Node app stays stateless; state lives in Postgres / Redis / Storage. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Score any POST with one fetch — Express, Fastify, Hono, anything. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Serve the widget from your layout; answers come from your site’s own pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → WordPress Fast, cheap and zero egress fees Drupal Enterprise PHP CMS, predictable bills Ghost Modern publishing, self-hosted Statamic Flat-file Laravel CMS, zero database drama Ship your Node app on Edge Start free. Any framework, any runtime, any deploy strategy. Start free Talk to an engineer --- ### Deploy Nuxt on Edge | Vue-powered SSR on global VMs URL: https://edge.network/solutions/nuxt/ Markdown: https://edge.network/solutions/nuxt.md JSON: https://edge.network/json/solutions/nuxt.json _Run Nuxt 3 on Edge — Node SSR on real VMs, S3-compatible storage for assets, a global CDN with zero egress and on-the-fly image optimisation._ For Nuxt Nuxt SSR without the lock-in Run Nuxt 3 on real VMs with the Nitro Node preset. Image optimisation, S3-compatible storage and a global CDN with zero egress fees — all the platform pieces, none of the platform tax. Start free Read the deploy guide # Build with the Nitro Node preset $ NITRO_PRESET=node-server nuxt build # Provision a VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-nuxt.sh # Front it with the CDN $ edge cdn create app.example.com \ --origin https://<vm-ip> ✓ Live, SSL provisioned Why Nuxt teams pick Edge All the framework features, none of the proprietary glue. Nitro Node preset on real VMs Build with the Node preset and run on any Edge VM. No proprietary runtime, no per-invocation pricing, no cold starts. @nuxt/image, optimised Wire @nuxt/image to Edge Image Optimization for AVIF/WebP, responsive srcsets and on-the-fly resizing — at the CDN. S3-compatible asset storage Store uploads, generated content and ISR-style snapshots in Edge Storage. The AWS SDK works unchanged. Global CDN with zero egress Cache the static parts of your Nuxt build globally and let SSR fall through to your VM. No egress fees on the way out. CI of your choice Build in GitHub Actions or GitLab CI, ship with the Edge CLI. No platform-specific YAML required. Agent-deployable Tell the Edge agent to deploy your Nuxt app to a domain — VM, DNS, CDN and SSL all wired up automatically. Reference architecture How Nuxt maps to Edge A standard Node SSR setup. Familiar tooling, no surprises. Compute Runs the Nitro Node server (`node .output/server/index.mjs`) Storage S3-compatible bucket for media, ISR snapshots and overflow assets CDN Caches the static `_nuxt/` bundle and any cacheable routes Image Optimization Powers @nuxt/image with edge-side transforms DNS Anycast DNS for the apex, www and per-environment subdomains Shield Free bot protection for forms — one server-side check in a Nitro route Assist AI answers from your rendered pages — one script tag in app.vue # nuxt.config.ts — image optimisation export default defineNuxtConfig({ image: { provider: 'edge' , edge: { baseURL: 'https://cdn.example.com' }, }, routeRules: { '/blog/**' : { swr: 3600 }, }, }) Common questions Does the Nitro Node preset work? Yes. `nuxt build` produces a standard Node bundle in `.output/`. Run it with `node .output/server/index.mjs` on an Edge VM behind Nginx or Caddy. Can I use other Nitro presets? For Edge we recommend the Node preset because it keeps the runtime under your control. The Cloudflare/Vercel presets are tied to those platforms — moving to Edge means Node, which is the most flexible target anyway. How does ISR / route caching work? Use Nitro's built-in route rules with `cache: { swr: true }` and back the cache with Edge Storage for multi-VM setups. The CDN handles the heavy lifting for guest traffic. What about previews? Spin up an ephemeral VM per branch from CI, point a `*.test.network` subdomain at it, tear it down on PR close. The Edge CLI makes this two lines of YAML. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Validate form submissions server-side in a Nitro route with a single HTTP call. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Drop the widget into app.vue and it answers visitor questions from your rendered pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → SvelteKit Tiny, fast, and Node-friendly Astro Content-first sites at the edge Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Laravel Production VMs, S3 storage and CDN Ship Nuxt on Edge Free to sign up — full platform access. Bring an existing Nuxt app or scaffold a new one — we'll help you size the VM. Start free Talk to an engineer --- ### Deploy Payload on Edge | TypeScript-first headless CMS, Next.js-ready URL: https://edge.network/solutions/payload/ Markdown: https://edge.network/solutions/payload.md JSON: https://edge.network/json/solutions/payload.json _Run Payload on Edge — Node.js + TypeScript on real VMs, MongoDB or Postgres, S3-compatible Edge Storage for uploads, and the global CDN out front. The headless CMS that ships inside Next.js._ For Payload Payload on Edge, Next.js-ready The TypeScript-first headless CMS that lives inside your Next.js app — running on a real VM with S3-compatible uploads and a global CDN. Schema in code, content in your DB, you in control. Start free See the Next.js page # payload.config.ts — Edge Storage import { s3Storage } from '@payloadcms/storage-s3' export default buildConfig({ plugins: [ s3Storage({ collections: { media: true }, bucket: 'payload-uploads' , config: { endpoint: 'https://storage.edge.run' , credentials: { ... }, }, }), ], }) Why Payload teams pick Edge A real VM means Payload runs the same as it does on your laptop. No serverless cold starts, no edge runtime restrictions. TypeScript-first, code-defined Define collections, fields and access control in TypeScript. No clicky-clicky admin builder — your CMS schema lives in the repo, version-controlled. Embed inside Next.js, or stand-alone Run Payload as part of a Next.js app on a single Edge VM, or split the admin and front-end across separate VMs. Both patterns are first-class. S3 plugin for uploads Drop in `@payloadcms/storage-s3` pointing at Edge Storage. Uploads, generated image sizes and exports all live in a durable bucket. MongoDB or Postgres, your choice Run either on the same VM for small projects or split onto a dedicated database VM with private networking for serious scale. Global CDN for the API Cache the public REST/GraphQL responses at the Edge CDN with zero egress fees. Your origin VM sees only authenticated traffic. Agent-deployable Tell the Edge agentic API to deploy your Payload + Next.js app to a domain — VM, DNS, CDN, SSL and storage bucket all wired up. Reference architecture How Payload maps to Edge Embedded in a Next.js app on a single VM, or split CMS / front-end across two VMs for independent scale. Both work the same way under the hood. Compute Runs Payload (Node.js) + your DB (Mongo or Postgres) on a VM Storage S3-compatible bucket for the upload collections CDN Caches the front-end and public API; admin UI hits origin Image Optimization Optional: replace built-in resize with edge transforms via custom upload handler DNS Anycast DNS for the apex, www and any preview branches Shield Validates form submissions in a Payload hook with one call — free Assist AI answers from your published content on the frontend # Next.js app pulling from Payload (same VM) import { getPayload } from 'payload' import config from '@payload-config' export default async function Page() { const payload = await getPayload({ config }) const posts = await payload.find({ collection: 'posts' , }) return <PostList posts={posts.docs} /> } Common questions Embedded in Next.js or standalone? Either. Embedded means a single VM serves both the Payload admin (`/admin`) and your Next.js front-end. Standalone means separate VMs for the CMS API and the front-end — useful when scaling independently or sharing one CMS across multiple apps. MongoDB or Postgres? Postgres for relational-heavy schemas and existing Postgres ops experience. MongoDB for document-heavy content and flexible field schemas. Both are first-class in Payload — pick what your team knows. How does this compare to Payload Cloud? Same software, you control the host. Self-hosting on Edge gives you predictable bills, custom plugins and the ability to colocate Payload with the rest of your infrastructure. Can I deploy via Docker? Yes — Payload runs cleanly in a Docker container. See the Docker stack page for the bootstrap pattern, or use plain Node + systemd for a leaner setup. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Validate form submissions in a Payload hook with one call. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Add the widget to your Next.js frontend — answers from your published content. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → WooCommerce Self-host the world's most popular store Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Ship Payload on Edge Start free. Pair with our Next.js stack page for the full TypeScript story. Start free Talk to an engineer --- ### Deploy Rails on Edge | Classic VPS workflow, modern network URL: https://edge.network/solutions/rails/ Markdown: https://edge.network/solutions/rails.md JSON: https://edge.network/json/solutions/rails.json _Run Ruby on Rails on Edge — Puma or Falcon on real VMs, Active Storage backed by S3-compatible Edge Storage, global CDN with zero egress._ For Rails Rails on Edge, no platform tax Real VMs for Puma, S3-compatible Active Storage, global CDN with zero egress fees. Keep your Capistrano or Kamal workflow, keep your sanity. Start free Read the deploy guide # config/storage.yml edge: service: S3 endpoint: https://storage.edge.run access_key_id: <%= ENV['EDGE_KEY'] %> secret_access_key: <%= ENV['EDGE_SECRET'] %> bucket: rails-uploads # config/environments/production.rb config.active_storage.service = :edge config.asset_host = 'https://cdn.example.com' # Provision and front the VM $ edge compute create --plan small ... $ edge cdn create app.example.com ... Why Rails teams pick Edge DHH was right about Linux + a VM. We've added a global CDN and S3 to make it sing. Puma / Falcon on real VMs Run any Rack server you like — Puma, Falcon, Iodine — on a sized-to-fit VM. Boring, predictable, fast. Active Storage on S3 Configure Active Storage with the AWS adapter and point it at Edge Storage. Variants, direct uploads, the lot — works unchanged. PostgreSQL or MySQL alongside Run your database on the same VM, a separate VM via private networking, or your existing managed provider. Low-latency either way. Image processing without queues Skip MiniMagick / libvips per-request — let Edge Image Optimization generate variants from a URL. Active Storage stays declarative. Global CDN, zero egress Front asset_host through the Edge CDN, point Active Storage URLs at it too. Fast, free egress on everything users download. Capistrano or Kamal Stick with the deployment workflow you love — Capistrano, Kamal, plain SSH, all work. The Edge CLI provisions the VMs. Reference architecture How Rails maps to Edge Standard Puma + Postgres + Sidekiq, with Active Storage on object storage and the CDN out front. Compute Runs Puma (or Falcon) behind Nginx/Caddy on a VM Storage S3-compatible bucket for Active Storage uploads and variants CDN Caches the asset pipeline output and Storage URLs Image Optimization On-the-fly variants without per-request processing DNS Anycast DNS for the apex, www and email records Shield Guards Devise logins and signups against credential stuffing — free Assist AI answers from your public pages — one line in application.html.erb # config/deploy.yml (Kamal) service: app image: ghcr.io/me/app servers: web: - <edge-vm-ip> env: RAILS_ENV: production EDGE_ENDPOINT: https://storage.edge.run # Deploy $ kamal deploy Common questions Does Kamal work on Edge? Yes — Kamal provisions any VM with SSH access. Use the Edge CLI to create the VM, then point Kamal at its IP. The container-based deploys play nicely with our infrastructure. How does Active Storage work? Configure the `:amazon` service with `endpoint: https://storage.edge.run` and your Edge Storage credentials. Direct uploads, variants and `service_url` all work as documented. Where do background jobs run? Run Sidekiq / GoodJob / SolidQueue as systemd services on the same VM (cheap, simple) or a dedicated worker VM (scalable). Backed by Redis on Edge Compute. How do I deploy multi-region? Provision VMs in two regions, point a multi-region DNS record at them, and have the Edge CDN serve assets globally. Active Storage stays in one region; reads are cached at the CDN. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection A before_action guards Devise logins and signups against credential stuffing. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers One line in application.html.erb — grounded answers on every page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Node.js Express, Fastify, Hono — your runtime WordPress Fast, cheap and zero egress fees Drupal Enterprise PHP CMS, predictable bills Ghost Modern publishing, self-hosted Ship Rails on Edge Start free. Bring your `bin/rails new` or your existing monolith. Start free Talk to an engineer --- ### Deploy Statamic on Edge | Flat-file Laravel CMS hosting URL: https://edge.network/solutions/statamic/ Markdown: https://edge.network/solutions/statamic.md JSON: https://edge.network/json/solutions/statamic.json _Run Statamic on Edge — production VMs, S3-compatible asset disks, global CDN with zero egress fees and on-the-fly image optimisation. Static or dynamic, your call._ For Statamic Statamic, served without the surprises Flat-file Laravel CMS on real VMs, asset containers backed by S3-compatible Edge Storage, global CDN with zero egress fees. Or generate static, push, serve — origin-less. Start free Read the deploy guide # config/filesystems.php — asset disk 'edge' => [ 'driver' => 's3', 'endpoint' => env('EDGE_ENDPOINT'), 'bucket' => env('EDGE_BUCKET'), ], # Generate the static site $ php please ssg:generate # Sync to Edge Storage $ aws s3 sync storage/app/static s3://my-site \ --endpoint https://storage.edge.run --delete # Front it with the CDN $ edge cdn create example.com \ --origin s3://my-site Why Statamic teams pick Edge Flat-file content meets a flat-fee infrastructure stack. No DB to babysit, no per-visit caps, no egress fees on the way to your readers. Flat-file by default, no DB drama Statamic's flat-file content lives in the repo. No MySQL to provision, snapshot or scale — your VM does one thing and does it well. Assets straight to Edge Storage Wire Statamic asset containers to the S3 driver and point them at Edge Storage. Uploads, thumbnails and downloads all live in one durable bucket. Image transforms at the CDN Use Statamic's native Glide tags for build-time work, or hand off to Edge Image Optimization for on-the-fly resize, AVIF/WebP and smart cropping. Global CDN, zero egress Front the console and the front-end through the Edge CDN. Public pages cached globally, console falls through to your VM. Static Site Generator out the box Run `php please ssg:generate`, push the output straight to Edge Storage, serve from the CDN. Origin-less hosting for content sites that change daily, not hourly. Laravel inside, agent-deployable It's Laravel under the hood — Forge, Envoyer, Kamal and the Edge agentic API all work as you'd expect. Spin up VMs, configure DNS, ship. Reference architecture How Statamic maps to Edge Two flavours: a small VM running Statamic (PHP) for dynamic sites, or pure CDN + Storage for SSG output. Both share the same asset and image pipeline. Compute Runs PHP-FPM + Nginx serving Statamic (or just builds the SSG output) Storage S3-compatible asset containers for uploads, generated thumbs and SSG output CDN Caches the front-end globally; optional origin pull from the SSG bucket Image Optimization Drop-in replacement for Glide URLs with on-the-fly transforms DNS Anycast DNS for the apex, www and any preview branches Shield Protects Statamic forms from spam with a humanity score — free Assist Your flat-file content, answered — one script tag in the layout # Antler template — Edge image URL <img src= "https://cdn.example.com/{{ asset:url }}?w=1200&fm=webp" srcset= "https://cdn.example.com/{{ asset:url }}?w=800&fm=webp 800w, https://cdn.example.com/{{ asset:url }}?w=1600&fm=webp 1600w" alt= "{{ alt }}" > # Or stick with Glide tags — both work {{ glide:hero_image width="1200" format="webp" /}} Common questions Static, dynamic, or both? Either. For a content site, run `php please ssg:generate` in CI, sync the output to Edge Storage, serve from the CDN — no origin VM needed at all. For a Statamic app with form submissions or member areas, run it on a small VM the same way you would Laravel. How do asset containers work? In `config/filesystems.php`, define an `s3` disk pointing at Edge Storage and reference it from your asset container config. Uploads, focal-point crops and Glide-cached variants all land in the bucket. What about Statamic Pro / Eloquent driver? Both work. The Pro features (multi-site, users, forms, REST/GraphQL APIs) are unaffected by where you host. If you switch to the Eloquent driver, just point Statamic at MySQL/PostgreSQL on the same VM or a separate Edge VM. How do I deploy content updates? Two patterns: (1) Edit in the console on the VM, then run `ssg:generate` and sync to Storage; (2) Commit content as code, push to git, let CI build and ship. The agentic API can wire either pattern up for you. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Score Antlers form submissions with a single HTTP check — no plugin stack. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Your flat-file content becomes an answer box in one line of the layout. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Craft CMS Premium PHP CMS for design-led teams Strapi The leading open-source headless CMS Directus Instant API over any SQL database Payload TypeScript-first headless CMS, Next.js-ready Ship your Statamic site on Edge Free to sign up — full platform access. Bring an existing site or scaffold a fresh one — flat-file or Eloquent, static or dynamic. Start free Talk to an engineer --- ### Deploy SvelteKit on Edge | Tiny, fast, Node-friendly hosting URL: https://edge.network/solutions/sveltekit/ Markdown: https://edge.network/solutions/sveltekit.md JSON: https://edge.network/json/solutions/sveltekit.json _Run SvelteKit on Edge — adapter-node on real VMs, S3-compatible storage, a global CDN with zero egress fees and image optimisation._ For SvelteKit SvelteKit, served from real VMs adapter-node + a small VM + a global CDN. The cleanest production recipe for SvelteKit — no platform-specific build, no cold starts, no egress fees on the way out. Start free Read the deploy guide # svelte.config.js import adapter from '@sveltejs/adapter-node' export default { kit: { adapter: adapter() } } # Build $ npm run build # Provision the VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-svelte.sh # CDN out front $ edge cdn create app.example.com \ --origin https://<vm-ip> Why SvelteKit teams pick Edge Tiny apps, real CPU, predictable bills. adapter-node, no fuss Build with adapter-node and run the resulting Node bundle on any Edge VM. Tiny RAM footprint, plain Linux, no platform-specific build. Real CPU, no cold starts Long-running Node process on a real VM means consistent response times — no serverless cold start to worry about on every request. Vite + edge image optimisation Use SvelteKit's `enhanced:img` for build-time work, then point public images at Edge Image Optimization for on-the-fly transforms. S3-compatible storage Use any AWS-SDK-compatible client to push uploads and downloads through Edge Storage. Works the same in dev and prod. Global CDN, zero egress Cache static assets and edge-cacheable routes globally with no egress fees. Your VM only sees the dynamic traffic that needs it. Push from your CI GitHub Actions, GitLab CI or a single SSH command. The Edge CLI is fully scriptable end-to-end. Reference architecture How SvelteKit maps to Edge Adapter-node + VM + CDN. Boring on purpose. Compute Runs `node build/index.js` from your adapter-node output Storage S3-compatible bucket for uploads, downloads and overflow assets CDN Caches `_app/`, public/ and any cacheable load functions Image Optimization Resize, crop and AVIF/WebP transforms via URL DNS Anycast DNS for production, staging and previews Shield Score form actions with one HTTP call — no CAPTCHA widget, free Assist AI answers grounded in your site content — one script tag in app.html # /etc/systemd/system/svelte.service [Service] WorkingDirectory=/srv/app ExecStart=/usr/bin/node build/index.js Restart=always Environment=PORT=3000 Environment=NODE_ENV=production [Install] WantedBy=multi-user.target Common questions Which adapter should I use? adapter-node. It produces a self-contained Node app that runs anywhere Node runs — including Edge VMs. We recommend it over the platform-specific adapters precisely because it keeps you portable. How do I run it as a service? Wrap `node build/index.js` in a systemd unit on the VM. Bootstrap script handles install, build and service registration on first boot. Server-only modules and form actions? Both work exactly as documented. SvelteKit runs as a normal Node process, so anything in the SvelteKit docs Just Works. How do I do previews per PR? Spin up an ephemeral VM in CI, alias a `*.test.network` subdomain to it, tear it down on PR close. The Edge CLI makes this trivial. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Check the humanity score in a form action before you accept the submission — no client bundle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers One line in app.html and visitors get grounded answers site-wide. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Astro Content-first sites at the edge Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Laravel Production VMs, S3 storage and CDN Django Python web apps, no surprise bills Ship SvelteKit on Edge Start free. Bring your repo, deploy in minutes. Start free Talk to an engineer --- ### E-commerce Solutions URL: https://edge.network/solutions/ecommerce/ Markdown: https://edge.network/solutions/ecommerce.md JSON: https://edge.network/json/solutions/ecommerce.json _Run your store on infrastructure built for conversion. Zero egress fees on product media, a global CDN for storefront speed, real compute for checkout, and free bot protection with Edge Shield._ E-commerce Infrastructure that converts Fast storefronts, zero egress fees on product media, real compute for checkout, and free bot protection. Run WooCommerce, Magento, Medusa, Saleor, or your Shopify storefront on infrastructure you control. Get Started Talk to Sales Your Store — Black Friday 1,847 orders today 12.4 TB media served Order confirmed · $34 Sydney · served in 47ms just now Order confirmed · $210 Berlin · served in 21ms just now Automated checkout attempt Humanity score 4/100 Blocked by Shield Order confirmed · $62 New York · served in 24ms just now Egress fees $0.00 Every terabyte, free to serve 988 Global PoPs $0 Egress Fees <50ms Global Latency Free Bot Protection 99.99% Uptime SLA Everything a store needs to be fast, safe, and cheap to run The whole platform pulls in the same direction: more conversions, fewer bots, and a bandwidth bill that doesn't scale with your success. Speed That Converts Every 100ms of load time costs conversions. Product pages and imagery served from 988 PoPs put your storefront within 50ms of buyers worldwide. Zero Egress on Product Media Product photos, zoom images, and video lookbooks are your biggest bandwidth line. On Edge, delivering them costs nothing — pay only for storage. Just-in-Time Media Resize, crop, and convert product imagery on the fly via URL parameters. One master image, every variant your theme needs, no build pipeline. Real Compute for Checkout Dedicated vCPU and NVMe-backed VMs keep cart and checkout fast when a drop or campaign lands. Scale up for the sale, back down after. Free Bot Protection Edge Shield stops carding, coupon abuse, inventory-hoarding bots, and fake accounts — invisibly, without a CAPTCHA in your checkout flow. Private Data Tier Run your database, cache, and queue on private networking, unreachable from the public internet. PCI-conscious architecture by default. Bring the platform you already know Reference architectures and quickstarts for every major open commerce stack — each one running on real VMs with S3-compatible media storage and a global CDN. WooCommerce Self-host the world's most popular store Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront Something else? Any stack that runs on a VM runs on Edge — browse all stacks . Edge Shield The bots that cost stores real money E-commerce is the most attacked vertical on the web. Shield protects the surfaces that hurt when they're abused — invisibly, and free forever. Carding & Payment Fraud Bots testing stolen card numbers against your checkout burn payment processor goodwill and chargeback budgets. Shield scores them out before they reach payment. Coupon & Promo Abuse Single-use discount codes farmed by fake accounts at scale. Invisible verification on signup and redemption keeps promotions for actual customers. Inventory Hoarding Scalper bots carting limited stock in seconds. A humanity score on add-to-cart lets you throttle automation without slowing real buyers. Account Takeover Credential stuffing against customer logins exposes saved cards and addresses. Step up verification only when the score says so. Explore Shield See our security solutions Success shouldn't raise your bandwidth bill A product page can carry megabytes of imagery, and every visitor downloads it. On per-GB CDNs, your best trading days are your most expensive. Edge charges nothing for egress — a viral product costs the same to serve as a quiet one. Combined with just-in-time image optimisation, most stores cut their media delivery costs to a flat, predictable storage fee. View Pricing Black Friday, 10TB of product media AWS CloudFront ~$850 Typical per-GB CDN ~$400 Edge CDN $0 egress Every region, every spike, every campaign — the egress line stays at zero. Ready to sell on better infrastructure? Launch your store on Edge, or let our Expert Services team migrate it for you — typically with zero downtime. Get Started Explore Expert Services --- ### Edge Labs URL: https://edge.network/solutions/labs/ Markdown: https://edge.network/solutions/labs.md JSON: https://edge.network/json/solutions/labs.json _Edge Labs is our AI-first R&D unit: a fixed monthly retainer delivering industry-specific frontier reports, needle-moving recommendations, and delivery._ Edge Labs Frontier R&D. Delivered. Edge Labs is our AI-first research and development unit — built for organisations in need of change. Rooted in our physical robotics lab and grounded in cutting-edge robotics and AI, Labs turns frontier capability into targeted, game-changing deliveries. Start the conversation How an engagement works Monthly frontier report Industry-specific, decision-ready Product recommendation Ad hoc, designed to shift the needle Built in the lab Robotics and AI on real hardware A different kind of unit Expert Services handles the heavy lifting of building and running systems. Labs exists for the moves that change the game. AI-first, frontier-leaning Labs works at the edge of what AI can do today — and watches what it will do next. Everything we recommend is grounded in what we build and test ourselves, not vendor decks. Rooted in a physical robotics lab This is not a slideware practice. Labs runs a physical robotics lab where cutting-edge robotics and AI meet real hardware, real sensors, and real-world constraints. Built for organisations in need of change Labs exists for one outcome: targeted, game-changing deliveries. Not incremental optimisation — interventions designed to meaningfully shift the needle. The base engagement One fixed retainer. Three things you can count on. Labs engagements start simple: a fixed monthly retainer, a predictable cadence, and outputs designed to be acted on — not filed. A monthly industry report Frontier AI and robotics developments, decoded for your industry. What moved this month, what it means for your organisation, and what to do about it — written by the people building with it. Ad-hoc product recommendations When we see an opening — a capability, a cost curve, a competitor blind spot — you hear about it straight away. Specific, actionable product recommendations designed to meaningfully shift the needle, not a backlog of maybes. Delivery, when you want it Every recommendation comes with a path to real. Labs can prototype, build, and deliver what it proposes — from proof of concept on lab hardware to production systems. The Lab Research with its sleeves rolled up Labs is anchored in a physical robotics lab — the discipline that keeps our thinking honest. Frontier AI is easy to talk about and hard to make work in the real world; robotics forces the two together. The result is advice grounded in what actually runs, and delivery teams who have already made it run. Cutting-edge robotics and AI, tested on real hardware Prototypes before proposals — we recommend what we've proven Frontier models applied to physical and digital problems alike Backed by the Edge platform for anything that needs to scale Why it matters to you Most advisory work stops at the deck. Labs is judged on what it ships. The same unit that spots the opportunity in your monthly report can prototype it in the lab and deliver it into your business — one accountable team from insight to production. 1 Team from insight to delivery 0 Slideware-only engagements How an engagement works A fixed retainer sets the cadence. Delivery scales up only when there's something worth building. 01 Immersion We get inside your industry and your organisation: where the value sits, where the friction is, and where frontier capability can change the game. 02 The monthly report A fixed retainer delivers an industry-specific report every month — frontier developments, competitive signals, and concrete implications for you. 03 Recommendations As opportunities surface, we send targeted product recommendations — each one scoped, justified, and designed to move your numbers, not your slide count. 04 Delivery Choose what to pursue and Labs delivers it: prototyped in our robotics lab where hardware is involved, and engineered to production quality throughout. Labs or Expert Services? They work best together: Labs finds and proves the game-changing move; Expert Services carries the day-to-day engineering around it. Frontier R&D Edge Labs Targeted, game-changing deliveries Monthly industry-specific frontier report Needle-moving product recommendations Grounded in robotics and frontier AI Heavy lifting, done well Expert Services On-demand senior development teams Business-as-usual engineering and delivery Project, retainer, or dedicated-team models Below-market day rates, no recruitment fees Explore Expert Services Bring the frontier to your industry Tell us about your organisation and the change you're after. We'll come back with how a Labs retainer would work for you — and what the first report would cover. Talk to Edge Labs --- ### Expert Services URL: https://edge.network/solutions/expert-services/ Markdown: https://edge.network/solutions/expert-services.md JSON: https://edge.network/json/solutions/expert-services.json _AI/ML solutions, infrastructure consulting, migration services, and ongoing support. Our experts help you build and scale._ Expert Services AI-Forward Development Edge's Expert Services team knows AI inside out. From LLM integration to ML pipelines, we build intelligent systems that scale – at rates below market average. Get in touch AI Integration LLM & ML pipelines Cloud Architecture Scalable infrastructure Full-Stack Dev Modern web & mobile Dedicated Teams Scale on demand £600 Day rate £0 Recruitment fees 24hr Response time Core Services Transform your business with expert development teams that scale with your ambitions AI & Machine Learning Solutions Deploy intelligent systems that drive real business value. Data-Driven Experiences Transform raw data into compelling user experiences and actionable insights. Content Management Systems Scalable, headless CMS solutions built for modern digital experiences. Cloud-Native Architecture Microservices, serverless, and distributed systems that scale seamlessly at the edge. DevOps & Infrastructure Automated deployment pipelines and infrastructure that grows with you. Agile Solutions for Modern Business Challenges Enterprise Services Perfect For: Mid market companies Growing businesses Large corporations Government agencies E-commerce & Retail Perfect For: Online retailers Marketplace Platforms D2C brands Omnichannel Businesses Media & Entertainment Perfect For: Streaming Services Publishers Production Companies Content Creators Get a free consultation with our solution architects Talk to us about your requirements and pain points and we'll provide a series of recommendations to help deliver meaningful results. Book Consultation Why Choose Edge? Expert Teams, On Demand Skip the lengthy hiring process. Our development team integrates seamlessly with your existing workflows, delivering enterprise-grade solutions from day one. Technology Agnostic Approach From React and Node.js to Python and Go—we work with your preferred tech stack or recommend the optimal solution for your specific needs. Better Value Than In-House Skip recruitment costs, benefits, and overhead. Get senior talent at rates below market average – 20%+ less than building your own team. End-to-End Delivery We handle everything from architecture design to deployment and ongoing maintenance. Focus on your business while we handle the technical complexity. Proven Track Record Hundreds of successful projects delivered for startups to the world's most recognisable brands. Our teams have built systems serving millions of users. UK, US & EU Based Teams Work with senior developers in your timezone. Our team has a global footprint, ensuring seamless communication and compliance with data protection regulations. Transparent, Predictable Pricing No hidden fees or surprise costs. Our day rates are published and below industry average – you'll know exactly what you're paying before we start. Dedicated Teams Expert Development Teams Assigned Exclusively to Your Project 1+ full-time equivalent developers Full-stack capabilities across modern tech stacks Project management included Direct communication channels with your team Seamless integration with your workflows Long-term partnerships built for sustained growth Flexible scaling as your needs evolve Below-market rates with volume discounts for longer commitments The Smarter Investment Hiring in-house means salaries, benefits, equipment, and recruitment fees. At $800/day for senior expertise, our rates deliver real savings over fully-loaded employment costs – without compromising on quality. 20%+ Less than in-house costs 0 Recruitment fees The True Cost of Hiring A £80k salary costs far more than £80k. When you factor in all employer costs and overheads, plus the hidden costs of recruitment, ramp-up, and turnover – the numbers tell a different story. 42% Average overhead on top of base salary (NI, pension, benefits, facilities) £15-20k Typical recruitment fee for a senior developer (15-25% of salary) 3-6 months Time to full productivity for a new hire (ramp-up period) Blended Expertise Senior dev, project direction, and design input in one rate Zero Ramp-Up Productive from day one with experienced teams Flexible Scaling Scale up or down based on project needs No Long-Term Commitment Month-to-month engagement, cancel anytime Start Your Project Today Senior expertise at rates that make in-house hiring hard to justify Full Name Email Address Project Type Select... New Development Migration Optimization Maintenance Budget Range Select... $10k - $50k $50k - $100k $100k - $250k $250k+ Technology Focus Web Development Infrastructure Data Engineering AI Mobile ML Project Details (optional) Book Free Consultation Ready to Transform Your Business? Book a free consultation with our solution architects. No commitment, just expert advice on your technical challenges. What You'll Get: Technical Assessment Comprehensive review of your current systems and challenges Solution Architecture High-level design recommendations for your project Team Recommendations Optimal team composition and engagement model Project Roadmap Timeline, milestones, and delivery approach Cost Estimation Transparent pricing with no hidden fees What's Included Our day rate covers everything you need to deliver successful projects. No hidden costs, no surprise invoices. Senior development resource Project management & coordination UI/UX design input Code review & quality assurance Technical architecture guidance Regular progress reporting Direct Slack/Teams communication Flexible scheduling Engagement Models Project-Based Fixed scope, fixed timeline. Ideal for well-defined projects with clear deliverables. Minimum: 10 days Retainer Ongoing capacity reserved for your projects. Priority scheduling and volume discounts. Minimum: 5 days/month Dedicated Team Full-time embedded resource working exclusively on your projects. Minimum: 3 months --- ### Host Shopify Hydrogen on Edge | Self-host your storefront URL: https://edge.network/solutions/hydrogen/ Markdown: https://edge.network/solutions/hydrogen.md JSON: https://edge.network/json/solutions/hydrogen.json _Self-host your Shopify Hydrogen storefront on Edge — React-based, Remix-powered, on real VMs with a global CDN. Keep Shopify for inventory and orders, run the front-end on your own infrastructure._ For Shopify Hydrogen Hydrogen on Edge, no Oxygen required Self-host your Shopify storefront on a real VM with a global CDN. Keep Shopify for inventory, orders and payments — run the React front-end where you control the bill. Start free See the Node.js page # Build the Hydrogen app $ npm run build # Provision a VM with Node + the build $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-hydrogen.sh # Run as a systemd service ExecStart=/usr/bin/node ./dist/server.js Environment=PORT=3000 Environment=PUBLIC_STORE_DOMAIN=... # Front it with the CDN $ edge cdn create shop.example.com \ --origin https://<vm-ip> Why merchants self-host on Edge All the Hydrogen developer experience, none of the Oxygen lock-in. Shopify backend, your storefront Hydrogen is the framework, Shopify is the back office. Self-host the React storefront on Edge while orders, inventory and payments stay in Shopify. Real VMs, real Node Hydrogen runs on a standard Node server (or in any container). An Edge VM gives you predictable CPU and a long-running process, with no Oxygen runtime constraints. Global CDN, zero egress Cache the static parts of your Hydrogen build globally; SSR routes hit your origin VM. No egress fees on any of the bytes your customers download. Image optimisation included Use Hydrogen's `<Image />` component pointed at Edge Image Optimization for AVIF/WebP and responsive variants generated on the fly at the CDN. Deploy from any CI GitHub Actions, GitLab CI, plain SSH — deploy Hydrogen however you like. The Edge CLI handles VM provisioning and CDN purges. No per-request pricing Oxygen and the serverless edge alternatives bill per request and per CPU-millisecond. An Edge VM is one fixed monthly fee — sized to your store, not your spreadsheet. Reference architecture How Hydrogen maps to Edge A small Node VM running the Hydrogen server, fronted by the Edge CDN. Shopify continues to handle inventory, orders, and payments — Edge handles your customers' eyeballs. Compute Runs your Hydrogen server (`node ./dist/server.js`) on a VM Storage Optional: cache product imagery via the CDN, or proxy from Shopify CDN CDN Caches static assets, page HTML and image transforms globally Image Optimization Powers Hydrogen's `<Image />` with AVIF/WebP at the edge DNS Anycast DNS for the apex storefront domain Shield Scores storefront form submissions in your Remix actions — free Assist Answers product and policy questions from your storefront routes # root.tsx — Hydrogen consuming Shopify import { createStorefrontClient } from '@shopify/hydrogen' const storefront = createStorefrontClient({ storeDomain: env.PUBLIC_STORE_DOMAIN, publicStorefrontToken: env.PUBLIC_STOREFRONT_API_TOKEN, }) # Image with Edge optimisation <Image data={product.featuredImage} loaderUrl= "https://cdn.example.com" /> Common questions Why self-host instead of using Oxygen? Predictable pricing (no per-request bill), no platform-specific runtime constraints, and the same VM can host other services — your blog, an admin tool, internal APIs. Trade-off is that you handle deploys yourself (or via standard CI). How does Hydrogen connect to Shopify? Through the Storefront API (and the Customer Account API for member features). Both are Shopify-hosted; Hydrogen just talks to them. Edge's job is hosting the React/Remix front-end that consumes those APIs. How do I handle product image transforms? Two options: rely on Shopify's CDN (default Hydrogen behaviour), or proxy product images through Edge Image Optimization for AVIF/WebP delivery and a single domain for all assets. How do I deploy a Hydrogen build? Build with `npm run build`, sync the output to your VM (or a Storage bucket if static parts only), restart the systemd service. Same workflow as our Node.js / Next.js stack pages. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Score storefront form submissions inside your Remix actions. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers product and policy questions from your storefront routes. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → PostgreSQL Self-hosted Postgres on dedicated NVMe MySQL MySQL or MariaDB on real VMs Redis In-memory cache and queue, your way MongoDB Self-hosted document store with replica sets Ship Hydrogen on Edge Start free. Move your storefront, keep your Shopify backend. Start free Talk to an engineer --- ### Media Management Solutions URL: https://edge.network/solutions/media-management/ Markdown: https://edge.network/solutions/media-management.md JSON: https://edge.network/json/solutions/media-management.json _Transform and optimise images on-the-fly. Resize, crop, format conversion, and smart compression at the edge._ Media Management Just-in-Time Transformations Transform, optimise, and deliver images on-the-fly. No pre-processing, no batch jobs – just fast, intelligent media delivery at the edge. Get Started Learn About Our CDN Original cdn.edge.network/ flamingo.jpg Transform with URL Parameters Add parameters to any image URL to transform it instantly. No SDKs required. # Original image https://cdn.edge.network/images/hero.jpg # Resize to 800px width, auto height https://cdn.edge.network/images/hero.jpg ?w=800 # Resize, crop to square, convert to WebP https://cdn.edge.network/images/hero.jpg ?w=400&h=400&fit=crop&format=webp # Add blur effect and reduce quality for thumbnails https://cdn.edge.network/images/hero.jpg ?w=200&blur=10&q=60 On-the-Fly Transformation Transform images in real-time via URL parameters. Resize, crop, format convert, and optimise without pre-processing. Automatic Optimisation Reduce file sizes automatically while maintaining visual quality. WebP, AVIF, and next-gen format delivery. Global Edge Delivery Transformed assets cached and served from 988 edge locations. Sub-50ms delivery worldwide. Smart Cropping AI-powered focal point detection ensures the important parts of your images are never cropped out. Real-Time Editing Adjust brightness, contrast, saturation, and apply filters on-the-fly. No design software required. Asset Protection Watermarking, signed URLs, and expiration timestamps to protect your visual content. 100+ Transformation Options From simple resizing to complex compositing, transform your media assets in any way you need – all via simple URL parameters. View full documentation Resize & Scale Dynamically resize images to any dimension Format Conversion Automatic WebP, AVIF, JPEG, PNG delivery Quality Control Fine-tune compression for size vs quality Cropping Modes Center, focal point, face detection, entropy Colour Adjustments Brightness, contrast, saturation, hue Filters & Effects Blur, sharpen, sepia, greyscale, and more Text Overlays Add dynamic text and watermarks Image Compositing Layer multiple images together Built for Every Use Case E-commerce Generate product thumbnails, zoom views, and responsive images on demand. No batch processing required. Media & Publishing Deliver optimised hero images, article thumbnails, and social share images from a single source. User-Generated Content Automatically optimise, moderate, and transform user uploads before delivery. Marketing Campaigns Quickly generate new visual variants for A/B testing and personalisation. Asset Protection Secure Your Visual Assets Protect your content with enterprise-grade security features built into every transformation. Signed URLs prevent tampering and hotlinking Expiration timestamps for time-limited access Dynamic watermarking for brand protection Face detection and automatic blurring for privacy Locked parameters enforce transformation rules Access logs and analytics for monitoring Signed URL Example # Unsigned (blocked) https://cdn.edge.network/private/image.jpg?w=800 # Signed (allowed) https://cdn.edge.network/private/image.jpg?w=800&sig=a3f2b... Blazing Fast Delivery Transformed images are cached at the edge. First request transforms and caches; subsequent requests are served in milliseconds from 988 global locations. First transformation cached automatically Sub-50ms delivery from edge cache Automatic format negotiation (WebP, AVIF) Lazy loading and responsive hints Zero egress fees on delivery 988 Edge Locations <50ms Cache Response 100+ Transformations $0 Egress Fees Ready to transform your media workflow? Stop pre-processing images. Start delivering optimised, transformed assets on demand. Get Started Talk to Sales --- ### Media Streaming Solutions URL: https://edge.network/solutions/media-streaming/ Markdown: https://edge.network/solutions/media-streaming.md JSON: https://edge.network/json/solutions/media-streaming.json _Purpose-built video delivery with adaptive bitrate streaming, global edge network, and zero egress fees. Stream to millions._ Media & Streaming Reliable Global Video CDN Deliver video content globally with zero egress fees. Edge's CDN is built for media – high throughput, low latency, and pricing that makes sense. Get Started Learn About Our CDN 988 Global PoPs < 50ms Average Latency < 1s Time to First Byte 99.99% Uptime SLA Unlimited Concurrent Viewers $0 Egress Fees Built for Media Delivery Every feature designed for streaming performance. Optimised for Video Purpose-built for video delivery with adaptive bitrate streaming, chunked transfer, and smart caching. Global Edge Network 988 PoPs worldwide ensure smooth playback for viewers anywhere. Sub-50ms latency globally. Instant Start Times Aggressive edge caching and smart prefetching mean videos start playing instantly. Content Protection Token authentication, geo-blocking, and DRM integration to protect your content. Real-Time Analytics Viewer metrics, quality of experience data, and bandwidth analytics in real-time. Massive Scale Handle millions of concurrent viewers. Auto-scaling infrastructure that grows with your audience. Built for Video Delivery Video on Demand Deliver your video library with instant playback, adaptive bitrates, and global reach. Course Platforms Stream educational content to learners worldwide with fast start times and zero buffering. Media Archives Host and deliver large video libraries cost-effectively with zero egress fees. Embedded Video Power video players on your website or app with reliable, high-performance delivery. Zero Egress Fees. Seriously. Traditional CDNs charge per GB of bandwidth delivered. For video streaming, that adds up fast. Edge charges nothing for egress – pay only for storage and compute. No per-GB bandwidth charges Predictable monthly costs Scale without surprises Same pricing in every region Cost Comparison 100TB Monthly Delivery AWS CloudFront $8,500/mo Cloudflare Pro $5,000/mo Edge CDN $0 egress View full pricing Ready to stream smarter? Join leading media companies already delivering content on Edge. Get Started Talk to Sales --- ### Run Docker on Edge | Containers on global VMs URL: https://edge.network/solutions/docker/ Markdown: https://edge.network/solutions/docker.md JSON: https://edge.network/json/solutions/docker.json _Run Docker and Docker Compose on Edge VMs. Any container, any language, deployed close to your users with zero egress fees and a global CDN._ For Docker Containers on the open edge Spin up a VM, run any Docker image. Compose your stack, front it with a global CDN, store state in S3-compatible Edge Storage. No proprietary runtime, no vendor lock-in. Start free Read the bootstrap docs # bootstrap-docker.sh curl -fsSL https://get.docker.com | sh git clone git@github.com:me/app . docker compose up -d # Provision the VM with that script $ edge compute create \ --image ubuntu-24-04 --plan medium \ --script ./bootstrap-docker.sh # Front the stack with the CDN $ edge cdn create app.example.com \ --origin https://<vm-ip> ✓ Containers running, CDN warm Why ship containers on Edge Real VMs you control, sized to fit, with a global network already wired in. The deployment story you sketched on a whiteboard, working. Plain Docker, plain Linux Provision a VM, install Docker, run your containers. No proprietary container runtime, no funny image registries, no surprises. Compose-ready docker compose up works exactly as you'd expect. Multi-container apps with shared networks and named volumes — straight from your repo. Persistent state, off-box Mount NVMe volumes for stateful containers, or push uploads and backups to S3-compatible Edge Storage. Your containers stay disposable. Global delivery Deploy near any user with a single CLI flag, then front it all with the Edge CDN. Zero egress on bandwidth out to your users. Bootstrap from one script Use the Edge CLI's --script flag to install Docker, pull images and start your stack on first boot. Idempotent, repeatable, version-controlled. Agent-deployable "Deploy this Compose file to api.example.com" — the Edge agentic API can stand up the VM, configure DNS and front it with a CDN deployment. Reference architecture How a containerised app maps to Edge Containers on a VM, persistent state in object storage, traffic through the global CDN. Same primitives as a hyperscaler — without the abstraction tax. Compute Hosts the Docker daemon and your running containers Storage S3-compatible object store for image artefacts, uploads, backups CDN Caches static assets your containers serve, with zero egress DNS Anycast DNS for routing and per-environment subdomains # compose.yml services: app: image: ghcr.io/me/app:latest restart: unless-stopped env_file: .env ports: ["80:3000"] db: image: postgres:16 volumes: ["pgdata:/var/lib/postgresql/data"] caddy: image: caddy:2 volumes: pgdata: Common questions Can I use Docker Compose? Yes. Compose runs unchanged on an Edge VM. We recommend committing your compose file and a small bootstrap script that installs Docker and runs `docker compose up -d` on first boot. What about Kubernetes? You can run k3s or k8s yourself on a cluster of Edge VMs. For most workloads under, say, 20 containers we strongly recommend Compose on a single VM (or a couple) — it's dramatically simpler. Where do my container images live? Anywhere you like — Docker Hub, GHCR, GitLab registry, or self-hosted. Edge Storage works as an OCI-compatible artefact store if you want to keep registries in-network. How do I update a running container? Standard Docker workflow: pull the new image, recreate the container. Wrap it in a CI step or a `watchtower`-style updater. The VM is yours, do it however you like. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Kubernetes k3s and full k8s on real VMs, no control-plane fees Next.js Self-host Next.js without the lock-in Nuxt Vue-powered SSR on global VMs SvelteKit Tiny, fast, and Node-friendly docker compose up — globally Free to sign up — full platform access. Bring your compose file and let us run it close to your users. Start free Talk to an engineer --- ### Run Kubernetes on Edge | k3s and full k8s on real VMs URL: https://edge.network/solutions/kubernetes/ Markdown: https://edge.network/solutions/kubernetes.md JSON: https://edge.network/json/solutions/kubernetes.json _Self-host Kubernetes on Edge — k3s, RKE2 or vanilla k8s on real VMs across regions. Persistent volumes, S3-compatible backups, global CDN ingress and zero control-plane fees._ For Kubernetes Kubernetes on Edge, without the platform tax k3s, RKE2 or vanilla k8s on real VMs across regions. Persistent volumes on local NVMe, backups in S3-compatible storage, global CDN as your ingress front-end. No control-plane fee. Start free Have us run it # Bootstrap a k3s control plane VM $ edge compute create \ --image ubuntu-24-04 --plan medium \ --script ./bootstrap-k3s-server.sh # Add worker nodes (any region) $ edge compute create --plan small \ --region eu-west --count 3 \ --script ./join-k3s-worker.sh # Front the ingress with the CDN $ edge cdn create *.cluster.example.com \ --origin https://<ingress-vip> ✓ Cluster live, CDN routing Why teams run Kubernetes on Edge Real VMs, real networking, real storage — all the primitives Kubernetes assumes, none of the managed-service markup. Your distribution, your call k3s for lightweight clusters, RKE2 for hardened production, kubeadm for vanilla — all run cleanly on Edge VMs. No proprietary control plane to negotiate with. Multi-VM clusters on private networks Spread control plane and worker nodes across Edge VMs and regions. Private networking keeps the etcd / API traffic off the public internet and off your egress bill. Persistent volumes that persist Local NVMe for stateful pods that need IOPS, plus the S3-compatible CSI driver pointing at Edge Storage for backups, snapshots and shared blob data. CDN as the cluster ingress Front your ingress controller (Nginx, Traefik, Istio) with the Edge CDN. Global delivery, zero egress fees on the way out, automatic SSL handled at the edge. No control-plane fees EKS, GKE and AKS all charge ~$73/month per cluster just to exist — before any nodes. On Edge, the control plane is just another VM you already paid for. GitOps-ready Run Flux or ArgoCD against your cluster, deploy from a repo, audit every change. The Edge CLI stands up the cluster; your GitOps pipeline takes it from there. Reference architecture How a cluster maps to Edge Control plane on one (or three) VMs, worker nodes wherever you need capacity, storage in object form for backups and shared data, and the CDN handling the world. Compute VMs for control plane and worker nodes (sized independently) Storage S3-compatible object store for backups, Velero snapshots, shared blob data CDN Sits in front of your ingress controller for global delivery Image Optimization On-the-fly image transforms for any pod-served media DNS Anycast DNS for `*.cluster.example.com` (pair with ExternalDNS) Indicative cost A modest production cluster 3 control-plane + 3 worker nodes, 200GB persistent storage, ~2TB monthly egress EKS + EC2 + EBS + NLB + egress ~$700–1,400 GKE Standard + nodes + LB ~$600–1,200 Edge (6 VMs + CDN + Storage) ~$120–280 Indicative figures. Egress alone often dwarfs the control-plane fee on hyperscalers. Common questions Which distribution should I use? For most teams, k3s. It's a single binary, runs in <512MB RAM per node, and supports almost all of vanilla Kubernetes. Use RKE2 if you need FIPS / CIS hardening, kubeadm if you have specific reasons to pin to upstream k8s. Do I really need Kubernetes? Probably not — if you're running fewer than ~20 containers, our Docker stack page (compose on a VM) will save you a lot of complexity. Kubernetes earns its keep with multi-region, fault tolerance, autoscaling, or large container counts. How does this compare to EKS / GKE / AKS? Cheaper (no control-plane fee, no per-LB-hour bill, zero egress), more portable (vanilla k8s, no cloud-specific CRDs), and you keep root on every node. Trade-off: you handle upgrades — or our Expert Services team can manage them. Persistent volumes — local or S3? Local NVMe for databases and anything IOPS-sensitive. S3-compatible CSI (e.g. `s3-csi`, `geesefs`) for shared assets and bulk data. Velero on top of Edge Storage handles cluster-wide backup and disaster recovery. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Next.js Self-host Next.js without the lock-in Nuxt Vue-powered SSR on global VMs SvelteKit Tiny, fast, and Node-friendly Astro Content-first sites at the edge Run Kubernetes the cheap way Start free. Stand up a cluster in minutes — or have our Expert Services team architect and run it for you. Start free Have us run it --- ### Run llama.cpp on Edge | Quantised LLM inference, CPU or GPU URL: https://edge.network/solutions/llama-cpp/ Markdown: https://edge.network/solutions/llama-cpp.md JSON: https://edge.network/json/solutions/llama-cpp.json _Self-host llama.cpp on Edge — GGUF model inference on CPU-only or hybrid GPU VMs, OpenAI-compatible server, models cached in S3. The leanest LLM runtime, on infrastructure you actually own._ For llama.cpp llama.cpp on Edge, the leanest LLM runtime Self-host quantised LLMs on CPU-only or GPU Edge VMs. GGUF models from S3-compatible storage, OpenAI-compatible server, zero per-token bills. The smallest possible AI footprint. Start free See Ollama (built on this) # Build with CUDA $ cmake -B build -DGGML_CUDA=ON $ cmake --build build --config Release -j # Serve a quantised model $ ./build/bin/llama-server \ -m /mnt/edge-storage/llama-3.1-8b-q4.gguf \ --host 0.0.0.0 --port 8080 \ -c 8192 -ngl 999 # OpenAI-compatible at /v1 curl http://localhost:8080/v1/chat/completions \ -d '{ "messages": [{"role":"user","content":"hi"}] }' Why teams pick llama.cpp on Edge The smallest AI footprint that still does the job — and the foundation Ollama is built on. CPU-friendly inference Run quantised models on regular Edge VMs without a GPU. Useful for tiny models, dev environments, and workloads where latency tolerance is high. GGUF: the standard for quantised GGUF is the de facto format for quantised open-weight models. Hugging Face, TheBloke, llama.cpp itself — all interoperate cleanly. OpenAI-compatible server `llama-server` exposes the OpenAI chat/completions API. Drop-in replacement for paid APIs at the SDK level. Models cached in S3 Cache GGUF files in Edge Storage so any new VM can pull them quickly. No Hugging Face rate-limit drama on cold starts. CUDA / Metal / ROCm builds When you do have a GPU, llama.cpp uses it. CUDA on Nvidia, Vulkan/ROCm on AMD, Metal on Apple Silicon. Your binary, your acceleration. Cheapest path to local LLMs For low-volume workloads or dev, the smallest non-GPU Edge VM serves a 7B Q4 model. Cheaper than any per-token API at any volume. Reference architecture How llama.cpp maps to Edge A CPU or GPU VM running llama-server, GGUF model files mounted from object storage. The least infrastructure to run a serious LLM. Compute CPU VM for small/dev workloads, or GPU VM for serious throughput Storage GGUF model cache in a bucket, mounted to the VM CDN Optional: caches non-streaming responses DNS Anycast DNS for `llm.example.com` # Pull a quantised model from HF $ huggingface-cli download \ bartowski/Meta-Llama-3.1-8B-Instruct-GGUF \ --include "*Q4_K_M*" # Cache it in Edge Storage for next time $ aws s3 cp ./Meta-Llama-3.1-8B-Q4.gguf \ s3://llm-models/ \ --endpoint storage.edge.run Common questions When should I pick llama.cpp over Ollama or vLLM? Pick llama.cpp when you want full control of the binary, need CPU-only inference, or want the smallest possible footprint. Ollama wraps llama.cpp with conveniences; vLLM is for high-throughput GPU serving. All have their place. CPU or GPU? For 7B Q4_K_M and below, CPU on a beefy VM is workable for dev and low-volume use. For production throughput or anything 13B+, you want a GPU. Which quantisation level? Q4_K_M is the usual sweet spot — ~75% quality of full precision at ~25% the size. Q5_K_M for higher fidelity, Q3 for the smallest footprint. Experiment with your specific use case. How do I serve to multiple users? llama-server handles concurrent requests, but doesn't do continuous batching like vLLM. For a small team it's fine; for production multi-tenancy switch to vLLM. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → ComfyUI Node-based Stable Diffusion on GPU VMs Docker Run any container on global VMs Kubernetes k3s and full k8s on real VMs, no control-plane fees Next.js Self-host Next.js without the lock-in Run LLMs the lean way Start free. CPU or GPU, your call. Start free Talk to an engineer --- ### Run Ollama on Edge | Self-host open LLMs on your own GPUs URL: https://edge.network/solutions/ollama/ Markdown: https://edge.network/solutions/ollama.md JSON: https://edge.network/json/solutions/ollama.json _Deploy Ollama on Edge GPU instances — single-binary LLM serving with an OpenAI-compatible API, models persisted to S3-compatible Edge Storage, global CDN out front. Llama, Mistral, Qwen and more, on your own infrastructure._ For Ollama Ollama on Edge, open LLMs on your GPUs Self-host Llama, Mistral, Qwen and friends on Edge GPU instances. OpenAI-compatible API, models cached in S3, no per-token bills and no data leaving your infrastructure. Start free See AI infrastructure # Provision a GPU VM $ edge compute create \ --image ubuntu-24-04 --plan gpu-a10 \ --script ./bootstrap-ollama.sh # Pull and run a model $ ollama pull llama3.1:8b $ ollama serve # From your app — drop-in OpenAI client const openai = new OpenAI({ baseURL: 'https://ai.example.com/v1', apiKey: 'ollama', }) await openai.chat.completions.create({ model: 'llama3.1:8b', ... }) Why teams pick Ollama on Edge All the convenience of an OpenAI API, with your data and your costs under control. GPU instances, sized to fit From a single consumer-grade GPU for 7B–13B models up to dedicated A100/H100 instances for large frontier models. You pick the GPU, you keep the model. Single binary, dozens of models Ollama is one binary that pulls and serves Llama, Mistral, Qwen, Gemma, Phi and 100+ others. `ollama run llama3` and you're away. OpenAI-compatible API Drop-in replacement for OpenAI API endpoints. Point your existing SDK at your Edge Ollama VM and your code runs unchanged. Models persisted in S3 Cache GGUF model files in Edge Storage so any new VM can pull them in seconds. Faster cold starts, no Hugging Face rate limits to dance around. Your prompts, your data Customer prompts and generated responses never leave your infrastructure. Critical for regulated industries and anyone with NDAs. No per-token bills OpenAI charges per million tokens. An Edge GPU VM running Ollama is a fixed monthly cost — generate as much as you like. Reference architecture How Ollama maps to Edge A GPU VM (or several) running Ollama, model weights cached in object storage. Add a tiny load balancer for multi-GPU horizontal scale. Compute (GPU) Runs Ollama on a GPU instance, 1-N depending on traffic Storage S3-compatible bucket caching GGUF models for fast cold starts CDN Optional: caches streaming responses where applicable DNS Anycast DNS for `ai.example.com` Indicative cost ~10M tokens/day, 8B model OpenAI gpt-4o-mini at this volume ~$50–100/mo Together / Replicate (Llama 3.1 8B) ~$30–80/mo Edge GPU VM (A10) flat fee Edge wins decisively as token volume grows. Common questions Which GPU should I pick? For 7B–13B models, a 24GB consumer card (or single-slot A10) works well. For 70B+, look at A100 80GB or H100 instances. Our Compute team can size for your exact model. How does this compare to OpenAI / Anthropic / Together? Cheaper at scale (no per-token bills), private (your prompts stay on your infra), and works offline. Trade-off: open-weight models lag closed frontier models on the hardest tasks — pick based on your workload. How do I scale beyond one GPU? Spin up more GPU VMs, put a small load balancer in front (Caddy or Nginx). Ollama is stateless so this scales linearly. Can I fine-tune? Ollama runs inference; for fine-tuning use vLLM, Axolotl or Unsloth on a separate GPU VM, then push the resulting model back to Ollama for serving. See our vLLM stack page. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → vLLM Production-grade LLM serving llama.cpp Quantised LLM inference, CPU or GPU ComfyUI Node-based Stable Diffusion on GPU VMs Docker Run any container on global VMs Run open LLMs on your terms Start free. Stand up a GPU VM, pull a model, hit the API in minutes. Start free Talk to an engineer --- ### Self-host BookStack on Edge | Open-source documentation platform URL: https://edge.network/solutions/bookstack/ Markdown: https://edge.network/solutions/bookstack.md JSON: https://edge.network/json/solutions/bookstack.json _Run BookStack on Edge — PHP + MySQL on a real VM, S3-compatible image storage, global CDN out front. The Confluence alternative your team will actually update._ For BookStack BookStack on Edge, docs your team will update Self-host the open-source documentation platform on a small VM with S3-compatible image storage and a global CDN. Confluence features, BookStack price. Start free Read the deploy guide # Provision a BookStack VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-bookstack.sh # .env — Edge Storage for images STORAGE_TYPE=s3 STORAGE_S3_KEY=... STORAGE_S3_SECRET=... STORAGE_S3_BUCKET=bookstack STORAGE_S3_ENDPOINT=https://storage.edge.run # Front it with the CDN $ edge cdn create docs.example.com ... Why teams self-host BookStack Confluence-class features, fixed monthly bill, your data on your infrastructure. Books, chapters, pages A simple three-level hierarchy that maps to how teams actually organise documentation. WYSIWYG or Markdown, your call. S3 image uploads Configure BookStack's `IMAGE_STORAGE` to point at Edge Storage. Embedded images and attachments live in a durable, CDN-fronted bucket. SAML, OIDC, LDAP Plug into Microsoft Entra, Google Workspace, Okta, Keycloak — all out of the box. No paid SSO tier to upgrade to. Full-text search included Built-in search across all your books and pages. Fast enough for any team-sized knowledge base. Per-page permissions Granular roles and per-shelf / per-book / per-page permissions when you need them. Confluence-grade access control, free. Confluence is per-seat. BookStack isn't. Confluence is ~$5/user/month and climbs fast. BookStack on Edge is one small VM, regardless of team size. Reference architecture How BookStack maps to Edge Standard LEMP + BookStack on a small VM, image bucket and CDN out front. One small VM serves everyone. Compute BookStack (PHP) + Nginx + MySQL/MariaDB on a VM Storage S3-compatible bucket for embedded images and attachments CDN Caches anonymous-readable docs and all static assets DNS Anycast DNS for `docs.example.com` Shield Guards BookStack registration and login forms — free Assist Your documentation answers its own questions — one script tag in the theme # SSO with OIDC (Microsoft Entra example) AUTH_METHOD=oidc OIDC_NAME=Microsoft OIDC_ISSUER=https://login.microsoftonline.com/.../v2.0 OIDC_CLIENT_ID=... OIDC_CLIENT_SECRET=... OIDC_USER_TO_GROUPS=true Common questions How does this compare to Confluence? Cheaper (flat fee, not per-seat), simpler (a wiki, not a Jira-bolt-on), and you keep root. Trade-off: fewer integrations than Confluence — but the integrations you need (SSO, image storage, search) are all built in. How do I do SSO? BookStack supports SAML 2.0 and OpenID Connect natively. Wire it up in `.env` to your identity provider — Microsoft Entra, Google Workspace, Okta, Authelia, Keycloak. How do I back it up? Nightly `mysqldump` to Edge Storage + your image bucket already lives there. A handful of cron lines is the entire backup strategy. Can I run multiple BookStack instances? Yes — one per team, project or product, all on the same VM with separate databases and CDN deployments. Cheap multi-tenancy without the platform plumbing. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Guards BookStack registration and login forms. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Your documentation answers its own questions — one script tag in the BookStack theme. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Plausible Privacy-first analytics, self-hosted Umami Lightweight, cookie-free analytics n8n Self-hosted workflow automation Vaultwarden Bitwarden-compatible password manager Stand up your docs Start free. Move off Confluence or stand up a fresh wiki. Start free Talk to an engineer --- ### Self-host ComfyUI on Edge | Node-based Stable Diffusion on GPU VMs URL: https://edge.network/solutions/comfyui/ Markdown: https://edge.network/solutions/comfyui.md JSON: https://edge.network/json/solutions/comfyui.json _Run ComfyUI on Edge GPU instances — Stable Diffusion XL, FLUX and any diffusion model, with checkpoints and LoRAs in S3-compatible Edge Storage. Headless API mode for production image generation._ For ComfyUI ComfyUI on Edge, image generation on your GPUs Self-host the most flexible diffusion runtime on Edge GPU instances. SDXL, FLUX, ControlNets, custom workflows — checkpoints in S3, outputs delivered through the global CDN. Start free See AI infrastructure # Provision a GPU VM $ edge compute create \ --image ubuntu-24-04-cuda --plan gpu-l4 \ --script ./bootstrap-comfy.sh # Mount Edge Storage as models/ $ s3fs models /opt/comfy/models \ -o url=https://storage.edge.run # Run headless $ python main.py --listen 0.0.0.0 --port 8188 # Trigger a workflow from your app POST https://comfy.example.com/prompt { "prompt": { ...workflow JSON... } } Why teams self-host ComfyUI Maximum flexibility per GPU dollar, with no per-image bills. Any diffusion model SDXL, FLUX, SD3, AnimateDiff, video models — if it has a checkpoint, ComfyUI runs it. The most flexible diffusion runtime. GPU VMs from L4 to H100 Pick the right card for your model. SDXL flies on an L4; FLUX wants an A10/A100; video models want H100. Sized to fit your workflow. Checkpoints + LoRAs in S3 Mount Edge Storage as the `models/` directory. Checkpoints, LoRAs, ControlNets, VAEs all centrally stored — share across multiple GPU VMs. Headless API for production ComfyUI exposes a REST API for triggering workflows. Pair with a small Node/Python service for queue management and you have a production image-gen pipeline. Custom nodes welcome The ComfyUI ecosystem is huge — IPAdapter, ControlNet, AnimateDiff, custom samplers. All install via `git clone` into `custom_nodes/`. Per-image bills, gone Replicate, fal.ai, Together charge per image. An Edge GPU VM running ComfyUI is one fixed monthly fee — generate millions of images for the same bill. Reference architecture How ComfyUI maps to Edge GPU VM(s) for inference, S3 for shared model weights, CDN for delivery of finished images. Add a small queue service for production volume. Compute (GPU) ComfyUI on a GPU VM, scaled horizontally for throughput Storage S3-compatible bucket for checkpoints, LoRAs, outputs CDN Serves generated images globally with image optimisation Image Optimization On-the-fly resize/format conversion of generated outputs DNS Anycast DNS for `comfy.example.com` (admin) and `cdn.example.com` (outputs) Indicative cost ~50k SDXL generations / month Replicate (SDXL) ~$200–500/mo fal.ai (SDXL) ~$150–400/mo Edge GPU VM (L4) flat fee Edge wins decisively as volume grows past the GPU's monthly cost. Common questions How does this compare to Replicate / fal.ai? Cheaper per image at scale, more flexible (any custom workflow you can build in the UI), and your prompts/outputs stay private. Trade-off: you handle scaling and queue management — but for steady-volume workloads it pays back fast. How do I expose it as an API to my app? Run ComfyUI in `--listen` mode behind the Edge CDN. Your app POSTs workflow JSON to `/prompt`; ComfyUI returns a job ID; poll for completion or use the WebSocket. Lots of community wrappers exist. How do I share models across multiple GPUs? Mount Edge Storage as the `models/` directory on every ComfyUI VM. Adding a new GPU is then just spinning up a VM — no model copying. What about NSFW / safety filters? ComfyUI doesn't enforce filters by default — that's your call as the operator. If you're building a public product, add a moderation step (CLIP-based classifier or external API) into the workflow. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Docker Run any container on global VMs Kubernetes k3s and full k8s on real VMs, no control-plane fees Next.js Self-host Next.js without the lock-in Nuxt Vue-powered SSR on global VMs Generate images on your terms Start free. Compute team can size the right GPU for your workflow. Start free Talk to an engineer --- ### Self-host Directus on Edge | Instant API over any database URL: https://edge.network/solutions/directus/ Markdown: https://edge.network/solutions/directus.md JSON: https://edge.network/json/solutions/directus.json _Run Directus on Edge — Node.js on real VMs, S3-compatible file library backed by Edge Storage, global CDN for the API. Wrap any SQL database with a polished admin app and headless API._ For Directus Directus on Edge, any database, instant API Wrap any SQL database with a polished admin app and a headless API. Self-host on a real VM, store files in S3-compatible Edge Storage, deliver globally through the Edge CDN. Start free Read the deploy guide # .env — Directus + Edge Storage DB_CLIENT="pg" DB_HOST="127.0.0.1" DB_DATABASE="directus" STORAGE_LOCATIONS="edge" STORAGE_EDGE_DRIVER="s3" STORAGE_EDGE_ENDPOINT="https://storage.edge.run" STORAGE_EDGE_BUCKET="directus-files" STORAGE_EDGE_KEY="..." STORAGE_EDGE_SECRET="..." # Run as a systemd service $ sudo systemctl enable --now directus Why Directus teams pick Edge Real database access, real file storage, real network — without paying SaaS multiples for any of it. Bring your own SQL database Postgres, MySQL, MariaDB, SQLite, MS SQL — Directus mirrors the schema and exposes a REST + GraphQL API instantly. Your data stays yours. S3-compatible file library Configure the Directus file driver with Edge Storage credentials. Uploads, generated thumbnails and exports all live in a CDN-fronted bucket. On-the-fly image transforms Directus has its own asset transformation API; for very high-volume sites you can offload to Edge Image Optimization at the CDN. Flows + webhooks at scale Run automation flows on the same VM; long-running ones can fan out to a worker VM via private networking. No serverless time-outs to dance around. Global CDN for the API Front the REST/GraphQL endpoints through the Edge CDN. Cache GETs aggressively, mutate at origin, no egress on the way out. Agent-deployable The Edge agentic API can stand up a Directus instance, point a domain at it, and configure the file storage bucket — all from a single prompt. Reference architecture How Directus maps to Edge A small VM running Directus + Postgres, files in object storage, and the global CDN out front. Compute Runs Directus (Node.js) + your existing or new SQL database Storage S3-compatible file driver for the asset library CDN Caches public API responses and asset URLs globally Image Optimization Optional: replace Directus transforms with edge processing DNS Anycast DNS for the API subdomain Shield Guards public form endpoints with a humanity-score check — free Assist AI answers on the sites your Directus data powers # Front-end → Directus on Edge import { createDirectus, rest } from '@directus/sdk' const directus = createDirectus( 'https://cms.example.com' ).with(rest()) # Cached via Edge CDN const articles = await directus.request( readItems( 'articles' , { fields: ['*'] }) ) Common questions Self-hosted vs Directus Cloud? Directus Cloud is the official managed service. Self-hosting on Edge gives you root, custom extensions, and full control over your database — at the cost of running a VM yourself. Can I point Directus at an existing database? Yes — that's arguably the killer feature. Directus introspects your existing schema and gives you an admin UI and API on top, without forcing migrations. How do I run flows and webhooks? On the same VM for low-volume use, or split into a worker VM that handles flows separately. Both connect to the same database via Edge's private networking. How do I deploy custom extensions? Mount your extensions folder, ship via git, restart the systemd service. Or build a Docker image and use our Docker stack page for a container-based deploy. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Guard public form endpoints with a humanity-score check before they write. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Whatever site your Directus data powers, Assist answers from it. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Payload TypeScript-first headless CMS, Next.js-ready WooCommerce Self-host the world's most popular store Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Ship Directus on Edge Start free. Bring an existing database or scaffold a fresh project. Start free Talk to an engineer --- ### Self-host Ghost on Edge | Modern publishing without the cloud bill URL: https://edge.network/solutions/ghost/ Markdown: https://edge.network/solutions/ghost.md JSON: https://edge.network/json/solutions/ghost.json _Run Ghost on Edge — Node.js on real VMs, S3-compatible storage for media, global CDN with zero egress fees. The Substack alternative, on infrastructure you actually own._ For Ghost Modern publishing, self-hosted properly Run Ghost on a real VM with S3-compatible media storage and a global CDN. Newsletters, paid subscriptions, members — all the features of Ghost(Pro), on infrastructure you control. Start free Have us migrate it # bootstrap-ghost.sh npm install -g ghost-cli ghost install --db mysql --process systemd npm install ghost-storage-adapter-s3 # config.production.json — Edge Storage "storage": { "active": "s3" , "s3": { "endpoint": "https://storage.edge.run" , "bucket": "ghost-media" } } # Front it with the CDN $ edge cdn create blog.example.com ... Why publishers move to Edge All the polish of Ghost(Pro), none of the per-member pricing. A real publishing platform Posts, pages, members, newsletters, paid subscriptions and a beautiful editor — out of the box, all open source, no Substack tax. S3-compatible media storage Drop in the official S3 storage adapter and point it at Edge Storage. Image uploads, theme assets and exports live in a durable bucket. Image transforms on the CDN Ghost includes responsive image processing, but for high-volume sites you can hand off to Edge Image Optimization for AVIF/WebP at the edge. Bring your own email provider Wire Ghost up to Mailgun, Postmark, AWS SES or anything SMTP. Newsletters and member emails work the same as on Ghost(Pro). Global CDN, zero egress Front the public site through the Edge CDN. Member-only and admin routes fall through to your VM; everything else is cached worldwide. Predictable bills A small VM, a CDN deployment and a bucket — no per-member pricing surprises and no platform percentage on subscription revenue. Reference architecture How Ghost maps to Edge A standard Ghost stack — Node + MySQL on a VM — with media offloaded and the front-end cached at the edge. Compute Runs Ghost (Node.js) + MySQL on a VM, behind Nginx or Caddy Storage S3-compatible bucket for the `images` content adapter and exports CDN Caches the public site globally; admin and member-only routes hit origin Image Optimization Optional: replace Ghost's built-in resize with edge transforms DNS Anycast DNS for the apex, www and any newsletter sending subdomains Shield Protects member signup and newsletter forms from bot floods — free Assist Answers reader questions from your posts and pages — one script tag Indicative cost Newsletter + paid memberships ~10k members, weekly newsletter, ~50k monthly site visits Substack (10% of revenue) $$$ % Ghost(Pro) Creator ~$50–100 Edge (VM + CDN + Storage + Mailgun) ~$25–45 Indicative figures. Email volume affects bills more than hosting at this scale. Common questions Self-hosted Ghost vs Ghost(Pro)? Same software, different host. Ghost(Pro) is the official managed service (which funds Ghost development). Self-hosted gives you root access, custom plugins via the Admin API, and predictable bills — at the cost of running a VM yourself. How do members and Stripe payments work? Identical to Ghost(Pro). You connect your own Stripe account, set tiers and prices in the admin, and Ghost handles checkout, gating and recurring billing. Edge has no involvement in the money side. Where do email newsletters go? Plug Ghost into Mailgun (Ghost's recommended provider) or any SMTP service for transactional email. Newsletter sending happens directly between Ghost and your email provider — no traffic through Edge. How do I deploy a Ghost theme? Either zip-upload via the admin, or commit themes alongside Ghost in your repo and pull on deploy. The bootstrap script handles install, theme placement and starting the systemd service. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Keeps bots out of member signup and newsletter forms. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers reader questions from your posts — fewer "where do I manage my subscription?" emails. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Statamic Flat-file Laravel CMS, zero database drama Craft CMS Premium PHP CMS for design-led teams Strapi The leading open-source headless CMS Directus Instant API over any SQL database Own your publication Start free. Migrate from Substack or stand up a fresh Ghost site — we'll help with the bootstrap. Start free Have us migrate it --- ### Self-host Medusa on Edge | Modern headless commerce, Node.js-native URL: https://edge.network/solutions/medusa/ Markdown: https://edge.network/solutions/medusa.md JSON: https://edge.network/json/solutions/medusa.json _Run Medusa on Edge — Node.js + Postgres + Redis on real VMs, S3-compatible media via the file plugin, global CDN for the storefront and admin. The open-source Shopify alternative for developers._ For Medusa Medusa on Edge, the Shopify alternative for devs Self-host the modern open-source commerce stack on real VMs. Node.js + Postgres + Redis, S3-compatible product imagery, global CDN — your storefront, your code, your data. Start free See the Next.js storefront page # medusa-config.js — file plugin (1.x) module.exports = { plugins: [ { resolve: 'medusa-file-s3' , options: { s3_url: 'https://cdn.example.com', bucket: 'medusa-assets', endpoint: 'https://storage.edge.run', }, }, ], } # Provision the VM $ edge compute create --plan small ... Why Medusa teams pick Edge A real VM means Medusa runs the same as on your laptop — and pairs naturally with our existing JS stack pages. Node.js + Postgres + Redis A small VM runs the entire core stack. Scale Postgres and Redis to dedicated VMs via private networking when you grow. S3 file plugin Wire `medusa-file-s3` (or the AWS S3 module in Medusa 2.x) to Edge Storage. Product imagery and uploads land in a CDN-fronted bucket. Storefront, your framework Medusa is API-first. Pair the backend with a Next.js, Nuxt or Astro storefront on its own Edge VM (or static-host it from Storage). Global CDN for the API and shop Cache the catalogue endpoints aggressively at the Edge CDN. Cart and checkout calls fall through to your origin region. Bring your own payments Stripe, PayPal, Klarna, Adyen — all the official payment provider modules work the same as on Medusa Cloud or your laptop. Agent-deployable "Deploy a Medusa store to shop.example.com" — the Edge agentic API can stand up the VM, DB, file bucket and storefront in one go. Reference architecture How Medusa maps to Edge Medusa core as the API origin, Postgres and Redis on the same or adjacent VMs, your storefront framework of choice on its own VM or in Storage. Compute Runs Medusa core (Node.js) + Postgres + Redis on a VM Storage S3-compatible bucket for product imagery and downloadable goods CDN Caches the public storefront, catalogue API and asset URLs Image Optimization Optional: replace built-in resizing with edge transforms DNS Anycast DNS for `shop.`, `cms.` and `admin.` subdomains Shield Scores checkout and signup calls from the storefront — free Assist Answers shipping, stock and returns questions from storefront content # Next.js storefront → Medusa on Edge import Medusa from '@medusajs/medusa-js' const medusa = new Medusa({ baseUrl: 'https://api.shop.example.com' , maxRetries: 3, }) # Cached via Edge CDN const { products } = await medusa.products.list() Common questions Medusa 1.x or 2.x? Both run cleanly on Edge. 2.x is the modular architecture (recommended for new projects); 1.x is fine if you already have a stack you're happy with. Same hosting story for both. How does this compare to Medusa Cloud? Same software, you control the host. Self-hosting on Edge gives you predictable bills at any scale, root access, and the ability to colocate storefront and core on the same private network. Which storefront framework should I use? Whichever you prefer — Medusa's starter is Next.js, but the API works with anything. We have stack pages for Next.js, Nuxt, SvelteKit, Astro and more. How do I scale beyond a single VM? Move Postgres and Redis to dedicated VMs over private networking, run the storefront on its own VM(s), and use the CDN to absorb spike traffic. The same architecture pattern as a hyperscaler — without the bill. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Score checkout and signup calls from your storefront before they hit Medusa. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Shipping, stock and returns — answered from your storefront content before support hears about it. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront PostgreSQL Self-hosted Postgres on dedicated NVMe Ship Medusa on Edge Start free. Bring an existing Medusa store or scaffold a new one with the official starter. Start free Talk to an engineer --- ### Self-host MongoDB on Edge | Document store with replica sets URL: https://edge.network/solutions/mongodb/ Markdown: https://edge.network/solutions/mongodb.md JSON: https://edge.network/json/solutions/mongodb.json _Run MongoDB on Edge — Community Server on real VMs with NVMe, replica sets across regions over private networking, and `mongodump` archives to S3-compatible Edge Storage. Atlas-class infrastructure without Atlas pricing._ For MongoDB MongoDB on Edge, Atlas-class without the price Self-hosted MongoDB Community on dedicated NVMe, replica sets across Edge VMs, archives to S3-compatible storage. Same Mongo you know, on infrastructure you actually own. Start free Have us run it # Provision a 3-node replica set $ edge compute create --plan db-medium \ --count 3 --script ./bootstrap-mongo.sh # mongod.conf — replica set + bind net: bindIp: 10.0.0.0/8 replication: replSetName: rs0 # Initialise from one node $ mongosh --eval "rs.initiate(...)" # Nightly archive → Edge Storage $ mongodump --archive --gzip | \ aws s3 cp - s3://mongo-backups/$(date +%F).gz \ --endpoint storage.edge.run Why Mongo teams pick Edge All the document-DB ergonomics, none of the Atlas markup. NVMe for hot working sets WiredTiger thrives on real disk. Dedicated NVMe on every Edge VM keeps the working set hot and the p99 sane. Replica sets across VMs Three-node replica sets across separate Edge VMs over private networking. Automatic failover, no Atlas premium for the privilege. mongodump → S3 Schedule `mongodump --archive --gzip` to Edge Storage, restore with `mongorestore`. Cheap, durable, no per-snapshot fees. Atlas Search alternatives Run native text indexes for simple cases, or stand up MeiliSearch / Elasticsearch on a separate VM if you need full-text. Your call, no platform lock-in. Community or Enterprise MongoDB Community Server runs cleanly. If you have an Enterprise licence (LDAP, encryption-at-rest, audit), that runs too — same install pattern. No per-IOPS Atlas surprise Atlas M30 + 500GB storage + IOPS provisioning is ~$700/month. The same workload on a 3-node Edge replica set is a fraction of that — same Mongo, no markup. Reference architecture How Mongo maps to Edge Three-node replica set, NVMe per node, archives to a bucket. Standard Mongo ops, modern infrastructure. Compute Three Mongo VMs forming a replica set, NVMe data directory on each Storage mongodump archives + oplog snapshots to a bucket for PITR DNS Anycast DNS for `db.example.com` (round-robin or primary-aware) Compute (search) Optional MeiliSearch / Elasticsearch VM if you need real text search # Connect from your app MONGO_URI="mongodb://mongo-1:27017,mongo-2:27017,mongo-3:27017/app?replicaSet=rs0" # Standard driver code const client = new MongoClient(process.env.MONGO_URI) const db = client.db('app') const users = db.collection('users') # Sub-ms over private networking { acknowledged: true, insertedId: ObjectId(...) } Common questions How does this compare to Atlas? Cheaper (no per-IOPS billing, no per-snapshot fees, no inter-AZ data transfer), and you keep root. Trade-off: you handle backups, upgrades and replica-set provisioning — or our Expert Services team can. Can I use the official drivers unchanged? Yes — point your driver at the replica-set hostnames and you're away. Same Mongo wire protocol, same connection strings, same client libraries. What about backups and PITR? Combine `mongodump` to Edge Storage on a schedule with oplog tailing for point-in-time recovery. There are several open-source tools (e.g. Percona Backup for MongoDB) that automate this. Sharding? Yes — config servers, mongos routers and shards are all just more VMs. Spread them across regions over private networking. We have customers running multi-TB sharded clusters this way. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Outline Team wiki you actually own BookStack Open-source documentation platform Plausible Privacy-first analytics, self-hosted Umami Lightweight, cookie-free analytics Move Mongo to Edge Start free. Migrate from Atlas or stand up a fresh replica set — Expert Services can plan the cutover. Start free Have us migrate it --- ### Self-host MySQL or MariaDB on Edge | Real VMs, real performance URL: https://edge.network/solutions/mysql/ Markdown: https://edge.network/solutions/mysql.md JSON: https://edge.network/json/solutions/mysql.json _Run MySQL or MariaDB on Edge — dedicated NVMe storage, binary log shipping to S3-compatible Edge Storage, replication over private networking. The classic LAMP database, on infrastructure you actually own._ For MySQL / MariaDB MySQL on Edge, no IOPS surprises Self-hosted MySQL or MariaDB on dedicated NVMe, with binlog shipping to S3-compatible storage and replication over private networking. The classic LAMP database, modernised. Start free Have us run it # Provision a MySQL VM with NVMe $ edge compute create \ --image ubuntu-24-04 --plan db-medium \ --script ./bootstrap-mysql.sh # my.cnf — binlog + S3 archive [mysqld] log_bin = /var/lib/mysql/binlog expire_logs_days = 7 innodb_buffer_pool_size = 12G # Nightly dump → Edge Storage $ mysqldump --all-databases | \ aws s3 cp - s3://mysql-backups/$(date +%F).sql \ --endpoint storage.edge.run Why MySQL teams pick Edge Real disk, real RAM, real network — the three things every MySQL workload depends on. NVMe storage with no IOPS bills Real local NVMe on every VM. No EBS-style burst credits, no per-IOPS provisioning, no surprise throttling on busy nights. Replication, your way Standard async replication, semi-sync, or group replication on separate VMs over private networking. Same MySQL features as RDS, none of the licensing locks. Binary log shipping to S3 Pipe binlogs to Edge Storage with `mysqlbinlog` or Percona's tools for point-in-time recovery — without the per-GB-month snapshot bills. MariaDB drop-in if you prefer Same install pattern, swap the binaries. Use Percona Server, MariaDB or vanilla MySQL — your call, no platform lock. Plugins and engines InnoDB, MyRocks, Spider — install whatever you compile. Sysbench-tune to your workload without permission from a console. No per-instance-hour markup A db.r6g.large RDS MySQL is ~$200/month before storage. The same workload on an Edge VM with bigger NVMe is a small fraction of that. Reference architecture How MySQL maps to Edge Primary VM with NVMe, optional async replica, binlogs and dumps to object storage. Boring, fast, predictable. Compute MySQL/MariaDB on a VM with NVMe data directory and ProxySQL pooler Storage Binary log archive bucket + nightly logical/physical dumps DNS Anycast DNS for `db.example.com` pointing at the primary VM Compute (replica) Optional async replica on a second VM via private networking # App config (Laravel / Django / etc.) DB_HOST=db.private.edge.network DB_PORT=3306 DB_DATABASE=app DB_USERNAME=app DB_PASSWORD=... # Sub-millisecond on the private network $ mysql -e "SELECT 1" Query OK, 1 row in 0.4ms Common questions How does this compare to RDS MySQL / Aurora? Cheaper (no per-instance-hour, no per-GB snapshot fees) and faster on like-for-like hardware. Trade-off: you handle backups, upgrades and HA — or our Expert Services team can. MySQL or MariaDB? Either. MariaDB is a drop-in replacement and slightly more open-source-friendly. Most apps that say "MySQL" run unchanged on MariaDB. Pick what your team knows. How do I do HA? Async replication to a hot standby for read scaling, semi-sync or group replication if you need synchronous. Pair with Orchestrator or MaxScale for automated failover. What about backups? Logical: `mysqldump` to Edge Storage. Physical: Percona XtraBackup or MariaDB Backup with binlog shipping. Both give point-in-time recovery to a bucket without RDS' markup. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Redis In-memory cache and queue, your way MongoDB Self-hosted document store with replica sets Outline Team wiki you actually own BookStack Open-source documentation platform Move MySQL to Edge Start free. Migrate from RDS or stand up a fresh primary — Expert Services can plan the cutover. Start free Have us migrate it --- ### Self-host n8n on Edge | Workflow automation without per-execution bills URL: https://edge.network/solutions/n8n/ Markdown: https://edge.network/solutions/n8n.md JSON: https://edge.network/json/solutions/n8n.json _Run n8n on Edge — Node.js + Postgres on real VMs, queue mode for scale, S3-compatible storage for binary data. The Zapier alternative without per-execution bills._ For n8n n8n on Edge, no per-execution bill Self-host the workflow automation platform on a real VM with S3-compatible storage and a global CDN. Run unlimited executions, keep your credentials on your network. Start free Pair with local AI # docker-compose.yml — n8n + Postgres services: n8n: image: n8nio/n8n:latest environment: DB_TYPE: postgresdb N8N_HOST: n8n.example.com N8N_PROTOCOL: https N8N_BINARY_DATA_MODE: s3 N8N_AVAILABLE_BINARY_DATA_MODES: filesystem,s3 postgres: { image: postgres:16 } # Front the editor with the CDN $ edge cdn create n8n.example.com ... Why teams self-host n8n Run automation at scale without a per-execution metre running. Hundreds of integrations Connect to 400+ services out of the box. Custom HTTP, webhook triggers, AI nodes — n8n does what Zapier and Make do, on your infrastructure. Node.js + Postgres on a VM A small VM runs the editor, scheduler and worker. Scale to queue mode (Redis + worker VMs) when execution volume grows. Binary data to S3 Configure n8n to push binary data (file attachments, exports, generated PDFs) to Edge Storage instead of local disk. Workflows stay portable. Credentials stay on your network API keys for Stripe, OpenAI, Salesforce, Slack — they all live in your VM's encrypted credential store. Nothing transits a third-party cloud. Webhooks behind the CDN Let inbound webhooks hit the Edge CDN, which forwards to your n8n VM. Caching is bypassed for webhook URLs but you get DDoS protection for free. No per-execution bills n8n Cloud charges per workflow execution. Self-hosted on Edge is one fixed monthly bill — run a million executions if you like. Reference architecture How n8n maps to Edge Single VM for low-volume teams, queue mode (Redis + worker VMs) for high-volume — all over private networking. Compute n8n (Node.js) + Postgres on a VM, optional Redis + workers for scale Storage S3-compatible bucket for workflow binary data and backups CDN Optional: webhook ingestion behind the CDN for DDoS protection DNS Anycast DNS for `n8n.example.com` # Queue mode for scale EXECUTIONS_MODE=queue QUEUE_BULL_REDIS_HOST=cache.private.edge.network # Spin up worker VMs $ edge compute create --plan small \ --count 3 --script ./n8n-worker.sh ✓ Main + 3 workers, scaling horizontally Common questions How does this compare to n8n Cloud / Zapier? n8n Cloud is per-execution; Zapier is per-task. Self-hosted on Edge is flat-fee. The trade-off is one VM to maintain — but the credential security and unlimited execution count usually justify it for any serious automation use. How does it scale? Single-VM "main mode" handles thousands of executions per day. For more, switch to queue mode: main process triggers, Redis queue, worker VMs execute. All Edge VMs over private networking. What about workflow backups? Workflows live in Postgres. Nightly `pg_dump` to Edge Storage covers them, plus n8n's built-in version-control feature can sync them to a git repo. Can I use AI nodes? Yes — n8n has first-class nodes for OpenAI, Anthropic, Ollama, etc. Pair with our Ollama or vLLM stack pages to keep the inference on Edge too. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Vaultwarden Bitwarden-compatible password manager Ollama Run open LLMs on your own GPUs vLLM Production-grade LLM serving llama.cpp Quantised LLM inference, CPU or GPU Run n8n on your terms Start free. Move off Zapier or Make and unlimited the executions. Start free Talk to an engineer --- ### Self-host Outline on Edge | Team wiki you actually own URL: https://edge.network/solutions/outline/ Markdown: https://edge.network/solutions/outline.md JSON: https://edge.network/json/solutions/outline.json _Run Outline on Edge — Node.js + Postgres + Redis on real VMs, S3-compatible file uploads, global CDN out front. The polished team wiki without sending your knowledge base to someone else's cloud._ For Outline Outline on Edge, a wiki you own Self-host the polished team wiki on a real VM with S3-compatible attachments and a global CDN. Your team\'s knowledge stays on your infrastructure — and the bill stays flat. Start free Have us run it # docker-compose.yml — Outline + deps services: outline: image: outlinewiki/outline:latest env_file: .env postgres: { image: postgres:16 } redis: { image: redis:7 } # .env — Edge Storage backend AWS_S3_UPLOAD_BUCKET_NAME=outline AWS_S3_UPLOAD_ENDPOINT=https://storage.edge.run AWS_S3_FORCE_PATH_STYLE=true Why teams self-host Outline A flat monthly bill, your data on your infrastructure, and an editor that doesn't feel like a step down from Notion. Notion-quality, self-hosted A polished collaborative editor, slash commands, real-time editing — without your team's knowledge base living on someone else's cloud. S3-compatible attachments Wire Outline's file storage to Edge Storage. Document attachments, images and exports all live in a durable, CDN-fronted bucket. SSO via OIDC / Google / Microsoft Plug into your existing identity provider — Google Workspace, Microsoft Entra, Authelia, Keycloak. No paid SSO tax. Full-text search included Postgres-backed search out of the box. Faster than the Notion search you're used to, and works without sending queries to a third party. Global CDN out front Edge CDN serves the static app shell and public docs globally. Authenticated traffic falls through to your origin VM. Notion is per-seat. Outline isn't. Notion business is ~$15/user/month. Outline self-hosted on Edge is one fixed monthly bill regardless of team size. Reference architecture How Outline maps to Edge Outline + Postgres + Redis on a single VM, attachments in object storage, CDN out front. One small VM is enough for most teams. Compute Outline (Node.js) + Postgres + Redis on a VM Storage S3-compatible bucket for document attachments and exports CDN Caches the static app shell and any public knowledge bases DNS Anycast DNS for `wiki.example.com` Shield Protects public share pages and login from bot floods — free Assist Answers questions from your public knowledge bases — one script tag Indicative cost A 50-person team wiki Notion Business (50 seats) ~$750/mo Outline Cloud (50 seats) ~$500/mo Edge (1 small VM + Storage) ~$15/mo Cost stays flat as the team grows. Common questions How does this compare to Outline Cloud or Notion? Outline Cloud is per-seat, Notion is per-seat — Edge self-hosting is a flat monthly cost regardless of team size. The trade-off is one VM to maintain. How does SSO work? Outline supports OIDC, Google Workspace, Microsoft, and Slack out of the box. Any of those work the same as on Outline Cloud — they're configured in environment variables on your VM. What about realtime collaboration? Built in — Outline uses Y.js + WebSockets for collaborative editing. Pin sticky sessions at the CDN if you scale beyond one VM. How do I back up the knowledge base? Snapshot Postgres to Edge Storage on a schedule, plus the Storage bucket already lives in object storage. Two-line cron and a `pg_dump`. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Protects public share pages and login from scrapers and bot floods. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers team and visitor questions from your public knowledge bases. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → BookStack Open-source documentation platform Plausible Privacy-first analytics, self-hosted Umami Lightweight, cookie-free analytics n8n Self-hosted workflow automation Stand up your wiki Start free. Migrate from Notion, Confluence or Outline Cloud — Expert Services can help. Start free Have us migrate it --- ### Self-host Plausible Analytics on Edge | Privacy-first, GDPR-friendly URL: https://edge.network/solutions/plausible/ Markdown: https://edge.network/solutions/plausible.md JSON: https://edge.network/json/solutions/plausible.json _Run Plausible Analytics on Edge — Elixir + Postgres + ClickHouse on real VMs, global CDN for the script, no cookies, no GDPR consent banners. The privacy-first analytics platform, on infrastructure you actually own._ For Plausible Plausible on Edge, analytics with no consent banner Self-host the privacy-first analytics platform on a small VM with the tracking script on a global CDN. GDPR-friendly, cookie-free, and no per-pageview surprise bills. Start free Read the deploy guide # docker-compose.yml — Plausible CE services: plausible: { image: plausible/community-edition } postgres: { image: postgres:16 } clickhouse: { image: clickhouse/clickhouse-server } # In your site <head> <script defer data-domain="example.com" src="https://analytics.example.com/js/script.js"></script> # Script served from Edge CDN, globally 200 OK • 1.2 KB • cache-hit Why teams self-host Plausible Real privacy, real data ownership, no per-pageview growth tax. No cookies, no consent banners Plausible doesn't use cookies or store any personal data. Self-hosted on Edge means visitor data never leaves your infrastructure. Elixir + Postgres + ClickHouse A small VM runs the whole stack. Scale ClickHouse to a dedicated VM via private networking when your traffic outgrows it. Tracking script on the CDN Serve `plausible.js` from the Edge CDN — global delivery, zero egress fees, faster than any third-party analytics script. Your data, your queries ClickHouse lives on your VM. Query it directly, export to BI tools, or feed it into your own data pipeline. No "premium tier" gating. Email reports, your SMTP Plug Plausible into your own SMTP (Postmark, Mailgun, AWS SES) for weekly reports. No platform email rate limits. No per-pageview pricing Plausible Cloud is ~$9 for 10k/month, scaling up. Self-hosted on Edge is one fixed monthly bill regardless of pageview volume. Reference architecture How Plausible maps to Edge Plausible CE on a small VM, tracking script delivered by the global CDN. Compute Plausible (Elixir) + Postgres + ClickHouse on a VM CDN Serves `plausible.js` globally and caches the dashboard shell Storage Optional: ClickHouse backups via `clickhouse-backup` to a bucket DNS Anycast DNS for `analytics.example.com` Indicative cost ~1M pageviews/month across sites Plausible Cloud Business ~$59/mo Fathom Pro ~$54/mo Edge (1 small VM) ~$15/mo Common questions How does this compare to Plausible Cloud? Same software, you control the host. Self-hosting on Edge gives you predictable bills (no per-pageview tier), data residency control, and the ability to query ClickHouse directly. Will I need to ask for cookie consent? No. Plausible is designed to comply with GDPR, CCPA and PECR without consent banners — it doesn't track individuals, store cookies, or collect personal data. How does it scale? Most sites are happy on a single VM. Heavy traffic? Move ClickHouse to a dedicated VM and put Plausible behind a load balancer. Standard Elixir/ClickHouse scaling, no platform-specific tricks. How do I migrate from Google Analytics? Plausible has an official GA importer that pulls historical data via the GA API. Run it once on a new VM, you're away. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Umami Lightweight, cookie-free analytics n8n Self-hosted workflow automation Vaultwarden Bitwarden-compatible password manager Ollama Run open LLMs on your own GPUs Stand up Plausible Start free. Move off GA or stand up a fresh analytics instance. Start free Talk to an engineer --- ### Self-host PostgreSQL on Edge | NVMe-backed Postgres without RDS markup URL: https://edge.network/solutions/postgresql/ Markdown: https://edge.network/solutions/postgresql.md JSON: https://edge.network/json/solutions/postgresql.json _Run PostgreSQL on Edge — dedicated NVMe storage, WAL archiving to S3-compatible Edge Storage, logical replication for HA, and zero per-IOPS surprises. The full Postgres experience, on infrastructure you actually own._ For PostgreSQL Postgres on Edge, without the RDS markup Self-hosted PostgreSQL on dedicated NVMe, with WAL archiving to S3-compatible storage and replication over private networking. Real performance, predictable bills, no managed-service guard rails. Start free Have us run it # Provision a Postgres VM with NVMe $ edge compute create \ --image ubuntu-24-04 --plan db-medium \ --script ./bootstrap-postgres.sh # pgbackrest.conf — WAL → Edge Storage [global] repo1-type=s3 repo1-s3-endpoint=storage.edge.run repo1-s3-bucket=postgres-wal repo1-s3-region=eu-west # Backup + verify $ pgbackrest --stanza=main backup ✓ archive-push, basebackup complete Why Postgres teams pick Edge All the Postgres features, none of the managed-service "you can't do that" answers. NVMe storage that doesn't throttle Real local NVMe on every Edge VM — no per-IOPS billing, no burst credits to track. Postgres is happy when its disk is happy. WAL archiving to S3 Pipe WAL segments to Edge Storage with `wal-g` or `pgbackrest` for point-in-time recovery — without the per-GB-month bills RDS charges for snapshots. Replication on private networking Run a primary + replicas on separate Edge VMs over private networking. No cross-AZ data transfer fees, no public-internet exposure. Any version, any extension Pin to whatever Postgres version you want. Install PostGIS, TimescaleDB, pgvector, pg_cron — anything that compiles, anything you compile yourself. Pgbouncer / PgCat included Run a connection pooler on the same VM (free) or a dedicated tiny one (cheap). No managed-service connection-limit panics. No per-instance-hour markup A db.r6g.large RDS instance is ~$220/month before storage. The same workload on an Edge VM with bigger NVMe is a small fraction of that — no licence fee. Reference architecture How Postgres maps to Edge Primary on a sized-to-fit VM, optional streaming replica, WAL archived to object storage. Standard Postgres ops, modern infrastructure. Compute Postgres + Pgbouncer on a VM, with NVMe for the data directory Storage WAL archive bucket + nightly basebackups for PITR DNS Anycast DNS for `db.example.com` — point it at the primary Compute (replica) Optional second VM as a streaming replica via private networking Indicative cost Mid-sized production DB ~4 vCPU, 16GB RAM, 500GB storage, daily backups, 100GB WAL/day RDS db.r6g.xlarge + storage + IOPS ~$500–800 Aurora equivalent ~$700–1,200 Edge (VM + Storage for WAL) ~$60–120 Indicative figures. Add a second VM for HA replication. Common questions How does this compare to RDS / Aurora? Cheaper (no per-instance-hour, no per-GB snapshot fees, no per-IOPS bills) and faster on like-for-like hardware (real NVMe). Trade-off: you handle backups, upgrades and HA — or our Expert Services team can. How do I do high availability? Streaming replication to a hot standby on a second VM, plus automated failover with Patroni or repmgr. Both work cleanly on Edge VMs over private networking. What about backups? Use `pgbackrest` or `wal-g` to ship WAL segments and basebackups to an Edge Storage bucket. Point-in-time recovery without paying RDS' premium for the privilege. Can I use it from other Edge resources? Yes — connect over private networking from your app VMs (Laravel, Django, Rails, Node.js, etc.). Latency is sub-millisecond, no egress fees between Edge resources. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → MySQL MySQL or MariaDB on real VMs Redis In-memory cache and queue, your way MongoDB Self-hosted document store with replica sets Outline Team wiki you actually own Run Postgres on your terms Start free. Migrate from RDS or stand up a fresh cluster — Expert Services can plan the cutover. Start free Have us migrate it --- ### Self-host Redis (or Valkey) on Edge | In-memory cache and queue URL: https://edge.network/solutions/redis/ Markdown: https://edge.network/solutions/redis.md JSON: https://edge.network/json/solutions/redis.json _Run Redis or Valkey on Edge — dedicated RAM on real VMs, AOF + RDB persistence to S3-compatible storage, replication over private networking. The cache, queue and key-value store you already use, on infrastructure you actually own._ For Redis / Valkey Redis on Edge, no per-hour cache fee Self-hosted Redis or Valkey on real RAM. AOF + RDB persistence to S3-compatible storage, replicas over private networking. The cache, queue and key-value store you already use — yours. Start free Read the deploy guide # Provision a Redis VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-redis.sh # redis.conf — persistence + bind bind 10.0.0.0/8 appendonly yes save 900 1 save 300 10 # Snapshot → Edge Storage (cron) $ aws s3 cp /var/lib/redis/dump.rdb \ s3://redis-snapshots/$(date +%F).rdb \ --endpoint storage.edge.run Why Redis users move to Edge Sub-millisecond cache, dedicated RAM, none of the surprise bills. Real RAM, real CPU A dedicated VM means Redis isn't fighting for cache or memory bandwidth with noisy neighbours. Sub-millisecond p99s without the Elasticache fees. AOF + RDB to S3 Run AOF for durability and snapshot RDB to Edge Storage on a schedule. Disaster recovery without paying for a hosted Redis just for the backup feature. Replicas + Sentinel Spin up replicas on separate Edge VMs over private networking, manage failover with Sentinel. Standard Redis HA, no proprietary plumbing. Cluster mode when you need it Redis Cluster across multiple VMs gives you sharding for huge keyspaces. Or stick with a single primary — most workloads never outgrow it. Redis or Valkey Same install pattern, swap the binary. Use Valkey if the licensing change matters to you, vanilla Redis otherwise. Both are first-class on Edge VMs. No per-hour cache markup Elasticache cache.r6g.large is ~$130/month. The same RAM on an Edge VM is a fraction of that — and you keep the keys. Reference architecture How Redis maps to Edge Primary on a small VM with plenty of RAM, optional replicas + Sentinel for HA, snapshots to object storage. Compute Redis (or Valkey) on a VM, optional Sentinel for HA Storage RDB snapshots and AOF rewrites archived to a bucket DNS Anycast DNS for `cache.example.com` pointing at the primary Compute (replica) Optional read replicas on private networking # From a Laravel / Rails / Node app REDIS_URL=redis://cache.private.edge.network:6379 # Standard client libs work unchanged await redis.set('user:42', JSON.stringify(user)) const cached = await redis.get('user:42') # Sub-ms over the private network PING → PONG (0.3ms) Common questions How does this compare to Elasticache / Memorystore? Cheaper (no per-hour cache fees), faster on like-for-like hardware (real CPU, real RAM), and you keep root access. Trade-off: you handle backups and Sentinel — or our Expert Services team can. Should I use Redis or Valkey? Functionally identical for almost all workloads. Use Valkey if the BSL/SSPL licence change in Redis 7.4+ is a concern; use Redis otherwise. Both are drop-in compatible. How do I do persistence? Combine AOF (every-write durability) with periodic RDB snapshots to Edge Storage. For pure-cache use cases, you can skip persistence entirely and treat the VM as ephemeral. How do I scale beyond one VM? Read scaling: spin up replicas on more VMs. Write scaling: Redis Cluster across multiple primaries. Both work over Edge's private networking with sub-millisecond latency. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → MongoDB Self-hosted document store with replica sets Outline Team wiki you actually own BookStack Open-source documentation platform Plausible Privacy-first analytics, self-hosted Run Redis on your terms Start free. Migrate from Elasticache or stand up a fresh cache. Start free Talk to an engineer --- ### Self-host Saleor on Edge | Python + GraphQL headless commerce URL: https://edge.network/solutions/saleor/ Markdown: https://edge.network/solutions/saleor.md JSON: https://edge.network/json/solutions/saleor.json _Run Saleor on Edge — Python (Django) on real VMs, Postgres, Redis and Celery workers, S3-compatible media storage, global CDN for the GraphQL API and storefront._ For Saleor Saleor on Edge, Python GraphQL commerce Self-host the modern Python + GraphQL commerce stack on real VMs. S3-compatible media, global CDN for the API, and a private network connecting Django, Postgres and Celery. Start free See the Django page # settings.py — S3 storage DEFAULT_FILE_STORAGE = 'storages.backends.s3.S3Storage' AWS_S3_ENDPOINT_URL = 'https://storage.edge.run' AWS_STORAGE_BUCKET_NAME = 'saleor-media' # Provision a VM $ edge compute create \ --image ubuntu-24-04 --plan medium \ --script ./bootstrap-saleor.sh # Front it with the CDN $ edge cdn create api.shop.example.com \ --origin https://<vm-ip> Why Saleor teams pick Edge All the platform plumbing of Saleor Cloud, on infrastructure that doesn't bill per request. GraphQL-first commerce A single, well-typed GraphQL endpoint for the entire store. Pair it with any front-end — Saleor's React storefront or your own Next.js app. Python / Django on real VMs Django + Gunicorn or Uvicorn on a sized-to-fit VM. Real CPU, real RAM, no per-request pricing — same as our standalone Django stack page. S3 storage backend Configure `django-storages` with Edge Storage for product imagery and downloadable goods. Standard Django plumbing, durable bucket. Celery workers without surprises Run async tasks (webhooks, email, exports) on the same VM or a dedicated worker VM. Backed by Redis on Edge Compute. Global CDN for the API Cache GraphQL GETs and storefront pages at the Edge CDN. Mutations and authenticated calls fall through to the origin Django app. Multi-channel ready Saleor's multi-channel feature works cleanly on a single host — different countries, currencies and warehouses, one Django process. Reference architecture How Saleor maps to Edge Saleor core (Django) + Postgres + Redis + Celery workers on one or two VMs, your storefront on its own VM or static-hosted from Storage. Compute Runs Saleor (Django) + Postgres + Redis + Celery on a VM Storage S3-compatible bucket via `django-storages` for media CDN Caches the GraphQL API responses and the storefront Image Optimization Optional: replace Saleor thumbnails with edge transforms DNS Anycast DNS for `api.`, `dashboard.` and `shop.` subdomains Shield Guards signup and checkout mutations from bots — free Assist A storefront sales assistant grounded in your own pages # Storefront → Saleor GraphQL on Edge const query = gql` query { products(first: 12) { edges { node { id name slug pricing { ... } } } } } ` # Cached at Edge CDN const data = await fetch('https://api.shop.example.com/graphql/', { method: 'POST', body: JSON.stringify({ query }) }) Common questions How does this compare to Saleor Cloud? Same software, you control the host. Self-hosting on Edge gives you predictable bills, root access, and the ability to colocate the Django app, database and storefront on the same private network. Which storefront should I use? The official React Storefront is a solid Next.js starter. You can also bring your own Vue, Svelte or Astro front-end — any framework that can hit a GraphQL endpoint. How do I deploy code updates? Standard Django deploy: pull, `pip install`, `manage.py migrate`, restart. Wrap it in a CI step or systemd path unit. Or build a Docker image and use our Docker stack page for a container-based deploy. What about payments? Saleor has official payment plugins for Stripe, Adyen, Braintree and authorize.net. They all work as documented — payment processing is direct between Saleor and the gateway, no Edge involvement. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Guard signup and checkout mutations from bots with one check in your storefront. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Give your storefront a sales assistant grounded in your own pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Shopify Hydrogen Self-host your Shopify storefront PostgreSQL Self-hosted Postgres on dedicated NVMe MySQL MySQL or MariaDB on real VMs Redis In-memory cache and queue, your way Ship Saleor on Edge Start free. Bring an existing Saleor instance or scaffold one fresh. Start free Talk to an engineer --- ### Self-host Strapi on Edge | The leading open-source headless CMS URL: https://edge.network/solutions/strapi/ Markdown: https://edge.network/solutions/strapi.md JSON: https://edge.network/json/solutions/strapi.json _Run Strapi on Edge — Node.js on real VMs, your choice of database, S3-compatible Edge Storage as the upload provider, and a global CDN for the API and assets._ For Strapi Strapi on Edge, the headless API stack Self-host the leading open-source headless CMS on real VMs. S3-compatible media storage, global CDN for the API and uploads, zero egress fees on the way to your front-end. Start free Read the deploy guide # config/plugins.js — S3 upload provider module.exports = ({ env }) => ({ upload: { config: { provider: 'aws-s3' , providerOptions: { endpoint: 'https://storage.edge.run' , params: { Bucket: env('EDGE_BUCKET') }, }, }, }, }) # Provision the VM $ edge compute create --plan small ... Why Strapi teams pick Edge A real Node host, a global delivery network, and a media bucket — the three things every Strapi production setup needs. Node.js + your database, your way Strapi runs on a small VM with Postgres, MySQL, MariaDB or SQLite. Pick the DB you already operate; Edge stays out of the way. S3 upload provider Use the official `@strapi/provider-upload-aws-s3` plugin pointing at Edge Storage. Media library uploads land in a durable, CDN-fronted bucket. Image transforms at the edge Skip Strapi's built-in image processing for high-volume use cases — let Edge Image Optimization generate responsive variants from a URL. Global CDN for the API Front the REST and GraphQL endpoints through the Edge CDN. Cache public content responses, fall through for authenticated requests. Pairs with your front-end Built to feed Next.js, Nuxt, SvelteKit, Astro and mobile apps. Run the front-end on its own Edge VM or static-host it from Edge Storage. Agent-deployable Tell the Edge agentic API to deploy a Strapi instance to a domain — VM, DNS, CDN and SSL all wired up. Reference architecture How Strapi maps to Edge Strapi as the API origin, your front-end (Next.js / Nuxt / Svelte) on a separate VM or in Storage, both fronted by the CDN. Compute Runs Strapi (Node.js) + your database on a VM Storage S3-compatible upload provider for the media library CDN Caches the public REST/GraphQL API and uploaded media Image Optimization Optional: replace Strapi image processing with edge transforms DNS Anycast DNS for `cms.example.com` and `app.example.com` Shield Scores submissions hitting public Strapi endpoints — free Assist AI answers on whatever frontend your Strapi content powers # Next.js front-end → Strapi API on Edge const posts = await fetch( 'https://cms.example.com/api/posts' , { next: { revalidate: 60 } } ).then(r => r.json()) # Image URL via Edge Image Optimization <img src= `https://cdn.example.com/${post.cover.url}?w=1200&fm=webp` /> Common questions {faqs.map((faq) => ( {faq.q} {faq.a} ))} Ship Strapi on Edge Start free. Bring an existing Strapi instance or scaffold one fresh. Start free Talk to an engineer } --- ### Self-host Umami Analytics on Edge | Lightweight, cookie-free URL: https://edge.network/solutions/umami/ Markdown: https://edge.network/solutions/umami.md JSON: https://edge.network/json/solutions/umami.json _Run Umami Analytics on Edge — Node.js + Postgres on a tiny VM, tracking script on the global CDN, no cookies. Privacy-first analytics with zero per-pageview bills._ For Umami Umami on Edge, analytics for $5/mo Self-host the lightweight, cookie-free analytics platform on a tiny VM with the tracking script on a global CDN. Unlimited sites, unlimited events, one fixed monthly fee. Start free For agencies # Provision a tiny Umami VM $ edge compute create \ --image ubuntu-24-04 --plan tiny \ --script ./bootstrap-umami.sh # In each site <head> <script defer data-website-id="abc-123" src="https://umami.example.com/script.js"></script> # Front it with the CDN $ edge cdn create umami.example.com \ --origin https://<vm-ip> ✓ Tracking globally, ~$5/month Why teams self-host Umami The lightest analytics stack that still does the job. Tiny script, tiny footprint Sub-2KB tracking script and a Node.js + Postgres backend that runs comfortably on the smallest Edge VM. Almost free to operate. No cookies, no PII Umami doesn't use cookies or collect personal data. GDPR / CCPA / PECR friendly without a consent banner. Script on the global CDN Serve `script.js` from the Edge CDN globally — fast for visitors anywhere, no third-party domain in your network requests. Multi-site by default One Umami instance tracks unlimited websites. Perfect for agencies running analytics across many client sites. Dashboards + custom events Real-time dashboard, page-level analytics, custom event tracking and goal conversion — everything most teams need from analytics. Free instead of per-event Umami Cloud is ~$20+ for 100k events. Self-hosted on Edge is one $5–10 VM serving unlimited events across unlimited sites. Reference architecture How Umami maps to Edge Umami + Postgres on the smallest Edge VM, tracking script on the global CDN. Compute Umami (Node.js) + Postgres on a small VM CDN Serves the tracking script globally Storage Optional: nightly Postgres dumps to a bucket DNS Anycast DNS for `umami.example.com` # Track a custom event window.umami.track('signup', { plan: 'pro' }) # Or via the API POST https://umami.example.com/api/send { "website": "abc-123", "name": "checkout_complete", "data": { "value": 49.99 } } Common questions How does this compare to Umami Cloud? Same software, you control the host. Self-hosting on Edge is a flat fee with no per-event bills, and data stays on your infrastructure. Umami or Plausible? Umami is lighter and simpler (Node + Postgres). Plausible is richer (Elixir + ClickHouse, more advanced reports). For most small-to-medium sites Umami is plenty. Can I run it for clients? Absolutely — multi-site is built in. Add each client domain to one Umami instance, share dashboard access, send branded weekly reports. Agency-friendly out of the box. How small can the VM be? For under ~500k events/month, the smallest Edge VM is fine. Postgres tuning matters more than raw CPU at that scale. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → n8n Self-hosted workflow automation Vaultwarden Bitwarden-compatible password manager Ollama Run open LLMs on your own GPUs vLLM Production-grade LLM serving Stand up Umami Start free. Run analytics for unlimited sites on a $5 VM. Start free Talk to an engineer --- ### Self-host Vaultwarden on Edge | Bitwarden-compatible password manager URL: https://edge.network/solutions/vaultwarden/ Markdown: https://edge.network/solutions/vaultwarden.md JSON: https://edge.network/json/solutions/vaultwarden.json _Run Vaultwarden on Edge — Rust + SQLite/Postgres on a tiny VM, S3-compatible attachments, global CDN. Bitwarden's feature set, on infrastructure you actually own._ For Vaultwarden Vaultwarden on Edge, Bitwarden you control Self-host the Bitwarden-compatible password manager on a tiny VM. Use the official apps, get every Enterprise feature for free, keep your vault on your infrastructure. Start free Read the deploy guide # docker-compose.yml — Vaultwarden services: vaultwarden: image: vaultwarden/server:latest environment: DOMAIN: https://vault.example.com SIGNUPS_ALLOWED: false ADMIN_TOKEN: ... volumes: - ./vw-data:/data # Front it with the CDN (auto-SSL) $ edge cdn create vault.example.com \ --origin https://<vm-ip> ✓ Live, ~$5/month for a family vault Why people self-host Vaultwarden All of Bitwarden's features, none of the per-seat upgrades. Bitwarden-compatible Use the official Bitwarden mobile, desktop and browser clients pointed at your Vaultwarden server. Same UX, your server. Rust on a tiny VM Vaultwarden is a single Rust binary with a tiny memory footprint. The smallest Edge VM is overkill for almost any team. Family / org sharing without paywalls Bitwarden's Family and Organization features cost extra in their cloud. Vaultwarden makes them all available, free, on your server. SSO and 2FA included OIDC SSO, TOTP, Yubikey, Duo, FIDO2 — all built in. No paid Enterprise tier to upgrade to. Encrypted attachments to S3 Configure Vaultwarden's attachment storage to point at Edge Storage. Encrypted-at-rest in your bucket, served via signed URLs. Behind the CDN with auto-SSL Edge CDN handles SSL automatically and adds DDoS protection. Bitwarden client traffic falls through to your Vaultwarden VM. Reference architecture How Vaultwarden maps to Edge A tiny Vaultwarden VM, attachments in S3, CDN out front. The most cost-effective password infrastructure you'll ever run. Compute Vaultwarden (Rust) on a tiny VM, SQLite or external Postgres Storage S3-compatible bucket for encrypted attachments CDN Auto-SSL and DDoS protection in front of the Vaultwarden VM DNS Anycast DNS for `vault.example.com` Indicative cost A 25-person team vault Bitwarden Enterprise (25 seats) ~$150/mo 1Password Business (25 seats) ~$200/mo Edge (1 tiny VM) ~$5/mo Common questions How does this compare to Bitwarden Cloud? Same clients, your server. Vaultwarden ships every Bitwarden feature including the ones gated behind paid Bitwarden tiers (organisations, families, SSO, hardware keys), all free. Is it really safe to self-host a password manager? Yes — vaults are end-to-end encrypted client-side before they ever reach the server. Even if someone got your VM's database, they'd see opaque encrypted blobs. Your master password never leaves your device. Will the official Bitwarden apps work? Yes. Mobile, desktop and browser apps all let you set a custom server URL. Point them at `https://vault.example.com` and you're done. How do I back it up? Snapshot the SQLite database (or `pg_dump` if you use Postgres) to Edge Storage on a schedule. Both files are tiny — backups can run every hour without breaking a sweat. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Ollama Run open LLMs on your own GPUs vLLM Production-grade LLM serving llama.cpp Quantised LLM inference, CPU or GPU ComfyUI Node-based Stable Diffusion on GPU VMs Stand up your vault Start free. A family or team vault on a $5 VM. Start free Talk to an engineer --- ### Self-host vLLM on Edge | Production-grade LLM serving URL: https://edge.network/solutions/vllm/ Markdown: https://edge.network/solutions/vllm.md JSON: https://edge.network/json/solutions/vllm.json _Run vLLM on Edge GPU instances — high-throughput batched inference, OpenAI-compatible API, models from S3-compatible Edge Storage. The serving stack production AI teams actually use._ For vLLM vLLM on Edge, production LLM serving Self-host the high-throughput LLM serving stack production AI teams use. PagedAttention, continuous batching, OpenAI-compatible API, models from S3-compatible storage. Start free See AI infrastructure # Provision a GPU VM $ edge compute create \ --image ubuntu-24-04-cuda --plan gpu-a100 \ --script ./bootstrap-vllm.sh # Serve a model $ vllm serve meta-llama/Llama-3.1-70B-Instruct \ --tensor-parallel-size 2 \ --quantization fp8 # From your app — drop-in OpenAI client const openai = new OpenAI({ baseURL: 'https://inference.example.com/v1', apiKey: 'EMPTY', }) Why production teams pick vLLM When you've outgrown Ollama and need real throughput per GPU dollar. Continuous batching for throughput PagedAttention and continuous batching make vLLM ~10x faster than naive serving for multi-tenant workloads. Same GPU, far more requests per second. GPU VMs sized for serious models A10, A100, H100 — pick the right card for your model size. Tensor parallelism across multiple GPUs on a single VM, or pipeline parallelism across VMs. OpenAI-compatible server `vllm serve` exposes the OpenAI chat completions, completions and embeddings endpoints. Existing SDKs work unchanged — just swap the base URL. Model weights in object storage Mount Edge Storage for model weights so spinning up a new GPU VM is fast and predictable. No 30-minute Hugging Face downloads on every restart. LoRA / quantisation supported AWQ, GPTQ, FP8, BNB quantisation; LoRA adapters loaded at request time. The full vLLM feature set on a real VM. Per-GPU-hour, not per-token Together and Replicate charge per million tokens. A vLLM instance on an Edge GPU VM is one fixed hourly rate — at any throughput. Reference architecture How vLLM maps to Edge One GPU VM per model, weights cached in S3 for fast spin-up, load balancer in front when you need horizontal scale. Compute (GPU) vLLM serving on a GPU VM (or multi-GPU for tensor parallelism) Storage Model weights cached in a bucket; mounted at boot CDN Optional: caches non-streaming responses DNS Anycast DNS for `inference.example.com` # systemd unit for vLLM [Service] ExecStart=/usr/local/bin/vllm serve $MODEL \ --host 0.0.0.0 --port 8000 \ --tensor-parallel-size 2 \ --max-model-len 8192 Environment=HF_HOME=/mnt/edge-storage/hf-cache Restart=always Common questions When should I pick vLLM over Ollama? Pick vLLM when you need throughput, multi-tenancy, or specific quantisation/LoRA features. Pick Ollama for ease of use and small-team / single-user workloads. Which GPU is right? For 7B–13B at high throughput: A10 / L4. For 70B-class: A100 80GB or H100. Multi-GPU tensor parallelism on a single VM unlocks larger models — our Compute team can size it. Can I run multiple models on one GPU? Yes — vLLM supports `--lora-modules` for serving multiple LoRA adapters on a single base model. For totally separate models, run multiple vLLM processes (or VMs) and route at the load balancer. How do I autoscale? GPU autoscale is generally a per-VM affair (cold starts are slow). Most production teams provision a static fleet sized for peak, plus burst-to-manual capacity for special events. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers An AI answer box for your site, grounded in your own content — one script tag on any page. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → llama.cpp Quantised LLM inference, CPU or GPU ComfyUI Node-based Stable Diffusion on GPU VMs Docker Run any container on global VMs Kubernetes k3s and full k8s on real VMs, no control-plane fees Serve LLMs at scale Start free. Compute team can help you size the GPU and architecture. Start free Talk to an engineer --- ### Self-host WooCommerce on Edge | Faster store, smaller bill URL: https://edge.network/solutions/woocommerce/ Markdown: https://edge.network/solutions/woocommerce.md JSON: https://edge.network/json/solutions/woocommerce.json _Run WooCommerce on Edge — a real VM running WordPress + LEMP, S3-compatible media via WP Offload Media, global CDN with zero egress fees and on-the-fly product image transforms._ For WooCommerce WooCommerce hosting without the gotchas Self-host the world's most popular store on a real VM with S3-compatible product imagery and a global CDN. Faster checkout, no visit caps, zero egress fees. Start free Have us migrate it # Bootstrap WooCommerce on a VM $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-woocommerce.sh # Offload media to Edge Storage define('AS3CF_SETTINGS', serialize([ 'provider' => 's3', 'access-key-id' => '...', 'bucket' => 'shop-media', 'endpoint' => 'https://storage.edge.run', ])); # Front the store with the CDN $ edge cdn create shop.example.com \ --origin https://<vm-ip> Why merchants move to Edge All the platform polish of premium WP/WC hosts, with hardware your store actually owns. Real CPU for checkout A dedicated VM means cart and checkout queries don't fight for resources with 50 other stores. Faster pages = better conversion. S3 media library Use WP Offload Media (or similar) to push product images and uploads to Edge Storage. Catalogue scales to terabytes without bloating your VM. On-the-fly product imagery Skip pre-generating six sizes of every variant — Edge Image Optimization resizes from a URL. Faster builds, smaller storage, snappier galleries. Global CDN, zero egress Cache catalogue HTML for guests, all static assets and Storage URLs globally. Your origin VM only sees logged-in users and checkout traffic. MySQL on the same network Run MariaDB on the same VM for cart-write latency you can't get on a SaaS host. Move it to a dedicated VM the day you outgrow that — same private network. Predictable bills, even on launch day No metered visit caps, no per-order fees, no per-GB egress. A small VM, a CDN deployment and a bucket — sized to your store, not their spreadsheet. Reference architecture How WooCommerce maps to Edge Standard LEMP + WooCommerce stack, media offloaded, catalogue cached at the edge, checkout safely at origin. Compute Runs WordPress + WooCommerce + Nginx + PHP-FPM (and MariaDB) on a VM Storage S3-compatible bucket for `wp-content/uploads` (product images, downloads) CDN Caches static assets, catalogue HTML for guests, and Storage URLs Image Optimization On-the-fly responsive product images, AVIF/WebP, smart cropping DNS Anycast DNS for the apex, www and email records Shield Blocks card-testing bots and fake accounts at checkout and signup — free Assist Answers sizing, shipping and returns questions from your store content Indicative cost A growing online store ~250k monthly visits, 2,000 SKUs, 500GB image bandwidth WooCommerce-managed (WP Engine eCom) ~$200–500 Shopify Advanced + apps ~$400+ Edge (VM + CDN + Storage) ~$30–70 Indicative figures. Payment processing fees not included anywhere. Common questions Will my payment gateway work? Yes — WooCommerce gateways (Stripe, PayPal, GoCardless, Klarna, Mollie, etc.) are all client-side or server-to-server. No special infrastructure required, they'll work the same as on any other LEMP host. How does this compare to dedicated WP/WC hosts? Cheaper and faster (real CPU on a real VM with NVMe), no visit caps, no transaction fees on top of your gateway, and you keep root. Trade-off: one bootstrap script (or our Expert Services) instead of a fully managed console. How do I cache HTML safely? Use a plugin like W3 Total Cache, LiteSpeed Cache or WP Rocket to bypass cache for logged-in users, cart pages and checkout. The Edge CDN serves the cached guest HTML; everything else hits origin. What about huge catalogues? No problem. Storage is unlimited, the CDN handles delivery, and you can scale the VM vertically (or split MySQL onto its own VM) as the catalogue grows. We have customers running 100k+ SKUs. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Blocks card-testing bots and fake accounts at checkout and signup. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers sizing, shipping and returns questions from your product pages and policies. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront Move your store to Edge Start free. Migrate one store, see the speed and savings before you commit anything else. Start free Have us migrate it --- ### Solutions URL: https://edge.network/solutions/ Markdown: https://edge.network/solutions.md JSON: https://edge.network/json/solutions.json _Cloud infrastructure solutions for agencies, developers, startups, and enterprises. AI/ML, media streaming, and expert services._ Solutions Built for how you work Whether you're a solo developer, growing startup, or global enterprise, Edge has the infrastructure and expertise to power your success. Solutions by Audience Tailored infrastructure and support for teams of every size. 40% faster deployments Agencies Scale client infrastructure without complexity. Predictable pricing and the reliability your reputation depends on. Learn more Free to start Developers CLI-first infrastructure designed for developers who ship. From local to global in minutes. Learn more Zero egress fees Startups Infrastructure that grows with you. Start small, scale infinitely. No surprise bills. Learn more 99.99% uptime SLA Enterprise Security, compliance, and performance without compromise. Dedicated support and custom SLAs. Learn more Free bot protection Security Teams Bot mitigation without user friction. A 1–100 humanity score on every request, privacy-first by construction, and free forever — powered by Edge Shield. Learn more Solutions by Use Case Purpose-built solutions for specific workloads and industries. Agentic Development Let your AI agent deploy for you. Official MCP server with one-line setup for Cursor, Windsurf, and Claude — free to start, no card. Learn more AI & Machine Learning Run LLMs and SLMs on distributed GPU infrastructure. Low-latency inference at the edge. Learn more Media Streaming Reliable global video CDN. 988 PoPs, zero egress fees, unlimited concurrent viewers. Learn more Media Management Just-in-time image and video transformations via URL. Resize, crop, convert on the fly. Learn more E-commerce Fast storefronts, zero egress on product media, real compute for checkout, and free bot protection. Learn more Solutions by Stack Reference architectures and quickstarts for the frameworks you already build with. Next.js Self-host Next.js without the lock-in Nuxt Vue-powered SSR on global VMs SvelteKit Tiny, fast, and Node-friendly Astro Content-first sites at the edge Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Laravel Production VMs, S3 storage and CDN Django Python web apps, no surprise bills Rails Classic VPS workflow, modern network Node.js Express, Fastify, Hono — your runtime WordPress Fast, cheap and zero egress fees Drupal Enterprise PHP CMS, predictable bills Ghost Modern publishing, self-hosted Statamic Flat-file Laravel CMS, zero database drama Craft CMS Premium PHP CMS for design-led teams Strapi The leading open-source headless CMS Directus Instant API over any SQL database Payload TypeScript-first headless CMS, Next.js-ready WooCommerce Self-host the world's most popular store Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront PostgreSQL Self-hosted Postgres on dedicated NVMe MySQL MySQL or MariaDB on real VMs Redis In-memory cache and queue, your way MongoDB Self-hosted document store with replica sets Outline Team wiki you actually own BookStack Open-source documentation platform Plausible Privacy-first analytics, self-hosted Umami Lightweight, cookie-free analytics n8n Self-hosted workflow automation Vaultwarden Bitwarden-compatible password manager Ollama Run open LLMs on your own GPUs vLLM Production-grade LLM serving llama.cpp Quantised LLM inference, CPU or GPU ComfyUI Node-based Stable Diffusion on GPU VMs Docker Run any container on global VMs Kubernetes k3s and full k8s on real VMs, no control-plane fees Expert Services Need hands-on help? Our Expert Services team provides dedicated development resources at rates below market average. From AI integration to full-stack development, we build what you need. 40% Less than in-house 0 Recruitment fees Explore Expert Services Capabilities Full-stack web & mobile development AI & machine learning integration Cloud architecture & migration DevOps & infrastructure automation Performance optimization Security audits & hardening Not sure where to start? Talk to our team. We'll help you find the right solution for your needs, whether that's self-service infrastructure or a fully managed engagement. Talk to Sales Start Free Today --- ### Solutions by Stack URL: https://edge.network/solutions/stacks/ Markdown: https://edge.network/solutions/stacks.md JSON: https://edge.network/json/solutions/stacks.json _Run any stack on Edge. Reference architectures and deploy guides for Next.js, Laravel, WordPress, Drupal, Ghost, Strapi, Directus, WooCommerce, Medusa, Docker and many more._ Solutions / By Stack Run any stack on Edge Production VMs, S3-compatible storage, a global CDN with zero egress fees, DNS, and an agentic API — wired together for the frameworks you already use. Frontend & Full-Stack Next.js Self-host Next.js without the lock-in Nuxt Vue-powered SSR on global VMs SvelteKit Tiny, fast, and Node-friendly Astro Content-first sites at the edge Static Sites Hugo, Eleventy, Jekyll — straight to the CDN Backend Frameworks Laravel Production VMs, S3 storage and CDN Django Python web apps, no surprise bills Rails Classic VPS workflow, modern network Node.js Express, Fastify, Hono — your runtime CMS WordPress Fast, cheap and zero egress fees Drupal Enterprise PHP CMS, predictable bills Ghost Modern publishing, self-hosted Statamic Flat-file Laravel CMS, zero database drama Craft CMS Premium PHP CMS for design-led teams Headless CMS Strapi The leading open-source headless CMS Directus Instant API over any SQL database Payload TypeScript-first headless CMS, Next.js-ready E-commerce WooCommerce Self-host the world's most popular store Medusa Modern headless commerce, Node.js-native Magento Enterprise PHP commerce without Adobe pricing Saleor Python + GraphQL headless commerce Shopify Hydrogen Self-host your Shopify storefront Databases PostgreSQL Self-hosted Postgres on dedicated NVMe MySQL MySQL or MariaDB on real VMs Redis In-memory cache and queue, your way MongoDB Self-hosted document store with replica sets Self-Hosted Apps Outline Team wiki you actually own BookStack Open-source documentation platform Plausible Privacy-first analytics, self-hosted Umami Lightweight, cookie-free analytics n8n Self-hosted workflow automation Vaultwarden Bitwarden-compatible password manager AI Runtimes Ollama Run open LLMs on your own GPUs vLLM Production-grade LLM serving llama.cpp Quantised LLM inference, CPU or GPU ComfyUI Node-based Stable Diffusion on GPU VMs Platform Docker Run any container on global VMs Kubernetes k3s and full k8s on real VMs, no control-plane fees Drop-in services Every stack ships with these Shield and Assist aren't infrastructure — they're a script tag and an HTTP call. Whatever you run above, they drop straight in. Edge Shield Bot protection Invisible bot protection for logins, signups and forms — a 1–100 humanity score instead of a puzzle. One HTTP check from any backend. Free for most sites Explore Shield → Edge Assist AI answers An AI answer box grounded in your site's own content — one script tag on any page, whatever renders it. Free tier: 250 answered questions a month Explore Assist → Don't see your stack? Edge is plain VMs, plain object storage, plain DNS and a plain CDN. If your stack runs on Linux, it runs on Edge — and our agentic API can deploy it for you in minutes. Talk to us about your stack Try the Agentic API # Ask the Edge agent "Deploy my Phoenix app to elixir.example.com" → POST /agent/compute/instances → POST /agent/dns/.../records (A → 64.34.86.42) → POST /agent/cdn/deployments "Live at https://elixir.example.com — ~$8/mo." --- ### Solutions for Agencies URL: https://edge.network/solutions/agencies/ Markdown: https://edge.network/solutions/agencies.md JSON: https://edge.network/json/solutions/agencies.json _Scale client infrastructure without complexity. Predictable pricing, multi-account support, and the reliability your reputation depends on._ For Agencies Scale Clients Without Complexity Edge gives agencies the infrastructure to deliver exceptional client work. Fast, predictable pricing, and the reliability your reputation depends on. Start Free Today Talk to Sales Built for Agency Workflows Everything you need to deliver world-class infrastructure for your clients. Infrastructure That Scales Spin up VMs, CDN, storage, and DNS in minutes. Global edge infrastructure that grows with your clients' needs. Multi-Account Support One login, multiple accounts. Switch between client accounts instantly without logging out. Keep billing, resources, and team members completely separate per client. Enterprise Security, Agency Pricing DDoS protection, SSL certificates, and free bot protection with Edge Shield on every client form. Keep clients secure without the enterprise price tag. Team Collaboration Built-In Granular permissions, team workspaces, and audit logs. Manage multiple clients and team members effortlessly. Predictable Margins Flat-rate pricing with zero egress fees. Know exactly what you'll pay and price your services with confidence. 24/7 Priority Support When your clients need you, you need us. Priority support ensures you're never left waiting. One Platform, Every Project From static marketing sites to complex web applications, Edge handles it all. Stop juggling multiple providers and consolidate your infrastructure. High-traffic marketing campaigns E-commerce infrastructure Media and publishing sites SaaS application backends API and microservices Content delivery at scale Agency Partner Program Volume Discounts Available Agencies managing multiple client accounts qualify for partner pricing. The more you grow, the more you save. Learn about partner pricing Case Study "Edge lets me focus on building, not infrastructure" Code+Ink is a digital consultancy with over 15 years of experience partnering with design agencies and startups. Specialising in decoupled, modular architecture with ReactJS and headless CMS solutions, they've delivered projects for clients including Bletchley Park, HUNGER, Damien Hirst, and the Royal Institution. By consolidating client infrastructure on Edge, Code+Ink reduced deployment complexity and eliminated the overhead of managing multiple cloud providers. The global CDN and zero egress pricing means predictable costs regardless of traffic spikes. A Andrew Founder, Code+Ink Visit codeandink.co Results 40% Faster deployments 1 Platform for all clients 0 Egress fees Ready to streamline your agency? See why agencies choose Edge to power their client infrastructure. Get Started Free Contact Sales Expert Services Extend Your Agency's Capacity Got more client work than your team can handle? Our Expert Services team becomes an extension of your agency—delivering senior development resources at rates 20%+ below hiring contractors. From overflow projects to specialised builds, we help agencies deliver exceptional work without the overhead of expanding your permanent team. 20%+ Less than in-house costs 0 Recruitment hassle Explore Expert Services How We Help Agencies Overflow Projects Handle peak demand without turning away work. Specialised Builds Access skills your team doesn't have in-house. White-Label Delivery We work under your brand, invisible to clients. Fast Turnaround Meet tight deadlines with dedicated resources. --- ### Solutions for Developers URL: https://edge.network/solutions/developers/ Markdown: https://edge.network/solutions/developers.md JSON: https://edge.network/json/solutions/developers.json _CLI-first infrastructure designed for developers who ship. Comprehensive APIs, global edge network, and flexible compute._ For Developers Build Fast. Deploy Faster. Edge is built by developers, for developers. Infrastructure with a proper CLI, sensible APIs, and none of the enterprise bloat. Start Building Read the Docs ▋ Developer Experience First Every feature designed with developer productivity in mind. CLI-First Workflow Manage your entire infrastructure from the terminal. Spin up VMs, configure CDN, update DNS – all from one CLI. Comprehensive APIs Full REST APIs for everything. Automate infrastructure, manage resources, and build custom tooling. Infrastructure as Code Version control your infrastructure. Terraform provider and declarative configs for repeatable deployments. Global Edge Network Deploy infrastructure across 2,000+ edge locations. Low latency for your users, wherever they are. Flexible Compute From lightweight containers to GPU instances. Run any workload on infrastructure sized to your needs. Real-Time Control Instant DNS propagation, sub-second cache purges, and live metrics. Infrastructure that responds when you need it. Pick Your Interface HTTPS, terminal, or AI agent — everything on Edge is scriptable. Jump straight to the reference you need. REST API Every Edge resource over HTTPS with API keys. The same API that powers the console and CLI. API reference CLI A single binary for macOS, Linux, and Windows. Manage VMs, CDN, DNS, storage, and Shield from the terminal. CLI docs Agent API & MCP Self-describing endpoints with scoped tokens, budgets, and dry-run — plus an official MCP server for Cursor, Windsurf, and Claude with one-line setup. Agent docs Authentication Create API keys with optional expiry, manage them programmatically, and pick the right credential per integration. Auth guide Compute API Create VMs, attach SSH keys and firewalls, take snapshots, and run startup scripts — all over HTTPS. Compute reference Storage & S3 S3-compatible object storage with presigned URLs, lifecycle rules, and any S3 SDK you already use. Storage reference New Agent Ready Building with AI? Give your coding agent an Edge access code and let it deploy your app, manage DNS, and monitor infrastructure — all without leaving your editor. One-line MCP setup — npx @edge-network/mcp puts native Edge tools in Cursor, Windsurf, Claude Desktop, and Continue Discovery-first API — the agent learns what it can do before doing it Budget-aware — set soft or hard spending caps per agent Project-based — resources grouped by app for easy management and teardown Human-readable responses — every response includes a summary the agent can relay to you Explore the Agent API Connect Your Tool # Give your agent the URL and access code User: "Deploy my React app to portfolio.example.com" # Agent discovers capabilities GET /agent → 5 products, $47 budget remaining # Agent deploys POST /agent/storage/buckets → Created POST /agent/cdn/deployments → Deployed POST /agent/dns/zones/.../records → CNAME added # Agent reports back "Your site is live at https://portfolio.example.com with CDN, SSL, and DNS configured. ~$2.80/month." No Domain? No Problem test.network Subdomains Need a domain for development, staging, or a side project? Pick a subdomain of test.network for $1/month. No registrar, no DNS setup, no waiting — just choose a name and start building. Instant setup — your DNS zone is ready in seconds Full control — add any record type, just like a real domain SSL included — automatic certificates when used with Edge CDN Explore test.network Read the Docs # Pick a subdomain my-project .test.network — Available # Register — $1/month ✓ DNS zone created ✓ Nameservers configured ✓ Ready to use # Add records, point at your resources edge dns records add my-project.test.network \ --type A --name @ --data 64.34.86.100 # Or deploy via agent "Deploy my app to my-project.test.network" → Site live at https://my-project.test.network Sensible Defaults, Full Control Get started quickly with smart defaults. When you need it, you have full control over every aspect of your infrastructure. Automatic SSL for all endpoints Private networking between resources Firewall rules and security groups Snapshots and automated backups Monitoring and alerting built-in API keys and team access controls Free Start Free Try the full platform with real infrastructure — no card required. See what Edge can do. Free DNS + free CDN & Storage tiers Full API & CLI access Zero egress fees Real support from real humans Start free Ready to build? Infrastructure that gets out of your way. Spin up your first VM in minutes. Start Building Read Documentation --- ### Solutions for Enterprise URL: https://edge.network/solutions/enterprise/ Markdown: https://edge.network/solutions/enterprise.md JSON: https://edge.network/json/solutions/enterprise.json _Enterprise-grade cloud infrastructure with dedicated support, custom SLAs, and 99.99% uptime. Security, compliance, and scale._ For Enterprise Enterprise Cloud. Simplified. Edge delivers the security, compliance, and performance that enterprise demands – without the complexity that slows you down. Contact Sales Start Free Today Built for Enterprise Requirements Security, compliance, and performance without compromise. Enterprise Security Advanced DDoS protection, WAF, and encryption at rest and in transit as standard. Global Performance 2,000+ edge locations worldwide. Sub-50ms latency for 95% of the world's internet users. 99.99% Uptime SLA Financially-backed uptime guarantee with proactive monitoring and rapid incident response. Dedicated Account Team Named account manager, solution architects, and priority engineering support. Advanced Analytics Real-time insights, custom dashboards, and detailed reporting for complete visibility. Security First Data residency controls, audit logging, and infrastructure designed with security at its core. Enterprise-Grade Capabilities Everything you need to run mission-critical workloads at scale. Custom contracts and SLAs Volume-based pricing Private networking and VPC peering SSO and SAML integration Dedicated IP addresses Custom SSL certificates Priority feature requests Quarterly business reviews 2,000+ Edge Locations 99.99% Uptime SLA $0 Egress Fees 24/7 Priority Support Case Study "Edge delivers the reliability our global clients expect" IGD is a leading research and training organisation providing insights for the food and consumer goods industry. With clients across 50+ countries relying on their platforms for critical business intelligence, uptime and performance are non-negotiable. By partnering with Edge, IGD consolidated their global infrastructure onto a single platform with guaranteed SLAs, dedicated support, and predictable costs. The result: faster content delivery to their international audience and significant operational savings. ID Ian Dunkley Chief Financial Officer, IGD Visit igd.com Results 50+ Countries served 99.99% Uptime achieved 1 Unified platform Ready to transform your infrastructure? Talk to our enterprise team about your requirements. We'll design a solution that meets your needs. Contact Sales Start Free Today Expert Services Augment Your Team with Ours Need additional engineering capacity without the overhead of hiring? Our Expert Services team integrates seamlessly with your organisation—delivering senior development talent at rates 20%+ below building an in-house team. From complex integrations to greenfield development, we've helped enterprises accelerate delivery without compromising on quality or security standards. 20%+ Less than in-house costs 0 Recruitment overhead Explore Expert Services Enterprise Capabilities Complex Integrations Legacy system modernisation and API development. Cloud Migration Seamless transition from legacy infrastructure. AI & Automation Intelligent solutions that scale with your business. Security & Compliance Development that meets your governance requirements. --- ### Solutions for Security Teams URL: https://edge.network/solutions/security-teams/ Markdown: https://edge.network/solutions/security-teams.md JSON: https://edge.network/json/solutions/security-teams.json _Bot mitigation without user friction. Edge Shield gives security teams a 1–100 humanity score on every request — privacy-first, accessible, and free. Plus DDoS absorption, audit trails, and scoped credentials across the platform._ For Security Teams Stop the bots. Keep the humans. Edge Shield gives you a 1–100 humanity score on every request — so you can write real policy instead of guessing. No puzzles for your users, no tracking for your lawyers to worry about, and no invoice for your budget. Try the Live Demo Talk to Our Team Edge Shield — Live Verification 1,231 humans verified today 53 bots blocked Human verified invisibly Mobile Safari · Sydney 94 /100 Human verified invisibly Firefox · Berlin 89 /100 Undeclared automation Headless browser · datacentre IP 3 /100 · blocked Verified AI agent Declared identity · verified Routed Puzzles shown to humans 0 Invisible to every real visitor The abuse you're paged about Automated abuse targets the same surfaces everywhere: logins, signups, forms, and content. Shield sits in front of all of them. Credential Stuffing Stop automated login attempts before they reach your authentication layer. Scripted traffic floors the humanity score; step-up or block on your thresholds. Fake Account Creation Bots signing up faster than you can clean them out? Protect registration flows invisibly, without adding friction for genuine new users. Scraping & Content Theft Distinguish humans, declared AI agents, and undeclared automation — and apply different policies to each instead of a blanket block. Form Spam & Abuse Contact forms, comments, and reviews stay clean. Tokens are single-use and expire in five minutes, so replay attacks fail by design. Edge Shield Built for how security teams actually work A signal you can build policy on, not a black box that silently drops your traffic. A Score, Not a Verdict Every verification returns a 1–100 humanity score. Set your own cutoffs for auto-approve, step-up, and block — policy stays in your hands, not ours. Invisible to Humans No image puzzles, no checkbox theatre. Legitimate visitors verify silently via proof-of-work and environment signals — conversion rates stay intact. Privacy by Construction No cookies, no fingerprinting, no per-visitor data. Your privacy policy doesn't need a section about your bot protection, and your DPO stays happy. Verified AI Agents AI agents are legitimate traffic now. Shield identifies declared, verified agents so you can route them to the right endpoints instead of blocking customers. Drop-in Migration Turnstile-compatible response fields and familiar siteverify semantics. Swap the widget, update one server-side call, and you're off reCAPTCHA. Accessibility Compliant No visual puzzles means nothing to fail an accessibility audit. Screen-reader friendly by default, with WCAG-conscious interactive fallback. 1–100 Humanity score on every check 0 Cookies & trackers <15KB JavaScript bundle Free Forever, unlimited widgets Explore Shield Read the docs Security across the whole platform Shield protects your application surfaces; the rest of the platform protects everything underneath. Every Edge product ships with security defaults your team doesn't have to bolt on afterwards. For the full picture of how Edge itself is secured — encryption, compliance, and incident response — see our security overview. Platform Security Overview DDoS Absorption Malicious traffic is absorbed and filtered across the global network before it reaches your origin. Full Audit Trail Every action on your account — human or agent — is logged and traceable. Scoped Credentials API keys and agent access codes carry granular permissions, budget caps, and instant revocation. Encryption Everywhere TLS 1.3 in transit, AES-256 at rest, with regularly rotated keys as standard. Expert Services Migrate without a protection gap Moving off reCAPTCHA, Turnstile, or hCaptcha? Our engineers swap the widgets, update your server-side validation, and verify every form — typically inside 48 hours, with zero unprotected windows. We'll also analyse your traffic and recommend humanity score thresholds for auto-approve, step-up, and block that fit your risk profile. Get Migration Help Sound familiar? "Our accessibility audit flagged our CAPTCHA." "We're worried about what our CAPTCHA provider does with visitor data." "Bots are signing up faster than we can clean them out." "AI agents are legitimate customers for us — we need to route them, not block them." Protect your first form in five minutes Two lines of code, one server-side call, free forever. See what your traffic really looks like. Get Started Free See the Demo --- ### Solutions for Startups URL: https://edge.network/solutions/startups/ Markdown: https://edge.network/solutions/startups.md JSON: https://edge.network/json/solutions/startups.json _Build your vision. We handle the rest. Infrastructure in minutes, scale without limits, and predictable costs._ For Startups Build Your Vision. We Handle the Rest. Edge gives startups enterprise-grade infrastructure without the enterprise complexity or cost. Launch fast, scale confidently, and keep your runway intact. Start Trial Apply for our Startup Program Startup Program $ 5,000 free credits for your first year on Edge Apply MVP live First users Scale What that means for your runway Without Edge 8 months With Edge credits 12 months + 4 months of runway, on us Infrastructure That Grows With You Everything you need to build and scale, without the complexity. Infrastructure in Minutes Spin up VMs, configure CDN, set up DNS – all in minutes. Focus on your product, not your infra. Scale Without Limits Start with a single VM, scale to hundreds. Our infrastructure grows with you from MVP to millions of users. Startup-Friendly Pricing Predictable costs with zero egress fees. Know exactly what you'll pay as you grow. Global from Day One CDN across 2,000+ edge locations. Fast experience for your users, wherever they are. Enterprise Security Included DDoS protection, SSL, and free bot protection with Edge Shield — stop fake signups and form spam from day one, at no cost. Team-Ready Invite your team, set permissions, and collaborate seamlessly from the start. Edge for Startups Startup Program Qualifying startups get exclusive benefits to help you build and scale. We're invested in your success. $5,000 in credits for the first year Priority technical support Direct access to engineering team Co-marketing opportunities Exclusive startup community access Apply Now Eligibility The Edge for Startups program is available to early-stage companies that meet the following criteria: Less than $5M in total funding Founded within the last 5 years Not currently an Edge customer Affiliated with an approved accelerator, incubator, or VC partner Case Study "Edge is the cloud as it should be" Ecohustler is an independent environmental media platform delivering news, investigations, and solutions for the climate crisis. With a global audience hungry for sustainability content, they needed infrastructure that matched their values. By choosing Edge, Ecohustler reduced their environmental footprint while improving performance. The distributed edge network means content is delivered from the nearest location, cutting data transmission distances and energy consumption by up to 50%. M Matt Mellen Founder & Editor, Ecohustler Visit ecohustler.com Results 50% Energy reduction 988 Edge locations 0 Egress fees Ready to build the next big thing? Infrastructure that scales with your ambition. Start free today. Start Free View Pricing Expert Services Build Faster with Our Team Don't have the engineering capacity to deliver your vision? Our Expert Services team becomes an extension of your startup—bringing senior development talent at rates 20%+ below hiring in-house. From MVP development to scaling your product, we've helped startups ship faster without the overhead of recruiting, onboarding, and managing a full engineering team. 20%+ Less than in-house costs 0 Recruitment hassle Explore Expert Services What We Build for Startups MVPs & Prototypes Validate your idea with a working product in weeks, not months. Full-Stack Development Web apps, mobile apps, APIs—whatever your product needs. AI Integration Add AI capabilities to your product without an ML team. Scale & Optimise Performance tuning and infrastructure for your growth phase. --- ### Static sites on Edge | Hugo, Eleventy, Jekyll, all the SSGs URL: https://edge.network/solutions/static-sites/ Markdown: https://edge.network/solutions/static-sites.md JSON: https://edge.network/json/solutions/static-sites.json _Host any static site generator on Edge — Hugo, Eleventy, Jekyll, Astro, Hexo, Pelican. Push to S3-compatible storage, serve via global CDN, zero egress fees._ For Static Sites Static sites, edge-delivered Hugo, Eleventy, Jekyll, Astro, Zola — any SSG, served from a global CDN with zero egress fees. No origin server, automatic SSL, and on-the-fly image transforms when you need them. Start free Read the deploy guide # Build $ hugo # or eleventy, jekyll, astro… # Sync to Edge Storage $ aws s3 sync ./public s3://my-site \ --endpoint https://storage.edge.run \ --delete # Front it with the CDN $ edge cdn create example.com \ --origin s3://my-site # Purge after each deploy $ edge cdn purge example.com ✓ Live, globally cached, ~$3/month Bring any SSG you like If it produces a folder of static files, it runs on Edge. Hugo Tens of thousands of pages in seconds Eleventy (11ty) Markdown, Nunjucks, Liquid Jekyll Classic Ruby SSG, GitHub Pages compatible Astro Component islands, partial hydration Hexo Node-based blogging Pelican Python-powered static sites Zola Single-binary Rust SSG mdBook / VitePress / Docusaurus Docs sites Why static sites belong on Edge Cheap, fast, durable. The web's original deployment model — done right. No origin server Static sites need no VM at all. Push the build to a Storage bucket, point a CDN deployment at it, you're live globally. Global CDN, zero egress Every page served from the edge location nearest your visitor — and never a per-GB egress bill on your way out. On-the-fly image transforms Stop pre-generating six sizes of every image at build time. Edge Image Optimization resizes from a URL, on demand. CI-friendly deploys Build in GitHub Actions or anywhere else, sync the output to Edge Storage with the AWS CLI, purge the CDN. Done. Pennies per month A bucket and a CDN deployment. Most static sites cost a few dollars a month — even at serious traffic volumes. Automatic SSL Bring your own domain, get a free SSL certificate, end-to-end TLS. No certbot, no renewals to track. Reference architecture How a static site maps to Edge Two products, no servers. The simplest deployment story we offer. Storage Holds the built site bundle (HTML, CSS, JS, images) CDN Serves the entire bucket from edge locations worldwide Image Optimization On-the-fly transforms instead of build-time pre-generation DNS Anycast DNS for the apex, www and any preview branches Shield Scores form submissions at your form handler — no JS puzzle, free Assist Gives a static site a working answer box — no backend required # .github/workflows/deploy.yml on: { push: { branches: [main] } } jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - run: hugo --minify - run: | aws s3 sync public s3://$BUCKET \ --endpoint $EDGE_ENDPOINT --delete - run: | curl -X POST $EDGE_API/cdn/.../purge \ -H "Authorization: Bearer $TOKEN" Common questions Which SSG is supported? All of them. If your generator produces a folder of HTML, CSS and JS, we can serve it. Hugo, Eleventy, Jekyll, Astro, Hexo, Pelican, Zola, Docusaurus, VitePress, mdBook — all fine. How do I deploy from CI? Build the site in your CI of choice, then `aws s3 sync ./public s3://your-bucket --endpoint https://storage.edge.run --delete`, then trigger a CDN purge via the Edge API. What about responsive images? Skip the build-time image gymnastics. Push originals to Storage, link them through Edge Image Optimization with `?w=` query params for responsive `srcset` markup. Build times drop dramatically. Can I do per-PR previews? Yes — sync each branch build to a `branch-name/` prefix in the bucket, alias a `branch.preview.example.com` subdomain to it, tear it down on PR close. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Even static sites have forms — score submissions at your form handler, no JavaScript puzzle. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers A static site plus Assist is a docs site that answers questions — no backend required. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Laravel Production VMs, S3 storage and CDN Django Python web apps, no surprise bills Rails Classic VPS workflow, modern network Node.js Express, Fastify, Hono — your runtime Static, served properly Two products, no servers, pennies per month. Static the way it was meant to be. Start free Talk to an engineer --- ### WordPress hosting on Edge | Fast, cheap, zero egress URL: https://edge.network/solutions/wordpress/ Markdown: https://edge.network/solutions/wordpress.md JSON: https://edge.network/json/solutions/wordpress.json _Production WordPress hosting on Edge — proper VMs, S3-compatible media library, global CDN with zero egress fees, and on-the-fly image optimisation._ For WordPress WordPress hosting without the visit caps A real VM, an S3-compatible media library, a global CDN with zero egress fees and on-the-fly image optimisation. Faster than the managed WP hosts, at a fraction of the price. Start free Have us manage it # Spin up a VM with WP + LEMP + MySQL $ edge compute create \ --image ubuntu-24-04 --plan small \ --script ./bootstrap-wordpress.sh # Offload uploads to Edge Storage define('AS3CF_SETTINGS', serialize([ 'provider' => 's3', 'access-key-id' => '...', 'bucket' => 'wp-uploads', ])); # Front it with the CDN $ edge cdn create example.com \ --origin https://<vm-ip> Why move WordPress to Edge Take the managed-WP performance promise — and actually deliver on it, for a fraction of the bill. Faster than managed WP hosts Dedicated vCPU and NVMe storage on a real VM, fronted by a global CDN. None of the noisy-neighbour problems of cheap shared WordPress. S3 media library Use a Media Cloud / WP Offload Media plugin to store uploads in Edge Storage. Survive any VM restore, scale to terabytes. Image optimisation built-in Skip the bloated optimisation plugins — Edge resizes, crops and converts to AVIF/WebP at the CDN. Faster site, fewer plugins. CDN, SSL and DDoS-resistant Global anycast CDN with automatic SSL. Soaks up traffic spikes so your origin VM stays calm and your editor experience stays fast. Predictable bills No metered visit limits, no per-GB egress, no "burst" upcharges. A small VM, a CDN deployment and a bucket — all known up front. MySQL on the same box Run MariaDB or MySQL on the same VM for low-latency queries. Move it to a separate VM the day you need to scale, no migration drama. Reference architecture How WordPress maps to Edge Standard LEMP stack on a VM, uploads offloaded to S3-compatible storage, CDN out front. Boring on purpose — and that's the point. Compute Runs WordPress + Nginx + PHP-FPM (and MySQL) on a VM Storage Stores wp-content/uploads via WP Offload Media or similar CDN Caches HTML for guests, all static assets, and media URLs Image Optimization On-the-fly responsive images straight from the bucket DNS Anycast DNS for the apex, www and email records Shield Free bot protection for comments, login and registration — no puzzle plugins Assist AI answers for visitors, drawn from your posts and pages — one script tag Indicative cost A busy WordPress site ~500k monthly visits, 250GB image bandwidth, WooCommerce WP Engine / Kinsta ~$200–400 Cloudways + media offload ~$80–160 Edge (VM + CDN + Storage) ~$25–50 Indicative figures. Your usage will vary. Common questions Will my plugins still work? Yes — this is a standard LEMP stack. Anything that works on a normal Linux VPS or a managed WordPress host works here, including WooCommerce. How does this compare to WP Engine / Kinsta? Cheaper, faster (real CPU on a real VM), no visit caps, no egress fees, and you keep root access. The trade-off is that you handle the OS — or we can quote our Expert Services team to manage it. How do I cache HTML? Use a plugin like W3 Total Cache or LiteSpeed Cache to generate static HTML, then let the Edge CDN serve it for guests. Logged-in users hit the origin as usual. What about backups? Use Edge Compute snapshots for the VM and an Edge Storage bucket for offsite database dumps and media — both fully automatable. How do I stop comment spam and login bots? Add Edge Shield — a free, invisible CAPTCHA alternative — to your comment, login and registration forms. No image puzzles for real visitors, a humanity score for everything else, and it works alongside any WordPress form plugin. Drop-in services Works with this stack out of the box No rebuild, no migration — Shield is one HTTP check and Assist is one script tag. Add either to what you're already running. Edge Shield Bot protection Protects comments, login and registration alongside any form plugin — no image puzzles. Free for most sites — no puzzles, no widget to style Explore Shield → Edge Assist AI answers Answers pre-sales and support questions straight from your posts and pages. Free tier: 250 answered questions a month Explore Assist → By Stack Other stacks on Edge View all stacks → Drupal Enterprise PHP CMS, predictable bills Ghost Modern publishing, self-hosted Statamic Flat-file Laravel CMS, zero database drama Craft CMS Premium PHP CMS for design-led teams Faster WordPress, smaller bill Run the trial. Migrate one site. See the speed and savings before you commit anything else. Start free Have us migrate it --- ## Case Studies (Optional) ### Bauer Media Case Study URL: https://edge.network/case-studies/bauer/ Markdown: https://edge.network/case-studies/bauer.md JSON: https://edge.network/json/case-studies/bauer.json _How Bauer unified 50+ brands on a single platform. Europe's largest media group streamlining infrastructure across their portfolio._ All case studies Enterprise How Bauer unified 50+ brands on a single platform Bauer Media is one of Europe's largest media groups, with a portfolio spanning radio, publishing, and digital platforms. Managing infrastructure for dozens of high-traffic brands requires enterprise-grade reliability and operational simplicity. Results 50+ Brands supported 99.99% Uptime 1 Platform 24/7 Support Products Used CDN Compute DNS Storage Expert Services "Edge enabled us to release in days and weeks, instead of weeks and months." Matt Hobbs CTO, Bauer Media Group The Challenge Managing infrastructure for 50+ brands meant dealing with multiple vendors, inconsistent performance, and complex billing. Each brand had different requirements, but the fragmented approach led to operational overhead, security gaps, and difficulty maintaining consistent SLAs across the portfolio. The Solution Edge provides Bauer with a unified platform for content delivery across their entire portfolio. Centralised management, consistent performance, and dedicated support mean their teams can focus on content rather than infrastructure. Volume-based pricing simplified budgeting across all brands. Key Results Single platform for all 50+ brands 99.99% uptime across portfolio Centralised management and billing Consistent SLAs for all properties Dedicated enterprise support Significant operational cost savings Learn more about Bauer Media Visit website Previous Minima Next Monocle Ready to get started? Join Bauer Media and thousands of other organisations using Edge. Start Free Today Explore Expert Services --- ### Case Studies URL: https://edge.network/case-studies/ Markdown: https://edge.network/case-studies.md JSON: https://edge.network/json/case-studies.json _See how leading companies use Edge Network. Real-world examples from XCOPY, Tinder, Bauer Media, and more._ Case Studies Trusted by industry leaders Learn how companies around the world use Edge to power their digital infrastructure and deliver exceptional experiences to their users. Trusted by leading organisations worldwide Digital Art & NFTs <100ms Load time How XCOPY delivers high-res art globally Pioneering crypto artist serving collectors with instant asset delivery. Read case study Blockchain 988 Edge nodes How Minima scaled decentralised infrastructure Layer 1 blockchain leveraging edge compute for node distribution. Read case study Enterprise 50+ Brands How Bauer unified 50+ brands on one platform Europe's largest media group streamlining infrastructure across their portfolio. Read case study Media & Publishing 180+ Countries How Monocle delivers content to 180+ countries Global affairs and lifestyle media brand achieving sub-50ms latency worldwide. Read case study Startup 50% Less energy How Ecohustler reduced their carbon footprint Environmental media platform choosing infrastructure that matches their values. Read case study Enterprise 99.99% Uptime How IGD serves clients across 50+ countries Global research organisation delivering business intelligence reliably. Read case study Agency 40% Faster deploys How Code+Ink consolidated client infrastructure Digital consultancy reducing deployment complexity for their clients. Read case study Consumer Tech 50M+ Daily users How Tinder optimised global image delivery Scaling real-time image processing for millions of daily active users. Read case study Community 4,800+ Members How Sacred Network connects a global community Platform for exploring the world's sacred places, hosted on infrastructure aligned with its values. Read case study Food & Health 0 Ops headcount How Peri Happy runs production with agents Nutrition platform for perimenopause deploying and managing its whole stack through agentic tooling. Read case study Ready to join them? Create a free account and see why leading organisations choose Edge. Start Free Today Contact Sales --- ### Code+Ink Case Study URL: https://edge.network/case-studies/code-ink/ Markdown: https://edge.network/case-studies/code-ink.md JSON: https://edge.network/json/case-studies/code-ink.json _How Code+Ink consolidated client infrastructure. Digital consultancy reducing deployment complexity for their clients._ All case studies Agency How Code+Ink consolidated client infrastructure Code+Ink is a digital consultancy with over 15 years of experience partnering with design agencies and startups. Specialising in decoupled, modular architecture with ReactJS and headless CMS solutions, they've delivered projects for clients including Bletchley Park, HUNGER, Damien Hirst, and the Royal Institution. Results 40% Faster deploys 1 Platform 0 Egress fees 15+ Years experience Products Used CDN Compute DNS Storage Expert Services The Challenge Managing infrastructure for multiple clients across different providers was time-consuming and complex. Each project had different requirements, billing cycles, and support channels. As a solo consultancy, Andrew needed to minimise operational overhead while maintaining high standards. The Solution By consolidating client infrastructure on Edge, Code+Ink reduced deployment complexity and eliminated the overhead of managing multiple cloud providers. The global CDN and zero egress pricing means predictable costs regardless of traffic spikes. Key Results 40% faster deployments Single platform for all clients Zero egress fees Simplified billing and management Consistent performance for all projects More time for actual development Learn more about Code+Ink Visit website Previous IGD Next Tinder Ready to get started? Join Code+Ink and thousands of other organisations using Edge. Start Free Today Contact Sales --- ### Ecohustler Case Study URL: https://edge.network/case-studies/ecohustler/ Markdown: https://edge.network/case-studies/ecohustler.md JSON: https://edge.network/json/case-studies/ecohustler.json _How Ecohustler reduced their environmental footprint. Environmental media platform choosing infrastructure that matches their values._ All case studies Startup How Ecohustler reduced their environmental footprint Ecohustler is an independent environmental media platform delivering news, investigations, and solutions for the climate crisis. With a global audience hungry for sustainability content, they needed infrastructure that matched their values. Results 50% Less energy 988 Edge locations 0 Egress fees 100% Values aligned Products Used CDN Compute DNS Storage Expert Services "Edge is the cloud as it should be. Conscious by design, clean in operation." Matt Mellen Founder & Editor, Ecohustler The Challenge As an environmental media platform, Ecohustler couldn't justify using traditional cloud infrastructure with its massive carbon footprint. They needed a hosting solution that aligned with their mission—one that could deliver content globally while minimising environmental impact. The Solution By choosing Edge, Ecohustler reduced their environmental footprint while improving performance. The distributed edge network means content is delivered from the nearest location, cutting data transmission distances and energy consumption by up to 50%. Key Results 50% energy reduction Infrastructure aligned with values Global audience served efficiently Zero egress fees Improved performance worldwide Walking the talk on sustainability Learn more about Ecohustler Visit website Previous Monocle Next IGD Ready to get started? Join Ecohustler and thousands of other organisations using Edge. Start Free Today Explore Expert Services --- ### IGD Case Study URL: https://edge.network/case-studies/igd/ Markdown: https://edge.network/case-studies/igd.md JSON: https://edge.network/json/case-studies/igd.json _How IGD delivers business intelligence to 50+ countries. Global research organisation delivering business intelligence reliably._ All case studies Enterprise How IGD delivers business intelligence to 50+ countries IGD is a leading research and training organisation providing insights for the food and consumer goods industry. With clients across 50+ countries relying on their platforms for critical business intelligence, uptime and performance are non-negotiable. Results 50+ Countries served 99.99% Uptime achieved 1 Unified platform 24/7 Support Products Used CDN Compute DNS Storage Expert Services The Challenge IGD's clients rely on their platforms for time-sensitive business decisions. Downtime or slow performance isn't just an inconvenience—it impacts their clients' ability to operate. Managing global infrastructure across multiple regions was complex and expensive. The Solution By partnering with Edge, IGD consolidated their global infrastructure onto a single platform with guaranteed SLAs, dedicated support, and predictable costs. The result: faster content delivery to their international audience and significant operational savings. Key Results 99.99% uptime achieved consistently Global infrastructure consolidated Dedicated enterprise support Predictable monthly costs Faster content delivery worldwide Simplified operations Learn more about IGD Visit website Previous Ecohustler Next Code+Ink Ready to get started? Join IGD and thousands of other organisations using Edge. Start Free Today Explore Expert Services --- ### Minima Case Study URL: https://edge.network/case-studies/minima/ Markdown: https://edge.network/case-studies/minima.md JSON: https://edge.network/json/case-studies/minima.json _How Minima scaled decentralised infrastructure globally. Layer 1 blockchain leveraging edge compute for node distribution._ All case studies Blockchain How Minima scaled decentralised infrastructure globally Minima is a Layer 1 blockchain designed to run on any device, enabling true decentralisation. Their network requires globally distributed infrastructure that can scale with node growth while maintaining consistent performance. Results 988 Edge nodes <50ms Global latency 0 Egress fees 99.99% Uptime Products Used CDN Compute DNS Storage Expert Services The Challenge Traditional cloud infrastructure contradicts the ethos of decentralisation—centralised data centres create single points of failure. Minima needed infrastructure that was inherently distributed, with nodes across the globe to support their growing network of participants. The Solution Edge's 988 edge locations provide the distributed infrastructure Minima needs. Content and updates are delivered from the nearest node, reducing latency and improving reliability for network participants worldwide. The decentralised nature of Edge aligns with Minima's core values. Key Results Truly distributed infrastructure Global node support Reduced latency for participants Aligned with decentralisation values Scalable as network grows Consistent global performance Learn more about Minima Visit website Previous XCOPY Next Bauer Media Ready to get started? Join Minima and thousands of other organisations using Edge. Start Free Today Contact Sales --- ### Monocle Case Study URL: https://edge.network/case-studies/monocle/ Markdown: https://edge.network/case-studies/monocle.md JSON: https://edge.network/json/case-studies/monocle.json _How Monocle delivers premium content to 180+ countries. Global affairs and lifestyle media brand achieving sub-50ms latency worldwide._ All case studies Media & Publishing How Monocle delivers premium content to 180+ countries Monocle is a global affairs and lifestyle media brand with print, digital, and broadcast platforms reaching audiences in over 180 countries. With readers and listeners expecting instant access to premium content worldwide, performance is paramount. Results 180+ Countries reached <50ms Global latency 0 Egress fees 99.99% Uptime Products Used CDN Compute DNS Storage Expert Services "Edge gives us the global reach our audience demands without the complexity we dreaded." M Monocle Media & Broadcasting The Challenge Monocle's global audience expects instant access to rich media content—high-resolution photography, audio streams, and video. Their previous infrastructure struggled with inconsistent performance across regions, particularly in Asia and South America. Traffic spikes during breaking stories caused slowdowns, and unpredictable egress costs made budgeting difficult. The Solution By leveraging Edge's global CDN with 988 edge locations, Monocle now delivers content with sub-50ms latency to their international audience. The zero egress pricing model means predictable costs regardless of traffic spikes from breaking stories or viral content. Smart routing automatically directs users to the fastest available node. Key Results Sub-50ms latency achieved globally Zero egress fees regardless of traffic Consistent performance across all regions Seamless handling of traffic spikes Simplified infrastructure management Predictable monthly costs Learn more about Monocle Visit website Previous Bauer Media Next Ecohustler Ready to get started? Join Monocle and thousands of other organisations using Edge. Start Free Today Explore Expert Services --- ### Peri Happy Case Study URL: https://edge.network/case-studies/perihappy/ Markdown: https://edge.network/case-studies/perihappy.md JSON: https://edge.network/json/case-studies/perihappy.json _How Peri Happy runs a full production stack with agents — CDN, DNS, Compute, and Shield deployed and managed through Edge's agentic tooling, with Edge Labs powering rapid R&D._ All case studies Food & Health How Peri Happy runs production with agents Peri Happy is a nutrition platform for perimenopause and beyond: 550+ evidence-based recipes organised by symptom, an AI planner that builds personalised weekly menus, and a weekly email read by 15,000 women. It's built and run by a tiny team with no dedicated ops. Results 0 Ops headcount 552 Recipes served 15k Weekly readers 988 Edge locations Products Used CDN Compute DNS Storage Shield Edge Labs "We describe what we want and it's live minutes later. The agent deploys, wires up DNS, and keeps watch — we spend our time on recipes and research, not infrastructure." PH Peri Happy Founding team The Challenge A media-rich recipe site with an AI planner behind it is a lot of moving parts for a small team: photography-heavy pages that need to load fast worldwide, a compute backend for the Peri Planner, signup and planner endpoints that attract bots and scrapers, and a weekly publishing cadence that leaves no time for infrastructure work. Hiring ops wasn't an option — the infrastructure had to run itself. The Solution Peri Happy runs entirely on Edge, deployed and managed through Edge's agentic tooling. Their coding agent connects to Edge over MCP: it deploys the site to the CDN, manages DNS records, provisions and updates the Compute instances behind the Peri Planner, and configures Shield to keep bots off signup and planner endpoints. Edge Labs works alongside the team as a rapid R&D partner, prototyping and shipping improvements to the planner itself. Key Results Full stack deployed and managed by agents over MCP Zero dedicated ops headcount Recipe photography served fast from the nearest edge location Peri Planner backend on Edge Compute Shield keeping bots off signup and planner endpoints Edge Labs delivering rapid R&D on the AI planner Learn more about Peri Happy Visit website Previous Sacred Network Ready to get started? Join Peri Happy and thousands of other organisations using Edge. Start Free Today Explore Agent Tooling --- ### Sacred Network Case Study URL: https://edge.network/case-studies/sacred-network/ Markdown: https://edge.network/case-studies/sacred-network.md JSON: https://edge.network/json/case-studies/sacred-network.json _How Sacred Network connects a global community around the world's sacred places — on infrastructure aligned with its values._ All case studies Community How Sacred Network connects a global community Sacred Network is a platform for exploring the world's sacred places — stone circles, temples, energy nodes, and natural sites — bringing together a community of thousands with curated site guides, audio guides, events, and local groups. Results 4,800+ Members 988 Edge locations 50% Less energy 0 Egress fees Products Used CDN Compute DNS Storage Expert Services "Edge gives us infrastructure that reflects what Sacred Network stands for — distributed, conscious, and close to our community wherever they are in the world." CM Connell Macquisten Sacred Network The Challenge A global community platform is demanding for a small team: interactive maps of sacred sites across dozens of countries, media-rich site and audio guides, and members on every continent expecting the site to feel local. And for a project centred on care for the living planet, running it all on energy-hungry centralised data centres would have sat uneasily with the mission. The Solution Sacred Network runs on Edge's decentralised infrastructure — hosting, global content delivery, and DNS on one platform. Guides, imagery, and audio are delivered from the edge location nearest each member, and the distributed architecture is up to 50% greener than the traditional cloud, keeping the infrastructure true to the community's values. Key Results A global community served from nearby edge locations Media-rich site and audio guides delivered fast worldwide Infrastructure aligned with the project’s values 50% greener than centralised cloud Zero egress fees on media delivery One platform for hosting, delivery, and DNS Learn more about Sacred Network Visit website Previous Tinder Next Peri Happy Ready to get started? Join Sacred Network and thousands of other organisations using Edge. Start Free Today Contact Sales --- ### Tinder Case Study URL: https://edge.network/case-studies/tinder/ Markdown: https://edge.network/case-studies/tinder.md JSON: https://edge.network/json/case-studies/tinder.json _How Tinder delivered Year in Swipe to 30M users. Scaling real-time image processing for millions of daily active users._ All case studies Consumer Tech How Tinder delivered Year in Swipe to 30M users Tinder is the world's most popular dating app. For their annual Year in Swipe campaign—a personalised wrap-up of each user's yearly activity—they needed infrastructure that could handle a massive traffic surge as millions of users rushed to see their stats. Results 30M Daily users 0 Downtime <100ms Load time 988 Edge locations Products Used CDN Compute DNS Storage Expert Services The Challenge Year in Swipe generates enormous traffic spikes as users share their personalised stats across social media. With 30 million daily active users expected to access the campaign simultaneously, Tinder needed CDN infrastructure that could handle viral-scale traffic without downtime or degraded performance. The Solution Edge's global CDN delivered Year in Swipe content from 988 edge locations worldwide, ensuring instant load times regardless of traffic spikes. The campaign launched flawlessly, handling peak loads without a single incident of downtime. Key Results 30M daily users served flawlessly Zero downtime during peak traffic Sub-100ms load times globally Viral sharing handled seamlessly Zero egress fees at massive scale Campaign delivered on time and on budget Learn more about Tinder Visit website Previous Code+Ink Next Sacred Network Ready to get started? Join Tinder and thousands of other organisations using Edge. Start Free Today Contact Sales --- ### XCOPY Case Study URL: https://edge.network/case-studies/xcopy/ Markdown: https://edge.network/case-studies/xcopy.md JSON: https://edge.network/json/case-studies/xcopy.json _How XCOPY delivers high-resolution art to collectors worldwide. Pioneering crypto artist serving collectors with instant asset delivery._ All case studies Digital Art & NFTs How XCOPY delivers high-resolution art to collectors worldwide XCOPY is one of the most influential crypto artists in the NFT space, known for distinctive dystopian artwork that has sold for millions. Collectors worldwide expect instant access to high-resolution digital assets. Results <100ms Load time 988 Edge locations 0 Egress fees 100% Uptime Products Used CDN Compute DNS Storage Expert Services The Challenge Digital art files are large—often hundreds of megabytes for full-resolution pieces. Collectors expect instant loading regardless of where they are in the world. Traditional hosting solutions meant slow load times in regions far from origin servers, frustrating collectors and impacting sales. The Solution Edge's global CDN ensures XCOPY's artwork loads instantly for collectors anywhere in the world. High-resolution files are cached at 988 edge locations, meaning a collector in Tokyo gets the same instant experience as someone in London or New York. Key Results Instant loading for high-res artwork Global collector experience improved Zero egress fees on large files Reliable delivery for drops and auctions Simplified infrastructure management Consistent performance worldwide Learn more about XCOPY Visit website Next Minima Ready to get started? Join XCOPY and thousands of other organisations using Edge. Start Free Today Contact Sales --- ## Blog (Optional) ### A Fairer Internet URL: https://edge.network/blog/a-fairer-internet/ Markdown: https://edge.network/blog/a-fairer-internet.md JSON: https://edge.network/json/blog/a-fairer-internet.json _Why the infrastructure that powers our digital society should be owned by the many, not the few — and how Edge is building a fairer, community-run internet._ Blog | Company 3 min read A Fairer Internet Why the infrastructure that powers our digital society should be owned by the many, not the few — and how Edge is building a fairer, community-run internet. WL Will Lebens COO & Co-founder Imagine the pandemic without the internet. No food delivery apps to keep you fed. No video calls to connect with family. No remote work to keep businesses running. No streaming to keep you sane during lockdown. It's almost unthinkable — and that tells us something important about where we are as a society. Connectivity has crossed from luxury to necessity. It's become analogous to water or power — a utility so fundamental to modern life that we can barely function without it. And yet, the infrastructure that underpins this essential service is owned and controlled by remarkably few organisations. A Concentrated Cloud AWS hosts over 9 million websites and commands more than 30% of the cloud infrastructure market. Google Cloud holds roughly 13%. Microsoft Azure sits at around 7%. Between just three companies, over half of the internet's infrastructure is accounted for. The digital backbone of modern society — the thing we rely on for everything from healthcare to education to commerce — is concentrated in the hands of a tiny number of corporations. That concentration comes with risks. It means single points of failure. It means pricing power that favours the provider, not the user. And it means that the wealth generated by the internet flows upward to a select few, rather than being shared with the communities that actually make it work. A Different Way Edge believes there is a different way. We're a not-for-profit organisation, and that's a deliberate choice. We believe that the infrastructure powering our digital society should be owned collectively — by the people who use it and contribute to it. Our lightweight infrastructure model makes this possible. Instead of requiring billions of pounds in capital to build data centres, Edge allows anyone with a laptop, phone, or gaming console to offer their spare computing capacity to the network. You become part of the cloud. You contribute to its power. And in return, you earn revenue from the services your device helps provide. Revenue Shared with Everyone This is the fundamental difference. In the traditional cloud model, the revenue generated by infrastructure flows to shareholders and executives at the world's richest companies. In the Edge model, that revenue is shared with everyone who contributes. The more you participate, the more you earn. It's a network that provides secure and performant services — the same compute, storage, and delivery that any cloud platform offers — but does so in a way that's distributed, community-owned, and fundamentally fairer. The internet should belong to the people who build it, use it, and depend on it. Edge is how we get there. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Blockchain Explained URL: https://edge.network/blog/blockchain-explained/ Markdown: https://edge.network/blog/blockchain-explained.md JSON: https://edge.network/json/blog/blockchain-explained.json _Edge Network uses its own blockchain — here's why. And how._ Blog | Engineering 4 min read Blockchain Explained Edge Network uses its own blockchain — here's why. And how. AD Adam K Dean CTO We use the #TechForGood hashtag a lot at Edge. It's not just a slogan — it captures something fundamental about why we built the network the way we did. Blockchain helps Edge Network be fair, and it keeps us accountable to the community that makes it all possible. But what does that actually mean in practice? Let's break down the why and the how. Why: Staking Every host on Edge Network is required to stake 5,000 $EDGE tokens before they can contribute capacity . This isn't an arbitrary barrier — it serves two critical purposes. First, the blockchain holds a public record of each contributor's commitment to the network. It's visible, verifiable, and immutable. Second, the stake protects the network against malicious actors. If someone wants to disrupt the network, they have skin in the game — and something to lose. This mechanism ensures that the people running infrastructure on Edge are genuinely invested in its success. Why: Value Attribution When customers use Edge Network — whether for compute, storage, CDN, or DNS — the blockchain measures that usage in real time. It tracks how much data is stored, how much bandwidth is consumed, and how much processing power is used. Then it divides rewards between the contributors who provided that capacity, proportionally and transparently. There's no middle manager deciding who gets paid what. No opaque algorithm making decisions behind closed doors. The blockchain handles value attribution automatically, and anyone can verify the calculations. This is what fairness looks like at the protocol level. Why: Network Governance Staking doesn't just protect the network — it gives contributors a voice. Stakers can make suggestions for how the network should evolve, vote on proposals, and even veto decisions they disagree with. We're starting with an advisory model — gathering input from the community and incorporating it into our roadmap. But the direction of travel is clear: full decentralisation of governance, where the community has direct control over the network's future. This isn't governance theatre. It's a structured, blockchain-backed system that ensures the people who build and maintain the network have a meaningful say in how it's run. How: Edge's Own Blockchain Edge runs its own independent blockchain, purpose-built for the demands of a distributed cloud network. Why not just use Ethereum or another existing chain? Because our network generates millions of micro-transactions — every data request, every storage operation, every compute task creates on-chain activity. On a public blockchain with gas fees, that would be prohibitively expensive. On Edge's own chain, those transactions are processed internally with no fees. Customers don't need to know or care about any of this. They can pay for Edge services with traditional currency — credit card, bank transfer, whatever works. The blockchain operates under the hood, handling the mechanics of value attribution and contributor rewards without requiring customers to hold or manage tokens. How: The Bridge For contributors and token holders, Edge maintains a bridge between its internal blockchain and connected external networks. The $EDGE token exists as an ERC-20 on Ethereum. When contributors want to participate in the network, they convert their $EDGE ERC-20 tokens to $XE via the bridge — $XE being the internal token used within Edge's own blockchain. When they want to cash out their earnings, they convert $XE back to $EDGE ERC-20 and can trade or hold as they see fit. This architecture gives us the best of both worlds: the speed and zero-fee transactions of a purpose-built chain for internal operations, combined with the liquidity and interoperability of the Ethereum ecosystem for external trading and staking. The Bigger Picture Blockchain isn't the product at Edge — it's the engine. It's the mechanism that ensures fairness, enables transparency, and gives the community genuine ownership of the network they're building. Every stake, every transaction, every vote is recorded on-chain and open to scrutiny. That's what #TechForGood looks like when you build it into the protocol itself. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Blog URL: https://edge.network/blog/ Markdown: https://edge.network/blog.md JSON: https://edge.network/json/blog.json _Technical articles and industry insights from the Edge team. Decentralized computing, cloud infrastructure, and the future of the web._ Blog Technical Articles & Insights Deep dives into decentralized computing, cloud infrastructure, and the technology shaping the future of the web. Recent Articles From the engineering, product, and research teams at Edge. Use case 3 min read Migrating a Ghost Blog from AWS Lightsail Practical steps to move a Ghost instance including database, media files and DNS, highlighting removal of egress exposure. Edge Team Read more Use case 3 min read Deploying WordPress 7.1 Beta on Edge Network Walkthrough for deploying the new beta on Edge VMs with live resize, private networking and free CDN tier. Focus on performance and cost advantages over traditional hosts. Edge Team Read more Company 12 min read The New Path for Edge: A New Cloud, New Tools, and What's Next We never stopped building. While the major cloud providers were making headlines for the wrong reasons, we went back to the foundations and rebuilt everything. Here's what's live today, and a first look at what comes next. Joseph Denne Read more Industry 8 min read Setting the Stage for Q2 Success with Edge Network Q2 is a pivotal time to set ambitious goals and ensure your infrastructure can keep up. Edge Network delivers 100% uptime, zero egress fees, and unmatched cost efficiency. Will Lebens Read more Industry 6 min read The Hidden Cost of Cloud Downtime Cloud downtime isn't just an inconvenience — it's a business killer. A single hour of outage can result in millions in lost revenue, damaged customer trust, and long-term reputational harm. Will Lebens Read more Industry 7 min read How to Avoid Cloud Cost Overruns in 2026: A Decentralised Solution Cloud cost overruns are a growing pain point for enterprises. Discover how Edge Network offers transparent pricing, zero egress fees, and 20%+ savings. Joseph Denne Read more Partnership 6 min read Edge Network Partner With BLOCKv: Unlocking True Decentralization For The Largest Web3 Enterprise Layer Edge and BLOCKv are partnering to bring fully decentralized cloud infrastructure to the largest Web3 enterprise layer, integrating Edge Storage, CDN and AI. Joseph Denne Read more Engineering 5 min read Why Decentralized Computing is Necessary for Fast Scaling AI Capabilities AI's insatiable appetite for compute power is pushing centralized clouds to their breaking point. We explore how decentralized computing offers the solution. Adam K Dean Read more Engineering 4 min read Edge Computing in CDN Technology: How Content Delivery is Changing Does edge computing include CDNs? How the two technologies overlap, where they differ, and how edge computing is reshaping content delivery for the better. Will Lebens Read more Engineering 4 min read Why Decentralization is Essential for DNS Security A new wave of decentralization is offering potential solutions to enhance DNS security, resilience and privacy. Adam K Dean Read more Sustainability 4 min read Environmental Implications of Decentralized Hosting Platforms Exploring how decentralized hosting reduces energy consumption, leverages underutilized resources and promotes renewable energy. Will Lebens Read more Engineering 4 min read How Decentralization Enhances Cloud Storage Security Decentralized cloud storage offers a more secure alternative to traditional centralized solutions through encryption, distribution and redundancy. Will Lebens Read more Engineering 4 min read Understanding Edge Computing in a Decentralized World The concept of decentralization is prompting a shift away from centralized systems. We examine edge computing in this new paradigm. Adam K Dean Read more Engineering 4 min read The Future of Internet: Decentralized Cloud Hosting Decentralized cloud hosting promises to dramatically shift the status quo and reshape the future of the Internet. Will Lebens Read more Sustainability 2 min read The Carbon Offset Cloud What if you could run your digital products in a cloud that was green from the off? One that didn't demand more leaves to cover its indiscretions? Will Lebens Read more Network 3 min read The World According to Edge What global reach means to us and why we're able to offer market-leading cloud services wherever you live. Will Lebens Read more Engineering 3 min read Why We Open Source The technology strategy and philosophy behind Edge Network: why we open source our code, how openness builds trust, and why all roads eventually lead to DAO. Adam K Dean Read more Engineering 4 min read Edge and Web3 Edge is the infrastructure of Web3 — but what is Web3 and why does it matter? And how does Edge Network fit into its decentralised future? Will Lebens Read more Community 2 min read Hosting the Future Running a blockchain project? Want to host for free on Edge Network? Our campaign to support crypto and web3 businesses. Will Lebens Read more Sustainability 2 min read The Offset Network Plant trees, by all means. But do it because you want to, not because you feel like you have to. Will Lebens Read more Community 3 min read Crowd Infrastructure Edge Network harnesses the power of people to change digital infrastructure — and with it the world. Will Lebens Read more Engineering 4 min read Blockchain Explained Edge Network uses its own blockchain — here's why. And how. Adam K Dean Read more Industry 2 min read The New Media Platform Edge offers enhanced performance for optimal user experience — an ideal application for media brands. Will Lebens Read more Product 2 min read Future CDN, Today How Edge Network's edge-native CDN cuts content delivery costs by up to 90% while improving performance, with zero egress fees and a global node network. Will Lebens Read more Sustainability 3 min read Cleaning Up the Cloud Is the cloud really just smog? It's time for digital infrastructure to take its carbon footprint more seriously. Will Lebens Read more Engineering 2 min read Hidden in Plain Sight Edge Network stores the Internet in homes and offices all around us. But that doesn't make it any less secure. Adam K Dean Read more Company 2 min read The Network That Works for You Edge can cut your digital infrastructure bill by up to 90%. How the community-powered network delivers cloud services for less, and works for its users. Joseph Denne Read more Engineering 3 min read The Cloud Is Not Enough We're on the cusp of unprecedented demand for data storage and traditional infrastructure just won't cut it. Adam K Dean Read more Sustainability 3 min read The Network Under Your Nose We don't need massive, dedicated server farms to power the internet. You already carry a perfectly usable cloud in your pocket. Will Lebens Read more Network 2 min read The Local, Global Network Edge is a global network, locally sourced: our nodes are located in homes and offices everywhere. Will Lebens Read more Company 3 min read A Fairer Internet Why the infrastructure that powers our digital society should be owned by the many, not the few — and how Edge is building a fairer, community-run internet. Will Lebens Read more Get Started Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Full access to all products Zero egress fees Unlimited bandwidth No commitment after Stay Updated Subscribe to our newsletter for the latest news, product updates, and engineering insights. Subscribe --- ### Cleaning Up the Cloud URL: https://edge.network/blog/cleaning-up-the-cloud/ Markdown: https://edge.network/blog/cleaning-up-the-cloud.md JSON: https://edge.network/json/blog/cleaning-up-the-cloud.json _Is the cloud really just smog? It's time for digital infrastructure to take its carbon footprint more seriously._ Blog | Sustainability 3 min read Cleaning Up the Cloud Is the cloud really just smog? It's time for digital infrastructure to take its carbon footprint more seriously. WL Will Lebens COO & Co-founder Microsoft made headlines by sinking servers into the ocean — an experiment in green cooling that captured imaginations but, in reality, amounted to little more than a PR solution. The carbon footprint of the cloud is a serious problem, and it demands serious answers. The Scale of the Problem By 2040, digital storage alone is projected to account for 14% of the world's carbon emissions. To put that in perspective, the cloud industry is already dirtier than all air travel combined. Every data centre built, every server rack powered around the clock, every cooling system running non-stop — it all adds up to an environmental cost that the tech industry has been remarkably slow to address. A Credible Alternative Edge has grown steadily in both clients and contributors, offering a credible greener alternative to centralised cloud infrastructure. This isn't greenwashing or offsetting — it's a structural change in how digital services are delivered. Greener by Design Edge is greener not because of a bolt-on sustainability initiative, but because of how the network is built . Two principles make the difference. First, Edge reuses existing hardware. Instead of building new data centres filled with purpose-built servers, the network runs on devices that already exist — laptops, PCs, phones, set-top boxes. These machines are already powered on, already connected, and already consuming energy. Edge puts their idle capacity to work, turning waste into utility without adding to the hardware footprint. Second, Edge reduces the distance between storage and consumption. Traditional cloud providers route data through a handful of massive data centres, often thousands of miles from the end user. Edge distributes content across a network of devices that are geographically closer to the people requesting it. Shorter distances mean less energy consumed in transit, fewer network hops, and a lighter load on the infrastructure that connects them. Beyond Offsets The cloud industry's approach to sustainability has largely relied on carbon offsets and renewable energy credits — accounting tricks that balance the books without reducing actual emissions. Edge takes a different path. By eliminating the need for new hardware and minimising the energy required to move data, the network reduces emissions at the source. It's not about compensating for damage — it's about doing less damage in the first place. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Crowd Infrastructure URL: https://edge.network/blog/crowd-infrastructure/ Markdown: https://edge.network/blog/crowd-infrastructure.md JSON: https://edge.network/json/blog/crowd-infrastructure.json _Edge Network harnesses the power of people to change digital infrastructure — and with it the world._ Blog | Community 3 min read Crowd Infrastructure Edge Network harnesses the power of people to change digital infrastructure — and with it the world. WL Will Lebens COO & Co-founder Jack Dorsey once said that Bitcoin is the one thing that unites people across borders. It's a powerful statement — and he's right. Bitcoin is perhaps the ultimate example of what blockchain technology can do when it's pointed at a real problem. It crosses borders, bypasses governments, and democratises finance. No single entity owns it. No one can shut it down. And yet it works, reliably, at global scale. Fairness in Digital Infrastructure For Edge, the principle is the same, but the arena is different. We're not trying to reinvent money — we're trying to bring fairness to digital infrastructure. The cloud, as it exists today, is controlled by a handful of companies: Google, Amazon, Microsoft. They set the prices. They hold the data. They decide the rules. And while those services are undeniably powerful, they also concentrate an extraordinary amount of control in very few hands. Edge Network is our answer to that. We're on a journey to join together laptops, phones, consoles, and servers into a new kind of cloud — one that doesn't depend on any single provider. A cloud built by people, for people. We call it crowd infrastructure. Blockchain at the Core Blockchain is what makes it possible. Our blockchain transparently calculates the data stored by customers and how much contributors earn for the capacity they provide. There's no black box. No opaque billing. No hidden margins. Everything is recorded, verifiable, and fair. That transparency isn't a nice-to-have — it's the core of why Edge exists. We set out to make the internet a fairer place. Not in an abstract, aspirational way, but through a concrete mechanism that ensures everyone who contributes to the network gets fairly rewarded, and everyone who uses it pays a fair price. That's what blockchain enables when you apply it to infrastructure rather than just finance. Real Change, Not Just a Vision We're not promising world peace. But we are offering one powerful example of how blockchain can bring real, tangible change. A distributed cloud network where the infrastructure belongs to the people who build it. Where pricing is transparent. Where governance is shared. Where fairness isn't a marketing term but a protocol-level guarantee. This is bigger than any single product or service. It's about proving that a better model is possible — and that people, when given the tools and the incentive, will build something extraordinary together. Be Part of It You can be part of it. Move your digital services to Edge and experience cloud infrastructure that's transparent, fair, and community-owned. Or join the growing crowd of contributors — plug your spare capacity into the network and earn for what you provide. Either way, you're helping build something that matters. Crowdfunding changed how projects get financed. Crowdsourcing changed how work gets done. Crowd infrastructure is changing how the internet itself is built. And it starts with people like you. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Deploying WordPress 7.1 Beta on Edge Network URL: https://edge.network/blog/wordpress-71-beta-edge/ Markdown: https://edge.network/blog/wordpress-71-beta-edge.md JSON: https://edge.network/json/blog/wordpress-71-beta-edge.json _Walkthrough for deploying the new beta on Edge VMs with live resize, private networking and free CDN tier. Focus on performance and cost advantages over traditional hosts._ Blog | Use case 3 min read Deploying WordPress 7.1 Beta on Edge Network Walkthrough for deploying the new beta on Edge VMs with live resize, private networking and free CDN tier. Focus on performance and cost advantages over traditional hosts. ET Edge Team Traditional WordPress hosts often impose egress charges on media-heavy sites and limit how quickly you can scale resources during testing. Edge Network removes those charges entirely while providing global VMs that deploy in under 60 seconds and resize live without downtime. WordPress 7.1 Beta 1 compatibility notes WordPress 7.1 Beta 1 runs on PHP 8.1 or later with the default MySQL or MariaDB backend. Edge Compute images based on Ubuntu 24.04 include PHP 8.3 by default, satisfying the requirement without additional configuration. The beta does not introduce new database schema changes that affect standard object storage mounts, so the free Storage tier can hold uploads alongside the VM filesystem. Deploying the base VM Use the Edge CLI to create a VM sized for typical WordPress workloads. The command below provisions a 2 vCPU, 4 GB instance with NVMe storage in under 60 seconds. edge compute create --name wp-beta-1 --size s-2vcpu-4gb --image ubuntu-24 After the instance reports as running, connect via SSH and update packages: Run apt update && apt upgrade -y Install required packages: apt install -y apache2 mysql-server php8.3 php8.3-mysql php8.3-curl php8.3-gd php8.3-mbstring php8.3-xml php8.3-zip Enable and start services: systemctl enable --now apache2 mysql Download and extract the beta: wget https://wordpress.org/wordpress-7.1-beta1.tar.gz tar -xzf wordpress-7.1-beta1.tar.gz -C /var/www/html --strip-components=1 Set ownership and create the configuration file from the sample, then complete the browser-based installer at your VM IP. Live resize during testing WordPress 7.1 Beta testing often requires temporary increases in memory or CPU when running multiple plugins. Edge supports live resize from the dashboard or CLI without instance restart. Change the size flag to a larger preset such as s-4vcpu-8gb and apply; the VM continues serving requests while resources adjust. Private networking with VxLAN Place the WordPress VM and a separate database VM on the same private network to keep query traffic off the public internet. Create a VxLAN network through the dashboard or API, attach both instances, and assign RFC 1918 addresses. This configuration removes the need for public database ports and supports the 99.99% SLA on the Compute platform. Update wp-config.php to point to the private database address rather than localhost or a public IP. Adding the free CDN tier Media-heavy WordPress sites benefit from Edge CDN for static assets and images. Create a free CDN zone, point it at your VM origin, and enable Edge Rules to cache /wp-content/uploads/* and /wp-includes/* paths. The CDN provides instant purge capability and DDoS protection at no extra cost. Because Edge levies zero egress fees on all traffic, bandwidth-heavy image or video content incurs no additional charges regardless of volume. Update WordPress site URL settings to the CDN hostname for static assets while keeping dynamic requests routed to the origin VM. Performance and cost comparison Sub-50 ms latency reaches 95% of internet users from the 5K+ node network. Traditional hosts typically add egress fees once monthly transfer exceeds a few hundred gigabytes; Edge removes this line item permanently. The same 2 vCPU, 4 GB workload runs at least 20% lower than equivalent hyperscaler or managed WordPress plans when measured on hourly prepaid billing. Free DNS, CDN and Storage tiers further reduce the baseline cost. A starter Compute credit of $5 is available on signup, sufficient to run the beta instance for initial testing periods. Next steps Monitor query performance through standard MySQL slow-query logging and adjust the live resize setting if plugin testing increases load. The combination of private networking, zero egress and global CDN gives WordPress 7.1 Beta testers a production-like environment without the usual hosting penalties. Full instructions for WordPress on Edge are available at /solutions/wordpress . Compute details appear at /compute and CDN configuration at /cdn . Current pricing is listed at /pricing . Free to sign up, no card required: https://edge.network/account Get Started Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Edge and Web3 URL: https://edge.network/blog/edge-and-web3/ Markdown: https://edge.network/blog/edge-and-web3.md JSON: https://edge.network/json/blog/edge-and-web3.json _Edge is the infrastructure of Web3 — but what is Web3 and why does it matter? And how does Edge Network fit into its decentralised future?_ Blog | Engineering 4 min read Edge and Web3 Edge is the infrastructure of Web3 — but what is Web3 and why does it matter? And how does Edge Network fit into its decentralised future? WL Will Lebens COO & Co-founder Our community is measured in hundreds of thousands. Some are deep experts in crypto and decentralised technology. Others are newer to the space — curious, interested, but still figuring out what all the terminology actually means. This one's for everyone. A Brief History of the Web To understand Web3, it helps to know what came before it. Web 1.0 was the read-only web. Static pages, hand-coded HTML, directories and links. You could look at things, but that was about it. The internet was a library — useful, but largely passive. Web 2.0 changed everything. Platforms emerged. Users started creating content — blogs, social media posts, videos, reviews. The internet became interactive, collaborative, and vastly more powerful. But it also became concentrated. A small number of massive companies — Google, Amazon, Facebook, Apple, Microsoft — came to control the infrastructure, the platforms, and the data. The web was built by its users, but owned by its landlords. That's the world we live in now. And it's the world Web3 is trying to change. What Is Web3? Web3 is the decentralised web. It's a vision for an internet where control isn't concentrated in the hands of a few corporations, but distributed among the people who use it and build it. The technology that makes this possible is blockchain — a way of recording information that's transparent, tamper-resistant, and doesn't require a central authority to maintain. Blockchain underpins a range of tools and systems that are reshaping how the internet works. DeFi — decentralised finance — facilitates financial transactions without banks or traditional intermediaries. Lending, borrowing, trading, and earning interest, all governed by code rather than institutions. DAOs — decentralised autonomous organisations — are transparent, rule-based entities where governance is shared among members rather than concentrated in a boardroom. Decisions are made collectively, with rules enforced by smart contracts rather than managers. These aren't theoretical concepts. They're working systems, used by millions of people, managing billions in value. And they all need infrastructure to run on. Where Edge Fits In Edge is the infrastructure of Web3. A decentralised web needs a decentralised cloud — and that's exactly what Edge provides. Compute, storage, content delivery, and DNS services, all running on a distributed network powered by blockchain technology. No centralised data centres. No single points of failure. No corporate gatekeepers. The irony of much of the current Web3 ecosystem is that it still runs on Web 2.0 infrastructure. Decentralised applications hosted on Amazon Web Services. DAOs with their governance tools stored on Google Cloud. The front end is decentralised, but the back end is the same old centralised stack. Edge solves that problem. It provides genuinely decentralised infrastructure — a cloud that practises what Web3 preaches. Setting Up a DAO Edge isn't just building infrastructure for DAOs — it's becoming one. The network is on a path toward full decentralised governance, where the community that runs the nodes and uses the services also has a say in how the project evolves. That's the whole point. Cloud infrastructure today is dominated by Amazon, Google, and Microsoft. They control the pipes, set the prices, and extract the value. Edge aims to share that infrastructure — and the revenue it generates — with everyone who participates. Spare Capacity, Shared Value The Edge Network is powered by spare capacity on devices around the world. If you've got a machine that's not working at full tilt, you can contribute its unused resources to the network and get paid for doing so. Your hardware becomes part of a global cloud, and you become part of a global community. It's a model where everyone gets paid for the value they contribute. Not just the shareholders of a tech conglomerate, but the actual people who make the network work. First-Mover Advantage Edge has been building this for years — long before "Web3" became a buzzword. The network is live, the technology is production-grade, and the community is growing. That head start matters. While others are still theorising about what decentralised cloud might look like, Edge is already running it. Created for the people. Powered by the people. And designed to share the wealth with the people who make it possible. That's what Web3 infrastructure looks like — and that's what Edge is building. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Edge Computing in CDN Technology: How Content Delivery is Changing URL: https://edge.network/blog/edge-computing-in-cdn-technology/ Markdown: https://edge.network/blog/edge-computing-in-cdn-technology.md JSON: https://edge.network/json/blog/edge-computing-in-cdn-technology.json _Does edge computing include CDNs? How the two technologies overlap, where they differ, and how edge computing is reshaping content delivery for the better._ Blog | Engineering 4 min read Edge Computing in CDN Technology: How Content Delivery is Changing Does edge computing include CDNs? How the two technologies overlap, where they differ, and how edge computing is reshaping content delivery for the better. WL Will Lebens COO & Co-founder In the digital era, the speed and efficiency of content delivery are paramount. As the volume of online content surges and user expectations for seamless experiences grow, Content Delivery Networks have become indispensable. CDNs have long served as the backbone of the internet, ensuring content reaches users quickly and reliably. However, the integration of edge computing into CDN technology is ushering in a new era — one defined by hyper-local processing, intelligent caching, and dramatically reduced latency. In this article, we explore how this convergence is reshaping the content delivery landscape. Understanding the CDN Foundation At their core, CDNs are networks of geographically distributed servers designed to deliver content to users based on their location. By caching copies of content across multiple points of presence, CDNs reduce the distance data must travel, resulting in faster load times and a better user experience. Several key concepts underpin traditional CDN architecture: Caching is the fundamental mechanism by which CDNs store copies of static content — images, stylesheets, scripts, and video — on servers closer to end users. This eliminates the need to fetch content from a distant origin server for every request. Load balancing distributes incoming traffic across multiple servers, preventing any single server from becoming overwhelmed. This ensures consistent performance even during traffic spikes and peak demand periods. Redundancy is built into CDN architecture through the replication of content across multiple nodes. If one server fails, traffic is automatically rerouted to another, ensuring high availability and resilience. Network optimization techniques such as TCP acceleration, route optimization, and protocol-level enhancements further reduce latency and improve throughput across the delivery chain. Edge Computing: Shifting the Paradigm Edge computing represents a fundamental shift in how data is processed. Rather than sending all data to a centralized cloud or data center for processing, edge computing pushes computation to the periphery of the network — closer to where data is generated and consumed. This approach minimizes the round-trip time for data, enabling near-instantaneous processing and response. When edge computing is integrated into CDN infrastructure, the result is a network that doesn't just deliver content — it processes, transforms, and optimizes it in real time, right at the point of delivery. The Impact on Content Delivery Reduced latency is the most immediate and tangible benefit. By processing requests at the edge rather than routing them to distant origin servers, edge-enabled CDNs can serve content with significantly lower round-trip times. For applications such as live video streaming, real-time gaming, and interactive web experiences, this reduction in latency is transformative. Localized content processing allows edge nodes to perform tasks such as image resizing, format conversion, A/B testing, and personalization without communicating with the origin. Content can be dynamically tailored to the user's device, location, and preferences at the point of delivery. Bandwidth optimization is achieved by processing and filtering data at the edge before it traverses the wider network. Only essential data is transmitted upstream, reducing bandwidth consumption and lowering costs for content providers. Enhanced security at the edge enables CDNs to detect and mitigate threats — such as DDoS attacks, bot traffic, and malicious requests — closer to the source, before they can reach the origin infrastructure. This distributed security model is inherently more resilient than centralized approaches. Real-World Applications The convergence of edge computing and CDN technology is already driving innovation across industries. Video streaming platforms leverage edge processing to transcode and adapt streams in real time based on network conditions and device capabilities. E-commerce platforms use edge nodes to personalize product recommendations and pricing without added latency. IoT networks rely on edge CDNs to process sensor data locally, enabling faster decision-making in manufacturing, logistics, and smart city infrastructure. Challenges and Considerations Despite its promise, the integration of edge computing into CDN technology is not without challenges. Managing a highly distributed network of edge nodes introduces complexity in orchestration, monitoring, and consistency. Ensuring data coherence across thousands of edge locations requires sophisticated synchronization mechanisms. Security, too, becomes a distributed challenge — each edge node represents a potential attack surface that must be hardened and monitored. Furthermore, the economics of edge deployment must be carefully considered. While edge processing reduces bandwidth and origin load, the cost of maintaining a large fleet of edge nodes — including hardware, energy, and operational overhead — can be significant. Summary The integration of edge computing into CDN technology represents one of the most significant evolutions in content delivery. By bringing processing power to the edge of the network, CDNs are evolving from passive content mirrors into intelligent, adaptive delivery platforms capable of meeting the demands of a real-time, data-intensive internet. At Edge, we are building this future today — a fully decentralized CDN that harnesses the power of edge computing to deliver content faster, smarter, and more efficiently than traditional centralized alternatives. The era of the intelligent edge is here, and it is transforming how the world accesses content. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Edge Network Partner With BLOCKv: Unlocking True Decentralization For The Largest Web3 Enterprise Layer URL: https://edge.network/blog/blockv-partnership/ Markdown: https://edge.network/blog/blockv-partnership.md JSON: https://edge.network/json/blog/blockv-partnership.json _Edge and BLOCKv are partnering to bring fully decentralized cloud infrastructure to the largest Web3 enterprise layer, integrating Edge Storage, CDN and AI._ Blog | Partnership 6 min read Edge Network Partner With BLOCKv: Unlocking True Decentralization For The Largest Web3 Enterprise Layer Edge and BLOCKv are partnering to bring fully decentralized cloud infrastructure to the largest Web3 enterprise layer, integrating Edge Storage, CDN and AI. JD Joseph Denne CEO & Co-founder Over a decade ago, Edge set out with a singular mission: to solve the challenge of decentralizing cloud computing. What started as an ambitious vision has evolved into a fully operational, production-grade platform — the Edge Network is the first fully decentralized cloud infrastructure, offering compute, content delivery, DNS and storage services without reliance on traditional centralized data centers. Today we are thrilled to announce a landmark partnership with BLOCKv, the most widely adopted Web3 enterprise stack in the world. Together, we are bringing truly decentralized cloud infrastructure to the enterprise layer of Web3 — unlocking new levels of resilience, sovereignty and performance for some of the world's biggest brands. BLOCKv: The Web3 OS BLOCKv has established itself as the operating system for Web3 enterprise adoption. With over 50 million SmartNFTs minted and more than 11 million unique wallets created, BLOCKv is not a speculative project — it is a battle-tested platform powering real-world campaigns at global scale. The roster of brands that have leveraged BLOCKv reads like a who's who of the Fortune 500: VISA, XGames, NBA, Accenture, Burberry, American Express, Pepsi, Yahoo, Procter & Gamble, Gucci, Ben & Jerry's, and eBay have all turned to BLOCKv to create immersive, token-driven experiences for their audiences. BLOCKv's SmartNFT technology goes far beyond static digital collectibles. These are dynamic, programmable digital objects that can evolve, interact, and deliver real utility — from loyalty rewards and exclusive access to gamified brand activations and supply chain verification. It is this deep enterprise integration that makes BLOCKv uniquely positioned to benefit from truly decentralized infrastructure. Bringing Edge's Cloud to BLOCKv Until now, even the most forward-thinking Web3 platforms have had to rely on centralized cloud providers for their underlying infrastructure. This creates a fundamental contradiction: decentralized applications running on centralized servers, subject to the same single points of failure, censorship risks, and vendor lock-in that Web3 was designed to eliminate. This partnership changes that. By integrating Edge Storage, Edge CDN, and Edge AI into the BLOCKv stack, we are providing a fully decentralized foundation for the platform's enterprise operations. Media assets, SmartNFT metadata, and campaign content will be stored and delivered through Edge's globally distributed network of nodes — ensuring high availability, low latency, and genuine decentralization from the ground up. Edge Storage provides resilient, distributed object storage that eliminates single points of failure. Edge CDN delivers content from the closest available node, dramatically reducing load times for end users regardless of their location. And Edge AI opens up new possibilities for intelligent, on-demand processing at the edge of the network, enabling BLOCKv to build smarter, more responsive experiences for its brand partners. Closing Thoughts This partnership represents a convergence of two complementary visions. BLOCKv has proven that Web3 can deliver real value to the world's largest enterprises. Edge has proven that cloud infrastructure can be fully decentralized without compromising on performance or reliability. Together, we are building the stack that Web3 was always supposed to have — decentralized from application layer to infrastructure layer. For brands and enterprises already using BLOCKv, this integration means greater resilience, improved performance, and the confidence that their Web3 initiatives are running on infrastructure that is as decentralized as the technology itself. For the broader Web3 ecosystem, it is a powerful signal that decentralized infrastructure is no longer a distant aspiration — it is here, it works, and it is ready for enterprise scale. We could not be more excited about what this partnership will unlock. Stay tuned for more updates as we roll out the integration and expand the capabilities of what is possible when two pioneering platforms come together. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Environmental Implications of Decentralized Hosting Platforms URL: https://edge.network/blog/environmental-implications-decentralized-hosting/ Markdown: https://edge.network/blog/environmental-implications-decentralized-hosting.md JSON: https://edge.network/json/blog/environmental-implications-decentralized-hosting.json _Exploring how decentralized hosting reduces energy consumption, leverages underutilized resources and promotes renewable energy._ Blog | Sustainability 4 min read Environmental Implications of Decentralized Hosting Platforms Exploring how decentralized hosting reduces energy consumption, leverages underutilized resources and promotes renewable energy. WL Will Lebens COO & Co-founder As the digital economy expands, so does its environmental footprint. Data centers — the backbone of traditional cloud hosting — consume vast amounts of energy, generate significant heat, and contribute measurably to global carbon emissions. The question of how we host and deliver digital services is no longer just a technical one; it is an environmental imperative. Decentralized hosting platforms offer a fundamentally different approach, one that has the potential to significantly reduce the environmental impact of our digital infrastructure. In this article, we explore the environmental implications of decentralized hosting and how it can contribute to a more sustainable internet. Reducing Energy Consumption Traditional data centers are enormous energy consumers. In the United States alone, data centers account for approximately 2% of total electricity consumption, and this figure is growing year on year as demand for cloud services, streaming, and AI workloads intensifies. These facilities require not only power for computation, but also substantial energy for cooling systems, redundant power supplies, and round-the-clock operations. Decentralized hosting reduces energy consumption by distributing workloads across a network of smaller, existing devices rather than concentrating them in purpose-built mega-facilities. By processing data closer to where it is needed, decentralized networks also reduce the energy spent on long-distance data transmission. At Edge, our network reduces data travel distance by approximately 50%, translating directly into lower energy usage across the delivery chain. This distributed model avoids the energy overhead associated with maintaining the massive cooling infrastructure that traditional data centers require. Smaller, distributed nodes generate less concentrated heat and can often operate within the ambient cooling capacity of their environment. Leveraging Underutilized Resources One of the most compelling environmental arguments for decentralized hosting is its ability to harness computing resources that already exist but are sitting idle. Around the world, millions of servers, workstations, and personal devices operate well below their capacity for significant portions of the day. This represents an enormous pool of untapped computational power. Decentralized hosting platforms tap into this idle capacity, effectively recycling existing hardware rather than requiring the manufacture, deployment, and powering of new infrastructure. The environmental benefits are twofold: reduced demand for new hardware production — which carries its own significant carbon and resource footprint — and more efficient utilization of the energy already being consumed to keep these devices running. By making productive use of resources that would otherwise be wasted, decentralized hosting achieves a level of resource efficiency that centralized models simply cannot match. Promoting Renewable Energy Usage The geographical distribution of decentralized hosting networks creates natural opportunities for renewable energy integration. Unlike centralized data centers, which are often located based on land cost and network connectivity rather than energy source, decentralized nodes can be deployed anywhere — including regions with abundant renewable energy resources. Node operators in regions powered by hydroelectric, solar, or wind energy can contribute clean computing power to the network. Over time, this creates a market incentive for node operators to seek out renewable energy sources, as lower energy costs translate into higher margins. The result is a hosting infrastructure that becomes progressively greener as the network grows. Furthermore, the smaller power requirements of individual nodes make them more compatible with local renewable energy installations. A single node can be powered by a modest solar array, whereas a traditional data center requires industrial-scale power infrastructure. Challenges and Mitigation It would be disingenuous to suggest that decentralized hosting is without environmental challenges. The coordination overhead of managing a distributed network — including consensus mechanisms, data replication, and node communication — introduces its own energy costs. Ensuring that the network operates efficiently requires careful protocol design and ongoing optimization. There is also the question of hardware lifecycle. While decentralized hosting makes better use of existing hardware, it also relies on a diverse fleet of devices with varying energy efficiency profiles. Encouraging node operators to use energy-efficient hardware and providing transparency around the network's overall energy consumption are important steps toward mitigating these concerns. Looking Ahead The environmental case for decentralized hosting is strong and growing stronger. As climate awareness increases and regulatory pressure mounts on high-energy industries, the demand for sustainable digital infrastructure will only intensify. Decentralized hosting platforms are uniquely positioned to meet this demand — not as a compromise, but as a genuinely superior model that delivers better performance, greater resilience, and a smaller environmental footprint. At Edge, sustainability is not an afterthought — it is built into the architecture of our network. By distributing workloads across a global network of nodes, reducing data travel distances, and harnessing idle capacity, we are building the kind of internet infrastructure that the planet needs. The future of hosting is decentralized, and it is greener than anything that came before. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Future CDN, Today URL: https://edge.network/blog/future-cdn-today/ Markdown: https://edge.network/blog/future-cdn-today.md JSON: https://edge.network/json/blog/future-cdn-today.json _How Edge Network's edge-native CDN cuts content delivery costs by up to 90% while improving performance, with zero egress fees and a global node network._ Blog | Product 2 min read Future CDN, Today How Edge Network's edge-native CDN cuts content delivery costs by up to 90% while improving performance, with zero egress fees and a global node network. WL Will Lebens COO & Co-founder The future of the cloud is faster, more secure, better for the environment, more cost effective, and fairer. That future isn't hypothetical — it's already here, and more than 70 brands are using it. A CDN Built for What Comes Next Edge CDN isn't just another content delivery network. It's a fundamentally different approach — one that decentralises infrastructure, reduces waste, and passes the savings directly to the businesses that use it. Where legacy providers charge premium rates for moving data through centralised data centres, Edge delivers from the network's edge, closer to users and at a fraction of the cost. Feature-Rich by Design Edge CDN comes loaded with powerful features out of the box, including just-in-time image manipulation. Blur, filter, flip, format, resize, rotate, saturate, sharpen, crop — all applied at the point of request, with no pre-processing required. This means your origin server stays lean while your users receive exactly the asset they need, optimised for their device and context. 60% Filesize Savings Every asset delivered through Edge CDN is compressed and optimised at the point of request. The result is an average of 60% filesize savings across images and static content — less bandwidth consumed, faster load times, and lower costs across the board. Monocle: 77.93% Cost Reduction Monocle, the global affairs and lifestyle publication, has seen a 77.93% reduction in content delivery costs since switching from AWS to Edge CDN. That's not a marginal improvement — it's a transformation of their infrastructure economics, freeing up budget that can be reinvested in content, design, and audience growth. Save Up to 90% The numbers speak for themselves. By removing the inefficiencies of centralised infrastructure and leveraging a distributed network of contributors, Edge CDN can deliver savings of up to 90% compared to traditional providers . The future of content delivery isn't coming — it's already here. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Hidden in Plain Sight URL: https://edge.network/blog/hidden-in-plain-sight/ Markdown: https://edge.network/blog/hidden-in-plain-sight.md JSON: https://edge.network/json/blog/hidden-in-plain-sight.json _Edge Network stores the Internet in homes and offices all around us. But that doesn't make it any less secure._ Blog | Engineering 2 min read Hidden in Plain Sight Edge Network stores the Internet in homes and offices all around us. But that doesn't make it any less secure. AD Adam K Dean CTO There's a common assumption that data is more secure when it's locked away in a distant server fortress — a vast, purpose-built data centre surrounded by fences and security guards. But is that really true? Or does all that distance just make your data slower and more expensive to access? More Cloud-Like Than the Cloud Edge is, in many ways, more cloud-like than the traditional cloud. The original promise of cloud computing was that your data would be everywhere you needed it, available on demand, without you having to think about where it physically lived. Centralised data centres broke that promise by concentrating everything in a handful of locations. Edge fulfils it — placing data onto the devices we actually use, distributed across a network that spans the real world. Close By Doesn't Mean Within Easy Reach The fact that data on the Edge network lives in homes and offices — close to the people who use it — doesn't mean it's exposed. Proximity is not vulnerability. No single file exists on any single device. Every piece of data is encrypted and broken into hundreds of parts, then seeded across devices throughout the network. The Impossibility of Attack To compromise data on Edge, an attacker would need to break into hundreds of homes, pickpocket thousands of phones, and somehow reassemble encrypted fragments without the keys to decrypt them. It's not just difficult — it's impossible. Compare that to a traditional data centre, where a single breach, a single insider threat, or a single misconfigured firewall can expose everything at once. Security Through Distribution Edge's security model is built on distribution, not isolation. By spreading data across a vast number of devices and encrypting every fragment, the network eliminates single points of failure. There is no central vault to crack, no master key to steal, no single server to target. The result is infrastructure that is not only more secure, but also faster and greener — delivering data from nearby devices rather than distant warehouses. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Hosting the Future URL: https://edge.network/blog/hosting-the-future/ Markdown: https://edge.network/blog/hosting-the-future.md JSON: https://edge.network/json/blog/hosting-the-future.json _Running a blockchain project? Want to host for free on Edge Network? Our campaign to support crypto and web3 businesses._ Blog | Community 2 min read Hosting the Future Running a blockchain project? Want to host for free on Edge Network? Our campaign to support crypto and web3 businesses. WL Will Lebens COO & Co-founder The future of the cloud is Edge. That's not a tagline — it's something we genuinely believe. The technology we're building today will be the backbone powering digital services for decades to come. A decentralised, distributed network of devices working together to deliver compute , storage , content delivery and DNS — all without relying on a handful of sprawling data centres controlled by a few big corporations. Proven Faith in Blockchain At the heart of Edge Network is a proven faith in blockchain technology. Not the hype-driven, speculative kind — but blockchain as a tool for fairness and accountability. Our blockchain transparently calculates the data stored by customers, how much contributors earn for the capacity they provide, and how the network operates as a whole. It's the mechanism that keeps everything honest. Blockchain also facilitates governance on the network. By staking $EDGE tokens, contributors don't just earn — they help run the network. They can make suggestions, vote on proposals, and have a genuine say in the direction we take. That's not theoretical. It's built into the protocol. Beyond Our Own Network But Edge isn't just about Edge. We believe in supporting the wider blockchain ecosystem. We've long championed the idea of #TechForGood — the notion that technology should serve people, not exploit them. And blockchain projects, especially new and emerging ones, are some of the most exciting examples of that principle in action. That's why we're planning the On the Edge programme — an initiative to host new and emerging crypto projects for free on Edge Network. If you're building something meaningful in the blockchain space and need reliable, decentralised infrastructure to host your website or digital product, we want to help you get there without the overhead of traditional cloud costs. Get Involved Whether you're a solo developer launching a token project or a small team building the next generation of decentralised tools, you could be eligible for free hosting on Edge Network. We're opening up our infrastructure to support the projects that share our vision of a fairer, more transparent internet. The future of hosting is decentralised, community-powered, and built on blockchain. We're not just hosting the future — we're inviting you to be part of it. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### How Decentralization Enhances Cloud Storage Security URL: https://edge.network/blog/decentralization-cloud-storage-security/ Markdown: https://edge.network/blog/decentralization-cloud-storage-security.md JSON: https://edge.network/json/blog/decentralization-cloud-storage-security.json _Decentralized cloud storage offers a more secure alternative to traditional centralized solutions through encryption, distribution and redundancy._ Blog | Engineering 4 min read How Decentralization Enhances Cloud Storage Security Decentralized cloud storage offers a more secure alternative to traditional centralized solutions through encryption, distribution and redundancy. WL Will Lebens COO & Co-founder As the volume of data generated worldwide continues to grow at an extraordinary pace, the need for secure and reliable cloud storage has never been greater. Traditional centralized cloud storage — where data resides in servers controlled by a single provider — has served as the backbone of modern digital infrastructure. However, it comes with inherent vulnerabilities that decentralized alternatives are uniquely positioned to address. Understanding Decentralized Cloud Storage Decentralized cloud storage distributes data across a network of independent nodes rather than housing it in a handful of data centers owned by one entity. Files are split into encrypted fragments and spread across geographically diverse locations, with no single node holding a complete copy of any file. This architecture fundamentally changes the security equation, removing the single points of failure that plague traditional systems. Instead of trusting one provider with the entirety of your data, a decentralized model relies on cryptographic guarantees and network consensus to ensure integrity, availability, and confidentiality. Improved Data Security One of the most significant advantages of decentralized storage is the use of client-side encryption. Before data ever leaves a user's device, it is encrypted with keys that only the user controls. Unlike centralized providers that often manage encryption keys on the user's behalf — creating a potential point of compromise — decentralized systems ensure that encryption keys remain solely with the data owner. This means that even if an individual node in the network were breached, the attacker would gain access to nothing more than an unintelligible encrypted fragment. Without the user's private key, reconstructing meaningful data is computationally infeasible. Resilience to Attacks Centralized data centers present high-value targets for cyberattacks. A single successful breach can expose millions of records. In a decentralized network, data is dispersed across a vast number of independent nodes. An attacker would need to simultaneously compromise a majority of these nodes — each with its own security measures — to piece together a usable dataset. This distributed architecture makes large-scale data breaches significantly more difficult to execute. The cost and complexity of mounting such an attack act as powerful deterrents, pushing the security posture of decentralized storage far beyond what centralized models can offer. Data Redundancy and Availability Decentralized systems achieve high availability through redundancy. Encrypted fragments of each file are replicated across multiple nodes in the network. If one or several nodes go offline — whether due to hardware failure, maintenance, or a localized attack — the remaining nodes still hold enough fragments to reconstruct the original data seamlessly. This stands in contrast to centralized providers, where an outage at a single data center or region can render data inaccessible for hours or even days. Decentralized redundancy ensures that data remains available around the clock, regardless of conditions at any individual node. Transparency and Trust Trust in centralized storage ultimately depends on the policies and practices of one organization. Users have limited visibility into how their data is stored, handled, or protected behind the scenes. Decentralized storage introduces a new trust model built on blockchain-based verification. Using blockchain, every storage transaction — from file upload to retrieval — can be cryptographically logged and independently verified. This transparent, tamper-proof audit trail allows users and auditors alike to confirm that data has been stored correctly and has not been altered, without relying on the word of a single provider. Privacy Preservation Privacy is a growing concern in an era of increasing regulation and data-driven business models. Centralized providers may be subject to government data requests, internal misuse, or opaque data-sharing agreements. Decentralized storage mitigates these risks by design: because data is encrypted before it leaves the user's device and fragmented across independent nodes, no single party — including the network operator — can access or read the stored information. This architecture aligns naturally with privacy-first principles and regulatory frameworks like GDPR, giving users genuine sovereignty over their data. Challenges and Future Prospects Decentralized cloud storage is not without its challenges. Coordinating a global network of independent nodes requires robust incentive mechanisms, efficient data retrieval protocols, and solutions for ensuring consistent performance across diverse hardware. Latency, network coordination, and user experience still demand continued innovation. However, the trajectory is clear. At Edge, we are building decentralized storage solutions that leverage blockchain technology for data consistency and retrieval verification. By combining client-side encryption, distributed redundancy, and transparent on-chain auditing, we are creating a storage layer that is more secure, more resilient, and more respectful of user privacy than any centralized alternative. The future of cloud storage is decentralized — and it is being built today. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### How to Avoid Cloud Cost Overruns in 2026: A Decentralised Solution URL: https://edge.network/blog/cloud-cost-overruns/ Markdown: https://edge.network/blog/cloud-cost-overruns.md JSON: https://edge.network/json/blog/cloud-cost-overruns.json _Cloud cost overruns are a growing pain point for enterprises. Discover how Edge Network offers transparent pricing, zero egress fees, and 20%+ savings._ Blog | Industry 7 min read How to Avoid Cloud Cost Overruns in 2026: A Decentralised Solution Cloud cost overruns are a growing pain point for enterprises. Discover how Edge Network offers transparent pricing, zero egress fees, and 20%+ savings. JD Joseph Denne CEO & Co-founder Introduction: The Cloud Cost Crisis Facing Enterprises in 2026 As enterprises continue to scale their digital operations into 2026, the promise of the cloud — flexibility, scalability, and cost-efficiency — has been overshadowed by a harsh reality: spiralling costs. Businesses migrating to or expanding within traditional cloud providers like AWS, Azure, and Google Cloud Platform (GCP) are increasingly blindsided by unexpected bills. Hidden fees, complex pricing structures, and punitive egress charges are turning what should be a strategic investment into a financial burden. In this article, we'll explore why cloud cost overruns are a growing pain point for enterprises and how Edge Network, the world's first decentralised cloud, offers a transparent, cost-effective alternative that can save businesses 20% or more. Ready to rethink your cloud strategy? Let's dive in. Why Are Cloud Costs Spiralling Out of Control? For many enterprises, the allure of Big Cloud providers lies in their vast infrastructure and seemingly endless scalability. However, the reality of working with these platforms often reveals a less appealing side: unpredictable and escalating costs. According to industry reports, over 80% of businesses experience cloud cost overruns, with many citing a lack of transparency as the primary culprit. Let's break down the key factors driving this crisis. Hidden Fees and Complex Pricing Models Traditional cloud providers often advertise low entry-level prices, but these are quickly overshadowed by hidden fees. Costs for data storage, compute resources, and bandwidth usage are buried in multi-tiered pricing structures that are difficult to predict or manage. For example, an enterprise might budget for a specific level of usage, only to find that slight overages trigger disproportionate charges. This lack of clarity makes financial planning a nightmare for IT teams. Egress Fees: The Silent Budget Killer One of the most notorious cost drivers is egress fees — charges for moving data out of a provider's ecosystem. For enterprises handling large datasets or operating hybrid cloud environments, these fees can accumulate rapidly. A business transferring terabytes of data to another platform or to end-users could face bills that dwarf their initial compute and storage costs. AWS, for instance, charges up to $0.09 per GB for data egress in some regions, a cost that scales alarmingly with volume. Over-Provisioning and Vendor Lock-In Many enterprises over-provision resources to avoid performance bottlenecks, leading to wasted spend on unused capacity. Compounding this issue is vendor lock-in, where businesses become so entrenched in a provider's ecosystem that switching becomes prohibitively expensive or complex. This dependency limits negotiation power and keeps costs high, as providers know customers have few viable alternatives. Edge Network: A Decentralised Solution to Cloud Cost Overruns Enter Edge Network, the world's first decentralised cloud, designed to address the pain points of traditional cloud providers head-on. Built on a global network of community-powered nodes, Edge offers a transparent, cost-effective, and scalable alternative that empowers enterprises to take control of their cloud spend. Here's how Edge Network is revolutionising the industry. Transparent Pricing with 20%+ Savings Unlike Big Cloud providers, Edge Network prioritises simplicity and transparency in its pricing model . There are no hidden fees or convoluted tier structures to navigate. Enterprises can expect to save 20% or more compared to AWS, Azure, or GCP, thanks to Edge's decentralised architecture, which reduces overheads by leveraging underutilised hardware from a global community of node operators. This means you pay only for what you use, with clear, predictable costs that align with your budget. Zero Egress Fees: Move Data Freely One of Edge Network's standout features is its zero egress fee policy. Whether you're transferring data to another platform, sharing it with end-users, or integrating with hybrid environments, you won't face punitive charges. This is a game-changer for enterprises dealing with large-scale data operations, enabling cost predictability and freedom to architect solutions without fear of spiralling transfer costs. Imagine the savings when moving terabytes of data without a single penny added to your bill for egress. Scalability Without Over-Provisioning Edge Network's decentralised model ensures resources are dynamically allocated based on demand, minimising the risk of over-provisioning. With a global network of nodes contributing compute and storage capacity, Edge can scale seamlessly to meet your needs without requiring you to pre-commit to excess resources. This elasticity ensures you're not paying for idle capacity, further driving down costs. Freedom from Vendor Lock-In Edge Network is built on open standards, ensuring interoperability and ease of migration. Unlike traditional providers that incentivise lock-in through proprietary tools and ecosystems, Edge empowers businesses to maintain flexibility. You can integrate Edge with existing systems or switch providers without facing punitive costs or technical barriers, putting control back in your hands. Real-World Impact: How Edge Network Delivers Value Consider a mid-sized enterprise running a data-intensive application on AWS. Between compute, storage, and egress fees for transferring data to external analytics platforms, their monthly bill regularly exceeds $50,000 — often with unexpected spikes. By migrating to Edge Network, this same enterprise could reduce costs by over 20%, saving upwards of $10,000 monthly, while benefiting from zero egress fees and transparent pricing. These savings can be reinvested into innovation, talent, or other strategic priorities, all while maintaining — or even enhancing — performance through Edge's global node network. Edge Network isn't just about cost savings; it's about redefining how enterprises approach the cloud. With a focus on community-driven infrastructure, Edge also offers a more sustainable model, reducing energy waste by utilising existing hardware rather than building energy-hungry data centres. It's a win for your budget and the planet. Getting Started with Edge Network: Test the Difference for Free If you're tired of unpredictable cloud bills and restrictive pricing models, it's time to explore a better way. Edge Network offers a zero-risk entry point — a free account with no card required — allowing you to experience the benefits of the world's first decentralised cloud firsthand. Whether you're running workloads for web hosting, data storage, or complex applications, Edge provides the tools and transparency you need to optimise costs without sacrificing performance. Here's what you can expect when you start with Edge: Instant Access: Sign up and deploy workloads in minutes through Edge's intuitive platform. Global Reach: Leverage a decentralised network of nodes for low-latency, high-performance delivery worldwide. Cost Control: Enjoy predictable pricing and zero egress fees from day one. Support: Access dedicated resources and community-driven support to ensure a smooth transition. Don't let cloud cost overruns hold your business back in 2026. Join the growing number of enterprises turning to Edge Network for a smarter, more sustainable cloud solution. Take the first step today by creating a free account at edge.network/account . Experience the future of cloud computing — decentralised, transparent, and built for your success. Exclusive Offer Start Free — No Card Required Create a free accou... --- ### Migrating a Ghost Blog from AWS Lightsail URL: https://edge.network/blog/ghost-migration-lightsail/ Markdown: https://edge.network/blog/ghost-migration-lightsail.md JSON: https://edge.network/json/blog/ghost-migration-lightsail.json _Practical steps to move a Ghost instance including database, media files and DNS, highlighting removal of egress exposure._ Blog | Use case 3 min read Migrating a Ghost Blog from AWS Lightsail Practical steps to move a Ghost instance including database, media files and DNS, highlighting removal of egress exposure. ET Edge Team Moving a Ghost blog from AWS Lightsail often surfaces one recurring cost: egress charges on every image, video and asset served to readers. Lightsail instances charge for outbound data once monthly allowances are exceeded, and media-heavy sites exceed those limits quickly. Edge Network removes that exposure entirely through zero egress fees on storage, CDN and compute. Before you begin Confirm you have a recent backup of the Ghost database and the content directory. Export the database through Ghost's built-in export tool or a direct MySQL dump. Copy the /content/images and /content/files folders to a local archive. Note the current domain and any custom DNS records in Lightsail. Edge provides a dedicated Ghost solution that includes a ready template for deployment. Review the steps at /solutions/ghost before starting the migration. Provision a new Ghost instance on Edge Create a compute instance sized for your traffic. A 2 vCPU, 4 GB RAM instance handles most blogs comfortably and can be resized live later. Install the Edge CLI if you have not already done so. Run the following command to launch an instance: edge compute create --name ghost-prod --size s-2vcpu-4gb --image ubuntu-24 Once the instance is running, follow the Ghost installation instructions in the solution guide. Use the same Ghost version that is running on Lightsail to avoid theme or plugin conflicts. Migrate the database Copy the exported database file to the new instance using scp or rsync. Import it with the mysql command after creating the ghost user and database exactly as they exist in the Lightsail environment. Update the config.production.json file with the new database credentials and the correct URL for the domain you will use. Restart the Ghost process to confirm it connects without errors. Transfer media files Upload the archived images and files to Edge Storage. The S3-compatible endpoint accepts the same content directory structure Ghost expects. Because Edge Storage carries zero egress fees, every future reader request for those assets incurs no additional outbound charge. Point Ghost's storage adapter to the Edge Storage bucket. Test that images load correctly by visiting a few posts. No further data transfer costs apply when the CDN later caches and serves those files. Set up DNS and CDN Edge DNS is free for up to 50 zones and provides the fast query responses needed for reliable blog availability. Create a new zone for your domain and add the A and CNAME records that point to the Edge compute instance and any subdomains. Enable the free CDN tier on the same domain. The global network caches static assets at the edge, delivering sub-50 ms latency to 95 % of internet users while protecting against DDoS traffic. Instant purge lets you clear specific paths when you publish new posts. Full instructions for DNS failover and multi-region CDN appear in the academy section at /academy/migrating-from-aws . Switch traffic and verify Lower the TTL on the Lightsail DNS records, then update the authoritative nameservers to Edge DNS. Monitor the new instance for 24 hours using Ghost's built-in logs and the Edge dashboard metrics. Confirm that: Database writes succeed from the admin interface. Images and files load without 404 errors. SSL certificates issued automatically through Edge. No egress charges appear on the Edge billing summary. Once traffic stabilises, terminate the Lightsail instance. The migration removes the previous egress exposure while keeping the same Ghost experience for authors and readers. Cost comparison after migration A typical 50 GB media library served to 100 000 monthly visitors on Lightsail can generate several hundred gigabytes of egress. Edge applies zero egress fees to the same workload. Storage remains at standard rates with a free tier available, and the CDN tier adds no per-request cost for cached assets. Hourly billing on the compute instance lets you scale down during quiet periods and resize upward only when needed, without long-term reservations. Next steps If you run multiple Ghost sites or need custom themes and members functionality, the same storage and CDN configuration applies across instances. Start the migration with the Ghost solution template at /solutions/ghost and the free signup at https://edge.network/account . Get Started Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Setting the Stage for Q2 Success with Edge Network URL: https://edge.network/blog/q2-success-edge-network/ Markdown: https://edge.network/blog/q2-success-edge-network.md JSON: https://edge.network/json/blog/q2-success-edge-network.json _Q2 is a pivotal time to set ambitious goals and ensure your infrastructure can keep up. Edge Network delivers 100% uptime, zero egress fees, and unmatched cost efficiency._ Blog | Industry 8 min read Setting the Stage for Q2 Success with Edge Network Q2 is a pivotal time to set ambitious goals and ensure your infrastructure can keep up. Edge Network delivers 100% uptime, zero egress fees, and unmatched cost efficiency. WL Will Lebens COO & Co-founder Setting the Stage for Q2 Success with Edge Network As the calendar flips to April 1st, businesses worldwide are gearing up for the second quarter of the year. Q2 is a pivotal time to set ambitious goals, refine strategies, and ensure your infrastructure can keep up with your vision. At Edge Network, we're here to help you start strong with the world's first decentralised cloud—a platform that delivers unmatched reliability, cost efficiency, and performance compared to traditional Big Cloud providers like AWS, GCP, and Azure. Whether you're scaling an app, managing data workloads, or launching a new project, Edge Network is your foundation for success in Q2 and beyond. Why Q2 Matters for Your Business The start of a new quarter is more than just a date—it's a mindset. April 1st is your chance to reassess, realign, and push forward with renewed energy. For many companies, Q2 is when budgets are refreshed, new initiatives are launched, and growth targets are set. But to achieve these goals, you need a cloud infrastructure that won't let you down with unexpected downtime or spiralling costs. That's where Edge Network shines as the smarter alternative to Big Cloud. Unlike centralised providers, Edge leverages a global network of decentralised nodes, ensuring your applications and services are always available, no matter the demand. Let's dive into how Edge Network can power your Q2 ambitions with proven reliability and groundbreaking cost savings. Edge Network: Outperforming Big Cloud in Reliability One of the biggest challenges with traditional cloud providers is their susceptibility to outages. Even giants like AWS and Azure have experienced significant downtime events, costing businesses millions in lost revenue. Edge Network, on the other hand, offers an unprecedented 100% uptime guarantee . How? Our decentralised architecture distributes workloads across thousands of nodes worldwide, eliminating single points of failure. If one node goes offline, others seamlessly pick up the slack, ensuring your services remain online without interruption. This reliability isn't just a promise—it's a proven fact. Edge Network has maintained perfect uptime since its inception, supporting everything from high-traffic web applications to critical data storage solutions . For businesses kicking off Q2 with big plans, this level of dependability means you can focus on growth without worrying about infrastructure failures. Real-World Impact of 100% Uptime Imagine launching a major marketing campaign or a new product on April 1st, only to have your cloud provider experience an outage. With Big Cloud, this risk is real. With Edge, it's non-existent. Our customers—ranging from startups to enterprises—have reported zero disruptions, even during peak usage periods. This stability gives you the confidence to execute your Q2 strategies without a hitch. Cost Efficiency: Zero Egress Fees and More Beyond reliability, cost is a major pain point for businesses using traditional cloud services. Big Cloud providers often lure customers with low entry fees, only to hit them with exorbitant charges for data egress—fees for transferring data out of their systems. These hidden costs can balloon budgets, especially for data-intensive applications or companies scaling rapidly in Q2. Edge Network eliminates this burden with a revolutionary pricing model that includes zero egress fees . That's right—move as much data as you need out of our cloud without paying a penny extra. This transparency allows you to plan your Q2 budgets with certainty, knowing there won't be surprise bills at the end of the month. But the savings don't stop there. Edge's decentralised model also reduces overheads by leveraging community-powered nodes rather than expensive, centralised data centres. This results in overall lower costs for compute, storage, and bandwidth compared to AWS, GCP, or Azure. For businesses looking to maximise ROI in Q2, Edge Network delivers the financial flexibility to invest in innovation rather than infrastructure. Case in Point: Savings That Scale Consider a mid-sized e-commerce platform gearing up for a Q2 sales surge. With a traditional provider, transferring customer data or hosting high-traffic events could incur thousands in egress fees alone. On Edge Network, that same platform pays only for the resources it uses, with no additional costs for data movement. This cost predictability empowers businesses to scale fearlessly, knowing their cloud provider won't penalise growth. Why Choose Edge Network for Q2? Starting Q2 with Edge Network isn't just about avoiding the pitfalls of Big Cloud—it's about gaining a competitive advantage. Here's why Edge is the ideal partner for your April 1st kickoff: Unmatched Reliability: 100% uptime ensures your services are always available, even during peak Q2 demand. Cost Transparency: Zero egress fees and lower overall pricing mean no nasty surprises in your budget. Global Reach: Our decentralised network spans the globe, delivering low-latency performance to users wherever they are. Community-Driven Innovation: Edge is powered by a network of contributors, ensuring constant improvements and a future-proof platform. Whether you're a developer building the next big app, an enterprise migrating workloads, or a startup launching your first product, Edge Network provides the tools and stability to make Q2 your most successful quarter yet. Launch Q2 with a Free Account There's no better time to experience the power of decentralised cloud than at the start of Q2. Signing up is free — no card required , with free DNS, free CDN and Storage tiers, and per-resource compute billed hourly, so you can test our platform risk-free and see the difference for yourself. You'll get hands-on experience with our 100% uptime guarantee and zero egress fee model, allowing you to explore how Edge can transform your business operations. Don't let outdated, overpriced cloud solutions hold you back this quarter. Join the growing number of companies switching to Edge Network and start Q2 with a platform built for the future. Take the Next Step Today April 1st is your moment to redefine what's possible for your business in Q2. With Edge Network, you're not just choosing a cloud provider—you're choosing a partner committed to your success through reliability, affordability, and innovation. Don't settle for the limitations of Big Cloud when you can build on a decentralised foundation that outperforms at every level. Ready to kick off Q2 with confidence? Create a free account now and discover why Edge Network is the leading alternative to AWS, GCP, and Azure. Visit edge.network/account to get started today. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Carbon Offset Cloud URL: https://edge.network/blog/the-carbon-offset-cloud/ Markdown: https://edge.network/blog/the-carbon-offset-cloud.md JSON: https://edge.network/json/blog/the-carbon-offset-cloud.json _What if you could run your digital products in a cloud that was green from the off? One that didn't demand more leaves to cover its indiscretions?_ Blog | Sustainability 2 min read The Carbon Offset Cloud What if you could run your digital products in a cloud that was green from the off? One that didn't demand more leaves to cover its indiscretions? WL Will Lebens COO & Co-founder When you hear the word "offset," your mind probably goes straight to carbon. Planting trees. Buying credits. Doing something good over here to excuse something bad over there. It's the bargain the cloud industry has struck with itself — build enormous data centres, burn through staggering amounts of energy, and then plant a forest to make it all feel okay. But what if you didn't need to offset at all? What if you could run your digital products in a cloud that was green from the very beginning? A Cloud That Starts Green That's what Edge Network is. Instead of building more warehouses full of servers — the kind run by Amazon, Microsoft and Google — Edge stores and delivers data using existing devices. Machines that have already been manufactured. Hardware that has already paid its debt to the environment. No new factories. No new server farms. No new carbon footprint to apologise for. It's a fundamentally different approach to cloud infrastructure. Rather than concentrating computing power in a handful of massive facilities, Edge distributes it across a network of devices that are already switched on and already connected to the internet. The environmental cost of those devices has already been incurred. By putting their spare capacity to work, Edge turns sunk cost into shared value. Closer to the Consumer, Lighter on the Planet There's another dimension to this. Traditional cloud providers route your data through centralised facilities that might be hundreds or even thousands of miles from the people who actually need it. That distance isn't free. Every mile costs energy — energy to transmit, to route, to cache, and to deliver. Edge devices sit closer to the end consumer. The data doesn't have to travel as far, which means less energy is consumed in the process. It's a greener model not because of what it adds, but because of what it removes. That doesn't mean fewer trees get planted. It just means Edge won't force you to offset in the first place. The Other Kind of Offset There is one kind of offset that Edge actively promotes — and it's not about carbon. It's about cost. Businesses everywhere have desktop machines sitting idle for large parts of the day. Those machines represent sunk investment — bought, powered, and maintained whether they're working hard or doing nothing. Edge lets those businesses contribute their idle capacity to the network, turning dormant tech into a revenue stream that offsets the cost of their own cloud services. It's a positive feedback loop. You reduce your cloud bill by contributing to a greener network . Your unused computing power stops being a cost and starts being an asset. And the broader network gets stronger, faster, and more distributed as a result. A Better Story The old cloud story goes like this: build big, consume hard, and offset later. The Edge story is different. Use what's already there. Stay close to the people who need it. And if you've got spare capacity, share it — because the economics and the environment both benefit when you do. No guilt. No greenwashing. Just a cloud that was built to be better from the start. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Cloud Is Not Enough URL: https://edge.network/blog/the-cloud-is-not-enough/ Markdown: https://edge.network/blog/the-cloud-is-not-enough.md JSON: https://edge.network/json/blog/the-cloud-is-not-enough.json _We're on the cusp of unprecedented demand for data storage and traditional infrastructure just won't cut it._ Blog | Engineering 3 min read The Cloud Is Not Enough We're on the cusp of unprecedented demand for data storage and traditional infrastructure just won't cut it. AD Adam K Dean CTO Remember the days of dial-up? A lonely shared computer sat in the corner of the room, next to a tired fax machine, tethered to the world by a single phone line. It felt like magic at the time — the idea that you could connect to something bigger, something beyond the walls of your home. Then wifi arrived and changed everything. The mobile web followed. Suddenly homes, offices, streets, and even cars were filled with connected devices. The internet wasn't something you sat down to use anymore — it was something that surrounded you. The 5G Revolution Now 5G is ushering in another revolution entirely. We're fast approaching a world where there are more connected devices than people on the planet. By 2023, an estimated 70% of new cars were expected to be networked. The Internet of Things is pushing past 40 billion connected machines — sensors, cameras, appliances, wearables — all generating, consuming, and demanding data at a scale we've never seen before. And yet, the infrastructure we rely on to handle all of this still looks remarkably similar to those old server farms we've been building for decades. Rows upon rows of machines, humming away in purpose-built warehouses, cooled by industrial air conditioning, burning through energy at an extraordinary rate. The Fax Machine of Tomorrow Those server farms are starting to look a lot like the old fax machine sitting next to the dial-up modem. They served us well, but change is inevitable. The demands of the modern internet — real-time data, low latency, always-on connectivity — are pushing traditional cloud infrastructure to its limits. This is where Edge comes in. Rather than sweating factory servers under air conditioning in remote data centres, Edge harnesses the spare capacity that already exists in the devices around us — phones, laptops, set-top boxes, gaming consoles. The computing power is already there, sitting idle for most of the day. The Internet Is All Around Us The internet is no longer a destination. It's all around us, woven into the fabric of daily life. Every new device that connects to the network doesn't just consume resources — it can expand the cloud. That's the fundamental insight behind edge computing: the infrastructure of the future isn't something we need to build from scratch. It's something we already have. Only Edge technology can truly secure the potential of our digital infrastructure. By distributing computation and storage across millions of everyday devices, we build a network that grows organically with demand — one that's faster, more resilient, and far more sustainable than anything a server farm could ever be. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Future of Internet: Decentralized Cloud Hosting URL: https://edge.network/blog/future-of-internet-decentralized-cloud/ Markdown: https://edge.network/blog/future-of-internet-decentralized-cloud.md JSON: https://edge.network/json/blog/future-of-internet-decentralized-cloud.json _Decentralized cloud hosting promises to dramatically shift the status quo and reshape the future of the Internet._ Blog | Engineering 4 min read The Future of Internet: Decentralized Cloud Hosting Decentralized cloud hosting promises to dramatically shift the status quo and reshape the future of the Internet. WL Will Lebens COO & Co-founder The Internet as we know it is built on centralized infrastructure — a relatively small number of massive data centers, owned and operated by a handful of corporations, serving billions of users worldwide. This model has driven extraordinary growth, but it has also introduced concentration risks, privacy concerns, and economic inefficiencies that are becoming harder to ignore. Decentralized cloud hosting offers a fundamentally different vision for how the Internet's infrastructure could work. What Is Decentralized Cloud Hosting? Unlike traditional cloud hosting, where resources are owned and managed by a single entity within centralized data centers, decentralized cloud hosting distributes computing, storage, and networking resources across a global network of independent nodes. No single organization controls the infrastructure. Instead, participants contribute resources to a shared network, and workloads are distributed across these nodes based on demand, proximity, and availability. This model transforms the relationship between infrastructure providers and users. Rather than renting capacity from a monolithic provider, users access a marketplace of distributed resources — more resilient, more competitive, and fundamentally more open. Decentralization and Privacy Privacy is one of the most compelling arguments for decentralized hosting. In centralized systems, a single provider has access to — and is responsible for securing — all of the data stored on its platform. This creates an attractive target for attackers and a potential vector for surveillance or misuse. In a decentralized model, data is encrypted and split into fragments before being distributed across multiple independent nodes. No single node holds a complete, readable copy of any file. Without the user's encryption keys, reassembling or accessing the original data is effectively impossible. This architecture ensures that privacy is enforced by design, not by policy — a critical distinction in an era of growing regulatory scrutiny and data breaches. Performance and Reliability Centralized hosting introduces latency by requiring data to travel from the user to a distant data center and back. Decentralized hosting reduces this latency by serving content and processing requests from nodes that are geographically closer to the end user. The result is faster load times, more responsive applications, and a better experience for users regardless of their location. Reliability also improves dramatically. Centralized systems have single points of failure — when a region goes down, so do the services that depend on it. A decentralized network has no such vulnerability. If one node goes offline, others absorb its workload automatically. This inherent redundancy makes decentralized hosting significantly more fault-tolerant than its centralized counterpart. Cost Efficiency The economics of decentralized cloud hosting differ fundamentally from the centralized model. Instead of investing billions in building and maintaining hyperscale data centers, a decentralized network leverages resources that already exist — unused compute capacity, idle storage, and spare bandwidth on devices and servers around the world. This peer-to-peer model dramatically lowers the cost of delivering cloud services. Resource providers earn revenue from capacity that would otherwise sit idle, while consumers benefit from competitive pricing driven by a distributed marketplace rather than the pricing structures of a few dominant providers. The result is a more efficient allocation of global computing resources. Environmental Sustainability The environmental impact of centralized data centers is substantial. They consume enormous amounts of electricity — both for computation and for the cooling systems required to prevent overheating — and are significant contributors to global carbon emissions. As demand for cloud services continues to grow, so does this environmental footprint. Decentralized hosting offers a more sustainable alternative. By distributing workloads across existing infrastructure, it reduces the need for new data center construction and the associated energy demands. Processing data closer to its source also minimizes the energy consumed in long-distance data transmission. The cumulative effect is a reduced energy footprint for the same level of service. Challenges and the Way Forward Decentralized cloud hosting is still maturing, and real challenges remain. Ensuring consistent performance across heterogeneous nodes, managing data integrity at scale, and building user-friendly interfaces that abstract away the complexity of distributed systems are all active areas of development. Blockchain technology plays a key role in addressing many of these challenges. It provides a transparent, tamper-proof mechanism for verifying data integrity and tracking resource usage. Smart contracts can automate resource allocation, enforce service-level agreements, and manage payments between participants — all without requiring a central authority. The trajectory is unmistakable. As the limitations of centralized infrastructure become more apparent — and as the tools for building decentralized alternatives mature — the Internet is moving toward a model that is more user-centric, more resilient, more affordable, and more sustainable. Decentralized cloud hosting is not a theoretical exercise; it is the foundation of the Internet's next chapter. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Hidden Cost of Cloud Downtime URL: https://edge.network/blog/cloud-downtime-costs/ Markdown: https://edge.network/blog/cloud-downtime-costs.md JSON: https://edge.network/json/blog/cloud-downtime-costs.json _Cloud downtime isn't just an inconvenience — it's a business killer. A single hour of outage can result in millions in lost revenue, damaged customer trust, and long-term reputational harm._ Blog | Industry 6 min read The Hidden Cost of Cloud Downtime Cloud downtime isn't just an inconvenience — it's a business killer. A single hour of outage can result in millions in lost revenue, damaged customer trust, and long-term reputational harm. WL Will Lebens COO & Co-founder The Hidden Cost of Cloud Downtime Businesses rely on cloud for everything. When it fails, it's a business killer. The average cost of downtime ranges from £4,000 to £400,000 per hour depending on your scale and sector — and the impact goes far beyond the financial. Disrupted customer experiences, delayed operations, and exposed vulnerabilities can compound the damage long after services are restored. We've all seen the headlines: AWS disruptions in 2021 affecting Netflix and Slack; Azure issues impacting enterprise clients across industries. These incidents underscore a fundamental truth: traditional cloud architecture has a single point of failure. Edge Network offers a different approach — 100% uptime through decentralisation. Why Traditional Cloud Providers Fall Short Centralised Systems: A Single Point of Failure Traditional cloud providers operate from a limited number of data centres. When disaster strikes — whether it's a natural disaster, cyberattack, or hardware failure — entire regions can go dark. Scalability during peaks like Black Friday or viral campaigns becomes a gamble: over-provision and waste money, or under-provision and risk crashing when it matters most. The Ripple Effect of Downtime Customer Trust Erosion: 80% of customers switch providers after a poor experience. Operational Paralysis: Teams can't work, transactions halt, and productivity grinds to zero. Reputational Damage: News of outages spreads fast; recovery takes years. Compliance Risks: Regulated industries face fines and audits when uptime SLAs are breached. Edge Network: The Decentralised Difference A Network with No Single Point of Failure Edge Network is distributed across thousands of global nodes. If one fails, others take over instantly. There's no single data centre to knock out — no region that can bring your entire operation to a halt. The result is 100% uptime with dynamic rerouting that keeps your services live when traditional providers would be scrambling. Scalability Without Limits Distributed resources mean traffic surges are absorbed across the network. No server crashes, no over-provisioning. Whether you're launching a product or weathering a viral moment, Edge scales with you — seamlessly and cost-effectively. Cost Efficiency Meets Reliability Transparent pay-as-you-go pricing , up to 90% lower than traditional cloud, and enterprise-grade reliability at a fraction of the cost. You don't have to choose between affordability and uptime. Real-World Impact: How Edge Saves Businesses Consider an e-commerce platform during a flash sale: traffic spikes that would overwhelm a centralised server are absorbed across thousands of Edge nodes. No crashes, no lost sales, no angry customers. Or a healthcare provider handling patient data: guaranteed uptime isn't just a convenience — it's a compliance requirement. Edge delivers both. Experience the Edge Difference — Free Stop gambling on uptime. See for yourself how decentralised infrastructure eliminates the hidden cost of cloud downtime. Start free at edge.network/account — free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Local, Global Network URL: https://edge.network/blog/the-local-global-network/ Markdown: https://edge.network/blog/the-local-global-network.md JSON: https://edge.network/json/blog/the-local-global-network.json _Edge is a global network, locally sourced: our nodes are located in homes and offices everywhere._ Blog | Network 2 min read The Local, Global Network Edge is a global network, locally sourced: our nodes are located in homes and offices everywhere. WL Will Lebens COO & Co-founder Think for a moment about where these words are coming from. They're stored on a server somewhere, piped through networks and infrastructure, and delivered to whatever device you're reading on right now. But where is that server? How far did this data have to travel to reach you? In the traditional cloud, your data lives in whichever data centre happens to be closest to you — a large farm of servers housed in a purpose-built warehouse. There aren't thousands of these facilities around the world. There aren't even hundreds in most regions. Yet millions of people are demanding data simultaneously, and that data is travelling billions of miles every single day to reach them. What If We Reduced the Distances? What if, instead of a handful of massive data centres, we had millions of smaller ones distributed all around us? Data stored closer to where it's needed, served faster, with less energy wasted in transit. That's not a hypothetical — it's exactly what Edge does. The result is straightforward: faster, cheaper, greener. Web pages load faster. Files download more quickly. Videos stream more seamlessly. And all of it consumes less energy, because the data simply doesn't have to travel as far. No Server Farms Required Edge doesn't require server farms. Instead, it uses millions of devices that are already sitting in homes and offices around the world — laptops, desktop PCs, gaming consoles, set-top boxes. These devices have spare processing power, memory, and storage that can be harnessed and coordinated into a globally distributed network . Every node on the Edge network is locally sourced. It's a device in someone's home, in someone's office, on someone's desk. And yet together, these nodes form a global network that's more distributed, more resilient, and more efficient than any centralised cloud could ever be. This is what the future cloud looks like. Not a warehouse in the desert, but the laptop on your kitchen table. Not a factory farm of servers, but a living network that grows with the people who use it. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Network That Works for You URL: https://edge.network/blog/the-network-that-works-for-you/ Markdown: https://edge.network/blog/the-network-that-works-for-you.md JSON: https://edge.network/json/blog/the-network-that-works-for-you.json _Edge can cut your digital infrastructure bill by up to 90%. How the community-powered network delivers cloud services for less, and works for its users._ Blog | Company 2 min read The Network That Works for You Edge can cut your digital infrastructure bill by up to 90%. How the community-powered network delivers cloud services for less, and works for its users. JD Joseph Denne CEO & Co-founder Every action you take on the internet profits someone. In roughly half of all cases, that someone is Google, Amazon, or Microsoft. The infrastructure that powers the modern web is concentrated in the hands of a few, and the economics flow in one direction — away from you. A Network That Shares Revenue Edge changes this equation. By allowing everyone to contribute to the network using everyday devices, Edge shares revenue with the people who power it. Your laptop, your desktop, your phone — these are machines with spare capacity that can be put to work, earning you money while contributing to a faster, greener internet. Good for Business This model is especially compelling for businesses. Every office is full of machines that sit idle overnight — desktops, workstations, servers that spend their evenings doing nothing. With Edge, every one of those desktop PCs could be a revenue earner, quietly offsetting your hosting bills while the office lights are off. Up to 90% Cheaper Edge is also fundamentally more efficient than traditional cloud infrastructure. Because data travels less far — served from nearby devices rather than distant data centres — the network consumes less energy, requires fewer network hops, and delivers content faster. The result is infrastructure that costs up to 90% less than the incumbents. Join the Pioneers We're currently onboarding pioneering clients who understand the value of this approach — businesses following in the footsteps of global media companies and ecommerce brands who have already made the switch. Whether you're looking to reduce your infrastructure costs, earn from your idle hardware, or simply move to a platform that's faster and greener, Edge is the network that works for you. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The Network Under Your Nose URL: https://edge.network/blog/the-network-under-your-nose/ Markdown: https://edge.network/blog/the-network-under-your-nose.md JSON: https://edge.network/json/blog/the-network-under-your-nose.json _We don't need massive, dedicated server farms to power the internet. You already carry a perfectly usable cloud in your pocket._ Blog | Sustainability 3 min read The Network Under Your Nose We don't need massive, dedicated server farms to power the internet. You already carry a perfectly usable cloud in your pocket. WL Will Lebens COO & Co-founder Take the average American household's energy consumption and multiply it by 17 million. That's how much energy cloud computing consumed in 2018 alone. And the number is only growing — accelerated by the rollout of 5G networks and the relentless expansion of the Internet of Things. Yet the cloud industry's response to this growing demand has been remarkably one-dimensional: build bigger server farms. More warehouses, more racks, more cooling systems, more energy. It's an approach that scales linearly with cost and environmental impact, and it simply isn't sustainable. The Hardware Already Exists Edge takes a fundamentally different approach. Instead of building new infrastructure from the ground up, we reuse the hardware that's all around us. Think about a set-top box — it's plugged in 24 hours a day, 7 days a week, but it's only actively used for a few hours. Now imagine joining millions of these devices together into a single, coordinated network . The result is something incredibly powerful. It's not just set-top boxes. Laptops, gaming consoles, desktop PCs, even smartphones — all of these devices have processing power, memory, and storage that goes unused for the vast majority of the day. That's capacity that could be put to work. Massive Capacity Going Spare We ran a community survey and found that the average disk space usage across our network was just 52.56%. That means nearly half of all available storage is sitting idle — massive capacity going completely spare. Scale that up across millions of devices worldwide and you begin to see the true potential of edge computing. This isn't theoretical. The spare capacity exists right now, in devices people already own, in homes and offices on every continent. It just needs to be connected and coordinated. The Biggest Beneficiary: The Planet The biggest beneficiary of this approach isn't any single company or user — it's the planet. When we reuse devices that have already been manufactured, we eliminate the enormous energy and material cost of building new server farms. There are no new factories to run, no new warehouses to cool, no new hardware to produce and eventually discard. And because data is stored closer to where it's actually consumed, less energy is needed to transfer it across the globe. Shorter distances mean fewer network hops, lower latency, and significantly reduced energy consumption. The internet becomes not just faster and cheaper, but genuinely greener. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The New Media Platform URL: https://edge.network/blog/the-new-media-platform/ Markdown: https://edge.network/blog/the-new-media-platform.md JSON: https://edge.network/json/blog/the-new-media-platform.json _Edge offers enhanced performance for optimal user experience — an ideal application for media brands._ Blog | Industry 2 min read The New Media Platform Edge offers enhanced performance for optimal user experience — an ideal application for media brands. WL Will Lebens COO & Co-founder Social media has its place, but inside their own proprietary websites, brands have far more control over their identity, their audience relationship, and the experience they deliver. For media companies in particular, the website is the product — and premium means performance. Performance Is the New Premium When it comes to digital media, premium is not just about the quality of content. It's about the entire user experience — from page load speed to image rendering, video playback to scroll responsiveness. Audiences expect it, and advertisers demand it. A sluggish site doesn't just frustrate users; it undermines the value of the brand itself. 70+ Media Brands and Counting Edge CDN is already used by more than 70 media brands, each benefiting from faster content delivery, reduced latency, and a greener digital footprint. These are publishers who understand that infrastructure is inseparable from experience. Bauer Media Bauer Media uses Edge to serve images and videos across some of the UK's most iconic titles — Empire, Grazia, Kiss, and Kerrang among them. With millions of monthly page views across a diverse portfolio, the performance gains from Edge CDN translate directly into better engagement and stronger advertising metrics. Ecohustler Ecohustler, a platform dedicated to environmental awareness, chose Edge not just for speed but because it's better for the environment. Delivering content through a decentralised network that reuses existing hardware aligns with their mission at every level. Monocle Monocle, the global affairs and lifestyle brand, saw a 35% increase in performance after switching to Edge CDN. For a publication built around the idea of quality and refinement, that performance boost contributes directly to the luxury experience their audience expects. Pioneers of a New Standard These brands are pioneers, but they won't be alone for long. Alongside media companies, businesses in ecommerce, fashion, financial services, and live events are already joining Edge — drawn by the same combination of performance, cost savings, and sustainability that makes the network compelling for anyone who takes their digital presence seriously. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The New Path for Edge: A New Cloud, New Tools, and What's Next URL: https://edge.network/blog/the-new-path-for-edge/ Markdown: https://edge.network/blog/the-new-path-for-edge.md JSON: https://edge.network/json/blog/the-new-path-for-edge.json _We never stopped building. While the major cloud providers were making headlines for the wrong reasons, we went back to the foundations and rebuilt everything. Here's what's live today, and a first look at what comes next._ Blog | Company 12 min read The New Path for Edge: A New Cloud, New Tools, and What's Next We never stopped building. While the major cloud providers were making headlines for the wrong reasons, we went back to the foundations and rebuilt everything. Here's what's live today, and a first look at what comes next. JD Joseph Denne CEO & Co-founder Three major cloud outages in the first quarter of 2025 alone. Millions of businesses taken offline. Billions lost. And every single time, the cause was the same: too much of the internet running through too few pipes, controlled by too few companies. This was never how the internet was supposed to work. The original vision was genuinely radical: a distributed, open network that no single entity could own or take down. That vision didn't fail, it got abandoned. Quietly, gradually, and with our collective permission. A handful of companies built the infrastructure, the rest of the world moved in, and somewhere along the way we all agreed to pretend that was fine. It isn't fine. When one company has a bad day, half the internet goes with it. We've watched it happen repeatedly this year alone. Edge was built on the refusal to accept that. Since 2013, we've believed one thing consistently: the internet should never have been owned by anyone, and it still doesn't have to be. Every node that joins our network is a small act of taking it back, of building something distributed and resilient by design. You may have noticed we've been quiet. We owe you an honest explanation for that, and a genuine apology for the silence. The truth is we never stopped building. Not for a single day. But we reached a point where we had to make a choice: keep talking, or go deep and get it right. We chose to get it right. In this industry, it's often the quietest teams that build the furthest, and we've always believed that what you ship matters more than what you announce. That said, we know silence has a cost, and we're grateful to everyone who stayed with us through it. We're back now, and stronger than we've ever been. Being at the forefront of decentralised infrastructure for over a decade means we've had a front-row seat to every major shift in this industry. Nothing has shifted it more completely than AI. Not just in what software does, but in what infrastructure needs to be. And the centralised model, already showing its cracks, is being stress-tested in ways it was never built to handle. We built Edge for exactly this world. But getting here required us to be honest about something: the complexity we'd accumulated over the years was slowing everyone down, including us. So we went back to the foundations, stripped everything back, and rebuilt with one clear goal in mind: mass adoption. Not just for the crypto-native community that has supported us from the beginning, but for every developer, every enterprise, and every organisation that deserves a better infrastructure. Today we're sharing the biggest upgrade in Edge's history, and a clear picture of what's coming next. Two Worlds, One Infrastructure The most important thing to understand about what we're launching today is that it represents a genuine split in direction, not just for Edge, but for what cloud infrastructure needs to look like from here. Edge Network is the cloud. A fully decentralised cloud platform built for enterprises, SMEs, developers, and increasingly for the AI agents and autonomous systems that are becoming the primary consumers of compute. But the cloud is only the beginning. The world is moving toward a machine economy, where AI agents transact with each other, where machines buy and sell compute autonomously, at a speed and scale that no centralised provider was ever designed to handle. That foundation is XE . A fully open, permissionless infrastructure layer and compute marketplace where no single party has an advantage. Agent-to-agent. Machine-to-machine. Native identity for every participant, whether human, organisation, or autonomous system. Payments that settle directly between machines, without intermediaries. An open marketplace where resources are bought and sold on equal terms by anyone. No party gets preferential treatment, including us. Infrastructure owned by everyone and controlled by no one. There is one thing we want to be clear about now: everyone who has believed in Edge and held with us through the journey so far will be at the centre of what comes next. EDGE holders are not being left behind. Quite the opposite. The community that has supported this project since the beginning will have a foundational role in both of these journeys, and we'll be laying out exactly what that looks like when we reveal the full XE story soon. This isn't a new direction. It's where Edge was always heading. Independently Verified as One of the Fastest Networks on the Planet Edge Network is now benchmarked by PerfOps , one of the most respected independent monitoring providers in the industry. The results are consistent: we rank amongst the fastest providers globally for both CDN and DNS, regularly outperforming names that have had decades and billions of dollars to build their position. Live comparisons are available at edge.network/cdn/performance and edge.network/dns/performance . Our network grows through decentralisation. Every node that connects makes the network bigger, faster, and more resilient, because content gets served from wherever is physically closest to the person requesting it. That could be a data centre. It could be your neighbour's node. That's the architecture, and it's why our average latency sits at 10.45 ms , making Edge the lowest latency cloud network available today. It's also why Edge delivers cost savings of between 20% and 95% compared to traditional providers, with no egress fees and no bill that requires a spreadsheet to understand. And while the major providers were making headlines for the wrong reasons this year, Edge stayed online. Storage Is Now Live Decentralised Storage has come out of public beta and is available to everyone today. It's S3-compatible object storage served from the edge, which means it inherits the performance and resilience of the network it runs on. Files are encrypted with AES-256, access is instant, and there are no cold-storage tiers to navigate. You get your data when you need it, from wherever you are, without the latency that comes with storage sitting in a single centralised location. For teams already using S3-compatible tooling, migration is straightforward. For teams starting fresh, it's the cleanest way to add storage to an Edge deployment without pulling in a separate provider. Introducing the New Edge Platform The new Edge Platform launches today with every core product live, production-ready, and available under a single account from one control centre. CDN covers more than 2,200 edge locations with sub-15ms global latency, PerfOps-verified fastest or runner-up in key markets, with Edge Rules, instant cache purge, and real-time analytics included. Compute deploys virtual machines in under 60 seconds across more than 20 global regions, from 1 vCPU to GPU-accelerated workloads, with live resize and private networking. DNS delivers sub-10ms globally distributed name resolution, independently verified by PerfOps. Storage is S3-compatible, AES-256 encrypted, served from the edge, with no cold-storage tiers and instant access. Pulse is a distributed monitoring service running from thousands of nodes globally, giving you a genuinely independent view of your uptime and performance from the edge rather than from a handful of centralised monitoring locations. The new account portal is the single place to deploy, manage, and monitor across the full stack, redesigned from scratch to match the clarity of the platform itself. Free to sign up with no card required — free DNS, free CDN and Storage tiers, and per-resource compute bi... --- ### The Offset Network URL: https://edge.network/blog/the-offset-network/ Markdown: https://edge.network/blog/the-offset-network.md JSON: https://edge.network/json/blog/the-offset-network.json _Plant trees, by all means. But do it because you want to, not because you feel like you have to._ Blog | Sustainability 2 min read The Offset Network Plant trees, by all means. But do it because you want to, not because you feel like you have to. WL Will Lebens COO & Co-founder Say "offset" and most people think carbon. More trees planted to excuse the damage done elsewhere. It's become a kind of environmental accounting trick — burn what you like, then buy your way back to neutral. But what if you didn't need to offset in the first place? What if you could move your digital services to a network that was greener from the start? Greener by Design That's Edge Network. Instead of spinning up banks of dedicated servers in purpose-built data centres, Edge stores and processes data on existing devices — machines that have already been manufactured, shipped, and powered on. The environmental debt has already been paid. By putting those devices to work as part of a distributed network, we squeeze more value out of hardware that would otherwise sit idle, without adding to the planet's growing stack of server infrastructure. And because those devices are closer to the end consumer — distributed across homes, offices, and co-working spaces rather than concentrated in remote facilities — there's less energy spent moving data across long distances. It's a fundamentally more efficient architecture, and a greener one too. We Won't Force You to Offset That doesn't mean fewer trees. Plant them. We're all for it. But Edge won't force you to offset your cloud usage with carbon credits or guilt-driven donations. Our model is greener from the ground up, so you don't need to compensate for what you consume. You can plant trees because you want to — not because you feel like you have to. The Other Kind of Offset There's another kind of offset that Edge promotes — and this one hits the balance sheet. If your business has idle desktop machines, rack servers gathering dust, or spare capacity on hardware you've already invested in, you can contribute that capacity to Edge Network and earn $EDGE tokens in return. Think about that for a moment. The technology you've already paid for can generate revenue, which you can then offset against your cloud services bill. Instead of paying a hyperscaler for infrastructure you don't control, you're turning your own idle tech into a productive asset — and helping build a more distributed, more resilient internet in the process. A Better Story It's a positive story on two fronts: greener digital services that don't rely on carbon guilt, and a real opportunity to take a chunk out of your infrastructure costs. That's the kind of offset we believe in — one that makes things better, rather than just less bad. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### The World According to Edge URL: https://edge.network/blog/the-world-according-to-edge/ Markdown: https://edge.network/blog/the-world-according-to-edge.md JSON: https://edge.network/json/blog/the-world-according-to-edge.json _What global reach means to us and why we're able to offer market-leading cloud services wherever you live._ Blog | Network 3 min read The World According to Edge What global reach means to us and why we're able to offer market-leading cloud services wherever you live. WL Will Lebens COO & Co-founder Sixty-plus countries and counting. Nodes scattered across every continent. When we talk about the Edge Network, we're not talking about a handful of data centres in Virginia and Frankfurt — we're talking about a genuinely global infrastructure that lives where people live. That matters. It matters for performance, for resilience, and for the kind of internet we think everyone deserves. Why Edge Is Different Edge is the future of cloud infrastructure because it does two things at once: it decentralises the web and it localises the internet. Traditional cloud computing works by concentrating enormous amounts of hardware in a small number of very large facilities. These server farms are expensive to build, expensive to run, and sparsely distributed around the world. If you're lucky enough to be near one, performance is decent. If you're not, your data has a long way to travel. Edge takes a fundamentally different approach. Instead of building more warehouses, it sprinkles internet infrastructure among us — using spare capacity on devices that are already running, already connected, and already distributed across the globe. The result is a network that's closer to the people who use it, which means data travels shorter distances. That makes it faster, greener, and cheaper. How the Network Is Built The Edge Network has a layered architecture, with each layer playing a distinct role in keeping things running smoothly. Stargates sit at the top. They orchestrate operations across the network — handling DNS resolution, traffic routing, and telemetry. Think of them as the control plane: they don't serve content directly, but they make sure everything else knows where to go and how to get there. Gateways are the entry point for requests. When a user hits a website or application powered by Edge, a Gateway receives that request and routes it to the right place. They're the front door of the network — fast, responsive, and distributed across key locations worldwide. Hosts are where the heavy lifting happens. These nodes provide the actual delivery capacity — storage, compute, and bandwidth. With hosts operating in over 51 countries, Edge has one of the most geographically distributed cloud networks in existence. And it's growing every day. Growth Is the Point The more nodes join the network, the more resilient and performant it becomes. Unlike traditional cloud providers who need to pour billions into new facilities, Edge grows organically. Every new host makes the network better for everyone. And here's the thing: you can be part of that growth. If you've got a device with spare capacity — a desktop, a server, a machine that's not working to its full potential — you can contribute it to the Edge Network and earn for doing so. You become part of the infrastructure, and the infrastructure becomes more global as a result. A Network for Everyone, Everywhere The traditional cloud is built for scale, but it's not built for reach. A few providers dominate, a few regions benefit, and the rest of the world makes do. Edge is different. By distributing infrastructure to where people actually are, we're building a network that serves everyone — not just those within range of a hyperscaler's nearest data centre. Sixty-plus countries today. More tomorrow. The world according to Edge is one where the cloud is everywhere — because the people who power it are everywhere too. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Understanding Edge Computing in a Decentralized World URL: https://edge.network/blog/edge-computing-decentralized-world/ Markdown: https://edge.network/blog/edge-computing-decentralized-world.md JSON: https://edge.network/json/blog/edge-computing-decentralized-world.json _The concept of decentralization is prompting a shift away from centralized systems. We examine edge computing in this new paradigm._ Blog | Engineering 4 min read Understanding Edge Computing in a Decentralized World The concept of decentralization is prompting a shift away from centralized systems. We examine edge computing in this new paradigm. AD Adam K Dean CTO From finance and governance to data storage and content delivery, the idea of removing central authorities and distributing control across networks has gained substantial momentum. At the intersection of this movement lies edge computing — a paradigm that brings computation and data processing closer to where it is needed, rather than funnelling everything through distant, centralized data centers. Edge Computing: The Basics Edge computing refers to the practice of processing data near the source of data generation, at or close to the "edge" of the network, rather than relying on a centralized data center that may be hundreds or thousands of miles away. By performing computations locally — on devices, gateways, or nearby servers — edge computing dramatically reduces the distance data must travel. The result is lower latency, faster response times, and reduced bandwidth consumption. For applications that depend on real-time decision-making — such as autonomous vehicles, industrial automation, and augmented reality — edge computing is not merely an optimization; it is a fundamental enabler. Decentralization: The New Paradigm Decentralization, in the broadest sense, is the redistribution of authority, computation, and data away from a single central entity toward a network of participants. Where traditional cloud computing relies on a small number of massive data centers operated by a handful of providers, a decentralized approach distributes workloads across a wide array of independently operated nodes. Edge computing and decentralization are natural allies. Both reject the assumption that all data must flow to a central hub before it can be useful. Together, they form the basis for a new kind of infrastructure — one that is distributed by design and resilient by default. Enhanced Privacy and Security When data is processed at the edge rather than transmitted to a distant data center, it spends less time in transit and is exposed to fewer intermediaries. This inherently reduces the attack surface. In a decentralized edge model, data can be encrypted and processed locally, with only the necessary results shared across the network. Because no single entity holds all the data, the consequences of any individual breach are contained. There is no central honeypot for attackers to target. This distributed trust model aligns with zero-trust security principles and provides a stronger foundation for privacy-sensitive applications. Lower Latency Latency is the silent bottleneck of centralized architectures. Every millisecond of delay compounds across millions of requests, degrading user experience and limiting what applications can achieve. Edge computing addresses this directly by placing processing power closer to end users and data sources. In a decentralized edge network, requests are routed to the nearest available node rather than a fixed data center. This geographic proximity translates to measurably faster response times — critical for gaming, video streaming, financial trading, and IoT applications where real-time interaction is expected. Improved Reliability Centralized systems carry an inherent risk: a single point of failure. If a major cloud provider's region goes down, every service depending on it is affected. Decentralized edge networks eliminate this vulnerability by distributing workloads across many independent nodes. If one node fails, others absorb its load without disruption. This fault-tolerant architecture ensures higher uptime and more consistent performance, even under adverse conditions. For businesses and services that cannot afford downtime, decentralized edge infrastructure offers a level of resilience that centralized models struggle to match. Cost and Energy Efficiency Building and maintaining hyperscale data centers is extraordinarily expensive and energy-intensive. Decentralized edge computing offers an alternative by leveraging existing infrastructure — spare compute capacity on servers, workstations, and devices already deployed around the world. This peer-to-peer approach dramatically reduces the capital expenditure required to scale. Processing data locally also reduces the volume of data that must traverse long-haul network links, lowering bandwidth costs and energy consumption. By making better use of resources that already exist, decentralized edge computing delivers both economic and environmental benefits. Challenges Decentralized edge computing is not without hurdles. Coordinating workloads across heterogeneous, independently operated nodes introduces complexity in orchestration, consistency, and quality of service. Ensuring that edge nodes meet security and performance standards requires robust monitoring and incentive mechanisms. Standardization across diverse hardware and network conditions remains an ongoing effort. These are engineering challenges, not fundamental limitations — and they are being actively solved by teams building the next generation of distributed infrastructure. The Road Ahead The convergence of edge computing and decentralization is accelerating, bolstered by the global rollout of 5G networks. With 5G providing the low-latency, high-bandwidth connectivity that edge applications demand, decentralized edge infrastructure is poised to move from an emerging concept to a production-grade reality. As more devices come online and more applications demand real-time responsiveness, the case for processing data at the edge — on a decentralized network — only grows stronger. The future of computing is not in bigger data centers; it is in smarter, more distributed networks that bring power to the edge. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Why Decentralization is Essential for DNS Security URL: https://edge.network/blog/decentralization-and-dns-security/ Markdown: https://edge.network/blog/decentralization-and-dns-security.md JSON: https://edge.network/json/blog/decentralization-and-dns-security.json _A new wave of decentralization is offering potential solutions to enhance DNS security, resilience and privacy._ Blog | Engineering 4 min read Why Decentralization is Essential for DNS Security A new wave of decentralization is offering potential solutions to enhance DNS security, resilience and privacy. AD Adam K Dean CTO The Domain Name System is one of the most critical yet underappreciated components of internet infrastructure. Every time you visit a website, send an email, or connect to an API, DNS is working behind the scenes to translate human-readable domain names into the IP addresses that machines use to communicate. It is, in many ways, the phonebook of the internet. But this foundational system was designed in an era when the internet was a far smaller, more trusted environment. Today, DNS faces an increasingly sophisticated threat landscape — and its inherently centralized architecture makes it a high-value target. A new wave of decentralization is offering potential solutions to enhance DNS security, resilience, and privacy. The DNS as a Centralized Target Traditional DNS infrastructure relies on a hierarchical system of authoritative name servers, with root servers at the top. While this architecture has scaled remarkably well, it concentrates control and creates single points of failure. High-profile DNS outages — such as the 2016 Dyn attack, which brought down major services including Twitter, Reddit, and Netflix — have demonstrated the fragility of centralized DNS at scale. Centralized DNS is also vulnerable to spoofing, cache poisoning, and man-in-the-middle attacks. When a DNS resolver is compromised, attackers can redirect users to malicious sites without their knowledge. These vulnerabilities are not theoretical — they are actively exploited in the wild, affecting millions of users and costing businesses significant revenue and trust. Decentralizing DNS: A New Era Decentralized DNS represents a fundamental rethinking of how domain resolution works. Rather than relying on a small number of centralized authorities, decentralized DNS distributes the resolution process across a network of independent nodes. This eliminates single points of failure and creates a system that is inherently more resilient, secure, and resistant to censorship. Several approaches to decentralized DNS have emerged, from blockchain-based naming systems to distributed hash table (DHT) resolution protocols. What they share in common is a commitment to distributing trust and control across a wide network of participants, rather than concentrating it in the hands of a few operators. Enhanced Resilience to Attacks One of the most compelling advantages of decentralized DNS is its resilience to distributed denial-of-service (DDoS) attacks. In a centralized system, overwhelming a DNS provider's servers can take down resolution for thousands or even millions of domains simultaneously. In a decentralized system, there is no single target to attack — queries are resolved across a distributed network of nodes, making it exponentially more difficult for attackers to disrupt the system. Even if a significant number of nodes are taken offline, the remaining nodes can continue to resolve queries, ensuring continuity of service. This fault tolerance is a fundamental property of decentralized architectures and represents a significant improvement over centralized alternatives. Reduced Risk of DNS Spoofing and Hijacking DNS spoofing and hijacking attacks exploit the trust model of centralized DNS. When a resolver or authoritative server is compromised, attackers can inject false records that redirect users to fraudulent or malicious destinations. These attacks can be difficult to detect and devastating in their impact. Decentralized DNS mitigates these risks by distributing the resolution process and incorporating cryptographic verification. Records can be signed and validated by multiple independent nodes, making it significantly harder for an attacker to inject false information. The distributed nature of the network means that even if one node is compromised, the broader network can detect and reject the fraudulent records. Privacy Protection Traditional DNS queries are typically sent in plaintext, allowing ISPs, network operators, and other intermediaries to monitor which domains users are visiting. This creates a detailed record of browsing activity that can be collected, analysed, and in some cases sold or shared with third parties. Decentralized DNS architectures can incorporate privacy-preserving techniques such as encrypted queries, onion routing, and zero-knowledge proofs. By distributing resolution across multiple nodes and encrypting communication between them, decentralized DNS can significantly reduce the ability of any single entity to surveil user activity. Censorship Resistance In many parts of the world, centralized DNS is used as a tool for censorship. Governments and authorities can compel DNS providers to block access to specific domains, effectively making websites and services invisible to users within their jurisdiction. Because DNS resolution is the first step in connecting to any internet resource, controlling DNS means controlling access to the internet itself. Decentralized DNS resists censorship by design. Without a central authority that can be compelled to block domains, censorship becomes technically infeasible. Records are maintained across a distributed network of nodes, and no single entity has the power to unilaterally remove or block access to a domain. Challenges and Future Directions Decentralized DNS is not without its challenges. Performance, consistency, and user experience must be carefully managed in a distributed system. Ensuring that DNS records propagate quickly and consistently across a large network of nodes requires sophisticated protocols and infrastructure. There are also questions of governance — how are disputes resolved, and who decides the rules of the network? Despite these challenges, the trajectory is clear. As cyber threats grow more sophisticated and the demand for privacy and resilience increases, the case for decentralized DNS becomes ever more compelling. At Edge, our DNS service is built on decentralized infrastructure from the ground up — delivering the performance, security, and resilience that the modern internet demands. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Why Decentralized Computing is Necessary for Fast Scaling AI Capabilities URL: https://edge.network/blog/decentralized-computing-and-scaling-ai/ Markdown: https://edge.network/blog/decentralized-computing-and-scaling-ai.md JSON: https://edge.network/json/blog/decentralized-computing-and-scaling-ai.json _AI's insatiable appetite for compute power is pushing centralized clouds to their breaking point. We explore how decentralized computing offers the solution._ Blog | Engineering 5 min read Why Decentralized Computing is Necessary for Fast Scaling AI Capabilities AI's insatiable appetite for compute power is pushing centralized clouds to their breaking point. We explore how decentralized computing offers the solution. AD Adam K Dean CTO The relentless growth in demand for AI has made scalable compute infrastructure an urgent necessity. While traditional centralized cloud computing models have served us well, they are increasingly strained by the exponential increase in processing power and performance required to fuel the next generation of AI innovation. In this article, we explore the limitations of centralized cloud computing to highlight the compelling benefits of distributed systems, focusing on their superior performance, enhanced security, cost-effectiveness, and remarkable operational efficiency. Pitfalls of Centralized Cloud Computing Centralized cloud computing relies heavily on data centers that are often located far from end users. This geographic separation introduces latency, or the time it takes for data to be transferred following a command. Although cloud providers offer scalable solutions, centralized data centers are inherently limited in their ability to scale. As demand increases, the process of adding resources within a centralized system becomes increasingly complex and costly. As a result, large-scale applications can experience performance bottlenecks and delays during peak usage periods as the centralized infrastructure struggles to meet sudden surges in demand. In addition, centralized data centers are significant energy consumers, contributing to global carbon emissions. These centers require continuous power not only for computing, but also for cooling and maintaining equipment. The growing energy consumption of data centers has profound environmental implications, exacerbating the carbon footprint associated with the increasing demand for cloud services. It is imperative to explore the potential of distributed computing as a superior alternative, offering solutions that address the limitations of centralized models and provide enhanced performance, improved security, cost efficiency and environmental sustainability. At Edge, we want to show how decentralized infrastructure not only supports, but also accelerates the rapid scaling of AI capabilities, making it in many ways indispensable to the development of AI. Reducing Latency Decentralized computing offers a significant advantage in reducing latency by bringing data processing closer to its point of origin and distributing it across various devices. This approach stands in stark contrast to traditional centralized systems, which typically concentrate computing power in data centers, geographically distant from end users. In a decentralized network, computational tasks are distributed across a vast array of nodes spread out over diverse locations. This distributed architecture ensures that data doesn't have to travel long distances to be processed, cutting down on transmission time. The result is a significant improvement in responsiveness, which is critical for a wide range of applications. By minimizing latency, decentralized computing not only improves the overall user experience for these applications, but also enables more efficient real-time decision-making processes. This efficiency is especially important as AI capabilities continue to scale rapidly. Lower latency allows AI systems to process more data and make decisions faster, facilitating the development of more sophisticated and responsive apps. This reduced latency in decentralized systems can lead to energy savings and improved resource utilization. By processing data closer to its source, less energy is used to transmit data over long distances. Cost Efficiency to the Max Instead of relying on expensive, centralized data centers, decentralized computing represents a revolutionary approach to computing resource cost efficiency by harnessing the power of existing hardware distributed across a wide network. This includes personal computers, smartphones, tablets, and all types of IoT devices, effectively creating a vast, interconnected web of computing power. This low-cost model has far-reaching implications for the rise of AI. By lowering the financial barriers to entry, decentralized computing fosters an environment ripe for innovation, making high-level computational power more accessible to a broader range of entities. Small businesses, startups, and even individual researchers can now access resources that were previously available only to large corporations or well-funded institutions. In addition, decentralized systems allow all types of organizations to tap into computational resources worldwide, potentially taking advantage of regions with lower energy costs. Increased Reliability and Security Reliability, fault tolerance and security are crucial aspects of any computing infrastructure, especially as our dependence on digital systems continues to grow. Distributed computing offers a robust solution to these challenges, providing a level of resilience that centralized systems struggle to match. This increased reliability comes from the distributed nature of decentralization and its ability to maintain operations even in the face of partial system failures. In a decentralized system, the failure of a single node has minimal impact on the entire network because other nodes can seamlessly take over the workload. This is in stark contrast to centralized systems, where a failure in a central data center can result in widespread service disruption, as we have witnessed in recent events. The distributed nature of decentralized computing ensures continuous availability and fault tolerance, making it an ideal infrastructure for critical applications that require high uptime and reliability. This robustness is essential for reliably scaling AI applications, which often operate in environments where downtime can have significant technical and economical consequences. With the looming threat of data breaches and cyberattacks, the need for secure solutions is greater than ever — decentralized computing offers a compelling option to many of the security challenges inherent to traditional centralized systems. By fundamentally changing the way data is stored and processed, decentralized networks provide a robust defense against a wide range of cyber threats, as they enhance security by distributing data and processing tasks across multiple nodes. In centralized systems, data stored in a few large data centers can be a tempting target for cyber-attacks, while decentralized networks employ advanced encryption and security protocols at each node, making it more challenging for attackers to compromise the entire system. Embracing Decentralisation for the Future of AI The transition to distributed computing models marks a fundamental shift in our approach to digital infrastructure. This paradigm shift is an evolution toward a more robust, efficient, and adaptable framework capable of meeting the escalating demands of AI technologies. Edge harnesses the transformative potential of decentralized computing. By leveraging the spare capacity of a global network of devices, our decentralized infrastructure can efficiently support and accelerate the scaling of AI capabilities. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Why We Open Source URL: https://edge.network/blog/why-we-open-source/ Markdown: https://edge.network/blog/why-we-open-source.md JSON: https://edge.network/json/blog/why-we-open-source.json _The technology strategy and philosophy behind Edge Network: why we open source our code, how openness builds trust, and why all roads eventually lead to DAO._ Blog | Engineering 3 min read Why We Open Source The technology strategy and philosophy behind Edge Network: why we open source our code, how openness builds trust, and why all roads eventually lead to DAO. AD Adam K Dean CTO Over 150 weekly updates and counting. Community roles on Discord. A path to DAO that's becoming clearer with every release. And now, another milestone: Edge Wallet has become open source — its code open to the world for anyone to read, audit, and contribute to. For some companies, open sourcing code is a marketing exercise. For Edge, it's a core part of the strategy. Here's why. Transparency Isn't Optional If you're building a decentralised network, trust is everything. People are contributing their devices, their bandwidth, and their computing power. They need to know what the software is doing — not because we say so, but because they can see for themselves. Open source makes that possible. When the code is public, anyone can inspect it. Anyone can verify that the software behaves the way we say it does. It's not about marketing transparency — it's about architectural transparency. The kind that's built into the system rather than bolted on afterwards. Edge empowers its community to contribute and to have a genuine say in how things evolve. That starts with visibility into the codebase itself. Open Contributions, Real Recognition Opening the code doesn't just invite scrutiny — it invites participation. Community members who contribute to Edge's open source repositories earn badges and the "Code Contributor" role on Discord. It's a small thing, but it matters. It signals that contributions are valued, recognised, and encouraged. We've seen contributors spot bugs, suggest improvements, and build features that the core team hadn't prioritised. That's the power of an open codebase: it multiplies the talent working on the project far beyond the people on the payroll. Open Source as Philosophy This isn't new territory for the team. The people building Edge have decades of collective experience working with and contributing to open source projects. We've seen first-hand what happens when talented, motivated people are given the tools and the freedom to build together. Open source isn't just a licensing model. It's a way of thinking about software — one that values collaboration over control, and shared progress over proprietary advantage. It aligns perfectly with what Edge is trying to do: build a fairer internet where the value is shared by the people who create it. All Roads Lead to DAO Open source is also a stepping stone toward something larger. As Edge moves toward becoming a DAO — a decentralised autonomous organisation — the codebase needs to be open. Governance needs to be transparent. Decisions need to be visible. Open sourcing the software is a necessary precondition for genuine decentralised governance. The path to DAO doesn't happen overnight. It's built piece by piece — every open repository, every community contribution, every transparent decision brings it closer. And the community is what makes it work. More Successful Together The internet was built on open protocols and shared standards. Somewhere along the way, that spirit got locked behind corporate walls. Edge is working to bring it back — not through ideology alone, but through practical, working software that anyone can see, use, and improve. We're more successful together. A fairer internet — one where the revenue is shared by everyone who helps build it — starts with code that belongs to everyone too. Exclusive Offer Start Free — No Card Required Create a free account in seconds. Free DNS, free CDN and Storage tiers, and per-resource compute billed hourly. Zero egress fees. Start Free Promo code: EDGE2FREE Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ## Other ### About URL: https://edge.network/about/ Markdown: https://edge.network/about.md JSON: https://edge.network/json/about.json _Edge is a distributed cloud platform built for performance, transparency, and sustainability. Meet our team and learn about our mission._ About Us Building the future of cloud infrastructure We're on a mission to create truly decentralized, transparent, and cost-effective cloud infrastructure for everyone. What Drives Us Our mission and vision guide everything we build. Our Mission Edge Network is the world's first decentralized cloud platform. We believe infrastructure should be transparent, distributed, and accessible to everyone—not controlled by a handful of tech giants. Our Vision A world where cloud infrastructure is as open and distributed as the internet itself. Where no single company controls the backbone of the digital economy. Our Values The principles that shape how we build and operate. Transparency Open infrastructure, clear pricing, no hidden fees. What you see is what you get. Zero egress. Sustainability 50% greener by design. Building infrastructure that respects the natural world. Community Powered by a global network of operators, built on XE, for developers and enterprises alike. Performance Speed without compromise. 988 edge locations delivering sub-50ms latency. Everywhere. Always. The Green Cloud 50% greener by design. Our distributed architecture harnesses existing spare capacity and processes data closer to users—cutting transmission distances and energy consumption in half. Learn About Our Impact 50% Less Energy 988 Edge Locations 0 New Data Centers 50% Shorter Data Paths Our Journey Eight years of building the network, the products, and the platform. 2018 Edge Founded Started with a vision for decentralized cloud infrastructure. 2020 Mainnet Launch Launched the Edge Network mainnet with initial node operators. 2022 CDN Launch Released our global CDN product to the public. 2023 DNS Launch Launched fast, reliable DNS hosting with global anycast. 2024 Compute Launch Introduced edge compute with VM support. 2025 Storage Launch Released S3-compatible object storage. 2025 Enterprise Ready Full enterprise feature set with SLA guarantees. 2026 Shield Launch Free, privacy-first bot protection without puzzles — with a humanity score and verified agent access. 2026 Assist Launch Conversational agents for any website — answers grounded in your content, embedded with one line of code. Leadership The team driving Edge forward. Joseph Denne CEO & Co-founder Will Lebens COO & Co-founder Adam K Dean CTO Tim Ludlow Project Director Mason Curry Head of Technology Join us We're always looking for talented people to join our mission. View Careers Tokenisation Edge is a fully tokenised platform, powering the world's lowest latency cloud through a dual-token architecture designed for seamless utility, governance, and network participation. $EDGE enables users to access enterprise-grade services (VMs, CDN, DNS, Storage, and Shield), contribute resources, and help shape the platform's future. $EDGE: The Utility & Governance Token Buy and Use Services Acquire $EDGE on leading exchanges (e.g., Uniswap) to pay directly for cloud services. Deploy VMs, deliver content via Edge CDN, manage domains with DNS, or run AI workloads. Enjoy resilient performance that remains online during outages at AWS, Cloudflare, or Google Cloud. Governance Participation Stake $EDGE to vote on protocol upgrades, fee structures, service expansions, and treasury decisions. Active stakers help guide the network's evolution to meet community needs. Referral Programme Earn $EDGE rewards by referring clients or node operators. Share your unique link through the Edge Portal—receive commissions on verified service spend or node contributions from your network. $EDGE drives real utility from the services layer, with protocol mechanisms creating demand through network activity. Edge Nodes Run a Node Operate an Edge node to contribute bandwidth, compute, or storage to the network. Enhance global performance with lower latency for real-time applications and scalable CDN. Earn $EDGE Nodes earn $EDGE rewards for their contributions – scaling with network demand and usage. Impact Your node supports the full stack, from cloud reliability to decentralised infrastructure. Every node strengthens the network and earns its share of growth. Why Tokenised? Power the Cloud. In a $2T cloud market facing frequent failures, Edge tokenises participation: $EDGE for accessing services, voting in governance, earning via referrals, contributing infrastructure and earning rewards. No central points of failure – just active users powering a decentralised, resilient alternative. Get Started Buy $EDGE Stake & Govern Run a Node Explorer Tokens provide access and participation rights – not investments. No guaranteed returns; rewards depend on network activity and contribution. Not financial advice. Stay Updated Subscribe to our newsletter for the latest news, product updates, and engineering insights. Subscribe --- ### Careers URL: https://edge.network/careers/ Markdown: https://edge.network/careers.md JSON: https://edge.network/json/careers.json _Join Edge Network and help build the future of cloud infrastructure. Fully remote, global team, meaningful work._ Careers Build the Future of Cloud Join a small, passionate team building infrastructure that powers the next generation of applications. Fully remote, global impact. Why Edge? We're not just another cloud company. We're building a decentralized infrastructure that's faster, greener, and more transparent than the hyperscalers. Our network spans thousands of locations across 80+ countries, powered by thousands of independent operators. We're a small team with outsized ambitions. Every person here has a direct impact on the product and the company's direction. If you want to work on hard problems with smart people, you'll fit right in. We've been remote since inception — long before it was hot. We believe great work can happen anywhere, and we've built our culture around that principle. Build in Public We share our progress, our challenges, and our learnings. Transparency isn't just for customers. Move Fast, Stay Stable We ship quickly but never compromise on reliability. Our customers depend on us. Think Long-Term We're building infrastructure for the next decade, not the next quarter. Question Everything The best ideas come from anywhere. We encourage healthy debate and fresh perspectives. Benefits & Perks We take care of our team so they can focus on doing their best work. Fully Remote Work from anywhere in the world. We've been remote since day one. Flexible Hours We care about output, not hours. Work when you're most productive. Competitive Pay We pay fairly and transparently, no matter where you're based. AI-Forward AI is at the heart of everything we do. Build with cutting-edge tools. Learning Budget Annual allowance for courses, conferences, and books. Tokenised Upside Share in Edge's success with $EDGE token allocations. Small Team, Big Impact We're a small team that punches above our weight. With AI at the core of how we work, we've built a global infrastructure platform with a fraction of the headcount you'd expect. We're actively hiring. Exceptional people should reach out. If you're genuinely passionate about infrastructure, decentralization, or the future of cloud, we'd love to hear from you. Get in Touch --- ### Contact Us URL: https://edge.network/contact/ Markdown: https://edge.network/contact.md JSON: https://edge.network/json/contact.json _Get in touch with Edge Network. Sales enquiries, technical support, and partnership opportunities._ Contact Get in Touch We'd love hearing from our customers, supporters and future friends. Choose the best way to reach us and we'll get back to you as quickly as possible. Contact Options Reach the right team for your inquiry. Sales Talk to our sales team about enterprise solutions. sales@edge.network Support Get help with your account or technical issues. support@edge.network Press Media inquiries and press resources. press@edge.network Partnerships Explore partnership and integration opportunities. partnerships@edge.network Send us a message Fill out the form and a member of the team will get back to you as soon as possible. Have a project in mind? Skip the form and book a free consultation with our Expert Services team instead. First Name Last Name Email Subject Sales inquiry Technical support Expert Services Edge Labs Partnership Press inquiry Startup programme Other Message Send Message Message sent Thanks for getting in touch. A member of the team will get back to you as soon as possible. Prefer email? Reach out to the founders directly at joseph@edge.network & will@edge.network Things we love hearing about "We want to move off AWS and need help migrating." "Our CDN bills are out of control." "We're launching in 3 weeks and need a partner." "Can you handle 10 million requests per second?" "We care about sustainability and want to work with companies that do too." Or just say hi. We're friendly. --- ### Edge Accreditation URL: https://edge.network/accreditation/ Markdown: https://edge.network/accreditation.md JSON: https://edge.network/json/accreditation.json _Become a certified Edge practitioner. A structured programme covering the whole platform — DNS, CDN, Compute, Storage, Shield, and the agentic cloud — with a verifiable certificate at the end. Coming soon; sign up for updates._ Coming soon Edge Accreditation Become a certified Edge practitioner. A structured, hands-on programme covering the whole platform — with a verifiable certificate at the end that proves you can build and run infrastructure on the network of the future. Be first in line Sign up for updates and we'll let you know when enrolment opens — plus early access to the first modules as they're released. Sign up for updates What it is The Academy teaches you Edge piece by piece. Accreditation puts it together: one programme, the full platform, and a credential at the end that means something. A structured programme Not a pile of docs — a guided path through the whole platform, from your first DNS zone to deploying infrastructure with AI agents. Each module builds on the last. Hands-on, not theoretical Every module is built around doing: real deployments, real configuration, real troubleshooting on the free tiers. If you finish it, you can genuinely run production workloads on Edge. A verifiable certificate Finish the programme and earn a certificate anyone can verify — a link an employer or client can check, not a PDF that could have come from anywhere. What you'll cover Eight modules spanning everything Edge does — each one hands-on, each one building towards infrastructure you've configured, secured, and shipped yourself. 01 DNS & Domains Zones, records, DNSSEC, and the anycast network. 02 CDN & Delivery Deployments, custom domains, caching, and image optimization. 03 Compute VMs, startup scripts, SSH keys, firewalls, snapshots, and backups. 04 Storage S3-compatible buckets, presigned URLs, and SDK integration. 05 Shield Bot protection, humanity scores, and verified AI agents. 06 CLI & API Automating everything from the terminal and over HTTPS. 07 The Agentic Cloud Agent access codes, budgets, and letting AI deploy for you. 08 Cost & Operations Right-sizing, budgets, monitoring, and running lean. Start learning now in the Academy Why it matters for your career Credentials are only worth what they prove. Edge Accreditation is built to prove something specific: that you can take infrastructure from nothing to production. Proof, not claims Anyone can write "cloud infrastructure" on a CV. A verifiable certificate shows you've actually deployed, secured, and operated real infrastructure — and lets anyone check it in one click. Ahead of the agentic curve Infrastructure that AI agents can deploy and manage is where the industry is heading. Accredited practitioners will be among the first who can demonstrate they know how to work this way. Visible to the people hiring Share your certificate on LinkedIn and in your email signature. As the Edge ecosystem grows, accreditation is how teams will find practitioners they can trust with their infrastructure. Skills that transfer DNS, CDNs, object storage, VMs, bot protection, APIs — the concepts you master are the backbone of every modern stack. Edge is the classroom; the skills go everywhere. Get certified first Enrolment isn't open yet. Sign up now and you'll hear the moment it is — with early access to the first modules as they're released. Sign up for updates --- ### Edge Hosting URL: https://edge.network/hosting/ Markdown: https://edge.network/hosting.md JSON: https://edge.network/json/hosting.json _Host static sites, Node.js apps, containers, and databases across a distributed edge network. Zero egress fees, global reach, and pricing that makes sense._ Hosting Edge Hosting Host your sites, apps, and data across a distributed edge network instead of a single region. Faster for every visitor, resilient by design, and with zero egress fees — ever. Start Hosting Free View Pricing 3K+ Customers 100% Network Uptime $0 Egress Fees Free To Start, No Card Trusted by teams like What is edge hosting? Most hosting puts your website in one place: a data centre in a single region. Users near that region get a fast experience; everyone else waits while their requests cross oceans. Edge hosting flips the model — your content and applications are served from a network of locations distributed around the world, so every request is answered close to the person making it. Edge takes this further than traditional providers. The network is powered by 988 independently operated nodes rather than a handful of corporate data centres, which means genuine geographic spread and no single point of failure. On top of that network sits a complete hosting platform: a CDN for delivery, virtual machines for your applications, S3-compatible object storage for your data, and anycast DNS to tie it all together. The result is hosting that behaves the way the internet should: fast everywhere, resilient to outages, and priced without the bandwidth penalties that make centralised clouds so expensive to scale. Edge hosting at a glance 988 edge locations – content served close to every visitor Zero egress fees – bandwidth is never a line item Full-stack platform – CDN, compute, storage, and DNS in one place No lock-in – standard VMs, S3-compatible APIs, plain DNS Free to start – free tiers across the platform, no card required to sign up What can you host on Edge? From a static landing page to a full production stack — if it runs on the web, it runs on Edge. Static Sites Deploy HTML, CSS, and JavaScript straight to the edge. Every page is served from the location nearest your visitor. Next.js & Modern Frameworks Run Next.js, Astro, Nuxt, and SvelteKit apps with global content delivery in front of your rendering layer. WordPress Host WordPress on your own VM with the Edge CDN accelerating every asset — no per-visitor bandwidth charges. Craft CMS A fast, flexible home for Craft with NVMe storage and edge caching for your templates and assets. Node.js Applications APIs, backends, and full-stack apps on virtual machines you control, billed by the hour from a prepaid balance. Docker Containers Bring any container. Deploy Docker workloads on Edge compute with full root access and NVMe disks. Databases PostgreSQL, MySQL, MongoDB, and Redis on dedicated VMs — your data, your instance, no managed-database markup. Files & Media S3-compatible object storage on NVMe with no egress fees, fronted by the CDN for global delivery. Looking for something specific? Browse the full range of stacks and solutions — including Laravel, Django, Rails, Ghost, Strapi, and more. Why edge beats single-region hosting Distribution isn't a nice-to-have. It changes performance, reliability, and cost. Lower Latency Single-region hosting is fast for users near the data centre and slow for everyone else. Edge serves content from 988 locations, so every visitor gets a nearby response. Built-in Resilience A distributed network has no single point of failure. If one node drops out, traffic routes around it automatically — an outage in one place never takes your site down everywhere. Zero Egress Fees Traditional clouds charge you to serve your own users. Edge doesn't. CDN bandwidth, storage egress, and compute transfer are all included at any volume. Secure by default, not by upgrade Protection isn't a product tier on Edge. Every site gets the full security stack from the moment it's deployed. DDoS protection as standard Attacks are absorbed at the network edge before they reach your site — included on every deployment, at no extra cost. Free SSL on every domain Automatic TLS certificates, provisioned and renewed for you. Every site on Edge is encrypted by default. Free bot protection Edge Shield scores every visitor from 1–100 and stops abuse at the front door — without ever showing a human a puzzle. No surprise bills Compute runs from a prepaid balance and free tiers hard-cap by default, so a runaway bill is impossible by design. Learn more about Edge Shield How Edge hosting works Four services, one platform. Use them together for a complete hosting stack, or pick just the pieces you need. CDN Caches and serves your content from the edge, with free SSL, image optimisation, and zero egress fees. Compute Virtual machines with custom vCPU, RAM, and NVMe disk. Billed hourly from a prepaid balance — stop any time. Storage S3-compatible object storage, all NVMe, with no egress fees and no per-request charges. DNS Fast anycast DNS, free for up to 50 zones with unlimited records. Point your domain at Edge and go. A typical deployment: your domain resolves through Edge DNS , the CDN caches and serves static assets from the nearest edge location, your application runs on a Compute VM, and uploads, media, and backups live in Storage . Everything is managed from one console with one bill — and none of it charges you for bandwidth. The Green Cloud Hosting that's 50% greener by design Hyperscale data centres run at a fraction of capacity while burning energy on idle servers and cooling. Edge takes the opposite approach: the network runs on distributed nodes utilising spare capacity, and because content is served close to your visitors, data travels half the distance — using roughly half the energy. Choosing where you host is one of the simplest ways to cut your digital footprint. With Edge, greener isn't a premium tier — it's how the network is built. How Edge is better for the environment 50% Less energy than hyperscale providers 50% Shorter data paths 100% Renewable energy, where available Pricing that stays predictable DNS and Shield are free forever. CDN, Storage, and Assist have free tiers. Compute is priced per resource — vCPU, RAM, and disk — and billed hourly from a prepaid balance, so a surprise bill is impossible by design. Free tiers hard-cap by default: exceeding one pauses the resource, it never silently starts billing. Explore Full Pricing Example rates Starter VM (1 vCPU, 2 GB, 40 GB NVMe) ~$9.62/mo CDN (after 500k free requests) $0.25/million Storage (after 5 GB free) $0.015/GB-mo Egress, at any volume $0 Hosted somewhere else? We'll move you. You don't have to migrate alone. Our Expert Services team handles migrations from legacy infrastructure and hyperscalers without downtime — from a single WordPress site to a full production stack. The initial consultation is free, and you'll get a clear plan before anything moves. Talk to Expert Services Read the migration guide What migration with Edge looks like Free initial consultation — scope, timeline, and costs agreed up front Zero-downtime cutover — DNS switches only once everything is verified Senior engineers — the same teams that take on full builds and integrations Prefer DIY? — standard VMs, S3-compatible APIs, and plain DNS make self-migration straightforward What our customers say "Edge enabled us to release in days and weeks, instead of weeks and months." Matt Hobbs CTO, Bauer Media Group Read the case study "Edge lets me focus on building, not infrastructure. That's exactly what I needed." Andrew Roberts Founder, Code+Ink Read the case study "Edge gives us the global reach our audience demands without the complexity we dreaded." Monocle Media & Broadcasting Read the case study Edge hosting FAQs The questions people ask before moving to the edge. What is edge hosting? Edge hosting means running your website or application across a distributed network of servers positioned close to your users, rather th... --- ### Edge Network | The cloud, closer URL: https://edge.network/refresh/ Markdown: https://edge.network/refresh.md JSON: https://edge.network/json/refresh.json _CDN, compute, storage, DNS, bot protection and AI assistants on a network of thousands of independent nodes near the people you serve. Zero egress. Free to start._ EDGE-NATIVE CLOUD Closer to your users than the cloud has ever been CDN, compute, storage and DNS on a network of thousands of nodes near the people you serve. Zero egress fees. Free to start. Built for humans and the agents working for them. Start free, no card required Connect your agent Every free tier hard-caps by default. Nothing on Edge silently starts billing. WHO WE ARE A cloud that runs where people are Edge is powered by thousands of independent node operators rather than a few hyperscale data centres. That makes it faster for every visitor, more resilient by design, cheaper to run, and radically lighter on the planet. Eight years in, it serves three thousand customers, from indie sites to Bauer and Tinder. About Edge 3K+ Customers 988 Nodes online 100% Network uptime $0 Egress fees WHY THE EDGE Three things geography buys you Centralised clouds solve distance with bigger machines and bigger bills. We solve it by not having the distance. Speed from geography, not brute force Your content and code run on 988 nodes near your users instead of a handful of regions. Shorter paths beat bigger data centres. See the network Zero egress. Not a promotion, a principle. You are never charged to move your own data. CDN bandwidth, storage egress and compute transfer are included at any scale. See pricing Half the energy Spare capacity on existing hardware, no new data centres, and data that travels half as far. Around 50% less energy than the centralised cloud. How we measure it ONE PLATFORM The whole stack. One console. One bill. Static sites, WordPress, Next.js, containers, databases, media. If it runs on the web it runs on Edge, and each product starts free. CDN Global delivery with image optimisation 3 deployments, 500k requests a month free Compute Dedicated VMs, billed hourly by resource From $0.004 per vCPU-hour, $5 starter credit Storage S3-compatible object storage on NVMe 2 buckets, 5 GB free, no egress fees DNS Authoritative anycast DNS with geo-routing Free for everyone, up to 50 zones Shield Bot protection that never shows a human a puzzle Free forever, unlimited verifications Assist AI answers grounded in your own content 250 answered questions a month free See all pricing What you can host on Edge PERFORMANCE One of the fastest clouds on Earth Not our benchmark. Live real-user measurements from PerfOps, the independent monitor used to rank every major CDN, refreshed as you read this. Powered by PerfOps Independent RUM monitoring About the methodology Loading performance data... Full performance data DESIGNED FOR HUMANS The cleanest control centre on Earth No 47-tab dashboards and no certification required. Every product in one place, with one bill, and a balance that tells you what it is doing and why. Open a free account THE AGENTIC WEB Built for people. Ready for their agents. A growing share of legitimate traffic is software acting for a person. Edge treats it as a first-class customer: deployable by API, readable by machine, verified at the door. One line to connect Cursor, Windsurf, Claude and any MCP client get native Edge tools. No account needed to start; the server signs itself up for a free tier. Machine-readable by default Every page on this site ships as llms.txt, markdown and JSON. Agents get clean answers, not HTML to scrape. Agents as a signal, not a threat Shield scores traffic instead of blanket-blocking it. Sites on Edge welcome humans, route verified agents and stop real abuse. Connect your tool Agent documentation mcp.json 22 tools { "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"] } } } > Deploy this folder to a CDN on mysite.com ✓ Signed up for a free explore-tier account ✓ Created CDN deployment and DNS zone ✓ TLS issued, live at https://mysite.com BEYOND INFRASTRUCTURE When you want us to build it too The same team that runs the network takes on migrations, full builds and frontier R&D for customers who would rather ship than hire. Expert Services AI-native development teams for migrations, integrations and full builds. Senior talent embedded month to month, at 20% or more below the cost of hiring in-house. Free initial consultation. Edge Labs A frontier R&D unit on retainer: a quarterly report on what matters in AI and robotics for your sector, a monthly brief, and two or three product concepts a year that we can build and hand over finished. Start free. Two minutes. No card. Deploy a site, a zone, a bucket or a Shield widget on the free tiers. Add a card only when you want more, and pay for what you use from a balance you control. Create your account View pricing Free tiers on every product, hard-capped by default Zero egress fees at any scale Prepaid balance; nothing bills without your say-so Stay updated Product updates, engineering notes and network news. Once or twice a month. Subscribe --- ### Edge Network Developer Resources | API, CLI, MCP & Agent Tooling URL: https://edge.network/developers/ Markdown: https://edge.network/developers.md JSON: https://edge.network/json/developers.json _Everything for building on Edge Network in one place: REST API documentation, OpenAPI specification, Agent API, MCP server, CLI, SDKs, and machine-readable discovery files._ Developers Edge Network developer resources Everything you need to build on Edge Network — human documentation, machine-readable specifications, and agent tooling — published at predictable URLs. Start Here Human-readable documentation for every surface — products, REST API, agents, and the CLI. Edge Network Documentation Guides and reference for every product: Compute, CDN, DNS, Storage, Shield, and Assist. Read the docs Edge Network REST API Conventional JSON API with API-key authentication, typed errors, and IETF rate-limit headers. API reference Edge Network Agent API Built for AI agents: discovery-first design, dry runs, idempotency keys, budget caps, and autonomous self-signup. Agent API docs Edge Network CLI Script deployments, DNS, storage, and VMs from your terminal. One-line install, works on Linux, macOS, and Windows. CLI docs Start in One Line Install the CLI, point an agent at the self-describing API, or pull the spec. # Install the Edge Network CLI curl -fsSL https://edge.network/install.sh | sh # Or point any agent at the self-describing API curl https://edge.network/agent # Or fetch the OpenAPI spec curl https://edge.network/openapi.json Machine-Readable Resources Specifications and discovery files for tools, agents, and integrations — each at a stable, predictable URL. OpenAPI Specification The full Agent API surface as OpenAPI 3.0 — unique operationIds, typed parameters, and response schemas on every operation. GET /openapi.json MCP Server Call Edge natively from Claude, ChatGPT, Cursor, and other MCP clients over streamable HTTP, or run it locally via npx @edge-network/mcp. POST https://edge.network/mcp MCP Manifest Standard discovery manifest for the Edge Network MCP server, also listed in the official MCP registry. GET /.well-known/mcp.json llms.txt A structured guide to Edge Network for AI agents and LLMs: products, pricing, docs, and when to use each service. GET /llms.txt Versioning & Deprecation Policy How the API is versioned, what counts as breaking, and how deprecations are signalled (Sunset headers, 6-month windows). X-API-Version: 1 Authentication API keys for the REST API, bearer agent access codes for the Agent API and MCP — and how to create each. Authorization: Bearer … Build something on Edge Network Free tiers on every product. Agents can even sign themselves up — no card, no human in the loop. Create Free Account Agent Self-Signup No card required to sign up. --- ### Edge Network Surpasses 2,500 Active Nodes URL: https://edge.network/latest/active-nodes/ Markdown: https://edge.network/latest/active-nodes.md JSON: https://edge.network/json/latest/active-nodes.json _A milestone for decentralized infrastructure as our network continues to grow._ Back to Latest Network Jan 5, 2026 Edge Network Surpasses 2,500 Active Nodes A milestone for decentralized infrastructure as our network continues to grow. 2,500+ Active Nodes 130+ Countries 10+ Tbps Total Capacity 99.99% Network Uptime We're thrilled to announce that the Edge Network has surpassed 2,500 active nodes — a significant milestone in our journey to build the world's most distributed cloud infrastructure. This growth represents not just numbers, but a global community of operators who believe in a different kind of cloud. The Power of Decentralisation Unlike traditional cloud providers who concentrate infrastructure in a handful of massive data centres, Edge Network distributes capacity across thousands of smaller nodes. This architecture delivers fundamental advantages: No single points of failure — when one node goes down, traffic seamlessly routes to others Data stays local — content and compute are served from nodes close to users, not distant data centres True global reach — nodes in regions that major cloud providers ignore entirely What 2,500 Nodes Means For You Lower Latency More nodes means shorter paths to users. Average global latency has dropped to under 50ms. Greater Resilience Distributed capacity ensures no single point of failure. The network self-heals around outages. Wider Coverage Nodes in 130+ countries bring edge infrastructure to regions previously underserved. Community Powered Independent operators worldwide contribute capacity, creating a truly decentralised network. Our Growth Journey 100 nodes March 2018 Initial network launch 500 nodes December 2020 First major expansion Thank You to Our Operators This milestone wouldn't be possible without the global community of node operators who contribute their infrastructure to the Edge Network. Whether running a single node or hundreds, each operator plays a vital role in building a more resilient, distributed internet. Operators earn $XE rewards for contributing capacity Join a global community of infrastructure enthusiasts Help build the future of decentralised cloud No minimum hardware requirements to get started What's Next 2,500 nodes is just the beginning. Our roadmap includes continued expansion into underserved regions, new node types optimised for specific workloads, and enhanced tooling for operators. We're also working on bringing GPU compute to the edge, enabling AI and ML workloads to run closer to users than ever before. The future of cloud infrastructure is distributed, and we're building it together. Join the Network Whether you want to use Edge Network's global infrastructure or contribute as a node operator, there's never been a better time to get involved. Start Using Edge Become an Operator Want to learn more about running a node or the technology behind our network? Explore our network page or get in touch with our team. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Edge Shield vs Cloudflare Turnstile URL: https://edge.network/latest/edge-shield-vs-cloudflare-turnstile/ Markdown: https://edge.network/latest/edge-shield-vs-cloudflare-turnstile.md JSON: https://edge.network/json/latest/edge-shield-vs-cloudflare-turnstile.json _A founder’s comparison of Edge Shield and Cloudflare Turnstile: same siteverify shape, a 1–100 score, no per-visitor data, and a drop-in migration._ Back to Latest Product August 31, 2026 Edge Shield vs Cloudflare Turnstile A founder’s comparison of Edge Shield and Cloudflare Turnstile: same siteverify shape, a 1–100 score, no per-visitor data, and a drop-in migration. Most “Turnstile alternative” pages are either Cloudflare’s own docs, a self-hosted proof-of-work project, or a vendor explaining why neither Turnstile nor hCaptcha is enough and you should buy them instead. I built Edge Shield because I wanted the other option: the same embed you’d actually ship in a form, without routing traffic through someone else’s CDN, without a fingerprint store, and with a score I can write a policy against. It went live on 26 July 2026. This is the comparison I would have wanted before we shipped it. If you need a DDoS product, this is the wrong page. Shield is a CAPTCHA-class widget. Same job as Turnstile. Same shape on purpose Turnstile’s contract is the one developers already know: a sitekey in the page, a secret on the server, a short-lived token, a siteverify POST. Their docs are clear that the widget can sit on any site; you do not have to put the hostname behind Cloudflare. Shield copies that contract. Three modes, mapped one-to-one: Managed, Non-Interactive, Invisible. Client script is https://shield.edge.network/api.js . Markup is a div with data-sitekey . The token is a 5-minute, single-use JWT. Server check is POST https://shield.edge.network/siteverify . Error names match Turnstile’s ( timeout-or-duplicate , invalid-input-secret , and the rest). If you already have Turnstile in production, set data-compat="turnstile" and the widget also fills cf-turnstile-response . Field names, callbacks, the siteverify body: we wrote a migration guide so this is a swap, not a rewrite. Full behaviour is in the Shield docs . We did not invent invisible proof-of-work. Turnstile already runs small non-interactive challenges (proof-of-work, proof-of-space, API probes, behaviour checks) and tries not to show a puzzle. Shield’s challenge is SHA-256 in a Web Worker, difficulty adaptive, typically tens of milliseconds on a phone. The interesting differences are what happens after that work is done. Binary answers are a blunt instrument Turnstile’s siteverify is pass or fail. That is fine for a newsletter form. It is awkward the moment you have more than one policy. Shield returns the same success fields, plus a humanity score from 1 to 100 . 1 is confirmed automation. 100 is confirmed human. The bands we actually use: 70–100: allow 40–69: step up (Managed can show a challenge; you can route to a slower path) 1–39: block, or send it to the agent path That is the post I have not seen on the comparison blogs. They argue catch rate and farm prices. Operators argue thresholds. A score lets you treat a login, a checkout, and a contact form as different risk, on the same widget. Agents are not failed humans The comparison pages still frame the problem as human vs bot. A lot of the traffic we see now is neither: signed crawlers, retrieval agents, tools that should be allowed on a docs site and thrown off a password reset. Shield understands Web Bot Auth , reverse-DNS confirmation for known crawlers, and per-widget agent policy. Siteverify can include an agent field. There is a separate agentverify API for paths that never render a widget. If your “bot problem” is actually “I need a policy for machines that identify themselves,” pass/fail CAPTCHA is the wrong primitive. Privacy is an architecture, not an addendum Turnstile’s docs say they process only what is necessary, do not read your form fields, and point at a Privacy Addendum. They also document a Pre-clearance cookie for SPAs. I am not going to invent the rest of Cloudflare’s data practices. Read their addendum. What I will say about Shield, because it is how we built it: No cookies, no local storage No fingerprint database No per-visitor record, not even an anonymised one Coarse environment signals are scored in memory and discarded Interaction noise (the stuff that separates a motor cortex from a script) stays on the device; we never ship raw movement or keystroke streams The only thing we persist is hourly aggregate counters : challenge counts, average score There is nothing to put in a consent banner for the widget itself. GDPR and CCPA are the default, not a region flag. The client is open source. Accessibility target is WCAG 2.2 AA, same bar Turnstile publishes. If your constraint is “no third-party cookie and nothing stored about this visitor,” that is a design choice, not a policy PDF. Offline verify, tarpit, size Three other deltas that matter in production: JWKS. Tokens are Ed25519-signed JWTs. You can verify them locally with our public keys and never call siteverify. Useful in CI, useful when you do not want a runtime dependency on our API for every POST. Tarpit. Repeat offenders get exponentially harder proof-of-work. Most hosted widgets either pass you or bounce you. Making the cheap attack expensive is the older, boring defence, and it is documented. Payload. The widget is under 15KB, no dependencies. Turnstile’s overview does not publish a size; we do because form pages feel it. Core protection is free forever: unlimited widgets, unlimited verifications, all three modes, score included. No card, no “analytics is on the paid plan.” I am not going to pretend Cloudflare’s free Turnstile is a trap. It is a good product. I am saying we did not hold the useful bits back for a WAF bundle. When I would still use Turnstile Use Turnstile if you already live in Cloudflare’s dashboard, you want their bot/WAF/DDoS stack on the same account, or you want their analytics and pre-clearance cookie as part of that world. Their challenge platform is battle-tested. I am not competing with that bundle. Use Shield if you want the widget without the rest of the network, a score you can branch on, an agent policy, local JWT verification, and a privacy model that does not keep a visitor around. Embed it on any origin. Your traffic does not come to us. Swap it Create a widget, get es_… / es_secret_… from the console or edge shield create . Point the script at https://shield.edge.network/api.js . Keep your existing siteverify flow; change the URL and secrets. Or verify the JWT yourself. Put data-compat="turnstile" on the div if you need the old field name for a release or two. Start in shadow/report-only, look at scores, then enforce. How-to with copy-paste markup: Bot protection with Edge Shield . Product page: edge.network/shield . Launch note: Introducing Edge Shield . I did not write this to dunk on Cloudflare. I wrote it because the SERP for “Turnstile alternative” currently offers you a self-hosted puzzle or a plugin bake-off, and the thing we actually shipped is neither. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Enterprise SLA URL: https://edge.network/sla/ Markdown: https://edge.network/sla.md JSON: https://edge.network/json/sla.json _Edge's Enterprise SLA: 99.99% uptime commitment, 24/7 critical response, dedicated account management, and service credits for mission-critical workloads._ Enterprise Enterprise SLA A 99.99% uptime guarantee across all Edge services, backed by service credits, guaranteed response times, and a dedicated account manager. Built for teams running mission-critical workloads. Contact Sales View Pricing Enterprise-grade guarantees As Edge serves increasingly mission-critical workloads, guarantees matter as much as performance. The Enterprise SLA provides comprehensive coverage across all Edge services — CDN, Compute, DNS, and Storage — with clear definitions, guaranteed response times, and financial backing through service credits. Two commitments work together. The uptime SLA guarantees 99.99% availability of the platform itself, with service credits if we fall short. The support response commitments guarantee how quickly a human — not an auto-responder — engages when you raise an issue, around the clock for critical severities. Whatever your tier, some things are never gated: billing questions, security incidents, and abuse reports are handled for every customer, always. 99.99% Uptime Guarantee The Enterprise SLA guarantees 99.99% uptime across all services, backed by service credits if we fall short. Rapid Response Times Priority support with guaranteed response times, defined in your agreement. Critical issues are covered 24/7. Dedicated Support A dedicated support team and account manager who know your infrastructure and can resolve issues faster. Comprehensive Coverage Full coverage across CDN, Compute, DNS, and Storage, with clear definitions and escalation paths. What the standard Enterprise SLA includes Clear commitments, financially backed. No ambiguity about what you're entitled to. 99.99% uptime guarantee Guaranteed response times, agreed up front 24/7 support for critical issues Defined severity levels and escalation paths Service credits for SLA breaches Monthly uptime reports Dedicated account manager How enterprise support works Every Edge account includes ticket-based support from the console, with issues categorised by product and prioritised by severity. Enterprise customers get a faster path: a dedicated account manager as a named point of contact, 24/7 coverage for critical issues, and guaranteed acknowledgement times for production-down incidents, agreed up front in your SLA. Severity levels and escalation paths are defined up front in the agreement, so there's no negotiation in the middle of an incident — everyone knows what counts as critical and what happens next. If a response target is missed, the SLA's service-credit remedy applies. Custom SLAs available Every enterprise has unique requirements. Alongside the standard agreement, Edge offers fully customised SLAs tailored to your specific needs. Custom response times Define response and resolution targets that align with your operational requirements. Extended coverage Additional coverage for specific services, regions, or use cases beyond the standard SLA. Custom definitions Tailored incident severity definitions and escalation procedures that match your internal processes. Enhanced service credits Customised credit structures for SLA breaches based on business impact. Who the Enterprise SLA is for Mission-critical workloads Production systems where downtime carries a real cost — revenue, reputation, or regulatory — and where a financial commitment to uptime matters. Teams that need guaranteed response When something breaks at 3am, "best effort" isn't good enough. Enterprise customers get 24/7 coverage for critical issues with guaranteed acknowledgement times. Organisations with compliance requirements Monthly uptime reporting and clearly defined severity levels and escalation paths give you the documentation your governance processes expect. The Enterprise SLA is part of Edge's enterprise offering, which combines volume-discounted pay-as-you-go pricing from $499/month with priority support, an account manager, unlimited seats, and annual discounts. See pricing for the full picture, or contact sales to discuss your requirements. Get started with the Enterprise SLA Ready to put a financial commitment behind your infrastructure? Or need a custom SLA tailored to your requirements? Our team is ready to help. Contact Sales View Pricing --- ### Enterprise SLA Now Available URL: https://edge.network/latest/enterprise-sla/ Markdown: https://edge.network/latest/enterprise-sla.md JSON: https://edge.network/json/latest/enterprise-sla.json _99.99% uptime guarantee with dedicated support for enterprise customers._ Back to Latest Product Jan 19, 2025 Enterprise SLA Now Available 99.99% uptime guarantee with dedicated support for enterprise customers. As Edge Network continues to grow and serve increasingly mission-critical workloads, we recognise the importance of providing enterprise-grade guarantees. Today, we're making our Enterprise SLA generally available to all customers on our Enterprise plan. What's Included Our Enterprise SLA provides comprehensive coverage across all Edge services, with clear definitions, guaranteed response times, and financial backing through service credits. 99.99% Uptime Guarantee Our enterprise SLA guarantees 99.99% uptime across all services, backed by service credits if we fall short. Rapid Response Times Priority support with guaranteed response times. Critical issues acknowledged within 15 minutes, 24/7. Dedicated Support Access to a dedicated support team who knows your infrastructure and can resolve issues faster. Comprehensive Coverage Full coverage across CDN, Compute, DNS, and Storage services with clear definitions and escalation paths. Standard Enterprise SLA Includes 99.99% uptime guarantee 15-minute response time for critical issues 1-hour response time for high priority 4-hour response time for medium priority 24/7 support for critical issues Service credits for SLA breaches Monthly uptime reports Dedicated account manager Custom SLAs Available We understand that every enterprise has unique requirements. That's why we also offer fully customised SLAs tailored to your specific needs. Custom SLAs can include: Custom response times — Define response and resolution targets that align with your operational requirements Extended coverage — Additional coverage for specific services, regions, or use cases beyond the standard SLA Custom definitions — Tailored incident severity definitions and escalation procedures that match your internal processes Enhanced service credits — Customised credit structures for SLA breaches based on business impact Get Started with Enterprise SLA Ready to upgrade to Enterprise? Or need a custom SLA tailored to your requirements? Contact our sales team to discuss your needs. Contact Sales View Pricing For more information about our Enterprise SLA or to discuss custom requirements, please contact us . Our team is ready to help you find the right solution for your business. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Environment URL: https://edge.network/environment/ Markdown: https://edge.network/environment.md JSON: https://edge.network/json/environment.json _Cloud infrastructure that's 50% greener. Utilising spare capacity, renewable energy, and smarter resource distribution._ SUSTAINABILITY The Green Cloud Cloud infrastructure that's conscious by design. We've built a fundamentally different approach to cloud computing – one that respects the planet while delivering enterprise-grade performance. Start Your Green Journey 50% Less Energy Used 988 Edge Locations 0 New Data Centers Built 100% Renewable Where Available The cloud has a carbon problem Traditional cloud computing is built on a wasteful model. Hyperscale data centers consume enormous amounts of energy—often running at just 20-30% capacity while burning power around the clock. Every request you make travels hundreds or thousands of miles to reach a distant data center, consuming energy at every hop. Then it travels all the way back. Multiply this by billions of requests per day, and you have a significant environmental footprint. We believe there's a better way. Our Approach Instead of building massive centralised facilities, we leverage existing spare capacity across a distributed network of 988 edge locations. We process data where it's created and consumed—eliminating unnecessary journeys and the energy they require. The result: the same enterprise performance with approximately 50% less energy consumption. How we reduce impact Every design decision we make considers environmental impact. Utilising Spare Capacity Rather than building new data centers, we harness existing unused compute capacity across thousands of locations worldwide. No new construction, no additional hardware manufacturing—just smarter use of what already exists. Shorter Data Journeys Traditional cloud routes your data through distant centralised data centers. Our edge network processes data closer to users, cutting transmission distances by 50% or more—and halving the energy required to move your bits. 50% Less Energy By combining spare capacity utilisation with shorter data paths, we achieve approximately 50% energy savings compared to traditional hyperscale cloud providers. Less energy means less carbon. No Wasteful Infrastructure Hyperscalers build massive facilities that run at a fraction of capacity. Our distributed model means no idle servers burning energy, no empty racks consuming power for cooling. "Edge is the cloud as it should be. Conscious by design, and as clean as possible in operation. We use them for everything we do digitally, and if you care about the environment, you should too." Matt Mellen Founder & Editor, Ecohustler The mathematics of green cloud Traditional cloud computing sends your data on a round trip that can span thousands of miles. Our edge network keeps data local, dramatically reducing the energy consumed in transit. 50% shorter data paths mean 50% less energy for data transmission Utilising existing capacity means zero energy spent building new facilities Distributed architecture eliminates the cooling overhead of massive data centers Traditional vs Edge Traditional Cloud 100% energy baseline Edge Network ~50% energy savings Make the switch to green cloud Same enterprise performance. Half the environmental impact. Start your trial today and see the difference. Start Free Today Explore Our Network Stay Updated Subscribe to our newsletter for the latest news, product updates, and engineering insights. Subscribe --- ### Features URL: https://edge.network/features/ Markdown: https://edge.network/features.md JSON: https://edge.network/json/features.json _Edge Network's cloud platform at a glance: CDN, edge compute VMs, DNS, object storage with zero egress fees, Shield bot protection and Assist AI answers._ PLATFORM Infrastructure built for the edge A complete platform for deploying, scaling, and managing modern applications at the edge of the network. Our Products Six products designed to work together seamlessly. Global content delivery in milliseconds Content Delivery Network Deliver static and dynamic content from 988 edge locations worldwide. Automatic SSL, instant cache purging, and real-time analytics. Get Started Learn More Key Features 988 global edge locations Sub-20ms latency worldwide Automatic SSL/TLS Instant cache purging Real-time analytics DDoS protection included Custom caching rules WebSocket support Virtual machines at the edge Edge Compute Deploy high-performance VMs with dedicated resources, NVMe storage, and up to 10 Gbps network connectivity. Linux and Windows supported. Get Started Learn More Key Features Dedicated vCPU and RAM NVMe SSD storage Up to 10 Gbps connectivity Linux & Windows support Snapshot backups Private networking Load balancing Auto-scaling groups Enterprise-grade DNS infrastructure DNS Authoritative DNS with global anycast, instant propagation, and built-in DNSSEC. Manage millions of queries with sub-10ms resolution. Get Started Learn More Key Features Global anycast network Instant propagation DNSSEC support Geo-routing Health checks & failover API-first management Unlimited records Query analytics Simple storage with zero egress Object Storage Store and serve files globally with a clean, modern API. No egress fees, automatic replication, and integrated CDN delivery. Get Started Learn More Key Features Dead simple API Zero egress fees Global replication Integrated CDN Versioning Lifecycle policies Access control Event notifications Bot protection without puzzles Edge Shield Free, privacy-first bot protection. Every request gets a humanity score, and you decide how to route humans, bots, and AI agents — no CAPTCHAs, no tracking. Get Started Learn More Key Features Free for everyone No puzzles for humans Humanity score per request Invisible & visible widgets Verified AI agent access Offline token verification Privacy-first — no tracking Drop-in Turnstile migration AI answers from your own content Edge Assist One line of code adds instant search and a conversational assistant to any site. Answers are grounded in your content, cited, and cached — 250 a month free. Get Started Learn More Key Features 250 answered questions/month free One-line script embed Instant full-text search Streamed, cited answers Answer caching & pre-warming Human handoff with transcript Question log & conversation replay White-label branding Platform capabilities Built-in features that power your infrastructure. Instant Deployment Deploy resources in seconds with our CLI, API, or dashboard. Real-time Monitoring Monitor performance, usage, and health across all services. Security First Built-in DDoS protection, encryption, and access controls. Detailed Analytics Understand your traffic with comprehensive analytics. 99.99% Uptime Enterprise-grade reliability with SLA guarantees. Zero Egress Fees No charges for data transfer out of our network. Global edge network 988 points of presence across 6 continents, delivering sub-50ms latency worldwide. 580 North America 720 Europe 540 Asia Pacific 180 South America 120 Middle East 66 Africa Pick Your Interface HTTPS, terminal, or AI agent — everything on Edge is scriptable. Jump straight to the reference you need. REST API Every Edge resource over HTTPS with API keys. The same API that powers the console and CLI. API reference CLI A single binary for macOS, Linux, and Windows. Manage VMs, CDN, DNS, storage, and Shield from the terminal. CLI docs Agent API & MCP Self-describing endpoints with scoped tokens, budgets, and dry-run — plus an official MCP server for Cursor, Windsurf, and Claude with one-line setup. Agent docs Authentication Create API keys with optional expiry, manage them programmatically, and pick the right credential per integration. Auth guide Compute API Create VMs, attach SSH keys and firewalls, take snapshots, and run startup scripts — all over HTTPS. Compute reference Storage & S3 S3-compatible object storage with presigned URLs, lifecycle rules, and any S3 SDK you already use. Storage reference Ready to get started? Deploy your first resource in minutes — free to sign up, no card required. Start Free Today View Pricing --- ### Introducing Edge Shield: Free Bot Protection That Never Shows Humans a Puzzle URL: https://edge.network/latest/introducing-edge-shield/ Markdown: https://edge.network/latest/introducing-edge-shield.md JSON: https://edge.network/json/latest/introducing-edge-shield.json _Edge Shield is our free, privacy-first CAPTCHA alternative. A humanity score on every request, cryptographic identification of legitimate AI agents, and zero puzzles for real visitors — live now for every Edge account._ Back to Latest Product July 26, 2026 Introducing Edge Shield: Free Bot Protection That Never Shows Humans a Puzzle Edge Shield is our free, privacy-first CAPTCHA alternative. A humanity score on every request, cryptographic identification of legitimate AI agents, and zero puzzles for real visitors — live now for every Edge account. Today we're launching Edge Shield — free bot protection for any website, built into the Edge platform. It stops automated abuse at the front door without doing the one thing every CAPTCHA does: punishing your real visitors. No puzzles. Ever. Traditional CAPTCHAs make humans prove they're human — squinting at traffic lights, deciphering warped text, clicking fire hydrants. Shield inverts the model. Verification happens invisibly in the background, and every request receives a humanity score from 1 to 100 . Genuine visitors sail through without seeing anything at all; only genuinely suspicious traffic is asked for a single click, and outright automation is stopped cold. Your server sees the score on every verification, so you stay in control of the threshold — treat a checkout differently from a newsletter form, or a login differently from a comment box. Privacy by architecture, not by policy Shield doesn't set cookies, doesn't build a fingerprint database, and doesn't store per-visitor data. There's nothing to disclose in a consent banner because there's nothing collected to consent to. That's not a configuration option — it's how the system is built. Ready for the agentic web A growing share of legitimate traffic isn't a person in a browser — it's software acting on a person's behalf. Shield is the first bot protection designed for that reality. AI agents that cryptographically declare their identity using Web Bot Auth are recognised and verified, and you choose the policy per widget: allow , challenge , or block . Welcome the good automation, stop the bad, and never confuse the two. Integration in five minutes Add two lines to your page: <script src="https://shield.edge.network/api.js" defer></script> <div class="edge-shield" data-sitekey="es_your_sitekey"></div> Then validate the token server-side with a single call to /siteverify . Tokens are single-use, so replayed submissions fail automatically. Three widget modes — managed, non-interactive, and fully invisible — cover everything from contact forms to API-driven flows, and migrating from Cloudflare Turnstile is a find-and-replace. Everything else in the box Analytics — challenge volume, solve rates, humanity scores, and blocked replays for every widget. Shield Examiner — an AI review of your widget's traffic that flags bot pressure, replay abuse, and calibration issues, with specific recommended fixes. Anomaly detection — volume spikes and score collapses are flagged automatically, and escalation tightens until the storm passes. Manage it anywhere — the Edge control panel, the CLI ( edge shield create ), or the Agent API, where your AI agent can add bot protection to a form it's deploying in one call. Free. Actually free. Unlimited widgets, unlimited verifications, no credit card, no premium tier holding the real features hostage. Bot protection shouldn't be a luxury good — and on Edge, it isn't. Create a free account to set up your first widget in minutes, try the live demo , or dive into the documentation to see how it fits your stack. Already running Turnstile? The migration guide has you covered. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Latest News URL: https://edge.network/latest/ Markdown: https://edge.network/latest.md JSON: https://edge.network/json/latest.json _Edge Network news, updates, and announcements. Stay up to date with our latest features and releases._ Latest News & Updates News, announcements, and insights from the Edge team. Recent Posts The latest from our engineering, product, and company teams. Product August 31, 2026 Edge Shield vs Cloudflare Turnstile A founder’s comparison of Edge Shield and Cloudflare Turnstile: same siteverify shape, a 1–100 score, no per-visitor data, and a drop-in migration. Read more Product July 26, 2026 Introducing Edge Shield: Free Bot Protection That Never Shows Humans a Puzzle Edge Shield is our free, privacy-first CAPTCHA alternative. A humanity score on every request, cryptographic identification of legitimate AI agents, and zero puzzles for real visitors — live now for every Edge account. Read more Network Jan 5, 2026 Edge Network Surpasses 2,500 Active Nodes A milestone for decentralized infrastructure as our network continues to grow. Read more Company Dec 28, 2025 Zero Egress: Why We Don't Charge for Bandwidth Our philosophy on transparent pricing and why egress fees are a thing of the past. Read more Network Dec 1, 2025 New Regions: Middle East and Africa Expansion Bringing edge infrastructure to underserved regions. Read more Product Jan 19, 2025 Enterprise SLA Now Available 99.99% uptime guarantee with dedicated support for enterprise customers. Read more Stay Updated Subscribe to our newsletter for the latest news, product updates, and engineering insights. Subscribe --- ### Let Your AI Agent Deploy Your Next Project URL: https://edge.network/ai-agent-deploy/ Markdown: https://edge.network/ai-agent-deploy.md JSON: https://edge.network/json/ai-agent-deploy.json _Give your coding agent an access code. It discovers, deploys, configures DNS + CDN + SSL, and reports back. All from your editor. Free to start. Zero egress._ Easter Weekend Special Let your AI agent deploy your next project this weekend. Give your coding agent one access code. It discovers what it can do, creates storage, configures CDN + DNS + SSL, and reports back with the live URL — all from your editor. Zero egress. No enterprise bloat. Create Agent Access Code — Start Free Read the Agent API Docs One-line MCP setup for Cursor, Claude, and Windsurf — or plain HTTP for everything else • Free to sign up, no card required • Cancel anytime AI Agent Session User: "Deploy my React app to portfolio.test.network" # Agent discovers capabilities GET /agent → 5 products, $47 budget remaining # Agent deploys POST /agent/storage/buckets → Created POST /agent/cdn/deployments → Deployed POST /agent/dns/zones/.../records → CNAME added "Your site is live at https://portfolio.test.network with CDN, SSL, and DNS configured. ~$2.80/month." Deployment shouldn't kill your flow. Without Edge 0:00 — App built in your AI editor. Time to deploy. 0:05 — Leave editor. Open hosting dashboard. 0:15 — Create project, upload files, configure build. 0:25 — Switch to DNS provider. Add CNAME. Wait. 0:40 — SSL broken. Debug certificates. 0:55 — Finally live… but you've lost all context. What were you even building? With Edge Agent API 0:00 — App built. Tell your agent: "Deploy this to my-project.test.network" 0:03 — Agent connects, discovers capabilities. 0:08 — Storage created, files uploaded, CDN configured, DNS + SSL set up. 0:15 — "Your site is live at https://my-project.test.network with CDN and automatic SSL. ~$2.80/month." 0:16 — You keep coding. Flow unbroken. 45 minutes of context-switching → 15 seconds . Never leave your editor. Create Agent Access Code From access code to live app in five steps. No SDKs, no plugins, no CLI required. Just an access code and a URL. 1 Create an Agent Access Code In your Edge console, scope it to the products you want (Compute, CDN, Storage, DNS) and set a budget cap. Takes 30 seconds. 2 Give it to your agent Add the one-line MCP config to Cursor, Windsurf, or Claude Desktop — or paste the code + https://edge.network/agent into any AI coding tool. 3 Agent discovers capabilities One API call — it learns available resources, limits, and existing deployments. No docs, no manual config. GET /agent → { "products": ["compute", "cdn", "dns", "storage"], "budget_remaining": "$47.00" } 4 Agent deploys your app It creates storage, uploads files, configures CDN, adds DNS records, enables SSL, and reports back with the live URL. 5 Agent monitors and reports Ask "How's my site doing?" — it checks health, tracks costs, and suggests optimisations. Infrastructure becomes a conversation. Ready to let your agent build? Built for how agents actually think. Not a bolted-on API. Every response is designed for LLM consumption. Discovery-First API Your agent calls one endpoint and learns everything: available products, current limits, budget, and existing resources. No crawling docs. Budget-Aware by Default Every response includes cost context. Set soft or hard monthly caps so your agent never surprises you with a bill. You Stay in Full Control Scoped permissions per agent. Soft and hard budget caps. Full audit trail. Instant revocation. Your agent works for you, not the other way around. Human-Readable Responses Every API response includes a tell_user field — a plain English summary your agent can relay directly to you. Project-based resources Errors as guidance Zero egress fees Automatic SSL Start free. Pay per resource. No bloat. Signing up is free with no card. Compute is billed hourly from a prepaid balance — most developers run their first real deploy for under $3. You control the budget cap from day one. $0 to start Free DNS + free CDN & Storage tiers • prepaid compute VM, CDN, DNS & Storage access Full Agent API + CLI access Zero egress fees Budget caps & scoped permissions Real support from real humans Start Free Cancel anytime. No lock-in. Common questions from developers What AI coding tools does it work with? All of them. Cursor, Windsurf, Claude Desktop, and Continue connect with a one-line MCP config ( npx @edge-network/mcp ), there are ready-made LangChain, LlamaIndex, and CrewAI wrappers, and anything else that speaks HTTP can use the REST API directly — no SDK required. Is it really free to start? Yes — signing up needs no card. DNS is free, CDN and Storage have free tiers, and compute is billed hourly from a prepaid balance you control. Zero egress fees, no hidden charges, no bandwidth penalties. How safe is giving my agent an access code? Fully scoped permissions, soft and hard budget caps, complete audit trail, and instant revocation from the console. You stay in control at all times. Do I need a custom domain? No. Get an instant test.network subdomain ($1/month), or bring your own domain. Your agent can configure either. What if my agent makes a mistake? Budget caps prevent overspend. Clear error messages guide the agent to fix issues. And you can revoke access or delete resources instantly from the console. Ready to let your AI agent ship this weekend? Create an access code, paste it into your editor, and tell your agent what to build. It handles the rest. Create Agent Access Code — Start Free Free to start • Zero egress • Cancel anytime --- ### Network URL: https://edge.network/network/ Markdown: https://edge.network/network.md JSON: https://edge.network/json/network.json _Global edge network with 988 PoPs, 10+ Tbps capacity, and sub-50ms latency worldwide. Built for performance and reliability._ Network Global Edge Network 988 points of presence across 130+ countries. Built for performance at scale, with direct peering to major carriers and ISPs worldwide. 988 Global PoPs 10+ Tbps Network Capacity <50ms Global Latency 99.99% Uptime SLA Network Architecture A powerful combination of strategically located PoPs and edge servers deployed directly within ISP networks. Super PoPs Strategically placed at major Internet Exchange Points with direct peering to Tier 1 carriers and regional ISPs. High-capacity nodes handling the bulk of traffic routing. Edge PoPs Distributed cache servers deployed within ISP networks and close to end users. Ensures low latency delivery even in hard-to-reach destinations. "Our network is built with end-users in mind. It's a powerful mixture of strategically located PoPs, cache servers deployed directly inside ISP networks, and thousands of community-contributed edge nodes reaching places traditional clouds simply don't. Combined with real-time latency-based routing and direct access to thousands of ISPs, it delivers the ultimate customer experience." Will Lebens COO, Edge Routing & Connectivity The perfect mix of Tier 1 transit providers and private peerings with local networks, combined with latency-based routing ensures packets are always delivered via the optimal path. Latency-Based Routing Real-time monitoring of network conditions enables automatic routing to the lowest latency endpoint. We analyse millions of routes per second to optimise every request. Direct Carrier Access Direct connections to major carriers and ISPs worldwide means fewer hops, lower latency, and more reliable delivery to end users. 12+ Tier 1 Transit Providers 200+ Private Peerings 2,000+ ISP Connections 300K+ Routes Monitored PERFORMANCE One of the Fastest Clouds on Earth Powered by PerfOps Independent monitoring PerfOps provides enterprise-grade RUM benchmarking for DNS, CDN, and cloud providers. Their methodology is trusted by thousands of companies worldwide. Learn more about PerfOps Loading performance data... See full performance data Global Coverage Points of presence across every major region, with deep coverage in emerging markets. North America 580 PoPs New York Los Angeles Chicago Toronto Miami Dallas Seattle Europe 720 PoPs London Frankfurt Amsterdam Paris Stockholm Madrid Milan Asia Pacific 540 PoPs Singapore Tokyo Sydney Hong Kong Seoul Mumbai Jakarta South America 180 PoPs São Paulo Buenos Aires Santiago Bogotá Middle East 120 PoPs Dubai Tel Aviv Riyadh Africa 66 PoPs Johannesburg Cape Town Lagos Nairobi Why Edge? Resilient by Design Distributed architecture with no single point of failure. If one PoP goes down, traffic automatically reroutes. Optimised for Speed Content and compute served from the nearest edge location. Sub-50ms latency to 95% of the world's internet users. True Global Reach Coverage in regions underserved by traditional cloud. Reach users in emerging markets with the same performance. Ready to deliver at the edge? Create a free account and experience global performance. Get Started Talk to Sales --- ### New Regions: Middle East and Africa Expansion URL: https://edge.network/latest/new-regions-middle-east-and-africa/ Markdown: https://edge.network/latest/new-regions-middle-east-and-africa.md JSON: https://edge.network/json/latest/new-regions-middle-east-and-africa.json _Bringing edge infrastructure to underserved regions._ Back to Latest Network Dec 1, 2025 New Regions: Middle East and Africa Expansion Bringing edge infrastructure to underserved regions. 186 New PoPs 10 New Cities 2 New Regions <20ms Local Latency Today we're excited to announce a major expansion of Edge CDN into the Middle East and Africa. This expansion adds 186 new CDN points of presence across 10 cities, bringing low-latency content delivery to regions that have historically been underserved by traditional CDN providers. Why This Matters For too long, users in the Middle East and Africa have experienced slow content delivery from global CDN services. Static assets, images, and video were served from distant edge locations in Europe or Asia, adding hundreds of milliseconds of latency. For media-rich websites, video streaming, and e-commerce, this meant slower load times and frustrated users. With this expansion, we're changing that. Local CDN presence means your content is cached and served from within the region, dramatically reducing latency and improving the experience for hundreds of millions of users. New Regions Middle East 120 PoPs Strategic CDN presence across the Gulf states and wider Middle East, delivering content at sub-20ms latency to one of the world's fastest-growing digital economies. Dubai Tel Aviv Riyadh Doha Kuwait City Africa 66 PoPs CDN edge locations across the African continent, serving over 1.4 billion people with low-latency content delivery. Johannesburg Cape Town Lagos Nairobi Cairo What This Means For You Faster Content Delivery Users in these regions now experience sub-20ms latency instead of 150ms+ when content was served from Europe. Local Caching Content is cached at edge locations within the region, reducing origin fetches and improving cache hit rates. Better User Experience Faster page loads, smoother video streaming, and snappier web applications for millions of users. Zero Configuration Traffic is automatically routed to the nearest PoP. No changes needed — your content is already being served locally. Already Live The new Middle East and Africa CDN regions are already active for all Edge CDN customers. No action required on your part: Traffic is automatically routed to the nearest PoP — no configuration needed Your existing CDN zones immediately benefit from the new locations Cache warming happens automatically as users request content Zero egress fees apply to these regions, same as everywhere else Looking Ahead This CDN expansion is part of our commitment to building a truly global content delivery network. We believe everyone deserves fast access to content, regardless of where they are. Over the coming months, we'll continue to add more edge locations in these regions based on demand. If you have specific requirements for locations not yet covered, we'd love to hear from you. Our CDN expansion roadmap is driven by customer needs. Ready to Go Global? Start delivering content to the Middle East and Africa with sub-20ms latency today. All regions are available to every account at no extra cost. Open Dashboard View Full Network Have questions about our CDN coverage or need help optimising delivery? Contact our team — we're here to help you make the most of our global CDN. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. --- ### Privacy Policy URL: https://edge.network/privacy/ Markdown: https://edge.network/privacy.md JSON: https://edge.network/json/privacy.json _Edge Network privacy policy. How we collect, use, and protect your data. GDPR compliant._ Legal Privacy Policy Last updated: July 2026 1. Introduction Edge Network Technologies Ltd ("Edge", "we", "us", or "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our services, website, and applications. 2. Information We Collect 2.1 Information You Provide We collect information you provide directly to us, including: Account information (name, email address, company name) Billing information (payment method, billing address) Communications (support tickets, emails, feedback) Profile information (preferences, settings) 2.2 Information We Collect Automatically When you use our services, we automatically collect: Usage data (features used, actions taken) Log data (IP address, browser type, access times) Device information (hardware model, operating system) Performance data (latency, errors, resource usage) 3. Edge Shield on Third-Party Websites Edge Shield is our bot-protection service. When a website operator embeds Shield on their site, we process a limited set of technical data about that site's visitors on the operator's behalf, acting as a data processor, for the sole purpose of distinguishing human visitors from automated traffic. If you encountered Shield on a website that isn't ours, the operator of that website is responsible for telling you about its use in their own privacy notice. 3.1 What Shield Processes IP address — used for short-window abuse-rate checks and to bind a verification token to the connection that earned it Browser and request characteristics (user agent, request headers, TLS connection properties, network operator) The hostname of the page embedding the widget Summarised interaction statistics, such as counts and variability of pointer movements and key presses — never the content of what you type 3.2 What Shield Does Not Do No cookies and no persistent identifiers are set No tracking across websites, and no behavioural profiles are built Raw mouse movements and keystrokes never leave your browser — only summary statistics are sent Scores are computed fresh on each page load and discarded; nothing follows you to your next visit This data is held only as long as the verification itself requires: tokens expire within minutes of being issued, and the short-lived operational records used for abuse-rate and replay protection are purged automatically. The legal basis for this processing is legitimate interest in preventing fraud, spam, and abuse. A plain-language explanation for visitors is published at shield.edge.network/what-is-this . Website operators requiring a data processing addendum can contact privacy@edge.network . 4. How We Use Your Information We use the information we collect to: Provide, maintain, and improve our services Process transactions and send related information Send technical notices, updates, and support messages Respond to your comments and questions Monitor and analyse trends, usage, and activities Detect, investigate, and prevent fraudulent transactions 5. Information Sharing We do not sell your personal information. We may share your information only in the following circumstances: With your consent or at your direction With service providers who assist in our operations To comply with legal obligations To protect rights, privacy, safety, or property In connection with a merger, acquisition, or sale of assets 6. Data Retention We retain your information for as long as your account is active or as needed to provide you services. We will retain and use your information as necessary to comply with legal obligations, resolve disputes, and enforce our agreements. Edge Shield verification data is retained on much shorter cycles, as described in Section 3. 7. Security We implement appropriate technical and organisational measures to protect your personal information against unauthorised access, alteration, disclosure, or destruction. For more details, see our Security page . 8. Your Rights Depending on your location, you may have the right to: Access the personal information we hold about you Request correction of inaccurate information Request deletion of your information Object to or restrict processing Data portability Withdraw consent at any time 9. Cookies Our marketing website uses privacy-friendly, cookieless analytics, and Edge Shield sets no cookies anywhere it runs. Cookies are used only where they are functionally necessary — for example, to keep you signed in to your account in the console. We do not use cookies for advertising or cross-site tracking. You can control cookies through your browser settings. 10. International Transfers Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place to protect your information in accordance with this Privacy Policy. 11. Changes to This Policy We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. 12. Contact Us If you have questions about this Privacy Policy or our privacy practices, please contact us: privacy@edge.network --- ### Referral Redirect URL: https://edge.network/r Markdown: https://edge.network/r.md JSON: https://edge.network/json/r.json Referral Redirect | Edge Redirecting... --- ### Releases URL: https://edge.network/releases/ Markdown: https://edge.network/releases.md JSON: https://edge.network/json/releases.json _Product releases, updates, and changelog for Edge Network services including CDN, Compute, DNS, Storage, Shield, and Assist._ Releases Changelog Track new features, improvements, and updates across all Edge products. v2.18.0 Aug 8, 2026 Product Assist Edge Assist: AI Answers for Any Website Edge Assist answers your visitors' questions from your own content — nothing else. Point it at a content index, drop one script tag on your pages, and visitors get streamed, cited answers plus instant search under a single ⌘K overlay. Sitekeys are origin-enforced, repeat questions are served from cache for free, and the free tier includes 250 answered questions per site per month with published overage pricing after that. One-line embed adds instant search and a chat assistant to any site, app, wiki, or intranet Answers are grounded in your own indexed content and streamed with citations — no hallucinated features or pricing Overrides: pin authoritative facts and curate exact Q&A answers that always take precedence Assist Examiner: AI review of your content coverage — unanswered themes, dead pages, and suggested fixes Human handoff turns any conversation into a support ticket with the transcript attached Fully agent-ready: AI agents can provision, index, and monitor Assist sites through the Agent API v2.17.0 Aug 2, 2026 Feature CDN Password-Protected CDN Domains Ship a dev build to a Storage bucket, put it on a test domain, and share the URL without sharing it with the whole internet. Password protection challenges visitors with the browser's native credential prompt before anything is served, including cached content. Verified credentials are cached at the edge so authenticated traffic runs at full CDN speed, while failed attempts are rate-limited by bcrypt's hash cost. Protect any CDN domain with a username and password (HTTP Basic Auth) Enforced at the edge, ahead of the cache — protected content is never served without credentials Passwords stored as bcrypt hashes; edge nodes never see plaintext SSL issuance and renewal keep working on protected domains One click from the Domains tab: lock icon → set credentials → save v2.16.0 Aug 1, 2026 Feature CDN Storage Platform Self-Serve CDN & Storage Overage CDN and Storage free tiers no longer end at "talk to us". Set a monthly usage budget on the billing page and keep serving past 500k requests and 5 GB at published pay-as-you-go rates, billed from the same prepaid balance as compute. No budget set means nothing changes: hard caps stay on and exceeding a free tier still pauses the resource rather than charging you. Published overage rates: $0.25 per million CDN requests, $0.015/GB-month for storage Opt in with a monthly usage budget from the billing page — free tiers stay hard-capped by default Overage bills hourly from your prepaid balance with itemised ledger entries When the budget is spent, free-tier limits re-apply automatically until next month Warnings at 80% and 100% of budget — a surprise bill remains structurally impossible v2.15.0 Aug 1, 2026 Feature Platform Cost Advisor The Cost Advisor reviews everything you run on Edge and tells you where you're overpaying — "this VM averages 3% CPU, downsize and save $40/month" — with every dollar figure computed from your actual usage and our published rates. It recommends more capacity only where the data shows real pressure, and if your account is already efficient, it says so. Free to run, as often as you like, from Billing → Cost Advisor. AI analysis of account-wide usage and spend — VMs, storage, CDN, DNS, and add-ons VM right-sizing from 7 days of CPU, memory, and disk metrics, with per-VM utilisation charts Prioritised recommendations with real dollar amounts: savings, upgrades, and protection gaps Spend breakdown and efficiency score (0–100) on a new Cost Advisor tab under Billing Honest by design: it flags waste and tells you when you're under-provisioned too v2.14.0 Jul 31, 2026 Feature Platform REST API Documentation The full REST API — the same one that powers the console and CLI — is now comprehensively documented. Every endpoint, request field, and response shape, plus authentication, errors, and rate limits, at edge.network/docs/api. Complete REST API reference at /docs/api covering Compute, CDN, DNS, Storage, and Shield Authentication guide: API keys with optional expiry, managed via console or API Error and rate-limit reference with stable machine-readable codes Indexed in llms.txt so AI coding agents can navigate the API without guesswork v2.13.0 Jul 31, 2026 Feature Compute CLI Startup Scripts in the CLI and Agent API Startup scripts are no longer console-only. The full script library — Edge-maintained and custom — is now available from the CLI and the Agent API, with parameter substitution handled for you. New edge compute scripts commands: list, get, create, update, and delete scripts from the terminal Provision VMs with --script and --script-param flags on edge compute create Agent API: reference scripts by ID with parameters on VM creation and app deploys New GET /agent/compute/scripts endpoint so agents can discover the script library v2.12.0 Jul 30, 2026 Feature Shield Shield: Built for Sceptical Engineers A wave of Shield features aimed at the details engineers check before trusting a verification product: trial it without blocking anything, test it deterministically in CI, and verify tokens entirely inside your own stack. Shadow mode: score live traffic in report-only mode before switching enforcement on Test sitekeys for CI: deterministic always-pass, always-fail, and always-escalate keys Offline verification: Ed25519-signed tokens with a public JWKS endpoint — verify with zero network calls Automatic signing-key rotation every 60 days, with a 24-hour overlap for seamless verification The tarpit: repeat offenders face exponentially harder proof-of-work Bot weather report: live view of global bot traffic conditions v2.11.0 Jul 21, 2026 Product Shield Edge Shield: Free Bot Protection Edge Shield is a CAPTCHA alternative that stops bots, spam, and fake signups without ever showing a real user a traffic light. Privacy-first by design: raw input never leaves the visitor's device, and Shield keeps no profile of anyone. Humanity score (1–100) computed from behavioural signals — humans never see a puzzle Managed, non-interactive, and invisible widget modes with a two-line embed Server-side validation compatible with the Turnstile/reCAPTCHA siteverify flow for drop-in migration Verified agents: cryptographically identify good bots and decide how to route them Shield Examiner: AI analysis of your widget configuration and traffic Free forever with unlimited verifications — no card required v2.10.0 Mar 21, 2026 Feature DNS DNS Examiner DNS Examiner analyses your zone configuration and performs live DNS lookups, then uses AI to identify misconfigurations across email (SPF, DKIM, DMARC), security (CAA), nameserver delegation, web accessibility, and best practices. Each issue includes a specific, actionable recommendation. No other DNS provider offers built-in AI analysis. AI-powered zone analysis checks email deliverability, security, nameservers, and best practices Live DNS lookups compared against configured records to catch propagation issues Health score (0–100) with issues ranked by severity and specific fix recommendations Results are persisted — return to the Examiner tab to see your last analysis Available in the console, CLI (edge dns examine), and agent API v2.9.0 Mar 3, 2026 Feature Compute Startup Scripts for Compute Automate your VM setup with startup scripts. Choose from a curated library of pre-built scripts or write your own custom scripts with configurable parameters. Scripts execute on first boot, and you can monitor progress and output directly from the console. Pre-built script library: Docker, Node.js, LAMP, LEMP, WordPress, PostgreSQL, Redis, Python, Hardened SSH Custom scripts with parameterised inputs for reusable p... --- ### Roadmap URL: https://edge.network/roadmap/ Markdown: https://edge.network/roadmap.md JSON: https://edge.network/json/roadmap.json _See what's coming next for Edge Network. Our product roadmap for CDN, Compute, DNS, Storage, Shield, and platform features._ Roadmap What's Next Our product roadmap is driven by customer feedback and our vision for the future of edge infrastructure. Status: Completed In Progress Planned Exploring Q1 2026 Shipped DNS Examiner Completed AI-powered zone analysis checking email deliverability, security, nameservers, and best practices. Available in console, CLI, and agent API. DNS AI DNS Backup Service Completed Automated daily backups of DNS zones with download, one-click restore, and per-zone monthly billing. DNS Agent API Completed Agentic API for AI-driven infrastructure management. Deploy static sites, provision VMs, manage DNS — all via a self-describing API with natural language summaries. Platform Edge CLI Completed Command-line tool for managing all Edge resources. Compute, DNS, Storage, and CDN operations from the terminal. Platform Speed Test Completed Developer-grade speed test at speed.edge.network. Parallel-stream throughput, latency under load, bufferbloat grading, live charts, and JSON export. Platform Q2 2026 Shipped Edge Shield Completed Free bot protection with a 1–100 humanity score. Invisible proof-of-work verification, privacy-first by construction — no cookies, no tracking, no puzzles for real visitors. Shield Verified Agents Completed Cryptographic agent identification via Web Bot Auth, the IETF standard backed by OpenAI, Google, and Amazon. Welcome automation that declares itself — reserve the aggression for automation that won't. Shield Shield Examiner Completed AI-powered analysis of your Shield traffic — solve rates, score distributions, and anomaly detection with plain-English recommendations. Shield AI DDoS Protection + WAF Completed DDoS mitigation and web application firewall at the CDN edge, protecting your origin at no extra cost. CDN Q3 2026 Current Quarter Shield Everywhere Completed Shield in the Edge CLI (edge shield) and the Agent API, so AI agents can add bot protection to the forms they deploy. Plus behavioural scoring that refines the humanity score as visitors interact. Shield Platform Edge Pulse — Synthetic Monitoring In Progress Global uptime and performance monitoring from residential locations. HTTP, API, SSL, and DNS checks from 2,000+ community edge hosts worldwide. The probe network is live; dashboards, alerting, and status pages are in build. Progress 40% Pulse Edge Accreditation Planned A structured programme through every Edge product, ending in an online exam. Pass to earn a verifiable certificate, an upweighted referral bonus, and a listing on the Approved Partners directory. Platform Edge Sparks Exploring Stateful sandboxes for AI agents and untrusted code — hardware-isolated microVMs with instant checkpoint & restore, scale-to-zero economics, and preview URLs on the Edge network. Compute Q4 2026 & Beyond Managed Databases Planned Hosted PostgreSQL, MySQL, and Redis with automated backups, failover, and point-in-time recovery. Compute Storage AI Gateway Planned API gateway for AI applications — model routing, semantic caching, rate limiting, cost management, and observability at the edge. AI CDN AI Platform Features Planned CDN Optimiser, Firewall Advisor, Setup Script Generator, Incident Explainer, Cost Advisor, and Migration Assistant — all AI-powered, built into the console alongside the DNS and Shield Examiners. AI Platform Domain Registration Planned Register domains directly from Edge. Automatic nameserver configuration, WHOIS privacy included, seamless DNS setup. DNS Video Platform Exploring Video hosting, transcoding, and adaptive streaming. Distributed transcoding via edge hosts. Zero egress delivery. CDN Storage Compute Marketplace Exploring Third-party applications, templates, and integrations. One-click deployments for WordPress, Ghost, Next.js, and more. Platform Have a Feature Request? Our roadmap is shaped by customer feedback. Tell us what features would help your business. Submit Feedback Talk to Sales Popular Requests Managed PostgreSQL databases Domain registration built into DNS GPU compute for AI/ML workloads Note: This roadmap represents our current plans and is subject to change. Timelines and features may be adjusted based on customer feedback, technical requirements, and market conditions. Items in "Exploring" status are being evaluated but not yet committed. --- ### Security URL: https://edge.network/security/ Markdown: https://edge.network/security.md JSON: https://edge.network/json/security.json _Enterprise-grade security at every layer. DDoS protection, encryption, access controls, and compliance certifications._ Security Security at Edge We take the security of your data seriously. Our infrastructure is designed with security as a foundational principle, not an afterthought. Security Features Enterprise-grade security built into every layer of our platform. Encryption in Transit All data transmitted to and from our services is encrypted using TLS 1.3. We enforce HTTPS across all endpoints. Encryption at Rest Customer data stored on our infrastructure is encrypted using AES-256 encryption with regularly rotated keys. DDoS Protection Built-in DDoS mitigation across our global network absorbs and filters malicious traffic before it reaches your infrastructure. Access Controls Role-based access control (RBAC), multi-factor authentication (MFA), and API key management for granular permissions. Team Security All Edge employees undergo background checks and security training. Access to production systems is strictly controlled and audited. Incident Response 24/7 security monitoring with defined incident response procedures. We notify affected customers promptly of any security events. Compliance We are committed to meeting industry standards and regulatory requirements. Our compliance program is continuously evolving as we grow. GDPR Compliant with EU General Data Protection Regulation ISO 27001 Information security management (in progress) SOC 2 Type II Security and availability controls (in progress) Security Practices Regular Audits We conduct regular security audits and penetration testing by independent third parties to identify and address vulnerabilities. Continuous Monitoring Our security team continuously monitors for threats, vulnerabilities, and anomalous activity across our infrastructure. Responsible Disclosure We welcome security researchers to responsibly disclose vulnerabilities. If you discover a security issue, please report it to us privately so we can address it before public disclosure. Report a Vulnerability Email security issues to our dedicated security team. Please include detailed steps to reproduce the vulnerability. security@edge.network Questions about security? If you have specific security questions or requirements, our team is happy to help. Contact Us Email Security Team --- ### State of the Cloud 2026: Agents vs DevOps URL: https://edge.network/state-of-the-cloud-2026/ Markdown: https://edge.network/state-of-the-cloud-2026.md JSON: https://edge.network/json/state-of-the-cloud-2026.json _Free report: How agentic AI is replacing traditional DevOps, unlocking 20%+ cost savings, and democratising cloud development. Download now._ Free Report State of the Cloud in 2026 Agents vs. DevOps — The Rise of Agentic Automation The cloud landscape is undergoing a profound transformation. AI agents are moving beyond chatbots to autonomous systems that deploy infrastructure, optimise pipelines, and resolve issues — with minimal human intervention. What you'll learn The rise of agentic tooling How orchestration layers like LangGraph are enabling autonomous deployment and management of cloud infrastructure. 20%+ cost savings Concrete strategies for reducing cloud spend through AI-optimised resource allocation and zero-egress platforms. The future of DevOps Why DevOps isn't dying — it's evolving from hands-on management to strategic oversight and platform engineering. The era of vibe coders How natural language interfaces are opening cloud development to entrepreneurs, creators, and non-technical experts. 50% greener infrastructure Why intelligent allocation and decentralised edge architecture is making cloud computing more sustainable. 40% of enterprise apps will use AI agents by end of 2026 100% of enterprises planning agent expansions 20%+ reduction in cloud spend with agentic ops Download the free report Enter your email to get instant access to the full 5-page PDF. Email address Name (optional) Download Report Your report is ready Your download should start automatically. If not, click below. Download PDF Use code AGENT2026 for 20% off your first year. We respect your privacy. Unsubscribe at any time. JD WL AD Written by the Edge Network team — building the agentic cloud. “The cloud in 2026 is agentic, efficient, and inclusive. Delegate to agents, and elevate your vision.” Explore Agentic Development View Pricing Inside the report A 5-page executive briefing covering the key shifts reshaping cloud infrastructure. Executive Summary The shift from traditional DevOps to agentic tooling and what it means for your organisation. The Rise of Agentic Tooling From reactive automation to proactive intelligence — real-world examples from Genentech and Amazon. Streamlining Operations How agents eradicate setup and maintenance overhead with self-healing infrastructure and dynamic allocation. The Evolution of DevOps Platform engineering, agent meshes, and why 2026 is the last cheap-learning year for AI in operations. Unlocking Cost Savings FinOps integration, predictive spend management, and 50% greener operations. Democratising Development The vibe coder era and how agent access codes are making cloud accessible to everyone. --- ### Support URL: https://edge.network/support/ Markdown: https://edge.network/support.md JSON: https://edge.network/json/support.json _Get help from Edge Network. Submit tickets, browse documentation, and access community resources._ Support How can we help? Get support, browse documentation, or learn with our tutorials. Get Help Choose the best way to find answers or reach our team. Chat with us Get instant answers from our AI assistant or connect with our team. Chat now Submit a Ticket Create a support ticket and get help from our team. Open Ticket Documentation Browse our comprehensive documentation and guides. View Docs Academy Learn with tutorials, videos, and best practices. Start Learning All Systems Operational View Status Page → Frequently Asked Questions Quick answers to common questions about Edge. How do I get started with Edge? Sign up for a free account — no card required — verify your email, and deploy your first resource in minutes. What payment methods do you accept? We accept all major credit cards, PayPal, and cryptocurrency payments. Do you offer refunds? Unused prepaid balance top-ups are refundable — contact support and we'll sort it out. What is your uptime SLA? We offer 99.9% uptime for standard plans and 99.99% for enterprise customers. How do egress fees work? They don't. We don't charge for bandwidth or data transfer. Ever. Response Times & Hours Support availability varies by plan tier. Response Times Hobbyist / Dev Community + automated Startup 24-48 hours (automated) Scaleup 4-8 hours (ticketed) Business 1-2 hours (priority) Enterprise <1 hour (dedicated) Support Hours Standard Mon-Fri, 9am-6pm GMT Business Mon-Fri, 8am-10pm GMT Enterprise 24/7/365 --- ### System Status URL: https://edge.network/status/ Markdown: https://edge.network/status.md JSON: https://edge.network/json/status.json _Real-time status of Edge Network services. View current operational status, uptime statistics, and incident history._ Status System Status Real-time status of all Edge Network services and infrastructure. All Systems Operational All services are running normally Last updated: --:--:-- Services Current status of individual Edge services. CDN Global content delivery network Compute Virtual machines DNS Domain name resolution Storage Object storage Shield Bot protection & verification Assist AI answers & site assistant API REST API endpoints Console Web console Regions Status by geographic region. North America Europe Asia Pacific South America Middle East Africa Uptime Historical uptime statistics. 100% Last 24 hours 100% Last 7 days 99.99% Last 30 days 99.99% Last 90 days Scheduled Maintenance Upcoming planned maintenance windows. Recent Incidents Past incidents and their resolution timelines. Loading... Stay Informed Subscribe to receive status updates and incident notifications. Subscribe --- ### Terms of Service URL: https://edge.network/terms/ Markdown: https://edge.network/terms.md JSON: https://edge.network/json/terms.json _Edge Network terms of service covering acceptable use, prepaid usage-based billing, the service level agreement, data and privacy, liability and termination._ Legal Terms of Service Version 2.1 — effective 27 July 2026 Version 2.1 adds provisions covering Edge Shield, our bot-protection service. Version 2.0 reflects our prepaid, usage-based billing model. Accounts remaining on a legacy subscription plan continue to be billed under their existing plan terms; all other provisions of these Terms apply to all accounts. For a copy of a previous version, contact legal@edge.network . 1. Acceptance of Terms By accessing or using Edge Network Technologies Ltd's ("Edge", "we", "us", or "our") services, website, and applications (collectively, the "Services"), you agree to be bound by these Terms of Service ("Terms"). If you do not agree to these Terms, do not use the Services. 2. Description of Services Edge provides cloud infrastructure services including but not limited to content delivery network (CDN), compute, DNS, object storage, and security services such as Edge Shield bot protection. The specific features and functionality available to you depend on your account type, applicable free tier limits, and the resources you enable and fund. 3. Account Registration To use certain features of the Services, you must register for an account. You agree to: Provide accurate, current, and complete information Maintain and update your information as needed Keep your password secure and confidential Accept responsibility for all activities under your account Notify us immediately of any unauthorised access 4. Acceptable Use You agree not to use the Services to: ✕ Violate any applicable laws or regulations ✕ Infringe intellectual property rights of others ✕ Transmit malware, viruses, or harmful code ✕ Engage in spam, phishing, or fraudulent activities ✕ Interfere with or disrupt the Services or servers ✕ Attempt to gain unauthorised access to any systems ✕ Attempt to bypass, probe, reverse-engineer, or manipulate Edge Shield verification or scoring, or submit traffic designed to distort its detection models ✕ Host or distribute illegal content ✕ Resell or redistribute the Services without authorisation 5. Fair Use Policy Edge Network services include generous allowances, including free tiers, unlimited bandwidth on qualifying services, and high-volume request allowances. These inclusions are designed for normal business and development use consistent with the intended purpose of each service. 5.1 What constitutes fair use Fair use means usage that is consistent with the typical patterns expected for services of this kind. Most customers will never need to think about this policy. It exists solely to protect the quality of service for all customers on the platform. 5.2 Examples of usage that may exceed fair use Bandwidth or request volumes that significantly and persistently exceed 10x the median usage across comparable accounts Using CDN or storage services primarily for content distribution unrelated to your own application (e.g. operating a public file hosting or torrent service) Cryptocurrency mining, password cracking, or other computationally exploitative workloads on virtual machines Generating excessive DNS query volume through misconfigured resolvers or automated abuse Any usage pattern that materially degrades the performance or availability of services for other customers 5.3 How we respond If we identify usage that may exceed fair use, we will take the following steps in order where possible: 1. Notify you — we will contact you to discuss the usage and explore options, such as moving to metered enterprise rates or optimising your configuration. 2. Throttle or restrict — if the usage continues to impact other customers, we may temporarily limit the affected service to sustainable levels. 3. Suspend — in cases of deliberate abuse or where service quality for other customers is at immediate risk, we may suspend the account without prior notice. 5.4 Metered and enterprise usage Usage billed at metered rates — including prepaid per-resource compute and enterprise pay-as-you-go agreements — is not subject to fair use limitations on those metered resources. Metered usage is billed at the applicable rates without volume restrictions. Fair use provisions relating to prohibited activities (Section 4) still apply. 6. Payment Terms Certain Services require payment. Paid usage is funded by a prepaid account balance, saved payment method, or (for grandfathered accounts) a legacy subscription. By using paid Services, you agree to pay all applicable fees. Fees and unused balance top-ups are non-refundable except as expressly stated in these Terms or required by law. Prepaid balance top-ups are charged at the time of purchase Usage is deducted from your prepaid balance as it accrues (typically hourly) Fixed-price add-ons are billed to your saved payment method or prepaid balance We may change pricing with 30 days' notice Services may be stopped or restricted when your balance is exhausted Legacy subscription fees (grandfathered plans) are billed in advance 7. Service Level Agreement Our Service Level Agreement (SLA) provides uptime guarantees and service credits for qualifying downtime. The SLA is incorporated into these Terms by reference. SLA commitments apply to enterprise agreements and are detailed in the applicable agreement; current service status is published at edge.network/status . 8. Intellectual Property The Services and all associated content, features, and functionality are owned by Edge and are protected by copyright, trademark, and other intellectual property laws. You retain ownership of content you upload to the Services. 9. Data and Privacy Our Privacy Policy describes how we collect, use, and protect your information. By using the Services, you consent to our data practices as described in the Privacy Policy. 9.1 Edge Shield and Your End Users When you embed Edge Shield on your website or application, Edge processes limited technical data about your visitors on your behalf, as described in Section 3 of our Privacy Policy . You are the controller of that data and Edge acts as your processor. You are responsible for ensuring you have a lawful basis for this processing and for disclosing your use of Edge Shield to your visitors in your own privacy notice — for example: "This site is protected by Edge Shield, which processes limited technical data to distinguish humans from bots. See shield.edge.network/what-is-this ." A data processing addendum is available on request from legal@edge.network . 10. Disclaimer of Warranties THE SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. 11. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY LAW, EDGE SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY. 12. Indemnification You agree to indemnify and hold harmless Edge and its officers, directors, employees, and agents from any claims, damages, losses, or expenses arising from your use of the Services or violation of these Terms. 13. Termination We may suspend or terminate your access to the Services at any time for any reason, including violation of these Terms. Upon termination, your right to use the Services will immediately cease. 14. Governing Law These Terms shall be governed by and construed in accordance with the laws of England and Wales, without regard to conflict of law principles. 15. Changes to Terms We may modify these Terms at any time. We will provide notice of material changes by posting the updated Terms on our website. Your continued use of the Services after changes become effective constitutes acceptance of the revised Terms. 16. Conta... --- ### Test Domains — Instant test.network Subdomains URL: https://edge.network/test-network/ Markdown: https://edge.network/test-network.md JSON: https://edge.network/json/test-network.json _Get a real test domain in seconds. yourname.test.network is $1/month: full DNS control, automatic SSL, no registrar, no waiting. Point it at any host — Edge or elsewhere._ test.network A real test domain, live in seconds Pick any name — yourname.test.network — and get a fully delegated domain with complete DNS control and automatic SSL for $1/month. No registrar, no WHOIS forms, no propagation wait. Claim Your Subdomain Read the Docs $1/month, up to 5 per account, cancel anytime. Free account required — no charge until you register a name. # Pick a subdomain my-project .test.network — Available # Register — $1/month ✓ DNS zone created ✓ Delegation live — no propagation wait # Point it anywhere edge dns records add my-project.test.network \ --type A --name @ --data 203.0.113.10 # HTTPS just works → https://my-project.test.network Stop working around not having a domain localhost tunnels expire, wildcard-IP hacks like nip.io can't hold real records or clean SSL, and buying a throwaway domain means a registrar account, WHOIS details, and a renewal you'll forget. A test.network subdomain is just... a domain. Instant Edge runs the parent zone, so delegation is live the moment you register. No nameserver dance, no 24-hour wait. Full DNS control A real delegated zone: A, AAAA, CNAME, MX, TXT — every record type, managed like any domain you own. Real HTTPS Automatic certificates with Edge CDN, or run any ACME client yourself — it validates like any other domain. Points anywhere Not locked to Edge. A record to your VPS, CNAME to Vercel or Netlify — it's standard DNS. What developers use them for Anywhere you'd otherwise burn a real domain — or fight a workaround. Staging environments Give every project a real staging URL — staging.test.network — that your whole team and your CI can reach over HTTPS. Client demos Ship review builds to client-name.test.network before going live on their domain. No throwaway registrar purchases. Webhooks & OAuth callbacks Stripe, GitHub, and OAuth providers want a real, publicly resolvable HTTPS URL — not localhost. A test domain solves it in one step. API development Host your API at api.test.network with real SSL and DNS while you build — swap the CNAME when you launch. Per-branch previews Spin up a VM per pull request from CI, alias a test.network subdomain to it, tear it down on merge. Learning DNS for real Practice zones, records, MX, TXT, and SSL issuance on a real delegated domain without buying one. Console, API, CLI, or agent Register it however you work Grab a name in the console under DNS → test.network , script it over the API, or just tell your AI assistant what you want — the Agent API and MCP server can register the subdomain, deploy your app, and wire up DNS and SSL in one conversation. Get Started Free DNS API Reference # API curl -X POST https://edge.network/api/dns/test-domains \ -H "Authorization: Bearer $API_KEY" \ -d '{"subdomain": "my-project"}' # Or tell your agent "Deploy this app to my-project.test.network and sort out DNS and SSL." One dollar. No surprises. $1/month per subdomain — also available as £1 or €1 — billed to your Edge account with a card on file. Up to 5 per account, cancel anytime, billing stops immediately. Want something shorter and more permanent? you.ed.ge domains are $5/month — see ed.ge domains . $1 /month per subdomain Fully delegated DNS zone, all record types Instant activation — no propagation wait Automatic SSL with Edge CDN Points at any host, on Edge or off Up to 5 per account, cancel anytime Claim Your Subdomain Test domain questions, answered Is it a real domain? Yes. You get a fully delegated DNS zone for yourname.test.network — A, AAAA, CNAME, MX, TXT, and every other record type, exactly like a domain from a registrar. Only the NS and SOA records are managed for you. Can I point it at servers outside Edge? Absolutely. It’s standard DNS — point an A record at any server, or a CNAME at Vercel, Netlify, a Raspberry Pi behind a tunnel, anywhere. Nothing about it is locked to Edge hosting. How fast is setup, really? Seconds. Edge operates the test.network parent zone, so there’s no nameserver verification and no propagation wait — the delegation already exists. Pick a name, register, add records, done. Does HTTPS work? Yes. Point the domain at Edge CDN and a certificate is provisioned automatically via Let’s Encrypt. Pointing elsewhere? Any ACME client can pass validation on it, because it’s a real domain you control. What does it cost? $1/month per subdomain (also £1/€1), up to 5 per account, cancel anytime. Registration is via the console or API with a card on file. What happens when I cancel? The zone is released and billing stops. Since it’s meant for development and testing, don’t build a permanent brand on it — that’s what your real domain (or an ed.ge domain) is for. Your test domain is a minute away Create a free account, pick a name, and it's live before your coffee cools. Get Started Read the Docs --- ### The Humanity Score | Edge Shield URL: https://edge.network/humanity/ Markdown: https://edge.network/humanity.md JSON: https://edge.network/json/humanity.json _Every visitor to your site, scored 1–100 — invisibly. No puzzles, no cookies, no fingerprinting. Welcome humans, route legitimate AI agents, and stop abuse. Free forever with Edge Shield._ Introducing the Humanity Score Every visitor scored 1–100 . Invisibly. No puzzles, no cookies, no fingerprinting. One API call returns pass/fail plus a score — automation is a signal, not a verdict. You decide what happens next. 96 1 25 50 75 100 1–30 · BLOCK Undeclared bots Automation that refuses to identify itself floors the score. Stop it before it reaches your forms. 30–70 · ROUTE Declared agents Shopping assistants and booking agents acting for real people — send them to the right endpoints. 70–100 · WELCOME Humans Real visitors sail through without ever seeing a challenge. Your conversion rate says thanks. The widget One score, produced by a widget your visitors never notice. Drop one script tag and a div into your form. Shield scores every visitor in the background and hands your server a verdict plus the humanity score — no traffic lights, no crosswalks, no fire hydrants. Invisible by default A background proof-of-work runs in a Web Worker while risk signals are scored. Real humans almost never see a challenge. Under 15KB Dependency-free and framework-agnostic. Your Core Web Vitals won't notice it exists. No cookies, no tracking No fingerprint database, no per-visitor storage — only hourly aggregate counters. Private by architecture. A score, not a verdict Every check returns 1–100. Allow, step up, redirect, or block — your rules, not a binary gate. Verified EDGE Sign up // siteverify response { "success" : true, "score" : 96 } Control / Shield / mysite.com See the whole picture Protecting 3 widgets Verifications (30d) 128.4K ↑ 12% vs last period Avg humanity score 87 /100 Healthy — mostly human traffic Challenges served 2.1K 1.6% of checks — invisible to the rest Abuse blocked 4.9K Credential stuffing, form spam Verifications — last 14 days Traffic breakdown Humans 91% Declared AI agents 5% Challenged 2% Blocked 2% Integration Live in five minutes. Familiar sitekey + secret model — a drop-in migration from Turnstile and reCAPTCHA. 1 Add the widget to your form <script src = "https://shield.edge.network/api.js" defer ></script> <form> ... <div class = "edge-shield" data-sitekey = "es_your_sitekey" ></div> </form> 2 Verify the token on your server // one API call → verdict + humanity score POST https://shield.edge.network/siteverify { "success" : true, "score" : 96 } Free forever — unlimited widgets No credit card Single-use tokens, 5-min expiry Web Worker — zero CWV impact Measure First Why score visitors before you have a problem? We don't have a bot problem. Why score visitors now? Because "no bot problem" is usually an assumption, not a measurement — automated traffic doesn't announce itself. In invisible mode the humanity score is a measurement instrument: every visitor is scored 1–100 in the background, and your dashboard shows the real mix of humans, declared AI agents, and undeclared automation — without a single challenge shown. Most sites are surprised by what they see in the first fortnight. What does scoring early actually protect? Your data quality — which is much cheaper to keep than to recover. Fake signups skew funnel metrics and the marketing decisions based on them. Bot addresses on a mailing list damage sender reputation, which takes months to repair. Screening at the door means the numbers you make growth decisions from stay trustworthy. Score your first visitor in five minutes. Free. The humanity score is part of Edge Shield — free forever for core protection, with unlimited widgets and no credit card. Welcome humans, route good agents, and stop abuse without ever showing a puzzle. Get Started Free Explore Edge Shield --- ### Zero Egress: Why We Don't Charge for Bandwidth URL: https://edge.network/latest/zero-egress/ Markdown: https://edge.network/latest/zero-egress.md JSON: https://edge.network/json/latest/zero-egress.json _Our philosophy on transparent pricing and why egress fees are a thing of the past._ Back to Latest Company Dec 28, 2025 Zero Egress: Why We Don't Charge for Bandwidth Our philosophy on transparent pricing and why egress fees are a thing of the past. When we started Edge Network, we asked ourselves a simple question: why do cloud providers charge you to send data out? The answer, it turns out, has more to do with legacy business models than actual costs. So we decided to do things differently. The Problem with Egress Fees Traditional cloud providers charge egress fees — the cost of transferring data out of their network. These fees might seem small at first glance, but they add up quickly: A video streaming service serving 100TB/month could pay $8,500+ in egress alone A popular website with global traffic faces unpredictable monthly bills Startups experiencing growth get punished for their success Worse still, egress fees create perverse incentives. They discourage multi-cloud architectures, lock customers into single providers, and make it expensive to leave. That's not how infrastructure should work. Why Zero Egress Matters Predictable Costs Know exactly what you'll pay each month. No surprise bills when your content goes viral or traffic spikes. Global Without Penalty Serve users worldwide without worrying about regional egress multipliers. Same price everywhere. Scale Freely Grow your traffic without growing your costs proportionally. Success shouldn't be punished. Lower Total Cost For bandwidth-heavy workloads, zero egress can reduce your cloud bill by 50% or more. How We Compare Provider Egress Cost Note AWS CloudFront $0.085/GB First 10TB/month Google Cloud CDN $0.08/GB North America Azure CDN $0.081/GB Zone 1 Akamai $0.10/GB+ Enterprise pricing Edge Network $0.00/GB Always free How We Make It Work Zero egress isn't charity — it's a better business model. Here's how we make it sustainable: Distributed architecture — Our edge network processes data closer to users, reducing long-haul bandwidth costs Efficient peering — Direct connections to ISPs and carriers minimise transit costs Sustainable margins — We build egress into our base pricing, so you know exactly what you're paying Volume economics — Higher utilisation across our network benefits everyone What This Means For You No surprise bandwidth bills Budget with confidence Scale without penalty Global delivery at no extra cost Multi-cloud freedom Fair, transparent pricing Ready to Stop Paying Egress? Join the thousands of companies who've switched to Edge and eliminated their egress bills. Start your free trial today. Start Free Trial View Pricing Have questions about our pricing model? Get in touch — we're happy to explain how zero egress can reduce your cloud costs. Edge Digest A weekly wrap-up of what's happening in tech — frontiers, trends, and exclusive offers delivered to your inbox. Subscribe No spam. Unsubscribe anytime. ---