A fast marketing site built from your existing Next.js repository and served as one application.
Why use it
Publish a product, campaign or waitlist on a public URL you can share and connect to your own domain.
Configure a Next.js production build for hosting
Keep the current design and configure Next.js standalone output.
Add a production multi-stage Dockerfile that contains the traced runtime files and static assets.
Bind the server to 0.0.0.0 on port 3000 and check the homepage after deployment.
Next.js runtime, port and environment variables
Resources
1 ServiceNo database
Required values
Only the public values your site uses
Check before you deploy
The aidrop address works on Starter. Connecting your own domain starts on Pro.
Deploy the Next.js app from your coding agent
Prepare this Next.js landing page for aidrop without redesigning it. Enable standalone output and add a production multi-stage Dockerfile that includes public and .next/static assets. Run the production server on 0.0.0.0:3000, use / as the health path and keep every required public environment value explicit. Build, deploy and return the public address.
NEXT.JS HOSTING DETAILS
Validate the production app before you share it
A successful build is only the first check. Open the public address, follow a client-side route directly, load images and assets, and confirm server-rendered pages answer without development-only dependencies.
Next.js hosting limits, pricing and persistence
Starter supports static exports and small Node.js server builds within 512 MB RAM and 0.5 vCPU, on an aidrop address. Choose Pro for managed PostgreSQL, a custom domain or more runtime resources. Application containers have no persistent disk, so uploads belong in external object storage and durable records belong in a database.
Check the Node.js version, lockfile, production build command and standalone output first. The server must listen on 0.0.0.0 and use the assigned port. Keep server-only environment values out of variables exposed with the NEXT_PUBLIC prefix.