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:
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).
2. Add a custom domain
Add your domain to the deployment. Edge will automatically provision an SSL certificate.
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.
4. Verify it's working
Once DNS propagates (usually within a few minutes), your content will be served through Edge's CDN.
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.
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.
3. Deploy your app
Once connected, install your dependencies and deploy. Here's a quick example with Docker:
4. Monitor
Check on your VM from the CLI or the control panel.
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 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:
4. Verify
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
2. Upload files
Upload individual files or entire directories.
3. List and manage
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.