# How Crewtavo updates

> On Railway, Crewtavo updates itself within hours of a new version, with no downtime. How to check your version, choose when updates install, or stay on one.

On Railway, Crewtavo keeps itself up to date. When a new version comes out, Railway installs it within several hours, and Railway notifies your workspace's admins after each update.

## No downtime

The new version starts next to the old one, updates the database, and takes over only once it's working. If something goes wrong, the old one keeps running. Your data is safe either way: each database update finishes completely or not at all.

The database service (`db`) gets a new version only when its setup changes. That happens overnight, between 02:00 and 06:00 UTC, and it's down for about a minute while it restarts.

Every new version installs itself, big ones included. The one exception is a move to a new major version of Postgres, which has to convert your data first. Its release notes will say what to do.

## Check your version

Open your Crewtavo's address with `/api/health` on the end, like `https://crm.yourbusiness.com/api/health`.

## Change when updates install

In Railway, open the **crewtavo** service, then **Settings → Source → Configure auto updates**. You can change when updates install there, or turn them off.

To stay on one version, change the image there from `ghcr.io/jviars/crewtavo:latest` to that version, such as `ghcr.io/jviars/crewtavo:0.2.0`.

## With Docker

Get the new version with `git pull` in the Crewtavo folder, then run `npm run instance` again. See [Self-host with Docker](https://crewtavo.com/docs/hosting/docker/).

Source: https://crewtavo.com/docs/hosting/updates/ (last updated 2026-10-18)