What is Nept (nept.cloud)?
Updated
Nept is a cloud platform for developers to deploy, host, and scale frontend and full-stack applications. You connect a Git repository, push code, and Nept builds and deploys it automatically to a global edge network. It's aimed at developers and teams who want to ship applications without managing servers or configuring DevOps pipelines.
How Nept works
The workflow is built around Git pushes rather than manual deployment steps:
- Push your code — Connect a repository from GitHub, GitLab, or Bitbucket. Every push triggers an automatic build.
- Auto-deploy — Nept builds, optimizes, and deploys the app. The site cites builds completing in seconds (for example, "done in 4.2s") using content-addressed caching and remote build workers.
- Go global — The app goes live on edge nodes without extra configuration, so users are served from locations close to them.
- Preview and iterate — Every branch gets its own preview URL (e.g.,
feat-xyz.app.nept.cloud) for team review before merging to production.
What you can deploy
Nept is framework-agnostic. According to the site, it auto-detects build settings for major frameworks including Next.js, Svelte, Astro, Remix, and Qwik, and supports custom Dockerfiles for everything else. The platform describes itself as supporting frameworks, containers, and edge functions through one deploy pipeline.
Core features
| Feature | What it does |
|---|---|
| Smart Builds | Incremental builds with content-addressed cache, remote build workers, and automatic asset optimization |
| Edge Functions | Lightweight TypeScript functions deployed globally in one command, suited to auth, personalization, A/B tests, and low-latency APIs |
| Framework support | Auto-detected build settings for major frameworks; custom Dockerfile support otherwise |
| Security | Automatic TLS certificates on every domain, DDoS mitigation, and a managed WAF included by default |
| Serverless scaling | Cold starts under 30ms, elastic concurrency, and pay-per-request pricing |
| Global edge | Real workloads across three regions: US-East (Ashburn), EU-West (Paris), and AP-South (Mumbai) |
The site reports region latency of 38 ms (US-East), 44 ms (EU-West), and 52 ms (AP-South), with uptime figures of 99.998%, 99.996%, and 99.994% respectively.
Who Nept is for
Nept targets developers and teams who want to ship frontend or full-stack applications quickly without handling infrastructure. It fits well if you:
- Already use Git-based workflows and want push-to-deploy
- Want preview environments per branch for team review
- Need edge functions for auth, personalization, or A/B testing
- Prefer pay-per-request serverless scaling over provisioning servers
It's less relevant if you need deep control over underlying infrastructure or have requirements outside the supported framework and container model.
Pricing
Nept lists a pricing page at nept.cloud/pricing. The available material does not specify plan details, costs, or whether a free tier exists, so check that page directly for current terms.