---
title: "Deploy Strapi on StackBlaze"
description: "Deploy Strapi 5 with managed Postgres, a volume for media, and email for password resets. Editors work in the admin panel; your frontend reads the content over REST or GraphQL. You pay for compute, not per seat or per API call."
category: "cms, development, data"
url: https://www.stackblaze.com/templates/strapi
---

# Deploy Strapi

Deploy Strapi 5 with managed Postgres, a volume for media, and email for password resets. Editors work in the admin panel; your frontend reads the content over REST or GraphQL. You pay for compute, not per seat or per API call.

**[Deploy Strapi on StackBlaze](https://dashboard.stackblaze.com/new/template/strapi)**

## This stack

- **Strapi**: Web service
- **PostgreSQL**: managed database · TCP:5432
- **Email**: platform add-on

## What you get

- **Admin panel for editors**: Write, edit and publish entries in the Content Manager, with drafts, relations, components and dynamic zones.
- **REST and GraphQL**: Every content type is served at /api/<name> and through /graphql on your own hostname, for any frontend or app.
- **A model to start from**: Ships with Strapi’s example blog model: Article, Author, Category, About and Global, with media and rich text blocks.
- **Roles and API tokens**: Choose what the Public role can read, or hand out read-only API tokens. Nothing is public until you allow it.
- **Managed Postgres**: Entries, users and settings live in an attached Postgres database. The schema is created on the first start.
- **Media and email included**: Uploads go to a 10 GB volume that survives redeploys. Password reset emails go out through the Email add-on.

## After you deploy

1. **Register the first admin**: Open the public URL at /admin. The first person to sign up becomes the super admin, so do it right after the deploy.
2. **Write and publish**: Create an Article in the Content Manager, add a cover image, and press Publish.
3. **Open the API**: Allow find and findOne for the Public role in Settings, Users & Permissions, or create an API token. Then read /api/articles from your frontend.

## How it is wired

- **Postgres holds the content**: Entries, admin users, roles and API tokens live in the attached database. Redeploy and everything is still there.
- **Media sits on a volume**: Uploads are stored on a 10 GB volume at /opt/app/public/uploads and served by Strapi itself.
- **Secrets are generated once**: APP_KEYS, the JWT secrets, the token salts and ENCRYPTION_KEY are unique to this deploy. Keep them: changing them signs everyone out and breaks saved API tokens.
- **Email through the add-on**: Admin password resets and user emails use the Email add-on over SMTP. No mail provider account needed.

## Common questions

### How do I sign in after deploy?

Open the public URL at /admin and register the first administrator. Strapi has no default account, so whoever registers first owns the admin. Invite more people from Settings, Users.

### Can I add my own content types?

Strapi only lets you edit content types in development mode; in production the Content-Type Builder is read-only. Run the template’s Strapi project locally with npm run develop, design your types, build the image with the included Dockerfile, and point this app at it. The database schema updates on the next start.

### Why does /api/articles return 403?

Strapi keeps every content type private until you allow it. Turn on find and findOne for the Public role in Settings, Users & Permissions, or call the API with an API token.

### Does it send email?

Yes. Admin password resets and the Users & Permissions emails (password reset, sign-up confirmation when you turn it on) go out through the Email add-on. It is for transactional mail, not newsletters.

### Where are uploads stored?

On the app’s 10 GB volume, so they survive redeploys and restarts. Strapi serves them at /uploads on your hostname.

### Can I use my own domain?

Yes. Attach a custom domain from the dashboard. The admin and the API move with it.

### What does it cost?

You pay for the compute, storage and bandwidth Strapi and Postgres use, plus emails sent. There is no per seat or per API call charge.


Source: https://github.com/strapi/strapi