Next.js hosting
on Shipped.
Bring your Next.js app from local development to a live domain, with a place for its server code and the data behind it.
Keep the server parts of your app
Deploy Next.js as a web service when your application needs request-time rendering, route handlers, or other server features. Shipped runs the application server and handles its public address and HTTPS. You keep the framework behavior your app depends on instead of flattening everything into a static export.
Connect the data behind each page
Use PostgreSQL for application records, object storage for uploads, and transactional email for account messages. Supply private credentials through server-side secrets. Your pages and routes can use these services together while you manage their capacity separately as the product grows.
Review changes before customers see them
Ship a working copy from your coding agent or deploy a repository update through GitHub. A staging environment gives you a place to review routes, forms, and server behavior. Logs help explain a failed request, and deployment history gives you a clear path back to an earlier app release.
A little more detail
Questions about Next.js?
Can I deploy a static Next.js export?
Yes. Use static hosting when your exported app only needs generated files. Features that require a Next.js server need a web service instead.
Can a deployment rollback undo a database migration?
An app rollback restores an earlier application release. It does not reverse database changes. Design Next.js releases and migrations so the previous app can still work with the current schema, or plan a separate data recovery.
From your workspace to the web