Full-stack

How to deploy a Strapi + Next.js site on Rock8Cloud

Deploy a full Strapi 5 CMS and Next.js 16 frontend to Rock8Cloud in one click - PostgreSQL and S3 media provisioned and wired for you, a published home page live on the first deploy.

Updated 16 July 2026

A headless CMS website in one deploy - Strapi 5 for the admin and Next.js 16 for the frontend, managed as a single Turborepo monorepo. Rock8Cloud provisions the database and media storage, wires them in, and puts a published page live before you even log in.

Deploy in one click#

The blueprint forks the monorepo to your GitHub, then builds two services from it - Strapi (port 1337) and the Next.js site (port 3000). PostgreSQL and an S3 media bucket are provisioned and connected for you.

Strapi + Next.js example
rock8-cloud/strapi-next-turborepo-starter

Pro tip:The first deploy seeds a published home page and grants public read access, so your site renders immediately. Create your admin user at /admin on the Strapi service.

What you get#

  • A private fork of the monorepo in your GitHub account - both services build from the one repo.
  • Two services - the Strapi admin and the Next.js site, each with its own public URL.
  • A managed PostgreSQL database, pre-wired via DATABASE_URL.
  • A managed S3 bucket for media, pre-wired via S3_* env vars, so uploads survive redeploys.
  • A seeded home page rendering at your site URL the moment the first deploy lands.
  • Deploy on push - every push to your default branch rebuilds and ships both services.

After it’s live#

Nothing to wire by hand. The two services already know each other’s URLs - Strapi has its own public URL and the web frontend URL (for CORS), and the frontend has both Strapi URLs. Your site and admin work on the first deploy.

Live preview works out of the box - a shared preview secret is set on both services automatically, so the admin Preview button renders drafts in the real frontend. Published pages refresh within a few minutes through ISR. For instant revalidation on publish, follow the webhook step in the repo README.

Customize it#

Edit content models under apps/strapi/src/api/* and render new blocks in apps/web/src/components/blocks/* in your fork. Push to your default branch and Rock8Cloud rebuilds. Need more services? PostgreSQL, Dragonfly, and S3 are one click each.

Frequently asked questions

Do I need to set anything up before deploying?
No. The blueprint forks the repo, provisions PostgreSQL and S3 media, generates Strapi's secrets, and wires everything through env vars. A published home page renders on the first deploy with no admin login.
How do the two services talk to each other?
The Next.js site reaches Strapi over the internal network for server-side fetches and over the public URL for browser-facing media. Strapi knows the web frontend URL for CORS. All of this is wired automatically at deploy - no manual URL setup.
Where do uploaded images go?
An S3-compatible bucket is provisioned automatically and wired into Strapi, so media survives redeploys out of the box - no manual storage setup.
Can I change the content models?
Yes. Edit the collections under apps/strapi/src/api/* and render new blocks in apps/web/src/components/blocks/* in your fork, then push to rebuild.

More guides

Ship today

Ship your CMS-backed site.In one click.

Strapi admin, a Next.js frontend, PostgreSQL and media storage - provisioned together and live on the first deploy.

60 days free. No credit card required to start.