Adios
Apps and APIs · plans from $10/month

Deploy Fastify.Keep the API fast and inspectable.

Deploy a Fastify service from its existing Node.js source, bind it to the production port, verify readiness, and inspect the exact build serving traffic.

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

Candidate release

Fastify

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

FastifyNode.js 24JSON APIsPluginsnpm

The production path

A working Fastify 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 Fastify build you already use

Install from the lockfile and compile TypeScript when the project requires it. Fastify plugins and schemas remain part of the repository under review.

Promote the version that reports healthy

Listen on 0.0.0.0 at the configured port, expose a health endpoint, and keep startup or plugin registration failures visible before promotion.

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: fastify-api
build_cmd: npm ci && npm run build
start_cmd: node dist/server.js

runtime:
  name: node@24
  port: 8080
  health_path: /healthz
Use npm ci without a build step for plain JavaScript projects and point start_cmd at the actual entrypoint.

Deployable starting points

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

Inspect the Fastify starter's plugin registration, health route, package commands, and Adios runtime configuration.

API starters

Node.js Fastify

Express, Fastify, Hono, and NestJS starters with production-ready start commands.

JavaScriptnpm
Template key
node-fastify
Runtime
node
Repository
templates
Source path
nodejs/fastify
git clone https://github.com/adiosdotdev/templates.git
cd templates/nodejs/fastify
adios up
DeployView source
Review the runtime manifest

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…

  • Plugin registration completes without development-only settings.
  • The server listens on 0.0.0.0 and the manifest port.
  • Schemas and serializers load during startup.
  • External credentials come from secrets.

Preview when…

  • Native modules build during npm install.
  • The API uses streaming or long-lived connections.
  • Plugins require external services before health can pass.

Questions, answered

What to know before deploying Fastify.

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

Can Adios deploy an existing Fastify 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 Fastify?

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 I deploy Fastify with TypeScript?

Yes. Compile the project during the build, start the emitted JavaScript, and verify that production dependencies contain everything required at runtime.

How should a Fastify health route behave?

Keep readiness checks fast and side-effect free. Include only dependencies that must be available before the release can safely receive traffic.

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 Fastify 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 Node.js

Deploy a persistent Node.js web process or worker from its existing package scripts, with release health, logs, secrets, routing, and Git history attached.

Deploy Express

Run an Express API as a persistent Node.js process with its install command, port, health endpoint, secrets, logs, and promoted release connected.

Deploy NestJS

Build a NestJS application from source, start the emitted production entrypoint, verify dependency readiness, and keep deployment evidence beside the project.

Deploy Redis

Start Redis 7 for cache, session, pub/sub, or fast state workloads, then verify connectivity, persistence expectations, eviction, and dependency failure behavior.

The first release

Deploy Fastify 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