Deploy now
New Edge Functions v3: live in 38 regions

Edge hosting that deploys in seconds.

Push to git and Nimbus builds, optimises and ships your app to 112 edge locations, with a preview URL for every branch and rollbacks that take one keystroke.

Start deploying for free Read the docs
npm i -g @nimbus-stack/cli
~/quillstack/docs git:(main) $ nimbus deploy --prod
◆Nimbus CLI 4.12.0
›Linked to quillstack/docs (team: quillstack)
›Uploading 284 files3.1 MB
›Detected Next.js 15 · installing with pnpm
✓ Dependencies installed1.2s
✓ Compiled successfully2.1s
✓ Generated 48 static pages0.4s
✓ Bundled 3 edge functions0.2s
✓ Propagated to 112 edge locations0.6s
✓ Deployed to production4.1s
→https://docs.quillstack.examplecopied

46,000 teams ship on Nimbus, from weekend side projects to public companies

  • Quillstack
  • orbitly
  • Fernway
  • Kitebase
  • halcyon_labs
  • Tessellate
  • Morrow
  • Lumafold
01Platform

From git push to global. Nothing in between.

Nimbus watches your repository, builds every commit in an isolated container and serves the result from the location closest to each visitor. No servers to patch, no CDN to configure, no YAML.

A global edge, on by default

Every request is answered by the nearest of 112 locations. Static assets and cached responses never touch your origin. A visitor in Lisbon is served from Madrid in single-digit milliseconds.

Instant rollbacks

Every deploy is kept. Point production at any previous build in under 300 ms. No rebuild, no cache purge, no downtime.

A preview URL for every push

Each branch and pull request gets its own live URL with comments, so reviewers click a link instead of pulling a branch.

Serverless & edge functions

Drop a file in /api and it’s a function. Run it at the edge with no cold starts, or pin it beside your database.

DDoS protection, included

Layer 3–7 mitigation is always on and never billed. Attack traffic is dropped at the edge before it reaches your functions.

Real-user analytics

Core Web Vitals from real visitors, broken down by route, device and region. Cookieless and privacy-friendly, so there’s no consent banner to add.

Domains & certificates

Point a domain and HTTPS is issued, renewed and stapled for you. Apex, subdomains and wildcards are all included.

02Edge network

One deploy. 112 cities. Under five seconds.

Deploys are immutable and atomic: static assets, edge functions and config land everywhere together, so no visitor ever sees half a release. Pick where you push from and watch it fan out.

Deploy from

Propagated from San Francisco (SFO) to 112 locations in 4.1 s

Live deploy propagation

Edge locations include: SFOSEADFWORDIADYYZMEXBOGGRUSCLLHRCDGFRAARNMADWAWLOSNBOJNBDXBBOMSINHKGICNHNDPERSYDAKL+84 more

Edge locations
112
Compute regions
38
Countries served
46
Network capacity
340 Tbps
03Performance

Fast for every visitor, not just the ones near Virginia.

Numbers from the last 30 days across every production deployment on the platform.

38ms

Global p50 time to first byte

4.1s

Median production deploy, push to live

98.7%

Average edge cache hit ratio

0ms

Cold starts on edge functions, vs 400 ms+ for containers

Time to first byte, p75

Same Next.js app, measured from real visitors by region

North America
Nimbus: 29 ms
Single-region origin: 88 ms
Europe
Nimbus: 34 ms
Single-region origin: 142 ms
South America
Nimbus: 51 ms
Single-region origin: 226 ms
Asia Pacific
Nimbus: 46 ms
Single-region origin: 287 ms
Africa & Middle East
Nimbus: 63 ms
Single-region origin: 318 ms
4.6×

faster time to first byte, averaged across regions1.2M real-user sessions · Sep 2026

All systems operational

Uptime over the last 60 days · updated 2 minutes ago

Edge network100.000%
Builds & deploys99.981%
Serverless functions99.994%
Dashboard & API100.000%
View status history
04Developer experience

Zero config for the frameworks you already use.

Nimbus reads your project, picks the right build, caches what it can and wires up routing. When you do want control, it’s one small file, not a pipeline.

  • Framework detection for 35+ frameworks: builds tuned per framework, not per guess.
  • Encrypted environment variables: scoped to production, preview or a single branch.
  • Monorepo-aware builds: only rebuild the apps a commit actually touched.
  • Logs you can tail: nimbus logs --follow streams every region.
  • Next.js
  • Astro
  • SvelteKit
  • Nuxt
  • Remix
  • Eleventy
  • Vite
  • Hugo
  • and +27 more
nimbus.json (optional: Next.js is detected automatically)
{  "framework": "nextjs",  "regions": ["all"],  "functions": {    "app/api/**/*.ts": { "runtime": "edge" },    "app/api/billing/*.ts": { "region": "fra", "memory": 512 }  },  "headers": [    { "source": "/_next/static/(.*)", "cache": "immutable" }  ],  "previews": { "comments": true, "protect": "team" }}
Deploys with: nimbus deploy Build cache hit · 2.3s
05Customers

Teams ship more when deploys stop being an event.

QuillstackCase study
We moved 40 marketing sites off a self-managed Kubernetes cluster in a weekend. Deploys went from eleven minutes to six seconds, and our hosting bill dropped by almost two thirds.
Meera VasudevanStaff Engineer, Quillstack
11m → 6sMedian deploy time
−62%Monthly infrastructure spend
40 sitesMigrated in one weekend
Fernwaypreview-urls
Preview URLs changed how our design team reviews work. There’s a clickable link on every pull request before CI has even finished.

148 preview deploys a week

Tomás FerreiraFrontend Lead, Fernway
Kitebaseddos
We absorbed a 1.8 Tbps flood during a product launch and the status page stayed green. I found out from the weekly report.

peak 1.8 Tbps · 0 requests dropped

Hana BrightwaterSite Reliability Engineer, Kitebase
orbitlyrollbacks
Rollbacks are one keypress and take less time than reading the error message. That alone justified the Pro plan for us.

rollback in 280 ms · downtime 0 s

Jonas VeldkampCTO, Orbitly
halcyon_labsedge-network
Our p75 time to first byte in Southeast Asia went from 410 ms to 46 ms without changing a single line of application code.

TTFB SEA 410 ms → 46 ms

Mei-Lin ChuaPlatform Engineer, Halcyon Labs
Tessellatefunctions
We pinned our functions to Frankfurt for data residency and kept static assets global. It was one line in nimbus.json.

functions fra1 · assets global

Anke VosEngineering Manager, Tessellate
marchetti.examplecli
The best CLI I’ve used. It tells you exactly what it’s doing, then gets out of the way. I deploy from my phone’s terminal on the train.

212 deploys last month · 9 projects

Dev MarchettiIndependent developer
06Pricing

Start free. Scale when your traffic does.

Hobby

For personal projects, experiments and learning in public.

$0forever

No credit card required

Start for free
  • Unlimited static sites
  • 100 GB bandwidth / month
  • Preview URL for every push
  • 100k function invocations
  • Community forum support

Pro

Most popular

For teams shipping production apps that real customers depend on.

$20/ member / month

Billed monthly · cancel anytime

Start a 14-day trial
  • Everything in Hobby, plus:
  • 1 TB bandwidth included
  • 1M function invocations
  • Instant rollbacks & deploy protection
  • Real-user analytics & Web Vitals
  • Spend caps per project
  • Email support, 24-hour response

Enterprise

For organisations with serious scale, security and compliance needs.

Custom

Annual contract · volume pricing

Talk to sales
  • 99.995% uptime SLA
  • Dedicated edge capacity
  • SSO / SAML, SCIM & audit logs
  • Custom WAF & advanced DDoS rules
  • EU / US data residency
  • 24/7 support, 15-minute response

Automatic HTTPS Global edge network Git integration DDoS protection on every plan

07FAQ

Questions, answered.

Can’t find what you need? Our engineers answer the support queue themselves.

4 engineers on shift
11 minmedian first reply
94%solved in one reply
Email support@nimbus.example or call (555) 014-2290, weekdays 8am–6pm PT.
Which frameworks does Nimbus support?
Nimbus detects 35+ frameworks automatically, including Next.js, Astro, SvelteKit, Nuxt, Remix and Eleventy. Anything that outputs static files works too: give us a build command and an output directory and we’ll do the rest.
How is bandwidth billed if I go over my plan?
Hobby projects are paused at the limit rather than billed, so you’ll never get a surprise invoice. On Pro, additional bandwidth is $0.06 per GB, and you can set a hard spend cap on every project.
Can I use my own domain and certificates?
Yes. Add any apex domain, subdomain or wildcard. TLS certificates are issued and renewed automatically, and Enterprise teams can upload their own certificates.
What happens if a deploy breaks production?
Every deploy is immutable, so rolling back is instant: pick any previous deployment and promote it, or press R in the dashboard. You can also turn on deploy protection to require passing checks before a build goes live.
Where is my data processed and stored?
Static assets are cached globally. Functions run in the region you choose, and builds, logs and function execution can be pinned to the EU or US for data-residency requirements.
Do you offer discounts for open source and education?
Open-source projects and accredited schools get Pro free for a year. Email oss@nimbus.example with a link to your repository or course page.
Get started

Your next deploy is four seconds away.

Import a repository, or run one command from any project folder. Free for personal projects, forever.

Start deploying for free Talk to an engineer
npx @nimbus-stack/cli deploy
  1. 1Connect

    Import a repository

    Nimbus detects your framework and build.

    $ nimbus link quillstack/docs
  2. 2Push

    Push a branch

    Every commit gets a shareable preview URL.

    $ git push origin feat/launch
  3. 3Ship

    Promote to production

    Live in 112 cities, with a one-key rollback.

    $ nimbus promote --prod