Adios

Deployment paths

Deploy the stack your project actually uses.

Choose a framework, runtime, frontend, data service, integration, or workflow. Each page shows the production contract, readiness checks, relevant documentation, and the closest templates for a quick first deployment.

JavaScript and TypeScript

Deploy Node.js APIs, server-rendered applications, and frontend frameworks with their normal package manager and production commands.

Deploy Next.js

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

Open deployment page

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.

Open deployment page

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.

Open deployment page

Deploy Fastify

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.

Open deployment page

Deploy NestJS

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

Open deployment page

Deploy React

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.

Open deployment page

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.

Open deployment page

Deploy Angular

Build an Angular application with the committed workspace configuration, serve its browser output, verify route fallback, and promote it to a managed HTTPS domain.

Open deployment page

Deploy Svelte

Build a Svelte or SvelteKit project with its chosen adapter, serve the emitted output, verify routes, and keep the production command attached to source.

Open deployment page

Python

Deploy Python services directly or start from a production-ready Django, Flask, or FastAPI configuration.

Go

Deploy Go applications and APIs as compiled production services with explicit ports and health checks.

Ruby

Deploy Ruby services or Rails applications with Bundler, persistent production processes, and health checks.

PHP

Deploy PHP applications directly or start with a Laravel production configuration managed through Composer.

.NET

Deploy .NET services and ASP.NET Core applications with a repeatable publish step and persistent runtime.

Apps and platforms

Deploy or connect application platforms with explicit runtime, persistence, credentials, and health configuration.

Databases and data services

Start from a versioned database, cache, broker, or managed-backend template and verify persistence and connectivity.

Workflows

Deploy inspectable backend workflows for HTTP calls, data operations, waits, approvals, and commands.

Other

Publish a static site with an explicit build, output directory, routing behavior, and release contract.

Start from source or a starter

Keep the template, documentation, and production release connected.

Each deployment page now combines the hosting decision with the exact starter variants, repository paths, console keys, and clone commands. Guides and docs cover the implementation details when you are ready to customize the first release.

Choose a deployment path