What You Can Deploy on Nept (nept.cloud)

Nept is a framework-agnostic deployment platform, so you can ship almost any frontend, full-stack, or containerized app as long as it builds from a Git repository or a Dockerfile. If your project is a Next.js, Svelte, Astro, Remix, or Qwik app, or anything that fits in a Docker container, Nept can host it. The main condition is that your code lives in GitHub, GitLab, or Bitbucket, since every deployment is triggered by a git push.

Frameworks and app types Nept supports

Nept auto-detects build settings for major frameworks and falls back to your own Dockerfile for everything else. That means you don't write deployment config for common stacks, and you aren't locked out if you use something unusual.

The platform describes itself as "framework-agnostic — we support them all," with auto-detection for every major framework and Dockerfile support "for the rest." So the practical answer is: if it builds, it deploys.

Frontend and full-stack applications

This is the core use case. You connect a repository, and every push triggers an automatic build and deploy. The site's own walkthrough shows the flow:

1. Push your code — connect your Git repo; every push triggers a build. Works with GitHub, GitLab, and Bitbucket.
2. Auto-deploy — Nept builds, optimizes, and deploys. The example shows a build finishing in about 4.2 seconds, with smart caching to keep later builds fast.
3. Go global — your app goes live on edge nodes with zero config, so users get responses from a node near them.
4. Preview and iterate — every branch gets its own preview URL (for example, preview: feat-xyz.app.nept.cloud) so you can share with your team before merging.

Edge functions

Nept supports lightweight TypeScript functions deployed globally with a single command. The platform positions these for auth, personalization, A/B tests, and low-latency APIs. If your app needs small pieces of logic running close to users rather than a full server, this is the deployment type to use.

Containerized apps via Dockerfile

If your stack isn't one of the auto-detected frameworks, you can supply a custom Dockerfile. This is the escape hatch that makes "framework-agnostic" meaningful — you're not limited to the supported list.

How deployment is triggered

Nept is Git-driven. There's no separate upload step described in the platform's flow; the trigger is a push:

git push origin main

That push starts the build. The platform reports the deploy status inline (the example shows nept deploying... done in 4.2s), and on success your app is live globally. Branch pushes produce preview URLs instead of production deploys, which is how you review changes before merging.

What comes with every deployment

These are defaults rather than add-ons, which matters when you're deciding whether Nept fits your project:

• Automatic TLS certificates on every domain
• DDoS mitigation and a WAF with managed rules, always on
• Serverless scaling — cold starts under 30ms, elastic concurrency, pay-per-request pricing
• Smart builds — content-addressed cache, remote build workers, automatic asset optimization, so builds get faster as you ship more

The platform also lists three regions with published health and latency figures: US-East (Ashburn, VA), EU-West (Paris, FR), and AP-South (Mumbai, IN).

How to decide if your project fits

Use these conditions to check your own case:

• Your code is in GitHub, GitLab, or Bitbucket → you can deploy directly.
• You use a major framework (Next.js, Svelte, Astro, Remix, Qwik) → build settings are auto-detected, no config needed.
• You use something else → you need a working Dockerfile.
• You need small server-side logic near users → use edge functions.
• You need a database → the platform's description mentions databases as part of the toolchain; check the current docs for supported options and setup before assuming a specific engine.
• You need to know the cost → Nept has a pricing page at nept.cloud/pricing; the site mentions pay-per-request pricing for serverless, but confirm current rates there rather than assuming a free tier.

If your project builds from a repo or a Dockerfile and you want push-to-deploy with previews and global edge delivery, Nept is designed for exactly that. If your app can't be built in a container or from a supported framework, or you need deployment methods outside Git-based flows, it won't fit.