---
title: "Deploy Twenty CRM on StackBlaze"
description: "People, companies, opportunities, tasks, and notes in one workspace — on your instance. You pay for compute, not per seat."
category: "productivity, work"
url: https://www.stackblaze.com/templates/twenty
---

# Deploy Twenty CRM

People, companies, opportunities, tasks, and notes in one workspace — on your instance. You pay for compute, not per seat.

**[Deploy Twenty CRM on StackBlaze](https://dashboard.stackblaze.com/new/template/twenty)**

## This stack

- **Web**: Twenty CRM server
- **Worker**: Background worker
- **PostgreSQL**: managed database · TCP:5432
- **Valkey**: managed cache · TCP:6379
- **Email**: platform add-on

## What you get

- **People and companies**: Keep people and company records together so the team works from shared customer context.
- **Opportunity tracking**: Track opportunities through the sales process, with the company and contact on the same record.
- **Tasks and notes**: Record follow-ups and notes next to the CRM records they support.
- **Flexible workspace**: Configure fields and views around how your team works, instead of a fixed spreadsheet.
- **Your own instance**: Run Twenty on your instance. Records stay here — not in a shared vendor-managed account.
- **HTTPS web access**: Open Twenty on a public HTTPS hostname. Attach your own domain when you want a branded URL.

## After you deploy

1. **Open the public URL**: The hostname is on the app page after deploy. First boot runs migrations — that can take up to 15 minutes, not a login form.
2. **Create the workspace**: Email, password, and a workspace name. That account owns the instance until you invite others.
3. **Use the records**: Companies, people, deals, tasks, and notes are in the sidebar. Dashboards and workflows are there too.

## How it is wired

- **Postgres holds the records**: Companies, people, deals, and notes live in the attached database. Restart the app and the workspace is still there.
- **Valkey is the cache**: The app reads cache from Valkey. It speaks the Redis protocol. You do not add a second cache. Jobs use Postgres (pg-boss), not the cache.
- **A worker sits beside the web app**: Background jobs run on the worker so a heavy run does not stall the UI. Scale the worker when jobs back up.
- **Add CPU when first boot is slow**: Migrations run on first start and need headroom. Raise RAM and CPU on the web app from the dashboard. Postgres and Valkey scale on their own.

## Common questions

### How do I sign in after deploy?

Open the public URL. First boot can take up to 15 minutes while migrations run. The first person to open it creates the workspace and becomes the admin. If the page stays blank, wait for the web pod to pass its startup probe, then reload.

### Where are companies and deals stored?

In the attached Postgres. APP_SECRET is set at deploy. Back up the database if the workspace matters. Valkey is a cache, not a backup target. Uploads live on the shared volume.

### What is already in the sidebar?

Companies, people, opportunities, tasks, notes, dashboards, and workflows. The first account is empty until you add records.

### Can I use my own domain?

Yes. Attach a custom domain from the dashboard. FRONT_BASE_URL and SERVER_URL follow the public hostname.

### Do I need Redis?

This template includes it. Valkey speaks Redis protocol and is the cache. You do not add Redis yourself.

### Why is first boot so slow?

Twenty runs database migrations in the web and worker on first start. That can take 10–15 minutes at the default size. The startup probe waits up to 25 minutes so the pod is not killed mid-migration.

### What does it cost?

You pay for the web app, the worker, Postgres, and Valkey — compute, storage, and bandwidth — not per seat. Developer is $10/mo with $10 of included usage; a small instance usually stays in that range.

### Is this the right setup for a team CRM?

Yes — this is the web-plus-worker stack. The UI stays on the web app; background jobs run on the worker. Scale the worker when jobs back up.


Source: https://github.com/twentyhq/twenty