---
title: "Deploy Colanode Server | (Just Updated) Slack and Notion Alternative, Local-First Workspace, Admin Login Pre-Created"
description: "Colanode server, self-hosted Slack and Notion alternative, local-first"
category: "Other"
url: https://railway.com/deploy/colanode-server-or-just-updated-slack-an
---

# Deploy Colanode Server | (Just Updated) Slack and Notion Alternative, Local-First Workspace, Admin Login Pre-Created

Colanode server, self-hosted Slack and Notion alternative, local-first

**[Deploy Colanode Server | (Just Updated) Slack and Notion Alternative, Local-First Workspace, Admin Login Pre-Created on Railway](https://railway.com/template/colanode-server-or-just-updated-slack-an)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/colanode-server-or-just-updated-slack-an/manifest.json

- **Creator:** SuperSlowSloth
- **Category:** Other

## Template content

### cache

- **Image:** redis:8.2.1-alpine@sha256:987c376c727652f99625c7d205a1cba3cb2c53b92b0b62aade2bd48ee1593232
- **Start command:** `/bin/sh -c 'chown -R redis:redis /data && exec docker-entrypoint.sh redis-server --requirepass "$REDIS_PASSWORD" --appendonly yes --dir /data'`

### colanode

- **Image:** ghcr.io/bon5co/colanode-railway:0.4.7@sha256:32d68688ad51d0c545b4695ba2bbb54c42ce014be656eeed3357720e1045065f
- **Public domain:** Yes

### database

- **Image:** pgvector/pgvector:pg17@sha256:b513c48566e4777cd3370451400000c78eda6a08131d68f4c31d4a76f27bd8fd

## Documentation

# Deploy and Host Colanode Server on Railway

**Built for an LLM agent to deploy and use.** The deploy form has no fields to fill: the administrator login, the database and Redis credentials are generated, the administrator account is created at boot with a password you can sign in with (the stock image has no way to create the first account without an emailed code), and anyone else who registers stays unverified and cannot sign in. Colanode is an open-source, local-first collaboration workspace: chat, pages, databases and files in one place, a self-hosted alternative to Slack and Notion.

## About Hosting Colanode Server

This template runs three services: **colanode**, the official `ghcr.io/colanode/server` image (0.4.7) pinned by digest through a thin wrapper, with a volume at `/data` for uploaded files; **database**, a PostgreSQL 17 instance with the pgvector extension and a volume at `/var/lib/postgresql` that holds every account, workspace, message and page; and **cache**, a Redis 8 instance with a volume at `/data` for the job queue, realtime events and upload locks. One public domain serves the Colanode API and sync server. The server listens on its fixed port 3000 and ignores `PORT`, so the domain targets 3000 and the service has no HTTP healthcheck.

**What the wrapper fixes.** The stock image reads a JSON config file and offers no way to create the first account without an emailed one-time code. The wrapper writes that config from plain Railway variables (database and Redis connections, files on the volume, public domain), starts the server, waits for its migrations to finish, and creates one active administrator from `COLANODE_ADMIN_EMAIL` and `COLANODE_ADMIN_PASSWORD`. The administrator is created only when no account with that address exists and the password is stored in the database as an argon2id hash, so a redeploy never overwrites a password you changed. Account verification is set to manual: a stranger who registers is left pending until an administrator verifies the account.

**Using it.** Install the Colanode desktop or mobile app, or open the Colanode web app pointed at your domain, and add the server with `https://YOUR_DOMAIN`. Sign in with the administrator email and password. A personal workspace is created on first login. Email and sign-in with Google are optional and not configured: without SMTP no notification mail is sent. A Colanode client (or an agent calling `/client/v1`) authenticates with the bearer token returned by the login call.

### Agent contract

- Public URL: `https://RAILWAY_PUBLIC_DOMAIN` (the generated domain of the `colanode` service)
- Private URL: `http://colanode.railway.internal:3000`
- Credentials: the variables `COLANODE_ADMIN_EMAIL` and `COLANODE_ADMIN_PASSWORD` on the `colanode` service (plain text)
- Auth: `POST /client/v1/auth/email/login` with JSON `{"email","password"}` returns a `token`; send it as `authorization: Bearer TOKEN` on every later call under `/client/v1`
- Health: `GET /config` returns 200 without credentials and reports the server version

```bash
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN, COLANODE_ADMIN_EMAIL, COLANODE_ADMIN_PASSWORD (variables of the colanode service); also curl, jq.
R="https://$RAILWAY_PUBLIC_DOMAIN"; J="content-type: application/json"; A="$R/client/v1"
n=0; until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/config")" = 200 ]; do n=$((n+1)); [ "$n" -le 90 ] || break; sleep 5; done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/config"
# signup: none - accounts are created in a pending state (verificationType manual): the attempt below is answered 400 account_pending_verification, and that account can neither sign in nor get a workspace until an administrator verifies it
curl -s -o /dev/null -w "public signup: %{http_code}\n" -H "$J" -d '{"name":"x","email":"stranger@example.com","password":"a-stranger-twelve"}' "$A/auth/email/register"
# sign in with the generated login: the token returned here authenticates every call after this
TOKEN=$(curl -s -H "$J" -d "$(jq -nc --arg e "$COLANODE_ADMIN_EMAIL" --arg p "$COLANODE_ADMIN_PASSWORD" '{email:$e,password:$p}')" "$A/auth/email/login" | jq -r '.token')
case "$TOKEN" in ""|null) echo "login: failed";; *) echo "login: 200";; esac
echo "read with token: $(curl -s -X POST -H "$J" -H "authorization: Bearer $TOKEN" -d '{}' "$A/accounts/sync" | jq -r '.account.email')"
echo "read without token: $(curl -s -X POST -H "$J" -d '{}' "$A/accounts/sync" | jq -r '.code')"
# write-auth: PATCH /accounts/me renames the signed-in account; without the token it answers 401
curl -s -o /dev/null -w "write with token: %{http_code}\n" -X PATCH -H "$J" -H "authorization: Bearer $TOKEN" -d '{"name":"Agent","avatar":null}' "$A/accounts/me"
curl -s -o /dev/null -w "write without key: %{http_code}\n" -X PATCH -H "$J" -d '{"name":"Agent","avatar":null}' "$A/accounts/me"
```

Expected output against a fresh deploy:

```text
health: 200
public signup: 400
login: 200
read with token: admin@RAILWAY_PUBLIC_DOMAIN
read without token: token_missing
write with token: 200
write without key: 401
```

The refusals are the contract: a request without a token is refused (`write without key: 401`), and a stranger's registration is accepted only as a pending account (`public signup: 400`, `account_pending_verification`), which cannot sign in.

## Why Deploy Colanode Server on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Colanode Server on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

- **Agent-ready** - no deployer fields, a contract block, and one script that proves the server is healthy, strangers cannot sign in, and the generated login can read and write.
- **Sign-in works without SMTP** - the administrator signs in with a generated password instead of an emailed code.
- **Strangers locked out** - new registrations stay pending until an administrator verifies them.
- **Data survives redeploys** - accounts and workspaces live in PostgreSQL on a volume, uploads on a second volume, the job queue on a third.
- **Pinned** - the upstream image is pinned by digest and the wrapper by tag and digest.

## Common Use Cases

- **Team chat and docs** - run chat, pages and databases for a small team on your own server instead of a Slack and Notion subscription.
- **Local-first workspace** - clients keep a local copy and sync through your server, so the team keeps working offline.
- **Workspaces for AI agents** - give an agent a generated login and a shared place to read and write notes and files.

## Dependencies for Colanode Server Hosting

- The colanode service, a PostgreSQL service with pgvector and a Redis service, each with its volume, created by the template.

### Deployment Dependencies

- [Colanode repository](https://github.com/colanode/colanode)
- [Wrapper image source](https://github.com/bon5co/colanode-railway)


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — Self-hosted virtual tabletop for role-playing games (license required)
- [Double Commander in your browser](https://railway.com/deploy/double-commander-in-your-browser) — The Double Commander file manager in the cloud, from any device

Open this page in a browser: https://railway.com/deploy/colanode-server-or-just-updated-slack-an
