Getting Started
Create a project, choose the appropriate service type, and configure a first deployment.
Getting Started#
Start a deployment from Dashboard → New Project. The creation flow asks for a service type before asking for source and build details. That choice is important: it determines how NexHost starts, checks, and exposes your application.
Choose the right service#
| If you are deploying… | Choose… |
|---|---|
| HTML, CSS, JavaScript, or a framework static export | Static Site |
| Next.js, Nuxt, Remix, or another server-rendered UI | Frontend App |
| An API, backend, or public full-stack server | Web Service |
| A service only other workspace services should reach | Private Service |
| A continuous queue or asynchronous process | Background Worker |
| A command that runs and exits on a schedule | Cron Job |
Add a source#
The source choices shown depend on the service type. They can include a local folder, ZIP archive, hosted NexHost Git repository, GitHub, GitLab, public Git URL, or an existing container image. Choose the branch and root directory when those controls are shown.
Configure the release#
Set the build command, start command, output directory, and environment variables to match your application. Public runtime services must listen on the injected PORT; static services publish the selected output directory instead of starting a server.
For public runtime services, set a health path that returns a successful HTTP response after startup. The dashboard accepts health-check timeouts from 2 to 300 seconds.
Deploy and inspect#
Start the deployment from the final review step. Follow the release in Deployments and use its build output if it fails. A successful public service receives the hostname displayed by the dashboard; add a custom domain afterwards when needed.
Continue with Your First Deployment.