Adios
Next.js hosting from $10/month

Deploy Next.js.Keep shipping.

Take your Next.js app from local source to a healthy production URL with one manifest and one command. Adios handles the build, runtime, logs, routing, custom domain, and TLS in one place.

No Docker requiredCustom domains includedKeep your Git repo
Adios deploy

Deployment #184

Production release

Healthy

BUILD

1m 14s

REGION

de

RUNTIME

Node 24

01Installing dependencies

02▲ Next.js production build

03✓ Compiled successfully

04✓ Runtime started on :3000

05✓ Health check passed

Live route

northstar.adios.run

Promoted

Current release is live

One deployment path for

App RouterPages RouterServer renderingAPI routesStatic output

The production path

Your framework is ready. The infrastructure should be too.

A working Next.js app still needs a repeatable build, a running production process, health checks, logs, secure configuration, and a route people can trust. Adios keeps that path short and inspectable.

Ship with your existing app

Keep your repository, package manager, and standard Next.js build and start commands. Add one small manifest instead of rebuilding your project around a hosting provider.

Promote a healthy release

Adios builds the uploaded source, starts the production process, checks the route you define, and promotes the version after it is healthy.

Run the whole Next.js app

Serve static pages, server-rendered routes, and API routes from the same persistent Node.js runtime, with logs and routing attached.

How it works

From repository to live route in three steps.

Adios uses the production commands your project already understands. The manifest makes the runtime explicit and reviewable for every release.

  1. 01

    Install and sign in

    Install the Adios CLI, then authenticate from the terminal. You only need a Next.js project that builds locally.

    $curl -fsSL https://adios.dev/install.sh | sh
  2. 02

    Describe the runtime

    Put the build command, start command, port, health path, and capacity beside your source in adios.yaml.

    $touch adios.yaml
  3. 03

    Deploy the current source

    Run one command from the project root. Follow the build and health output, then open the generated HTTPS route.

    $adios up
adios.yaml
name: my-nextjs-app
region: de
replicas: 1

build_cmd: npm install && npm run build
start_cmd: npm start

runtime:
  name: node@24
  port: 3000
  health_path: /api/health
  memory_mb: 1024
Adjust the package commands, region, capacity, and health path to match your app.

What is included

The production basics stay connected.

No separate build service, log viewer, certificate project, and release checklist. The app, runtime contract, and promoted route live in one system.

Next.js rendering

Static pages, server rendering, and API routes

Release safety

Build logs, runtime logs, and an explicit health path

Domains

Generated HTTPS route, custom domains, and managed TLS

Configuration

Environment variables plus secret references kept out of Git

Source workflow

CLI and Git deploys, previews, web editor, and local sync

Growth path

Choose more CPU, memory, storage, and bandwidth as needed

Simple starting point

Start small.Scale when it earns it.

The Starter plan is designed for a first app, small API, or personal workspace. Move up when production traffic or your project portfolio needs more headroom.

Starter

$10/month
A practical first app
1 vCPU and 1 GB RAM
10 GB storage
500 GB included bandwidth
Custom domains and TLS
Git and CLI deploys
Web editor and AI assistant
Choose Starter and deploy

Final terms and availability are shown at checkout.

Before you deploy

A good fit for standard Next.js production apps.

The fastest deployment starts with a project that already behaves like a production app locally. Here is the short readiness check.

You are ready when…

  • Your app installs and builds from a clean checkout.
  • You have a production start script such as next start.
  • Runtime secrets are not hard-coded in the repository.
  • The process can listen on the port declared in adios.yaml.

Check in a preview when…

  • The build depends on native or operating-system packages.
  • You use image processing, middleware, or other runtime-specific behavior.
  • The application depends on a database or external service to report healthy.
  • You are changing package managers, Node versions, or build output at the same time.

Questions, answered

Everything to make the decision.

Technical details, fit, and cost—before you create an account.

Can Adios deploy an existing Next.js repository?

Yes. Run the CLI from the project root and add an adios.yaml file with the app's production build and start commands. You can keep the repository, source structure, and package manager you already use.

Does it support server-side rendering and API routes?

Yes. Adios runs the Next.js production server as a persistent Node.js process, so static output, server-rendered routes, and Next.js API routes can ship together.

Do I need Docker or a custom server?

Not for a standard Next.js deployment. Define the Node.js runtime and your normal npm or pnpm build and start commands in adios.yaml. If your app has unusual system dependencies, confirm them in a preview before promotion.

Can I use npm, pnpm, JavaScript, or TypeScript?

Yes. Adios provides official Next.js starters for JavaScript and TypeScript with npm and pnpm. Existing applications can keep their current package manager and lockfile.

How do environment variables and secrets work?

Public runtime configuration can be declared as environment variables. Sensitive values can be stored outside the repository and referenced by name from adios.yaml, so the credential itself is not committed to Git.

Can I connect my own domain?

Yes. Every plan includes custom domains and managed TLS. Add and verify the hostname, point its DNS as instructed, and Adios keeps the domain connected to the promoted release.

What happens if the build or health check fails?

The build and runtime output remain available for inspection. Adios promotes the current version after it reports healthy, so a failed candidate does not become the healthy promoted release.

How much does Next.js hosting cost?

Plans currently start at $10 per month for the Starter plan, which includes 1 vCPU, 1 GB RAM, 10 GB storage, and 500 GB included bandwidth. Choose a larger plan when the app needs more capacity. Final terms and availability are shown at checkout.

Your next release

Turn your Next.js repo into a live app.

Keep the source and commands you know. Add a clear runtime contract, deploy, and see what is serving production.