DEV Community

Cover image for Orbit: Self-Host an Open-Source Linear + Notion + Slack in One Click
alphasec
alphasec

Posted on AI-assisted

Orbit: Self-Host an Open-Source Linear + Notion + Slack in One Click

A lot of small teams run on the same trio: Linear for issues, Notion for notes, Slack for chat. It works, but you have to keep switching tabs, and each tool charges per seat, adding up quickly.

So when the Coolify team released Orbit, I wanted to try it straight away. It's an open-source workspace that does tasks, docs and chat in one app, with mail on the way. I deployed it on Railway with Postgres, ran into a handful of problems, and ended up packaging it as a one-click template. This post is a quick tour of Orbit and then the problems, since anyone self-hosting it elsewhere will probably hit some of them too.

What you get

Tasks feel a lot like Linear. Each project has its own workflow and statuses, and you can switch between list, board and timeline views. There are sub-issues, labels and saved views, and two people can edit a task description at the same time.

Docs are a page tree with teamspaces, a rich editor and page history. Again, editing is live and collaborative. If you're coming from Notion, there's an importer.

Chat has channels, DMs, threads and file uploads. When you paste a link to a task or a doc, it shows up as a preview in the conversation, which is the part that makes having everything in one app feel worth it.

A few other things I liked:

  • There's an MCP server with OAuth built in. You point an AI client such as Claude at your instance, choose which workspace and projects it may read, and it can answer questions about your tasks without you copying anything over.
  • GitHub sync works per workspace. Label an issue or pull request and Orbit creates a task for it. Merge the pull request and the task closes.
  • Linear, Asana and Trello tasks can be imported, as well as Notion pages.
  • Scoped API tokens, roles and a CSV-exportable audit log are already there, which is more than I expected from a v0.4.

Mail (a shared team inbox) is listed as coming soon. Orbit is Apache 2.0 licensed, and if you don't want to host it, coolLabs runs a cloud version for $10 per workspace per month.

Why it's easy to host

The whole thing is one Rust binary. It serves the API and the web app on a single port, stores data in SQLite by default or Postgres if you prefer, and keeps attachments on disk or in S3. Images are built for both amd64 and arm64.

It's also strict. In production it won't start without an encryption key or a list of trusted proxies. Backups are encrypted with that key, you can schedule them, and Orbit takes a verified backup before any migration that can't be undone. I like that. It did mean a few extra steps on Railway, which I'll get to below.

One-click deploy on Railway

The Railway template deploys Orbit, Postgres 18, and a volume for attachments and backups:

Deploy on Railway

Once it's running:

  1. Open the deploy logs of the orbit service and look for Initial setup URL: https://YOUR-DOMAIN/setup?token=....
  2. Open that link and create your account. The link only works once, and that first account becomes the root admin.
  3. Set up a workspace and a project, and invite people.
  4. Copy ORBIT_APP_KEY from the service variables into your password manager. If you lose it, your backups can't be decrypted. ## The problems I ran into

Postgres wanted a different locale

My first attempt pointed Orbit at Railway's default database, and it refused to start:

Postgres database ... does not order and fold text like Orbit needs; create it with
CREATE DATABASE <name> TEMPLATE template0 ENCODING 'UTF8' LOCALE_PROVIDER builtin BUILTIN_LOCALE 'C.UTF-8' LOCALE 'C.UTF-8'
Enter fullscreen mode Exit fullscreen mode

The builtin locale provider was added in Postgres 17. Railway ships 18, so the fix was to create a separate orbit database with the right locale before the app starts. The Orbit image includes psql, so a pre-deploy command does it:

sh -c 'psql "$PG_ADMIN_URL" -c "$DB_BOOTSTRAP_SQL" || true'
Enter fullscreen mode Exit fullscreen mode

After the first deploy the database already exists, the command errors, and the || true lets the deploy carry on. One side effect is that Railway's Data tab only shows the default railway database, so Orbit's tables won't appear there. Use any Postgres client against the orbit database if you want to look around.

Every request came back as "HTTPS required"

Orbit only trusts X-Forwarded-Proto when the request comes from an address in ORBIT_TRUSTED_PROXIES, and in production it turns away anything that isn't HTTPS. I started with just 127.0.0.1/32, and every request through Railway's edge got a 400.

Railway's network-flow logs showed the edge connecting from 100.64.0.1, so the template trusts 127.0.0.1/32,100.64.0.0/10. That covers Railway's internal range and nothing else. Setting it to 0.0.0.0/0 would get rid of the error too, but then anyone could fake their IP and protocol.

Railway's healthcheck can't pass

This one took me a while. With the trusted range in place, real traffic worked fine, but Railway's healthcheck still got 400 on every attempt. I went into Orbit's source and found that a request from a trusted proxy is only treated as HTTPS if it carries X-Forwarded-Proto: https. Railway's healthcheck doesn't send that header.

So the template doesn't use a Railway healthcheck. Orbit has its own /health/ready endpoint that reports on the database, migrations, scheduler and storage, and you can open it in a browser whenever you want to check on things.

A valid key one time in four

ORBIT_APP_KEY has to be base64 of exactly 32 bytes, and Orbit decodes it strictly. Railway's docs suggest 43 random base64 characters followed by = for this, but the last character of a 32-byte base64 string also holds two padding bits that must be zero. Pick it at random and the key is valid only about a quarter of the time.

The template draws the last character from the 16 values that leave those bits at zero:

${{secret(42, "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/")}}${{secret(1, "AEIMQUYcgkosw048")}}=
Enter fullscreen mode Exit fullscreen mode

A few smaller things

Orbit won't start if it finds an ORBIT_* variable it doesn't know about. I learned that by giving a helper variable the ORBIT_ prefix, so helper variables in the template use other names.

The image runs as UID 65532, and Railway mounts volumes as root, so the template sets RAILWAY_RUN_UID=0 to let Orbit write to its volume.

Railway gives each service one volume, so backups live in /var/lib/orbit/backups alongside attachments.

What won't work on Railway yet

Outgoing email needs SMTP, which you configure in Orbit's admin settings. Railway only allows outbound SMTP on the Pro plan and up. The upcoming shared inbox will need inbound port 25, which Railway doesn't offer at all. For now, think of Orbit on Railway as tasks, docs and chat.

Is it worth trying?

Orbit is young (v0.4 as I write this), and it's changing quickly. Still, for a small team that wants to stop paying per seat for three tools, it's already usable, and running it costs a small server and a database.

If you try the template, tell me in the comments how it went, especially if you run into something I didn't. And if you like the project, give the repo a star.

Top comments (0)