Adios
Frontend apps · plans from $10/month

Deploy React.Publish the built site.

Build a React application from its existing repository, serve the generated output or production Node.js process, and connect the release to a stable HTTPS route.

Deploy my projectDeploy a template
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

React

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

ReactViteStatic outputNode.jsCustom domains

The production path

A working React project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Keep the React build you already use

Use the project's current npm build and lockfile. Serve a client-side app from its output directory, or keep the explicit Node.js command required by a server-rendered React framework.

Promote the version that reports healthy

Verify the root route and client-side fallback before promotion. Server-rendered applications should expose a lightweight health endpoint on the runtime port.

Trace production back to source

Build output, runtime logs, health state, secrets, domains, and the promoted release stay attached to the project instead of being split across unrelated tools.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: react-app
build_cmd: npm ci && npm run build
start_cmd: npm start

runtime:
  name: node@24
  port: 3000
  health_path: /
Make npm start serve the production build. A static-only project can begin with the Nginx static template instead.

Deployable starting points

Start React from a template when the repository is not ready.

Use the Nginx static starter for a client-only build, or inspect the Next.js TypeScript starter when the React app needs a server runtime.

Web apps

Nginx Static

An Nginx starter for static HTML, CSS, JavaScript, and single-page apps.

HTMLNone
Template key
nginx:static
Runtime
nginx
Repository
templates
Source path
nginx/static
git clone https://github.com/adiosdotdev/templates.git
cd templates/nginx/static
adios up
DeployView source

Web apps

Next.js TypeScript with npm

JavaScript and TypeScript Next.js starters using npm or pnpm and Adios runtime config.

TypeScriptnpm
Template key
nextjs-typescript
Runtime
node
Repository
template-nextjs-typescript
Source path
.
git clone https://github.com/adiosdotdev/template-nextjs-typescript.git
cd template-nextjs-typescript
adios up
DeployView source
Review the template deployment flow

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • npm run build succeeds from the committed lockfile.
  • The production command serves the built output.
  • Client-side routes fall back to the application shell when required.
  • Public and private environment variables are separated.

Preview when…

  • The project uses server rendering or API routes.
  • Asset URLs depend on the final base path or hostname.
  • Runtime configuration is currently baked into the client bundle.

Questions, answered

What to know before deploying React.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can Adios deploy an existing React project?

Yes. Run the Adios CLI from the project root, keep the repository and dependency files you already use, and add an adios.yaml file that describes the production build, start command, port, and health path.

Do I need Docker to deploy React?

Not for a standard supported runtime. Use the project's normal production commands in adios.yaml. If the build needs unusual operating-system packages or native libraries, verify those dependencies in a preview before promotion.

Can Adios deploy a Vite React app?

Yes. Build the Vite project and serve its output with a production static server. Confirm the output directory and SPA fallback behavior before promotion.

What if my React app uses server-side rendering?

Use the framework's production server and declare its start command, port, and health path. The Next.js landing page covers the common Next.js-specific path.

What happens when the build or health check fails?

The candidate release keeps its build and runtime output for inspection. It must report healthy before it becomes the promoted version serving the application route.

Can I start from a template instead of an existing repo?

Yes. This page links to the closest official Adios React starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

Related deployment paths

Connect the rest of the stack.

Browse all deployment pages

Deploy Static sites

Publish HTML, CSS, JavaScript, or a framework-generated static build from a small Nginx starter with routes, domains, TLS, and release state attached.

Deploy Next.js

Deploy static pages, server-rendered routes, and APIs from one persistent Node.js release.

Deploy Vue

Build a Vue application from its existing repository, serve the production output, verify client-side routes, and promote it to a managed HTTPS domain.

Deploy Supabase apps

Deploy the frontend, API, or worker that connects to Supabase. Adios runs the application release; your Supabase project remains the external database and backend service.

The first release

Deploy React with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.

Start with AdiosCompare plans