GitHub is the starting point
Connect the repository and branch that hold the application you actually want to ship.
Next.js Hosting
Next.js hosting that keeps the path visible.
The first Host Little App Hosting path starts with a GitHub-hosted Node.js or Next.js HTTP application. It is focused on a dependable release journey rather than pretending every runtime is already the same product.
Source to release
Health gates trafficGitHub source
A repository and branch
Isolated build
An admitted release artifact
Healthy release
Traffic follows the health check
PostgreSQL alongside the appCreate, connect, and meter usage
Explore the boundaryA release contract you can explain to another developer.
The runtime has a boundary
The current public launch path is for GitHub-hosted Node.js and Next.js HTTP applications.
A health check decides traffic
A finished build is not enough. A healthy release earns its path to production traffic.
Delivery belongs with the release.
When your app makes it to production, the useful work is not over. The operational context should still be close by, simple enough to use when a real change needs attention.
Domains and HTTPS
Bring the public domain into the same application path and use managed certificates on the supported HTTP route.
Release context
Keep release history and bounded, redacted operational information with the project instead of splitting its story across tools.
Start with the Next.js app you already have.
Follow the supported GitHub to Next.js path, then bring the right operational context into one project workspace.