Public testing phase We’re in a public testing phase — feel free to look around, but we’re not taking orders yet. Ordering opens 1 October 2026. See plans →

Strapi: your first steps

Picked Strapi? Your site came with Strapi 5 scaffolded and built on the Node.js runtime — a headless CMS: you model content in the admin panel and read it through an API from any front end.

What gets installed

  • Strapi 5 scaffolded with the official create-strapi-app (pinned, TypeScript, no example data), its admin panel built, running as a systemd service on Node.js 22 with its own PostgreSQL database in your container.
  • Your administrator (the email address on your veldhost account) registered as the first admin.
  • Settings live in .env in the site's code root (Files tab): the database, the app keys and the public address. config/server.ts binds the app to the port we hand it, behind our proxy.

First login

  1. Your site page shows the sign-in address (/admin), your login email and a generated password — we display it for 7 days, so save it now.
  2. Sign in, then set your own password under your profile (top left).
  3. Create your first content type in the Content-Type Builder, add an entry in the Content Manager, and open Settings → Users & Permissions → Roles → Public to allow find on it — it is then readable at /api/<type>.
  4. Uploads go to public/uploads and are served straight from disk.

Updating

  • Press Back up now on the Files tab first.
  • Bump the @strapi/* versions in package.json (Files tab), then run a deploy: it runs npm install and npm run build (the admin panel), restarts, and Strapi migrates its database on start.
  • Rebuilding the admin panel needs about 1.5 GB for a minute; on the Pro plan that fits.

Limits

  • Strapi needs 1 GB of memory (Pro or higher). The first install borrows more memory for the build automatically.
  • Strapi Cloud features and the Enterprise edition are Strapi's own products; the install is the open-source Community edition.