# 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.

## Agent API

> Authenticated REST API designed for AI coding agents. Issue an access code (prefix ea_live_) from the Edge control panel, set it 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://api.edge.network/agent` — auth: `Authorization: Bearer ea_live_...`

### Endpoints

- `GET    /agent` — Discovery — returns account, products, limits, available regions / OS templates, and a self-describing API schema.
- `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 require `Authorization: Bearer ea_live_…`.
- Pass `?dry_run=1` (or header `X-Dry-Run: 1`) to validate without executing.
- Pass header `Idempotency-Key: <uuid>` on POST/PATCH/DELETE 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.

---

## Home

### Edge | Decentralised Cloud Infrastructure

URL: https://edge.network/
JSON: https://edge.network/json/index.json

_Reliable performance, fair pricing, and 50% greener infrastructure for media and enterprise workloads. CDN, Compute, DNS, and Storage._

EDGE-NATIVE CLOUD INFRASTRUCTURE

The Evolution of Cloud Computing

A distributed cloud platform that runs closer to users – delivering
 reliable performance, transparent infrastructure, and cost efficiency
 for modern media and enterprise workloads.

Get Started Now

Learn More
 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
 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 Yourself
 GET STARTED

Start with Edge CDN

The world's only dedicated edge CDN. No bundled services, no upsells—just lightning-fast
 content delivery from 1,778 locations worldwide.

Deploy in minutes. Zero egress fees. See why teams are switching from Cloudflare, Fastly,
 and AWS CloudFront.

Get Started Today

Learn More

30 day trial. Complete setup in 2 minutes.

 1,778

 Edge Locations

 <15ms

 Global Latency

 $0

 Egress Fees

 99.99%

 Uptime SLA

 OUR SOLUTIONS

Built 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.

 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
 $ 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.

Get Started 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/
JSON: https://edge.network/json/pricing.json

_Disruptive cloud pricing with subscription plans from $6/month. Zero egress fees, unlimited bandwidth, and enterprise pay-as-you-go options._

Pricing

Disruptive Pricing

We've rejected the complexity tax. No usage calculators, no surprise bills, no egress fees.
 Pick a plan, know what you'll pay. Infrastructure without the spreadsheet.

 Save 10-15% with annual billing Subscription Plans

Bundled resources at a fixed monthly price. No surprises, no calculators.

 Hobbyist

 For hobbyists, students, and side projects

 $6 /mo $5/mo billed annually

Access all products

 1 vCPU / 2 GB RAM
 20 GB VM Storage
 Max 1 instance
 5M CDN requests
 5 GB Object Storage
 1M DNS queries
 Single seat
 Community support
 Get started Dev

 For solo developers and personal projects

 $12 /mo $10/mo billed annually

Access all products

 2 vCPUs / 4 GB RAM
 60 GB VM Storage
 Unlimited bandwidth
 25M CDN requests
 25 GB Object Storage
 5M DNS queries
 Single seat
 Automated support
 Get started Startup

 For side projects and small apps

 $25 /mo $21/mo billed annually

Access all products

 4 vCPUs / 8 GB RAM
 120 GB VM Storage
 Unlimited bandwidth
 50M CDN requests
 100 GB Object Storage
 10M DNS queries
 Single seat
 Automated support
 Get started Most Popular Scaleup

 For growing teams and products

 $49 /mo $42/mo billed annually

Access all products

 16 vCPUs / 32 GB RAM
 500 GB VM Storage
 Unlimited bandwidth
 250M CDN requests
 1 TB Object Storage
 50M DNS queries
 $5 per seat/month
 Ticketed support
 Get started Business

 For established businesses

 $199 /mo $169/mo billed annually

Access all products

 48 vCPUs / 96 GB RAM
 2 TB VM Storage
 Unlimited bandwidth
 1B CDN requests
 10 TB Object Storage
 100M DNS queries
 $2.50 per seat/month
 Priority support
 Get started
30 Day Trial

Try Everything for $2.50

Full access to Edge Network for 30 days. No commitments, no restrictions.
 Just powerful infrastructure at your fingertips.

Start Your Trial
 2 vCPUs / 4 GB RAM 50 GB VM Storage Unlimited bandwidth 10M CDN requests 10 GB Object Storage 1M DNS queries Enterprise

 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.88/mo)
 RAM: $0.00256/GiB-hr (~$1.84/mo)
 Disk: $0.074/GiB-mo (NVMe)
 Bandwidth: $0.011/Mbps-mo
 CDN

 Traffic: $0.048 per GB delivered to users
 Requests: $0.24 per 1M
 Egress fees: $0 (delivery rate includes all transfer costs)
 DNS

 $0.35 per 1M queries
 Volume discounts available
 Unlimited domains
 Storage

 $0.013/GB-mo
 No egress fees
 All NVMe

Zero Egress Fees. Always.

Traditional cloud punishes success – the more users you have, the more you pay to serve them.
 We've eliminated egress fees entirely. Your data, your bandwidth, no penalty.

 CDN bandwidth included in every plan Storage egress completely free Compute transfer included Same pricing in every region The Old Way vs Edge

 Traditional Cloud (100TB egress)

 $8,000 - $12,000 /mo

 Edge (100TB egress)

 $0 /mo

Ready to simplify your cloud bill?

Start with a 30-day trial or talk to our team about enterprise pricing.

Start 30 Day Trial

Contact Sales
 Stay Updated

Subscribe to our newsletter for the latest news, product updates, and engineering insights.

Subscribe

---

## Agent Documentation

### Agent Access Codes

URL: https://edge.network/docs/agent/access-codes/
JSON: https://edge.network/json/docs/agent/access-codes.json

_Create scoped credentials for AI agents to interact with your Edge infrastructure._

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

 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 API

URL: https://edge.network/docs/agent/
JSON: https://edge.network/json/docs/agent.json

_An API designed for AI agents and LLMs to deploy, manage, and monitor applications on Edge Network._

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

 Learn More

 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 Projects

URL: https://edge.network/docs/agent/projects/
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?

---

### Deploy Application

URL: https://edge.network/docs/agent/deploy-app/
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
 }
} 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.setup_script No Bash script to run on first boot via cloud-init 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@<ip> . 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@<vm-ip> 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/&#123;id&#125; — 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/&#123;id&#125; Delete a key from the account (must be detached first) GET /agent/compute/vms/&#123;id&#125;/ssh-keys List keys attached to a specific VM POST /agent/compute/vms/&#123;id&#125;/ssh-keys/&#123;keyId&#125; Attach an existing key to a VM (works on running VMs) DELETE /agent/compute/vms/&#123;id&#125;/ssh-keys/&#123;keyId&#125; 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/&#123;id&#125; VM details with live metrics GET /agent/compute/os-templates Available operating systems 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/&#123;id&#125;/ssh-keys/&#123;keyId&#125; Attach SSH key to existing VM DELETE /agent/compute/vms/&#123;id&#125;/ssh-keys/&#123;keyId&#125; Detach SSH key from VM GET /agent/compute/firewall List security groups GET /agent/compute/firewall/&#123;id&#125; Security group details POST /agent/compute/firewall Create security group POST /agent/compute/vms/&#123;id&#125;/firewall/&#123;groupId&#125; Attach security group DELETE /agent/compute/vms/&#123;id&#125;/firewall/&#123;groupId&#125; 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

Check the status of all resources in a project:

 GET /agent/projects/proj_b2c3d4e5f6a7/health
Authorization: Bearer ea_live_...

# Response:
{
 "project": "my-saas-app",
 "overall_status": "healthy",
 "resources": [
 {
 "type": "compute",
 "id": "vm_xyz789",
 "name": "my-saas-app",
 "status": "running",
 "metrics": {
 "cpu_percent": 42,
 "ram_percent": 61,
 "disk_percent": 28
 }
 },
 {
 "type": "cdn",
 "id": "dep_abc123",
 "name": "my-saas-app-cdn",
 "status": "active",
 "domains": 1
 }
 ],
 "summary": { "total": 2, "healthy": 2, "issues": 0 },
 "tell_user": "Project \"my-saas-app\" is healthy. All 2 resources are running normally."
} Scaling

Scale compute resources up or down:

 POST /agent/projects/proj_b2c3d4e5f6a7/sca...

---

### Deploy Static Site

URL: https://edge.network/docs/agent/deploy-static-site/
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/&#123;projectId&#125; 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/
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.

 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" }
 },
 "capabilities": [
 "deploy_static_site", "deploy_app", "upload_assets",
 "provision_vm", "manage_dns", "check_health", "scale",
 "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/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" }
 },
 "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\". 4 products available: compute, cdn, storage, dns. 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

# 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

# Firewall
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 firewall
DELETE /agent/compute/vms/{id}/firewall/{groupId} Detach firewall

# CDN
GET /agent/cdn/deployments List CDN deployments

# Storage
GET /agent/storage/buckets List buckets
POST /agent/storage/buckets Create bucket

# DNS
GET /agent/dns/zones List zones
GET /agent/dns/zones/{id} Zone details + records
POST /agent/dns/zones/{id}/records Add DNS record Key Concepts

 Dry Run

Add X-Dry-Run: true to any mutating request to preview what would happen without making changes.
 The response shows what would be created, modified, or deleted.

 Idempotency

Add Idempotency-Key: unique-id to POST requests.
 If the same key is sent again, the original response is returned without re-executing the action. Safe for retries.

 tell_user

Every response includes a tell_user field — a plain English summary the agent can relay
 directly to the user without interpretation. Error responses include it too.

 Error Handling

Errors return a structured object with code , message ,
 and tell_user . The agent can use the code for programmatic handling and tell_user for reporting.

 SSH Keys & VMs

Defau...

---

## Documentation

### Documentation - Edge Network

URL: https://edge.network/docs/
JSON: https://edge.network/json/docs.json

_Learn how to use Edge Network products. Comprehensive guides for Compute, CDN, DNS, and Storage._

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.

 Dev Tooling

 Tools for developers to integrate and automate.

 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' revenue for 3 years by sharing your referral code.

 Popular Guides

 Jump straight to the most common tasks.

 CDN

 Deploy your first CDN

 CDN

 Image optimization

 Compute

 Create your first VM

 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/
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
 Screenshot: Create Snapshot dialog

 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 Screenshot: Snapshots list with multiple backups

 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

 Included

 In your plan

 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/
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/
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.

 Screenshot: Region selection in Create VM form

 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 also upload and boot from custom ISO images. Contact support to enable this feature for your account.

 VM Configuration

Configure your VM's resources using the sliders. Resources come from your subscription allocation.

 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

 Screenshot: Resource configuration sliders

 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/
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 control panel
 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 &rarr; Firewall in the control panel
 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 control panel 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/
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
 Screenshot: SSH Keys page with Add Key button

 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
 Screenshot: Create VM form with configuration options

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.

 Screenshot: VM Overview page showing 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/
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 control panel.

 VM Dashboard

Click on any VM to access its dashboard. Here you'll find quick actions, status information, and navigation to detailed management pages.

 Screenshot: VM Dashboard overview page

 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
 Screenshot: VNC Console window

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.

 Screenshot: VM Resize page with sliders

 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/
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 control panel
 Click on the Metrics tab
 Select a time range (1 hour, 6 hours, 24 hours, 7 days, or 30 days)
 Screenshot: Metrics dashboard with graphs

 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.

 Screenshot: Network metrics graph showing traffic over time

 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:

 Screenshot: Quick stats on VM Overview page

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/
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
 Screenshot: Networking tab showing IP addresses

 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
 Screenshot: Add IP confirmation dialog

 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.

 Screenshot: Your Private Networks table

 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
 Screenshot: Bandwidth Usage section

 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/
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 control panel
 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
 Screenshot: Add SSH Key modal

 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.

 Screenshot: SSH key selection during VM creation

 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/
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) 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 (Agent)

 POST /agent/deploy/app
{
 "project": "my-blog",
 "compute": {
 "size": "small",
 "setup_script": "#!/bin/bash\n..."
 }
} 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/
JSON: https://edge.network/json/docs/cdn/purging.json

_Learn how to clear cached content from Edge CDN when you need to update or remove content._

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.

 Screenshot: Cache Size section showing cached objects, total size, and average object size

 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
 Screenshot: Purge Cache modal with URL input field

 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/
JSON: https://edge.network/json/docs/cdn/analytics.json

_Monitor your CDN performance with detailed analytics on requests, bandwidth, cache hits, and more._

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.

 Screenshot: CDN Analytics dashboard with traffic charts and stats cards

 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 Screenshot: Time range selector with traffic trend chart

 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.

 Screenshot: Top Content table showing popular paths with stats

 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.

 Screenshot: Interactive line charts showing requests, cache performance, and bandwidth

 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.

 Screenshot: Activity log showing deployment events with filters

 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/
JSON: https://edge.network/json/docs/cdn/caching.json

_Learn how Edge CDN caches content and how to configure cache behavior for optimal performance._

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.

 Screenshot: Pause Cache button in deployment header

 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.

 Screenshot: Analytics showing cache hit rate over time

 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/
JSON: https://edge.network/json/docs/cdn/configuration.json

_Configure your Edge CDN deployment with presets, caching rules, and image optimization settings._

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.

 Screenshot: Preset selection in the Configuration tab

 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/
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/
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 &amp; SSL

URL: https://edge.network/docs/cdn/domains/
JSON: https://edge.network/json/docs/cdn/domains.json

_Learn how to add domains to your CDN deployment and configure SSL certificates._

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.

 Screenshot: Domain row showing DNS pending status with CNAME instructions

 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

 Screenshot: Domain with SSL active badge and green shield icon

 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.

 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/
JSON: https://edge.network/json/docs/cdn/getting-started.json

_Deploy your first CDN and start serving content globally in under 5 minutes._

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
 Screenshot: Create CDN Deployment form

 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
 Screenshot: Add Domain modal with domain and origin fields

 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
 Screenshot: Domain with DNS pending status and CNAME instructions

 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.

 Screenshot: Domain with SSL active status and green shield icon

 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/
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 Screenshot: Side-by-side comparison of original vs optimized image with file size reduction

 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:

 <img
 src="https://cdn.yoursite.com/hero.jpg?width=1200&format=webp"
 srcset="
 https://cdn.yoursite.com/hero.jpg?width=400&format=webp 400w,
 https://cdn.yoursite.com/hero.jpg?width=800&format=webp 800w,
 https://cdn.yoursite.com/hero.jpg?width=1200&format=webp 1200w
 "
 sizes="(max-width: 600px) 400px, (max-width: 1000px) 800px, 1200px"
/> 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

 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/
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.

 Interactive world map with regional traffic distribution

 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?

---

## Documentation › DNS

### DNS Backups

URL: https://edge.network/docs/dns/backups/
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. Retention period depends on your plan.

 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 based on your plan. 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/
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 in every plan

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 <zone-id>

# View the last result
edge dns examine-last <zone-id>

# Output as JSON
edge dns examine <zone-id> --output json
Backups

test.network

Back to Docs

Need help?

---

### DNS Metrics &amp; Analytics

URL: https://edge.network/docs/dns/metrics/
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/
JSON: https://edge.network/json/docs/dns.json

_High-performance authoritative DNS with global anycast, instant propagation, and advanced routing._

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/
JSON: https://edge.network/json/docs/dns/records.json

_Learn about DNS record types, how to create them, and best practices for configuration._

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/
JSON: https://edge.network/json/docs/dns/zones.json

_Create, configure, and manage DNS zones for your domains._

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/
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 control panel.

 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 &rarr; ed.ge in the control panel
 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 &rarr; 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 &rarr; 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/
JSON: https://edge.network/json/docs/dns/geo-routing.json

_Route DNS queries to different endpoints based on the geographic location of users._

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/
JSON: https://edge.network/json/docs/dns/getting-started.json

_Add your first domain to Edge DNS and start serving queries globally in under 5 minutes._

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 control panel, 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 &amp; Domain Verification

URL: https://edge.network/docs/dns/nameservers/
JSON: https://edge.network/json/docs/dns/nameservers.json

_Understand Edge DNS's unique nameserver system that secures domain ownership._

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/
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 control panel under DNS → test.network .

 1 Choose a subdomain

 Navigate to DNS → test.network in the control panel. 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/
JSON: https://edge.network/json/docs/dns/zone-editor.json

_Advanced JSON editing for complete control over your DNS zone configuration._

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: <flags> <tag> <value> .
 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: <priority> <weight> <port> <target>

 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/
JSON: https://edge.network/json/docs/storage/access-keys.json

_Generate and manage S3 access keys for Edge Storage._

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/
JSON: https://edge.network/json/docs/storage/buckets.json

_Create and manage storage buckets on Edge Storage._

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 Control Panel

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/
JSON: https://edge.network/json/docs/storage/metrics.json

_Monitor storage usage, request volume, and bandwidth for your Edge Storage buckets._

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, control panel 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

 Control Panel

 Navigate to Storage in your control panel
 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/
JSON: https://edge.network/json/docs/storage/getting-started.json

_Set up Edge Storage and upload your first object in minutes._

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 control panel:

 $ 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/
JSON: https://edge.network/json/docs/storage/multipart-uploads.json

_Upload large files reliably using multipart uploads._

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/
JSON: https://edge.network/json/docs/storage/presigned-urls.json

_Generate time-limited signed URLs for direct uploads and downloads without exposing credentials._

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/
JSON: https://edge.network/json/docs/storage/sdk-examples.json

_Code examples for using Edge Storage with popular programming languages._

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/
JSON: https://edge.network/json/docs/storage.json

_S3-compatible object storage with global edge distribution and per-account isolation._

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
 Control Panel

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 Control panel 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 control panel, 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 › Account

### Account &amp; Support

URL: https://edge.network/docs/account/
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.

 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 &rarr; Settings &rarr; 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

Contact Support

Back to Docs

Need help?

---

### Alerts &amp; Notifications

URL: https://edge.network/docs/account/alerts/
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/
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 control panel
 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
 Screenshot: Activity log with filters

 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 (control panel), 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 control panel.

 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?

---

### Referral Program

URL: https://edge.network/docs/account/referral-program/
JSON: https://edge.network/json/docs/account/referral-program.json

_Share your referral code and earn up to 15% of referred customers' revenue for 3 years. Learn how to get your code, what your referrals get, and how payouts work._

Account & Support

Referral Program

Share your referral code and earn revenue share when you bring new customers to Edge Network.

 Overview

Every Edge account gets a referral code. Share it with others and earn up to 15% of referred customers' revenue for 3 years . The referred customer gets a discount too, so everyone benefits.

 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/&#123;code&#125;

 What Your Referrals Get

By default, referred customers get 10% off their first 12 months on any subscription plan. The discount is applied automatically at checkout when they sign up using your referral link.

 What You Earn

You earn a revenue share on referred customers' payments. The rate depends on how long they've been a customer:

 Period Revenue Share Year 1 15% Year 2 10% Year 3 5% Indirect referrals (your referral refers someone else) 5% flat Payout Options

You can receive your referral earnings in three ways:

 Invoice credit — Applied automatically to your next invoice
 Bank transfer — Paid out quarterly
 EDGE tokens — Paid out quarterly

Minimum payout: $5 .

 How It Works

 Share your referral link with potential customers
 The new customer signs up and sees your discount applied
 They subscribe to a plan and get the discount at checkout
 You start earning when their first payment processes
 Credits accumulate in your account and are paid out according to your chosen method
 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
 The referred customer must make at least one payment for you to earn
 Credits are issued only after the referred customer has been active for a minimum of 30 days
 Maximum 2 levels of referral depth (direct referrals + one level of indirect)

Back to Docs

Need help?

---

### Security

URL: https://edge.network/docs/account/security/
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/
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 control panel.

 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 control panel.

 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/
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/
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 control panel
 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
 Screenshot: 2FA setup with QR code

 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 › Tooling & CLI

### CLI Authentication

URL: https://edge.network/docs/cli/authentication/
JSON: https://edge.network/json/docs/cli/authentication.json

_Set up API key authentication for the Edge CLI._

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.

 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/
JSON: https://edge.network/json/docs/cli/cdn.json

_Manage CDN deployments, domains, and cache purging from the command line._

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/
JSON: https://edge.network/json/docs/cli/compute.json

_Manage virtual machines, SSH keys, and security groups from the command line._

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 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 --ssh-key SSH key name or ID to attach --security-group Security group name or ID --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/
JSON: https://edge.network/json/docs/cli/configuration.json

_Customize the Edge CLI with configuration options._

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/
JSON: https://edge.network/json/docs/cli/dns.json

_Manage DNS zones and records from the command line._

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/
JSON: https://edge.network/json/docs/cli/installation.json

_Install the Edge CLI on macOS, Linux, or Windows._

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 .

 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 Storage Commands

URL: https://edge.network/docs/cli/storage/
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 control panel 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/
JSON: https://edge.network/json/docs/tooling/command-palette.json

_Navigate and take actions across the Edge control panel instantly with keyboard shortcuts._

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 control panel 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 control panel 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/
JSON: https://edge.network/json/docs/tooling.json

_Developer tools and productivity features built into the Edge control panel._

Dev Tooling

Developer Tools

Productivity features built into the Edge control panel for faster infrastructure management.

 Command Palette

Navigate anywhere, trigger actions, and search across the entire control panel 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/
JSON: https://edge.network/json/docs/cli.json

_Command-line interface for managing Edge Network resources._

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

 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/* 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/
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.

 Quick Start Guide
 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
 Security Hardening
 Cost Optimization
 High Availability
 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 a Decentralised Cloud?
 Why do we Charge for the Trial Period?
 What Makes Edge Better for the Environment?
 What is XE and how does it Power Edge?
 Featured Guides

Popular tutorials to get you started quickly.

 Migrating from AWS to Edge 15 min read Setting up a multi-region CDN 10 min read Deploying a Node.js app on Edge Compute 12 min read Configuring DNS failover 8 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/
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 Get Started

 Head to edge.network and click the "Get Started" button to begin the signup process.

 Visit edge.network
 Click "Get Started" in the top navigation
 You'll be taken to the account creation page
 02 Create Your Account

 Enter your details to create your Edge account. You'll need a valid email address and a secure password.

 Enter your email address
 Create a secure password
 Accept the terms of service and privacy policy
 Click "Create Account" to proceed
 03 Complete Your Profile

 Add your details to personalise your account and help us provide better support.

 Enter your full name
 Add your company or organisation (optional)
 Select your primary use case
 Choose your preferred timezone
 04 Add Payment Method

 Add a credit or debit card and pay $2.50 to start your 30-day trial. This small upfront charge helps us prevent abuse and keeps the platform secure for everyone.

 Enter your card details securely
 Add a billing address
 You'll be charged $2.50 immediately
 Trial begins with $2.50 in credits
 05 Your Account is Ready

 You're all set! Your Edge account is now active and you can start deploying resources immediately.

 You'll be taken to your dashboard
 Your 30-day trial is now active
 Start deploying CDN, Compute, DNS, or Storage
 Check out the Quick Start guide to deploy your first resource
 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

 Configure how and when you want to be notified about your account and services.

 Navigate to Settings → Notifications
 Choose email, SMS, or both
 Select notification types (billing, alerts, updates)
 Set your preferred frequency
 08 Verify Your Email

Complete this step anytime within 24 hours of creating your account. Check your inbox for a verification email and click the link to confirm your address.

 Check your email inbox (and spam folder)
 Click the verification link in the email
 You'll be redirected back to Edge
 Verification must be completed within 24 hours
 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 Dashboard
 Related guides

Quick Start Guide
 10 min
CLI Installation
 3 min
First Deployment
 8 min

---

### API Reference

URL: https://edge.network/academy/api-reference/
JSON: https://edge.network/json/academy/api-reference.json

_Edge Network REST API: authentication, endpoints for Compute, CDN, DNS, and Storage, 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, and Storage. 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 Control Panel → 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

---

### Caching Strategies

URL: https://edge.network/academy/caching-strategies/
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 control panel 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 control panel 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 control panel, 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 control panel, 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 control panel 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

---

### CLI Installation

URL: https://edge.network/academy/cli-installation/
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
 control panel 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

---

### Configuring DNS Failover

URL: https://edge.network/academy/dns-failover/
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 control panel 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 control panel 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

---

### Cost Optimization

URL: https://edge.network/academy/cost-optimization/
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 bundled plans that include compute, storage, CDN, and DNS. 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.

Plan tiers: Hobbyist ($6/mo), Dev ($12/mo), Startup ($25/mo), Scaleup ($49/mo),
 and Business ($199/mo). Each tier includes a set amount of vCPU, RAM, storage, and CDN usage.
 Stay within your limits and your bill is predictable.

 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 control panel under Compute → Metrics .

If utilisation is consistently low (e.g. under 20%), resize to a smaller instance. Edge lets you
 resize VMs without data loss — shut down, change the plan, start again. Scaling up is easy when
 you need it.

 Monitoring usage against plan limits

The Usage page in the control panel shows how much of your plan you've consumed:
 vCPU hours, RAM, storage, CDN requests, and bandwidth. Use it to avoid overages and to decide
 when to upgrade vs optimise.

 When to upgrade: If you're consistently near or over plan limits, upgrading is
 often cheaper than overage charges. The next tier may also unlock features (e.g. more CDN origins,
 more VMs) that improve your setup.

 When to optimise: If usage is well under limits but you want to cut costs,
 right-size VMs, enable CDN caching to reduce origin load, and clean up unused storage.

 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.

 Annual billing discount

Pay annually and save roughly 15%. In Settings → Billing , switch to annual
 billing. Your plan is charged upfront for 12 months at a discounted rate — useful if you're
 committed to Edge and want to lock in savings.

 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

---

### Deploying a Node.js App on Edge Compute

URL: https://edge.network/academy/deploy-nodejs-app/
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 control panel 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 control panel.

 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

---

### First Deployment

URL: https://edge.network/academy/first-deployment/
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 control panel .

 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 control panel.

 # View VM details edge compute get <vm-id>
You can also create VMs from the control panel ,
 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 control panel
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

 Control Panel

 Manage everything visually

---

### Go SDK

URL: https://edge.network/academy/sdk-go/
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

---

### High Availability

URL: https://edge.network/academy/high-availability/
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 control panel, 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 control panel 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

---

### JavaScript SDK

URL: https://edge.network/academy/sdk-javascript/
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 Control Panel → 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

---

### Migrating from AWS to Edge

URL: https://edge.network/academy/migrating-from-aws/
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

---

### Python SDK

URL: https://edge.network/academy/sdk-python/
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 control panel to retain only recent backups.

 Next steps

Go SDK

Storage Documentation

---

### Quick Start Guide

URL: https://edge.network/academy/quick-start/
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. Start with a 30-day trial for just $2.50.

 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 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

---

### Security Hardening

URL: https://edge.network/academy/security-hardening/
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, and agent access codes with limited permissions._

Back to Academy

Best Practices
 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 control panel, 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 control panel, 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 control panel.
 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 control panel.
 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.

 Next steps

Cost Optimization

Compute Documentation

---

### Setting up a Multi-Region CDN

URL: https://edge.network/academy/multi-region-cdn/
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 control panel, 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 control panel 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

---

### Video: CDN Setup

URL: https://edge.network/academy/video-cdn-setup/
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 control panel, 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

---

### Video: DNS Management

URL: https://edge.network/academy/video-dns-management/
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 control panel, 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

---

### Video: Storage Basics

URL: https://edge.network/academy/video-storage-basics/
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 control panel, 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 Control Panel)

 Control panel: 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. Monitor your usage
 to stay within your plan.

 Next: Caching Strategies

 Best practices for CDN caching

 Storage Documentation

 Full reference docs

---

### Video: VM Configuration

URL: https://edge.network/academy/video-vm-configuration/
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
 control panel. 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 control panel. 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

---

### What is a Decentralised Cloud?

URL: https://edge.network/academy/what-is-a-decentralised-cloud/
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 with a 30-day trial.

Start Your Trial

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

---

### What is the Agentic Cloud?

URL: https://edge.network/academy/what-is-the-agentic-cloud/
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 control panel 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

---

### What is XE and how does it Power Edge?

URL: https://edge.network/academy/what-is-xe/
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

---

### What Makes Edge Better for the Environment?

URL: https://edge.network/academy/edge-and-the-environment/
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?

---

### Why do we Charge for the Trial Period?

URL: https://edge.network/academy/why-do-we-charge-for-the-trial-period/
JSON: https://edge.network/json/academy/why-do-we-charge-for-the-trial-period.json

_Learn why Edge requires a small payment to start your trial and how it helps us maintain a secure, high-quality platform._

Back to Academy

Information
 4 min read
Why do we Charge for the Trial Period?

We believe in being upfront about how we operate. Here's why we ask for a small
 payment to start your Edge trial—and why it benefits everyone.

The Short Answer

To keep Edge a secure platform and avoid abuse, we verify accounts through a small
 payment of $2.50 . This
 acts as a barrier to platform abuse while giving you real credits to use during
 your 30-day trial.

The Problem We're Solving

Cloud infrastructure is a valuable resource. Unfortunately, that makes it a
 target for abuse. Spammers, crypto miners, and other bad actors regularly
 exploit free trial offers to access computing power without paying for it.

This isn't just a problem for us—it's a problem for our legitimate customers.
 When platforms are overrun with abuse, performance suffers, costs rise, and
 everyone has a worse experience.

We tried the traditional "free trial" model. What we found was that a significant
 portion of sign-ups were from accounts that had no intention of becoming real
 customers. They consumed resources, created support overhead, and ultimately
 made the platform worse for everyone else.

Our Solution: Verified Trials

Instead of a free trial with hidden limitations, we ask for a small upfront
 payment of $2.50. This simple step accomplishes several things:

 Platform Security

 Payment verification prevents bad actors from creating multiple accounts to abuse our infrastructure.

 Better for Everyone

 By filtering out abuse, we can offer better performance and reliability to legitimate customers.

 Full Access Immediately

 Once verified, you get complete access to all Edge services with no artificial limitations.

 Real Credits

 Your $2.50 isn't a fee—it becomes credits you can use for any Edge service.

What Your $2.50 Gets You

This isn't a fee—it's credit. Your $2.50 goes directly into your account and
 can be used for any Edge service during your 30-day trial.

 Full access to Edge CDN with global distribution Deploy virtual machines in any of our 33 regions Complete DNS management with anycast routing Object storage with zero egress fees API and CLI access Priority support during your trial
The Result: A Better Platform

Since implementing verified trials, we've seen a dramatic reduction in abuse
 and a significant improvement in platform quality. Our support team spends
 less time dealing with bad actors and more time helping real customers succeed.

Most importantly, our infrastructure performs better. Resources that were
 previously consumed by abuse are now available for legitimate workloads.
 Response times are faster, uptime is higher, and the overall experience is
 significantly improved.

We know asking for payment upfront isn't the norm in cloud computing. But we
 believe in doing what's right for our platform and our customers, even when
 it's unconventional. The small barrier to entry ensures that everyone on
 Edge is here because they genuinely want to build something.

Common Questions

Is the $2.50 refundable?

The $2.50 is converted to account credit, so there's nothing to refund—you
 get to use it! If you decide Edge isn't for you, you can use your credits
 before your trial ends.

What happens after the 30-day trial?

At the end of your trial, you can choose which plan to move to, or cancel
 entirely—it's completely up to you. If you need more time to decide, just
 drop us a line and we'll be happy to help.

Can I get more credits during my trial?

If you need more during your trial period, you can switch to a subscription
 tier at any time. Your trial payment will be subtracted from the cost of
 your first month.

Ready to Get Started?

Join thousands of developers and businesses building on Edge's secure,
 high-performance infrastructure.

Start Your Trial — $2.50
 Related articles

Account Setup Guide
 5 min
What is a Decentralised Cloud?
 8 min
Quick Start Guide
 10 min

---

## Products

### CDN Features

URL: https://edge.network/cdn/features/
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 on every plan.

 Global Edge Network

 1,778 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.

 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.

Trial Edge Today

---

### CDN Help | Expert Services

URL: https://edge.network/cdn/help/
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

URL: https://edge.network/cdn/performance/
JSON: https://edge.network/json/cdn/performance.json

_Independent benchmarking shows Edge CDN consistently delivering fast response times. Real-time data from PerfOps measuring median latency against major providers._

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 Regions

URL: https://edge.network/cdn/regions/
JSON: https://edge.network/json/cdn/regions.json

_Explore 1,778+ edge locations across 6 continents. Sub-20ms latency from anywhere in the world._

CDN CDN

Global Edge Network

 1,778+ 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 1,778+

 Edge Locations

 6

 Continents

 95%

 Global Coverage

 <20ms

 Avg Latency

 Deploy globally in minutes

Your content, cached at every edge location, automatically.

Trial Edge Today

---

### Compare CDN Providers

URL: https://edge.network/cdn/compare/
JSON: https://edge.network/json/cdn/compare.json

_Compare Edge CDN to AWS CloudFront, Cloudflare, Akamai, and more. See why Edge offers better performance at lower cost._

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 1,778 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 Decentralized Transparent Pricing No Vendor Lock-in 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

---

### Compare Compute Providers

URL: https://edge.network/compute/compare/
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.

 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/
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 Domains Unlimited 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 $0.35/million 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 $3.50 Free $9 $50 50 domains, 100M queries/mo $35 Free $65 $250 100 domains, 500M queries/mo $175 Enterprise $250 $500 500 domains, 1B queries/mo $350 Enterprise $650 $2,500 Why choose Edge DNS?

The key advantages that set us apart.

 $0.35

 Per million queries

 <5s

 Propagation time

 ∞

 Unlimited domains

Get Started with Edge DNS

---

### Compare Monitoring Providers | Edge Pulse

URL: https://edge.network/pulse/compare/
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 Included $29/mo extra $7/mo extra Included Starting Price $0 (3 checks) $15/mo $0 (5 min) $5/check/mo $0 (5 monitors) Bundled with Cloud 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.

 Included, not add-on

 If you already use Edge CDN, Compute, DNS, or Storage, Pulse monitoring is included in your plan at no extra cost. No separate tool, no separate bill, no per-check pricing.

 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, includes status pages, and starts free.

 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

 Pulse is dramatically cheaper for monitoring 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

 $0

 Free plan with 3 checks

 Included

 Status pages on every plan

Start Monitoring Free

---

### Compare Storage Providers

URL: https://edge.network/storage/compare/
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.

 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/
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 on every plan.

 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.

Trial Edge Today

---

### Compute Help | Expert Services

URL: https://edge.network/compute/help/
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/
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. Your subscription includes bundled resources
 you can allocate across one or many servers.

 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 Resources bundled in your subscription

Your subscription includes compute resources you allocate freely. No per-server pricing,
 no data transfer limits. Need more capacity? Upgrade your plan or contact us for enterprise options.

View Plans

Contact Sales

---

### Compute Regions

URL: https://edge.network/compute/regions/
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.

Trial Edge Today

---

### DNS

URL: https://edge.network/dns/
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

Start with a 30-day trial for $2.50. DNS included in every plan.

 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 included in every plan

 No separate DNS charges. Queries included with your subscription.

 Hobbyist

 $6 /mo

 1M DNS queries
 Unlimited domains
 All record types
 Community support
 Dev

 $12 /mo

 5M DNS queries
 Unlimited domains
 All record types
 Geo-routing
 Startup

 $25 /mo

 10M DNS queries
 Unlimited domains
 All record types
 Geo-routing
 Scaleup

 $49 /mo

 50M DNS queries
 Unlimited domains
 All record types
 Geo-routing
 Enterprise

 $0.35 /1M queries

 Pay-as-you-go
 Volume discounts
 Unlimited domains
 99.99% SLA

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
Ready to speed up your DNS?

Add your first domain in under 2 minutes. Start with a 30-day trial.

Get Started Free

---

### DNS Examiner

URL: https://edge.network/dns/examine/
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 in every Edge DNS plan.

Get Started

---

### DNS Features

URL: https://edge.network/dns/features/
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 on every plan.

 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/
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/
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 faster

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 Record Types

URL: https://edge.network/dns/records/
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/
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 Cache | Edge CDN

URL: https://edge.network/cdn/edge-cache/
JSON: https://edge.network/json/cdn/edge-cache.json

_Permanent edge caching for 100% cache hit rates. Faster performance and reduced origin load._

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 1,778 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/
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

30 day trial. 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 Scalable By Design

 Maximize your growth and expansion with our infinitely scalable infrastructure. Handle any traffic spike without breaking a sweat.

 Global Edge Network

 1,778 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.

 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.

 1,778

 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

Start your trial

Deploy to our global network of 2,200+ PoPs with zero egress fees and sub-20ms latency worldwide.

Start Now

30 day trial. Complete setup in 2 minutes.

---

### Edge CDN vs Akamai

URL: https://edge.network/cdn/compare/akamai/
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 – 1,778 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 1,778 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/
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 1,778 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/
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 – 1,778 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 1,778 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 1,778 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?

Get started with our 30-day trial and experience the difference.

Get Started with Edge CDN

View All Comparisons

---

### Edge CDN vs CDN77

URL: https://edge.network/cdn/compare/cdn77/
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 (1,778 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 – 1,778 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 1,778 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?

Get started with our 30-day trial and experience the difference.

Get Started with Edge CDN

View All Comparisons

---

### Edge CDN vs Cloudflare

URL: https://edge.network/cdn/compare/cloudflare/
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 – 1,778 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 1,778 300+ Instant Purge Free Tier $2.50 trial 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 1,778 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?

Start with our 30-day trial and experience the difference.

Get Started with Edge CDN

View All Comparisons

---

### Edge CDN vs Fastly

URL: https://edge.network/cdn/compare/fastly/
JSON: https://edge.network/json/cdn/compare/fastly.json

_Compare Edge CDN to Fastly. Zero egress fees, 1,778+ 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 (1,778 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 – 1,778 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 1,778 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?

Get started with our 30-day trial and experience the difference.

Get Started with Edge CDN

View All Comparisons

---

### Edge Compute - Global Virtual Machines

URL: https://edge.network/compute/
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

30 day trial. Complete setup in 2 minutes.

Flexible resources, your way

Your subscription includes bundled compute resources. Use them across one server or many –
 configure each exactly how you need it.

 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

 Bundled with your subscription

Unlike per-instance pricing, your Edge subscription includes compute resources you can
 allocate freely. Spin up multiple small servers or consolidate into fewer powerful ones –
 it's your choice. Need more? Upgrade your plan or add enterprise pay-as-you-go resources.

View Plans

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
Ready to deploy?

Start with a 30-day trial today.

Get Started Free

---

### Edge Pulse | Synthetic Monitoring from Real User Locations

URL: https://edge.network/pulse/
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 plan available. 3 checks, no credit card required.

 2,000+

 Probe Locations

 30s

 Check Frequency

 6

 Probe Types

 Included

 Status Pages

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, included

Every competitor charges $29–79/month extra for status pages. Pulse includes them with every plan. Give your users a professional, branded 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. Free plan available — no credit card needed.

Start Monitoring Free

---

### GPU Compute

URL: https://edge.network/compute/gpus/
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/
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 control panel, 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 control panel, 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/
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, powered by Edge CDN + DNS, and included with every plan.

 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. Free plan available with 3 checks.

Start Monitoring Free

---

### Pulse Help | Expert Monitoring Setup

URL: https://edge.network/pulse/help/
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-check pricing

 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/
JSON: https://edge.network/json/pulse/pricing.json

_Synthetic monitoring from 2,000+ residential locations. Free plan available. Status pages included. No per-check billing surprises._

Pulse Pulse

Pricing

Monitoring from residential locations at a fraction of the cost. Status pages included. No per-check billing surprises.

Included with every Edge plan

Already using Edge CDN, Compute, DNS, or Storage? Pulse monitoring is included in your subscription at no extra charge. Here's what you get:

 Plan Price Checks Frequency Locations Status Page Trial $2.50 3 checks 5 min 3 Shared Hobbyist $6/mo 3 checks 5 min 3 Shared Dev $12/mo 5 checks 2 min 3 Shared Startup $25/mo 15 checks 1 min 5 1 custom Scaleup $49/mo 30 checks 30s 10 1 custom Business $199/mo 100 checks 30s All 3 custom Enterprise $499/mo+ Unlimited 30s All Unlimited
View full Edge pricing

Standalone plans

Just need monitoring? Use Pulse on its own — no CDN, Compute, or DNS required. Start free and scale as you grow.

 Pulse Free

 $0 forever 3 HTTP/HTTPS checks 5-minute check interval 3 probe locations Email alerts Shared status page 7-day data retention Start Free Most Popular Pulse Pro

 $29 /mo 50 checks (all types) 30-second check interval All 2,000+ locations Email, Slack, webhook alerts 1 custom status page 90-day data retention Response time analytics Get Started Pulse Business

 $99 /mo 200 checks (all types) 30-second check interval All 2,000+ locations All alert channels incl. PagerDuty 3 custom status pages 1-year data retention Multi-step API workflows Page speed monitoring Get Started Pulse Enterprise

 $299 /mo Unlimited checks 30-second check interval All 2,000+ locations All alert channels Unlimited status pages Unlimited data retention Multi-step API workflows Page speed monitoring Dedicated support Custom SLA Get Started
Add-on packs

Need more than your plan includes? Add extra checks or unlock advanced probe types on any plan.

 +10 checks

 10 additional monitoring checks

 $5/mo +50 checks

 50 additional monitoring checks

 $20/mo +200 checks

 200 additional monitoring checks

 $60/mo Multi-step API

 Unlock API workflow probes

 $10/mo Page speed

 Full page load monitoring

 $10/mo SMS alerts

 SMS notifications (100 SMS/mo)

 $5/mo
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 Status pages Included $29/mo extra $7/mo extra Not included Starting price $0 (3 checks) $15/mo $0 (5 min) $5/check/mo Bundled with cloud Real user conditions
Start monitoring for free

3 checks from residential locations, email alerts, and a status page — completely free. No credit card required.

Start Free

Explore Features

---

### Smart Routing | Edge CDN

URL: https://edge.network/cdn/smart-routing/
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 1,778 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/
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

30 day trial. 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

 Included in subscription
 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
Ready to store without limits?

Create your first bucket in seconds. Start your 30-day trial today.

Get Started Free

---

### Storage Features

URL: https://edge.network/storage/features/
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.

Trial Edge Today

---

### Storage Help | Expert Services

URL: https://edge.network/storage/help/
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 Regions

URL: https://edge.network/storage/regions/
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/
JSON: https://edge.network/json/solutions/agentic-development.json

_The first cloud platform built for AI agents. Let your coding assistant deploy, manage, and monitor your infrastructure._

Agent-Native Cloud Platform

Your AI agent
 deploys your app

The first cloud platform with an API designed for AI agents.
 Give your coding assistant an access code and let it handle deployment,
 DNS, SSL, and monitoring — while you keep building.

Explore the Agent API

Create Agent Code
 Cursor Agent # You say:

 "Deploy my React app to portfolio.example.com"

 # Agent connects to Edge

 GET /agent → 4 products, $47.20 remaining

 # Agent deploys

 ✓ Storage bucket created

 ✓ 12 files uploaded

 ✓ CDN deployment configured

 ✓ DNS CNAME added

 ✓ SSL certificate issued

 # Agent reports back:

 "Your portfolio is live at https://portfolio.example.com

 with CDN, automatic SSL, and image optimization.

 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.

 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 an Agent Access Code

 In your Edge account, create a scoped code with the products and budget you want.

 2 Give it to your agent

 Share the code and the URL https://edge.network/agent with your AI assistant.

 3 Agent discovers capabilities

 One API call tells the agent everything it can do, what limits exist, and what's already deployed.

 4 Agent deploys your app

 The agent creates storage, configures CDN, sets up DNS, and reports back with the live URL.

 5 Agent monitors and reports

 Ask your agent how things are going. It checks health, tracks costs, 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 — any agent that can run tools or make API calls

 CI/CD Pipelines

 GitHub Actions, GitLab CI, Jenkins — automate deployments with agent codes in your pipeline

 Custom Agents & Scripts

 LangChain, CrewAI, AutoGPT, 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=&#123;"Authorization": "Bearer ea_live_..."&#125;)

 # JavaScript
fetch("https://edge.network/agent", &#123;
 headers: &#123; Authorization: "Bearer ea_live_..." &#125;
&#125;)

 # 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 Permissions

 Deploy Manage Delete Budget Cap

 $50/month Soft cap Ready to let your agent build?

 Create an agent access code and start deploying in seconds.

Create Agent Code

Read the Docs

---

### AI/ML Infrastructure

URL: https://edge.network/solutions/ai/
JSON: https://edge.network/json/solutions/ai.json

_GPU compute at the edge for AI and ML workloads. Train models, run inference, and scale globally with low latency._

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

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

---

### Deploy Astro on Edge | Content-first sites at the edge

URL: https://edge.network/solutions/astro/
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 your trial

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

 # .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.

 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 your trial

Talk to an engineer

---

### Deploy Craft CMS on Edge | Premium PHP CMS for design-led teams

URL: https://edge.network/solutions/craft/
JSON: https://edge.network/json/solutions/craft.json

_Run Craft CMS 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,
production-grade and predictable

The premium PHP CMS for design-led teams, on real VMs with
 S3-compatible asset volumes and a global CDN. Servd-class
 infrastructure at a fraction of the cost.

Start your trial

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

 # Twig template — Craft asset → Edge Image URL

 <img

 src="https://cdn.example.com/&#123;&#123; asset.path &#125;&#125;?w=1200&fm=webp"

 srcset="https://cdn.example.com/&#123;&#123; asset.path &#125;&#125;?w=800&fm=webp 800w,

 https://cdn.example.com/&#123;&#123; asset.path &#125;&#125;?w=1600&fm=webp 1600w"

 alt="&#123;&#123; asset.title &#125;&#125;"

 >

 # Or use native transforms

 &#123;&#123; asset.getUrl({ width: 1200, format: 'webp' }) &#125;&#125;

 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.

 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

 30-day trial. Bring an existing Craft site or scaffold a new one — agency-friendly pricing all the way up.

Start your trial

Talk to an engineer

---

### Deploy Django on Edge | Python web apps without surprise bills

URL: https://edge.network/solutions/django/
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 your trial

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

 # /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.

 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

 30-day trial. Bring an existing project or start fresh.

Start your trial

Talk to an engineer

---

### Deploy Drupal on Edge | Enterprise PHP CMS, predictable bills

URL: https://edge.network/solutions/drupal/
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 your trial

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

 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.

 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

 30-day trial. Migrate a single site or a whole multi-site estate — Expert Services can plan and run it.

Start your trial

Have us migrate it

---

### Deploy Laravel on Edge | Production VMs, S3 storage and CDN

URL: https://edge.network/solutions/laravel/
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 your trial

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

 # 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.

 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

30-day trial of the full platform. Bring an existing site or start fresh — we'll help you size the VM and migrate the storage.

Start your trial

Talk to an engineer

---

### Deploy Magento Open Source on Edge | Enterprise PHP commerce

URL: https://edge.network/solutions/magento/
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 your trial

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

 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.

 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

 30-day trial. Migrate one store or a whole estate — Expert Services can plan and execute.

Start your trial

Have us migrate it

---

### Deploy Next.js on Edge | A self-hosted Next.js platform

URL: https://edge.network/solutions/nextjs/
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 your trial

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

 # 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/$&#123;src&#125;?w=$&#123;width&#125;&q=$&#123;quality||75&#125;`

 }

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.

 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

30-day trial of the full platform. Bring an existing app or start from scratch —
 we'll match your current performance and slash your bill.

Start your trial

Talk to an engineer

---

### Deploy Node.js on Edge | Express, Fastify, Hono — your runtime

URL: https://edge.network/solutions/nodejs/
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 your trial

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

 # 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.

 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

 30-day trial. Any framework, any runtime, any deploy strategy.

Start your trial

Talk to an engineer

---

### Deploy Nuxt on Edge | Vue-powered SSR on global VMs

URL: https://edge.network/solutions/nuxt/
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 your trial

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

 # 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.

 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

 30-day trial of the full platform. Bring an existing Nuxt app or scaffold a new one — we'll help you size the VM.

Start your trial

Talk to an engineer

---

### Deploy Payload on Edge | TypeScript-first headless CMS, Next.js-ready

URL: https://edge.network/solutions/payload/
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 your trial

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

 # 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.

 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

 30-day trial. Pair with our Next.js stack page for the full TypeScript story.

Start your trial

Talk to an engineer

---

### Deploy Rails on Edge | Classic VPS workflow, modern network

URL: https://edge.network/solutions/rails/
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 your trial

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

 # 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.

 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

 30-day trial. Bring your `bin/rails new` or your existing monolith.

Start your trial

Talk to an engineer

---

### Deploy Statamic on Edge | Flat-file Laravel CMS hosting

URL: https://edge.network/solutions/statamic/
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 your trial

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 control panel and the front-end through the Edge CDN. Public pages cached globally, control panel 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

 # Antler template — Edge image URL

 <img

 src= "https://cdn.example.com/&#123;&#123; asset:url &#125;&#125;?w=1200&fm=webp"

 srcset= "https://cdn.example.com/&#123;&#123; asset:url &#125;&#125;?w=800&fm=webp 800w,

 https://cdn.example.com/&#123;&#123; asset:url &#125;&#125;?w=1600&fm=webp 1600w"

 alt= "&#123;&#123; alt &#125;&#125;"

 >

 # Or stick with Glide tags — both work

 &#123;&#123; glide:hero_image width="1200" format="webp" /&#125;&#125;

 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 control panel 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.

 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

30-day trial of the full platform. Bring an existing site or scaffold a fresh one — flat-file or Eloquent, static or dynamic.

Start your trial

Talk to an engineer

---

### Deploy SvelteKit on Edge | Tiny, fast, Node-friendly hosting

URL: https://edge.network/solutions/sveltekit/
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 your trial

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

 # /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.

 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

 30-day trial. Bring your repo, deploy in minutes.

Start your trial

Talk to an engineer

---

### Expert Services

URL: https://edge.network/solutions/expert-services/
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

 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 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&#x27;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/
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 your trial

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

 # 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.

 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

 30-day trial. Move your storefront, keep your Shopify backend.

Start your trial

Talk to an engineer

---

### Media Management Solutions

URL: https://edge.network/solutions/media-management/
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 1,778 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 1,778 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 1,778

 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/
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
 1,778

 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

 1,778 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/
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 your trial

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.

 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

30-day trial of the full platform. Bring your compose file and let us run it close to your users.

Start your trial

Talk to an engineer

---

### Run Kubernetes on Edge | k3s and full k8s on real VMs

URL: https://edge.network/solutions/kubernetes/
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 your trial

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.

 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

30-day trial. Stand up a cluster in minutes — or have our Expert Services team architect and run it for you.

Start your trial

Have us run it

---

### Run llama.cpp on Edge | Quantised LLM inference, CPU or GPU

URL: https://edge.network/solutions/llama-cpp/
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 your trial

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.

 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

 30-day trial. CPU or GPU, your call.

Start your trial

Talk to an engineer

---

### Run Ollama on Edge | Self-host open LLMs on your own GPUs

URL: https://edge.network/solutions/ollama/
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 your trial

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.

 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

 30-day trial. Stand up a GPU VM, pull a model, hit the API in minutes.

Start your trial

Talk to an engineer

---

### Self-host BookStack on Edge | Open-source documentation platform

URL: https://edge.network/solutions/bookstack/
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 your trial

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`

 # 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.

 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

 30-day trial. Move off Confluence or stand up a fresh wiki.

Start your trial

Talk to an engineer

---

### Self-host ComfyUI on Edge | Node-based Stable Diffusion on GPU VMs

URL: https://edge.network/solutions/comfyui/
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 your trial

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.

 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

 30-day trial. Compute team can size the right GPU for your workflow.

Start your trial

Talk to an engineer

---

### Self-host Directus on Edge | Instant API over any database

URL: https://edge.network/solutions/directus/
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 your trial

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

 # 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.

 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

 30-day trial. Bring an existing database or scaffold a fresh project.

Start your trial

Talk to an engineer

---

### Self-host Ghost on Edge | Modern publishing without the cloud bill

URL: https://edge.network/solutions/ghost/
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 your trial

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

 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.

 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

 30-day trial. Migrate from Substack or stand up a fresh Ghost site — we'll help with the bootstrap.

Start your trial

Have us migrate it

---

### Self-host Medusa on Edge | Modern headless commerce, Node.js-native

URL: https://edge.network/solutions/medusa/
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 your trial

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

 # 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.

 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

 30-day trial. Bring an existing Medusa store or scaffold a new one with the official starter.

Start your trial

Talk to an engineer

---

### Self-host MongoDB on Edge | Document store with replica sets

URL: https://edge.network/solutions/mongodb/
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 your trial

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.

 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

 30-day trial. Migrate from Atlas or stand up a fresh replica set — Expert Services can plan the cutover.

Start your trial

Have us migrate it

---

### Self-host MySQL or MariaDB on Edge | Real VMs, real performance

URL: https://edge.network/solutions/mysql/
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 your trial

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 control panel.

 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.

 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

 30-day trial. Migrate from RDS or stand up a fresh primary — Expert Services can plan the cutover.

Start your trial

Have us migrate it

---

### Self-host n8n on Edge | Workflow automation without per-execution bills

URL: https://edge.network/solutions/n8n/
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 your trial

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.

 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

 30-day trial. Move off Zapier or Make and unlimited the executions.

Start your trial

Talk to an engineer

---

### Self-host Outline on Edge | Team wiki you actually own

URL: https://edge.network/solutions/outline/
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 your trial

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`

 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`.

 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

 30-day trial. Migrate from Notion, Confluence or Outline Cloud — Expert Services can help.

Start your trial

Have us migrate it

---

### Self-host Plausible Analytics on Edge | Privacy-first, GDPR-friendly

URL: https://edge.network/solutions/plausible/
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 your trial

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.

 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

 30-day trial. Move off GA or stand up a fresh analytics instance.

Start your trial

Talk to an engineer

---

### Self-host PostgreSQL on Edge | NVMe-backed Postgres without RDS markup

URL: https://edge.network/solutions/postgresql/
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 your trial

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.

 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

 30-day trial. Migrate from RDS or stand up a fresh cluster — Expert Services can plan the cutover.

Start your trial

Have us migrate it

---

### Self-host Redis (or Valkey) on Edge | In-memory cache and queue

URL: https://edge.network/solutions/redis/
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 your trial

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.

 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

 30-day trial. Migrate from Elasticache or stand up a fresh cache.

Start your trial

Talk to an engineer

---

### Self-host Saleor on Edge | Python + GraphQL headless commerce

URL: https://edge.network/solutions/saleor/
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 your trial

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

 # 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.

 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

 30-day trial. Bring an existing Saleor instance or scaffold one fresh.

Start your trial

Talk to an engineer

---

### Self-host Strapi on Edge | The leading open-source headless CMS

URL: https://edge.network/solutions/strapi/
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 your trial

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`

 # 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

 30-day trial. Bring an existing Strapi instance or scaffold one fresh.

 Start your trial

 Talk to an engineer

 }

---

### Self-host Umami Analytics on Edge | Lightweight, cookie-free

URL: https://edge.network/solutions/umami/
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 your trial

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.

 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

 30-day trial. Run analytics for unlimited sites on a $5 VM.

Start your trial

Talk to an engineer

---

### Self-host Vaultwarden on Edge | Bitwarden-compatible password manager

URL: https://edge.network/solutions/vaultwarden/
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 your trial

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.

 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

 30-day trial. A family or team vault on a $5 VM.

Start your trial

Talk to an engineer

---

### Self-host vLLM on Edge | Production-grade LLM serving

URL: https://edge.network/solutions/vllm/
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 your trial

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.

 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

 30-day trial. Compute team can help you size the GPU and architecture.

Start your trial

Talk to an engineer

---

### Self-host WooCommerce on Edge | Faster store, smaller bill

URL: https://edge.network/solutions/woocommerce/
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 your trial

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

 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 control panel.

 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.

 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

 30-day trial. Migrate one store, see the speed and savings before you commit anything else.

Start your trial

Have us migrate it

---

### Solutions

URL: https://edge.network/solutions/
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
 30 day trial 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

Solutions by Use Case

Purpose-built solutions for specific workloads and industries.

 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. 1,778 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

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

Trial Edge Today

---

### Solutions by Stack

URL: https://edge.network/solutions/stacks/
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

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/
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.

Trial Edge 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 WAF included. 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/
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.

 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.

 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

Create an Agent Code
 # Give your agent the URL and access code

 User: "Deploy my React app to portfolio.example.com"

 # Agent discovers capabilities

 GET /agent → 4 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
Learn more
 # 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 Trial

 30-Day Trial

Try the full platform with real infrastructure. See what Edge can do.

 VM, CDN, DNS & Storage access
 Full API & CLI access
 Zero egress fees
 Real support from real humans

Start your trial

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/
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

Trial Edge 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

Trial Edge 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 Startups

URL: https://edge.network/solutions/startups/
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

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 security best practices built-in. No additional cost or configuration.

 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

 1,778

 Edge locations

 0

 Egress fees

Ready to build the next big thing?

Infrastructure that scales with your ambition. Start your 30-day trial today.

Start Your Trial

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/
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 your trial

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

 # .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.

 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 your trial

Talk to an engineer

---

### WordPress hosting on Edge | Fast, cheap, zero egress

URL: https://edge.network/solutions/wordpress/
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 your trial

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

 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.

 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 your trial

Have us migrate it

---

## Case Studies (Optional)

### Bauer Media Case Study

URL: https://edge.network/case-studies/bauer/
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.

Trial Edge Today

Contact Sales

---

### Case Studies

URL: https://edge.network/case-studies/
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 1,778

 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

Ready to join them?

Start your 30-day trial and see why leading organisations choose Edge.

Trial Edge Today

Contact Sales

---

### Code+Ink Case Study

URL: https://edge.network/case-studies/code-ink/
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.

Trial Edge Today

Contact Sales

---

### Ecohustler Case Study

URL: https://edge.network/case-studies/ecohustler/
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

 1,778

 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.

Trial Edge Today

Contact Sales

---

### IGD Case Study

URL: https://edge.network/case-studies/igd/
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.

Trial Edge Today

Contact Sales

---

### Minima Case Study

URL: https://edge.network/case-studies/minima/
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

 1,778

 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 1,778 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.

Trial Edge Today

Contact Sales

---

### Monocle Case Study

URL: https://edge.network/case-studies/monocle/
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 1,778 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.

Trial Edge Today

Contact Sales

---

### Tinder Case Study

URL: https://edge.network/case-studies/tinder/
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

 1,778

 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 1,778 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

 Ready to get started?

 Join Tinder and thousands of other organisations using Edge.

Trial Edge Today

Contact Sales

---

### XCOPY Case Study

URL: https://edge.network/case-studies/xcopy/
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

 1,778

 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 1,778 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.

Trial Edge Today

Contact Sales

---

## Blog (Optional)

### A Fairer Internet

URL: https://edge.network/blog/a-fairer-internet/
JSON: https://edge.network/json/blog/a-fairer-internet.json

_The network that powers our new digital society should be in the hands of the many, not the few._

Blog
 | Company
3 min read
 A Fairer Internet

 The network that powers our new digital society should be in the hands of the many, not the few.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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.

 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 Revolutionizing Content Delivery: The Integration of Edge Computing in CDN Technology

 How edge computing is reshaping the CDN paradigm — and how Edge is at the forefront of this change.

 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 tech strategy and philosophy for Edge Network and how all roads 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

 Switch to Edge Network and save up to 90% on your content delivery costs.

 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 could save you up to 90% on your digital infrastructure. Think about that next time you pay your bill.

 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

 The network that powers our new digital society should be in the hands of the many, not the few.

 Will Lebens
Read more
Exclusive Offer

Two Months Free

Start with a 30-day trial, then get two months free on any plan. Use promo code EDGE2FREE at checkout.

Start Your Trial
 EDGE2FREE 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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 and Web3

URL: https://edge.network/blog/edge-and-web3/
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?_

Blog
 | Engineering
4 min read
 Edge and Web3

 Edge is the infrastructure of Web3 — but what is Web3 and why does it matter?

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/blockv-partnership.json

_Edge and BLOCKv partner to bring fully decentralized cloud infrastructure to the largest Web3 enterprise layer._

Blog
 | Partnership
6 min read

Edge Network Partner With BLOCKv: Unlocking True Decentralization For The Largest Web3 Enterprise Layer

Unlocking True Decentralization For The Largest Web3 Enterprise Layer.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 the impact of decentralized hosting platforms on our environment.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/future-cdn-today.json

_Switch to Edge Network and save up to 90% on your content delivery costs._

Blog
 | Product
2 min read
 Future CDN, Today

 Switch to Edge Network and save up to 90% on your content delivery costs.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/hosting-the-future.json

_Running a blockchain project? Want to host for free on Edge Network?_

Blog
 | Community
2 min read
 Hosting the Future

 Running a blockchain project? Want to host for free on Edge Network?

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/decentralization-cloud-storage-security.json

_Decentralized cloud storage offers a more secure alternative to traditional centralized solutions._

Blog
 | Engineering
4 min read

How Decentralization Enhances Cloud Storage Security

Decentralized cloud storage: a more secure alternative than traditional, centralised solutions.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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. Hidden fees, complex pricing, and punitive egress charges are turning strategic investments into financial burdens.

 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 $2.50

 If you're tired of unpredictable cloud bills and restrictive pricing models, it's time to explore a better way. Edge Network offers a low-risk entry point with a trial for just $2.50, 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 starting your $2.50 trial at edge.network/account . Experience the future of cloud computing — decentralised, transparent, and built for your success.

 Exclusive Offer Two Months Free After Trial

 Start ...

---

### Revolutionizing Content Delivery: The Integration of Edge Computing in CDN Technology

URL: https://edge.network/blog/edge-computing-in-cdn-technology/
JSON: https://edge.network/json/blog/edge-computing-in-cdn-technology.json

_How edge computing is reshaping the CDN paradigm with hyper-local peering, reduced latency and intelligent caching._

Blog
 | Engineering
4 min read

Revolutionizing Content Delivery: The Integration of Edge Computing in CDN Technology

In the digital era, the speed and efficiency of content delivery are paramount.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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.

---

### Setting the Stage for Q2 Success with Edge Network

URL: https://edge.network/blog/q2-success-edge-network/
JSON: https://edge.network/json/blog/q2-success-edge-network.json

_As Q2 begins, ensure your infrastructure can keep up with your vision. 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

As the calendar flips to April, businesses worldwide are gearing up for the second quarter. Ensure your infrastructure can keep up with your vision.

 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 $2.50 Trial

 There's no better time to experience the power of decentralised cloud than at the start of Q2. To help you hit the ground running on April 1st, we're offering a special trial for just $2.50 . This gives you full access to Edge Network's suite of services, from scalable compute to secure storage, so you can test our platform risk-free and see the difference for yourself.

 With this trial, 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? Sign up for our $2.50 trial now and discover why Edge Network is the leading alternative to AWS, GCP, and Azure. Visit edge.network/account to get started today.

 In this article

 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/
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?_

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?

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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: a system that 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/cloud-downtime-costs.json

_Cloud downtime can cost businesses up to £400,000 per hour. Discover how Edge Network's decentralised cloud guarantees 100% uptime._

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 with a $2.50 Trial

 Stop gambling on uptime. See for yourself how decentralised infrastructure eliminates the hidden cost of cloud downtime. Start your trial at edge.network/account — full access to Compute, CDN, DNS and Storage for just $2.50.

 Exclusive Offer Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/the-local-global-network.json

_Edge is a global network, locally sourced: our nodes are in homes and offices everywhere._

Blog
 | Network
2 min read
 The Local, Global Network

 Edge is a global network, locally sourced: our nodes are 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/the-network-that-works-for-you.json

_Edge could save you up to 90% on your digital infrastructure._

Blog
 | Company
2 min read
 The Network That Works for You

 Edge could save you up to 90% on your digital infrastructure.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/the-network-under-your-nose.json

_We don't need massive, dedicated server farms. 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. 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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&#39;s Next

URL: https://edge.network/blog/the-new-path-for-edge/
JSON: https://edge.network/json/blog/the-new-path-for-edge.json

_We never stopped building. Here's what's live today — a fully rebuilt decentralised cloud platform — and a first look at what comes next with XE._

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 subscription 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. Five subscription tiers, all features bundled, 25% or more in savings versus per-service pricing, an...

---

### The Offset Network

URL: https://edge.network/blog/the-offset-network/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
JSON: https://edge.network/json/blog/edge-computing-decentralized-world.json

_The concept of decentralization is prompting a shift away from centralized systems towards distributed computing._

Blog
 | Engineering
4 min read

Understanding Edge Computing in a Decentralized World

The concept of decentralization has been permeating various spheres of technology, prompting a shift away from centralized systems towards a more distributed model.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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.

 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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 delve into how decentralized computing offers the solution to this looming crisis.

 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

Two Months Free After Trial

Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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 a...

---

### Why We Open Source

URL: https://edge.network/blog/why-we-open-source/
JSON: https://edge.network/json/blog/why-we-open-source.json

_The tech strategy and philosophy for Edge Network and how all roads lead to DAO._

Blog
 | Engineering
3 min read
 Why We Open Source

 The tech strategy and philosophy for Edge Network and how all roads 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 Two Months Free After Trial

 Start with a 30-day trial for $2.50, then get two months free on any plan. Full access to Compute, CDN, DNS and Storage with zero egress fees.

Start Your Trial
 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/
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. 1,778 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

 1,778

 Edge Locations

 0

 New Data Centers

 50%

 Shorter Data Paths

 Our Journey

From founding to enterprise-ready in seven years.

 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.

 2024 Compute Launch

 Introduced edge compute with VM support.

 2025 Enterprise Ready

 Full enterprise feature set with SLA guarantees.

 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, and Storage),
 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/
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 not actively hiring, but exceptional people should still 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/
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.

 First Name Last Name Email Subject Sales inquiry Technical support Partnership Press inquiry Other Message
Send Message

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 Network Surpasses 2,500 Active Nodes

URL: https://edge.network/latest/active-nodes/
JSON: https://edge.network/json/latest/active-nodes.json

_A milestone for decentralized infrastructure as our network continues to grow with 2,500 active nodes across 130+ countries._

Back to Latest

Network

Jan 5, 2026

Edge Network Surpasses 2,500 Active Nodes

A milestone for decentralised infrastructure as our network continues to grow,
 powered by operators worldwide.

 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.

---

### Enterprise SLA Now Available

URL: https://edge.network/latest/enterprise-sla/
JSON: https://edge.network/json/latest/enterprise-sla.json

_Edge Network Enterprise SLA is now generally available. 99.99% uptime guarantee with dedicated support and custom SLA options._

Back to Latest

Product

Jan 19, 2025

Enterprise SLA Now Available

We're excited to announce general availability of our Enterprise Service Level Agreement,
 offering 99.99% uptime guarantees and 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/
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

 1,778

 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 1,778 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.

Trial Edge 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/
JSON: https://edge.network/json/features.json

_Explore all Edge Network features. CDN, Compute, DNS, and Storage with global edge infrastructure._

PLATFORM

Infrastructure built for the edge

A complete platform for deploying, scaling, and managing modern applications
 at the edge of the network.

 Our Products

Four core services designed to work together seamlessly.

 Global content delivery in milliseconds Content Delivery Network

 Deliver static and dynamic content from 1,778 edge locations worldwide. Automatic SSL, instant cache purging, and real-time analytics.

Get Started

Learn More
Key Features

 1,778 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

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

 1,778 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

Ready to get started?

Deploy your first resource in minutes with a 30-day trial.

Trial Edge Today

View Pricing

---

### Latest News

URL: https://edge.network/latest/
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.

 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/
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. $2.50/month. 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 &mdash; all from your editor. Zero egress. No enterprise bloat.

Create Agent Access Code &mdash; Start 30-Day Trial

Read the Agent API Docs

Works with Cursor, Claude Code, Windsurf, and any AI assistant that makes HTTP calls &bull; $2.50/month after trial &bull; Cancel anytime

 AI Agent Session User: "Deploy my React app to portfolio.test.network"

 # Agent discovers capabilities

 GET /agent &rarr; 4 products, $47 budget remaining

 # Agent deploys

 POST /agent/storage/buckets &rarr; Created

 POST /agent/cdn/deployments &rarr; Deployed

 POST /agent/dns/zones/.../records &rarr; 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 &mdash; App built in your AI editor. Time to deploy.

 0:05 &mdash; Leave editor. Open hosting dashboard.

 0:15 &mdash; Create project, upload files, configure build.

 0:25 &mdash; Switch to DNS provider. Add CNAME. Wait.

 0:40 &mdash; SSL broken. Debug certificates.

 0:55 &mdash; Finally live&hellip; but you've lost all context. What were you even building?

 With Edge Agent API

 0:00 &mdash; App built. Tell your agent: "Deploy this to my-project.test.network"

 0:03 &mdash; Agent connects, discovers capabilities.

 0:08 &mdash; Storage created, files uploaded, CDN configured, DNS + SSL set up.

 0:15 &mdash; "Your site is live at https://my-project.test.network with CDN and automatic SSL. ~$2.80/month."

 0:16 &mdash; You keep coding. Flow unbroken.

 45 minutes of context-switching &rarr; 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 dashboard, 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

 Paste the code + https://edge.network/agent into Cursor, Claude Code, or any AI coding tool.

 3 Agent discovers capabilities

 One API call &mdash; it learns available resources, limits, and existing deployments. No docs, no manual config.

 GET /agent &rarr; &#123; "products": ["compute", "cdn", "dns", "storage"], "budget_remaining": "$47.00" &#125; 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?" &mdash; 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 &mdash; a plain English summary your agent can relay directly to you.

 Project-based resources Errors as guidance Zero egress fees Automatic SSL Try everything for $2.50. No bloat.

 Your first month is $2.50 with full access to every product. Most developers run their first real deploy for under $3. You control the budget cap from day one.

 $2.50 /month 30-day trial with full access

VM, CDN, DNS & Storage access

Full Agent API + CLI access

Zero egress fees

Budget caps & scoped permissions

Real support from real humans

Start 30-Day Trial
 Cancel anytime. No lock-in.

 Common questions from developers

 What AI coding tools does it work with?

 Any that can make HTTP calls. Cursor, Claude Code, Windsurf, Aider, custom scripts, LangChain agents &mdash; no SDK required. If it speaks HTTP, it works.

 Is the $2.50/month the real price?

 Yes &mdash; after the 30-day trial. Zero egress fees. Pay only for the resources you use. 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 dashboard. You stay in control at all times.

 Do I need a custom domain?

 No. Use free test.network subdomains instantly ($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 dashboard.

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 &mdash; Start Free Trial
 $2.50 first month &bull; Zero egress &bull; Cancel anytime

---

### Network

URL: https://edge.network/network/
JSON: https://edge.network/json/network.json

_Global edge network with 1,778 PoPs, 10+ Tbps capacity, and sub-50ms latency worldwide. Built for performance and reliability._

Network

Global Edge Network

 1,778 points of presence across 130+ countries. Built for performance at scale,
 with direct peering to major carriers and ISPs worldwide.

 1,778

 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 and cache servers deployed directly inside ISP networks — combined with
 real-time latency-based routing and direct access to thousands of ISPs to deliver
 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

 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?

Start your 30-day trial 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/
JSON: https://edge.network/json/latest/new-regions-middle-east-and-africa.json

_Edge CDN expands to the Middle East and Africa with 186 new points of presence across 10 cities for faster content delivery._

Back to Latest

Network

Dec 1, 2025

New Regions: Middle East and Africa Expansion

Expanding Edge CDN to underserved regions with 186 new points of presence
 across the Middle East and Africa for faster content delivery.

 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 included in your existing plan 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/
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: January 2026

 1. Introduction

Edge Network Limited ("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. 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
 4. 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
 5. 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.

 6. 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 .

 7. 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 8. Cookies

We use cookies and similar tracking technologies to collect and track information about
 your activity on our services. You can control cookies through your browser settings.

 9. 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.

 10. 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.

 11. 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
JSON: https://edge.network/json/r.json

Referral Redirect | Edge
 Redirecting...

---

### Releases

URL: https://edge.network/releases/
JSON: https://edge.network/json/releases.json

_Product releases, updates, and changelog for Edge Network services including CDN, Compute, DNS, and Storage._

Releases

Changelog

Track new features, improvements, and updates across all Edge products.

 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 control panel, 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 control panel.

 Pre-built script library: Docker, Node.js, LAMP, LEMP, WordPress, PostgreSQL, Redis, Python, Hardened SSH
 Custom scripts with parameterised inputs for reusable provisioning
 Scripts run automatically on first boot with real-time execution tracking
 Script status and output visible on VM detail page
 v2.8.0 Jan 28, 2026 Feature CDN Regional Distribution Analytics

 Traffic distribution is now tracked per-region based on CDN node location, providing insights into where your content is being served from without GeoIP overhead.

 New Geo Distribution tab showing traffic breakdown by region
 Seven global regions: North America, Latin America, Europe, MEA, East Asia, South Asia, and China
 Region-based analytics stored and aggregated for historical viewing
 v2.7.0 Jan 20, 2026 Security CDN Set-Cookie Cache Protection

 This security enhancement ensures that responses containing Set-Cookie headers are never cached, protecting user sessions and preventing authentication tokens from being shared between users.

 Responses with Set-Cookie headers now automatically bypass cache
 Prevents session and cookie leakage between users
 Follows industry best practices (Cloudflare-compatible behavior)
 v2.6.0 Jan 15, 2026 Feature Platform Activity Audit Log

 The new Activity tab in your account provides a comprehensive audit trail of all actions across your Edge resources, essential for compliance and troubleshooting.

 Unified activity log aggregating events across all products
 Track account actions: password changes, plan upgrades, payments
 Filter by product: CDN, Compute, or view all activity
 Fixed-height container with lazy loading for performance
 v2.5.0 Jan 10, 2026 Security Platform Two-Factor Authentication

 Secure your Edge account with industry-standard TOTP authentication. Compatible with Google Authenticator, Authy, and other authenticator apps.

 TOTP-based two-factor authentication
 Recovery codes for account recovery
 Session management with device tracking
 Active sessions view with revocation
 v2.4.0 Jan 5, 2026 Feature Compute Automated VM Backups

 Never lose data again. Configure automated backup schedules for your VMs with flexible retention policies and instant restore capabilities.

 Scheduled automatic backups for virtual machines
 Configurable retention: daily, weekly, monthly
 One-click restore from any backup point
 Background job processing with status tracking
 v2.3.0 Dec 20, 2025 Feature CDN Cache Pause Mode

 The new Cache Pause feature allows you to temporarily bypass the cache entirely, making it easier to debug origin issues or test changes without waiting for cache expiration.

 Instantly switch CDN to proxy mode for debugging
 All requests pass through to origin
 One-click resume to restore normal caching
 Useful for troubleshooting cache issues
 v2.2.0 Dec 15, 2025 Feature CDN JIT Image Processing

 Process images on-the-fly at the edge. Resize, convert formats, and optimize quality without pre-processing—all cached for subsequent requests.

 Real-time image resizing and format conversion
 WebP and AVIF automatic format negotiation
 Quality adjustment with configurable defaults
 BlurHash placeholder generation
 v2.1.0 Dec 1, 2025 Product DNS DNS Management

 Complete DNS hosting with sub-second propagation. Manage your domains with our intuitive interface or programmatically via API.

 Full DNS zone management
 Support for A, AAAA, CNAME, MX, TXT, SRV records
 Instant propagation across edge network
 DNSSEC support
 v2.0.0 Nov 15, 2025 Product Compute Edge Compute Launch

 Deploy VMs at the edge with full control over resources. Choose from popular Linux distributions and scale resources as needed.

 Virtual machine deployment
 Multiple OS templates: Ubuntu, Debian, AlmaLinux, Rocky
 Flexible resource allocation: vCPU, RAM, storage
 SSH key and security group management
 Stay Updated

Subscribe to release notes and be the first to know about new features and improvements.

Subscribe

---

### Roadmap

URL: https://edge.network/roadmap/
JSON: https://edge.network/json/roadmap.json

_See what's coming next for Edge Network. Our product roadmap for CDN, Compute, DNS, Storage, 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

Current Quarter
 DNS Examiner

 Completed AI-powered zone analysis checking email deliverability, security, nameservers, and best practices. Available in control panel, 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 Cloudflare-style network speed test at speed.edge.network. Download, upload, latency, and jitter measurements.

 Platform Q2 2026

 DDoS Protection + WAF

 Planned Layer 3/4/7 DDoS mitigation and web application firewall, integrated with CDN. Managed WAF rules, bot detection, and real-time attack dashboard.

 CDN DNS Synthetic Monitoring

 Planned Global uptime and performance monitoring from residential locations. HTTP, API, SSL, and DNS checks from 2,000+ edge hosts worldwide.

 Monitoring Container Registry

 Planned Private Docker/OCI container image registry built on Edge Storage. Vulnerability scanning and pull-through caching.

 Storage AI Platform Features

 Planned CDN Optimiser, Firewall Advisor, Setup Script Generator, Incident Explainer, Cost Advisor, and Migration Assistant — all AI-powered, built into the control panel.

 AI Platform Q3 2026

 Managed Databases

 Planned Hosted PostgreSQL, MySQL, and Redis with automated backups, failover, and point-in-time recovery.

 Compute Storage Video Platform

 Planned Video hosting, transcoding, and adaptive streaming. Distributed transcoding via edge hosts. Zero egress delivery.

 CDN Storage Compute AI Gateway

 Planned API gateway for AI applications — model routing, semantic caching, rate limiting, cost management, and observability at the edge.

 AI CDN Q4 2026

 Domain Registration

 Planned Register domains directly from Edge. Automatic nameserver configuration, WHOIS privacy included, seamless DNS setup.

 DNS 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/
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/
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 &mdash; 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 &mdash;
 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 &mdash; 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 &mdash; building the agentic cloud.

&ldquo;The cloud in 2026 is agentic, efficient, and inclusive. Delegate to agents, and elevate your vision.&rdquo;

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 &mdash; 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/
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 an account, complete the $2.5 trial, 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?

 Yes, trial fees are fully refundable within 30 days if you're not satisfied.

 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/
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

 API

 REST API endpoints

 Dashboard

 Web dashboard and 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/
JSON: https://edge.network/json/terms.json

_Edge Network terms of service. Service level agreements, acceptable use, and payment terms._

Legal

Terms of Service

Last updated: January 2026

 1. Acceptance of Terms

By accessing or using Edge Network Limited'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, and object storage services. The specific features and
 functionality available to you depend on your subscription plan.

 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
 ✕ Host or distribute illegal content
 ✕ Resell or redistribute the Services without authorisation
 5. Fair Use Policy

Edge Network subscription plans include generous resource allocations, including unlimited bandwidth
 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 your subscription tier.
 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 for your plan tier

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 upgrading your plan 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 Enterprise customers

Enterprise customers on pay-as-you-go plans are not subject to fair use limitations on metered resources.
 Usage is billed at the agreed rates without volume restrictions. Fair use provisions relating to
 prohibited activities (Section 4) still apply.

 6. Payment Terms

Certain Services require payment. By subscribing to paid Services, you agree to pay all
 applicable fees. Fees are non-refundable except as expressly stated in these Terms or
 required by law.

 Subscription fees are billed in advance Usage-based charges are billed in arrears We may change pricing with 30 days' notice Late payments may result in suspension 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. Current
 SLA commitments vary by plan and are detailed in your subscription agreement.

 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.

 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. Contact

For questions about these Terms, please contact us:

legal@edge.network

---

### Zero Egress: Why We Don&#39;t Charge for Bandwidth

URL: https://edge.network/latest/zero-egress/
JSON: https://edge.network/json/latest/zero-egress.json

_Our philosophy on transparent pricing and why egress fees are a thing of the past. Learn why Edge Network offers zero egress fees._

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.

---