Name: OpenMausBot
Availability: InStock
Author: onepush

Deploy and Host self hosted OpenMausBot (Open-Source AI Bot Team) on Railway

OpenMausBot is an open-source team of AI bots you chat with like contacts, each with its own model, computer and connected apps.

About Hosting OpenMausBot open-source software on Railway (self hosted OpenMausBot template)

This template runs one OpenMausBot service built on the onepush-dev image over the official upstream release.

Why Deploy OpenMausBot, the open-source AI bot team on Railway (Railway Free Trial)

Closed personal-agent apps keep the model, the computer and your data on the maker's side. OpenMausBot runs on your own Railway service, with your own Claude or ChatGPT logins and everything on one volume.

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 OpenMausBot 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.

Railway vs Other Hosting Providers and VPS for OpenMausBot self hosting

Railway handles the public domain, persistent storage and restarts for you, while a VPS gives you full machine control.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	One click deploy with a /data volume and healthcheck wired up.	A Droplet you manage, including Docker, Caddy and upgrades.
AWS	A single service with no VPC or load balancer to set up first.	Deep networking control, useful if you already run AWS.
Hetzner	Managed deploys and a public domain with no SSH needed.	Low cost capacity if you are happy running Docker and Caddy yourself.

Common Use Cases for hosted OpenMausBot

Always-on bot team: Bots work with your laptop closed.
Research bots that browse: Each bot gets its own isolated, persistent browser session, using the bundled Chrome for Testing.
Coding bots on Claude Code or Codex: Bots run on the claude or codex CLIs with your own signed-in subscription. The login persists on the volume across redeploys.
Routines and webhooks: Schedule recurring runs as routines, or trigger bots from outside through webhooks under /hooks, each with its own secret.
Connected apps with approval cards: Connect Gmail, Slack, GitHub, Notion and Linear through Composio. Shell commands, file edits and questions surface as Allow or Deny cards, so you approve sensitive actions before they run.

Dependencies for OpenMausBot Docker hosted on Railway

OpenMausBot runs as one Railway service built from the onepush-dev image. No API key is needed to deploy.

Deployment Dependencies for Managed OpenMausBot Service (single service with a /data volume)

The template creates one service with a volume at /data for chats, routines, bot workspaces, browser profiles, engine logins and paired sessions.

Variable	Purpose
OMB_ADMIN_PASSWORD	Generated secret that protects the /_railway/pair page
OMB_PUBLIC_URL	https plus the service's Railway public domain, used in pairing links
OMB_WEBHOOK_PUBLIC_URL	Same domain, printed as the base for /hooks webhook URLs

Three optional variables are not set by the template: OMB_ANTHROPIC_API_KEY, OMB_SIGNIN_EMAILS and OMB_SIGNIN_MEMBER_EMAILS.

Implementation Details for OpenMausBot (Using the onepush-dev OpenMausBot image built on the official upstream image)

The image ghcr.io/onepush-dev/openmausbot:0.1.136 is built on the upstream ghcr.io/milind-soni/openmausbot:v0.1.136, pinned by digest. It adds Caddy 2.10.2, the Claude Code 2.1.316 and Codex 0.166.0 CLIs, tini as PID 1 and a small pairing gate. Caddy is the only public listener, on port 8080. The server binds 127.0.0.1:8799 and webhooks 127.0.0.1:8800, never exposed, because upstream trusts session-less loopback callers as the owner. Every request through Caddy counts as remote and needs a paired session.

How does OpenMausBot compare against other self-hosted AI agent apps

OpenMausBot vs Open WebUI (Open WebUI Alternative)

Core Focus: Open WebUI is a chat front end for models. OpenMausBot is built around a team of bots, each with its own personality, model and connected apps.
Agent Tools: Bots run on the Claude Code and Codex CLIs with your own logins, behind approval cards for shell commands and file edits.
Browsing: Each bot gets its own isolated, persistent browser session.

OpenMausBot vs LibreChat (LibreChat Alternative)

Core Focus: LibreChat is a multi-provider chat interface. OpenMausBot treats bots as teammates you message like contacts.
Automation: Routines run scheduled bot tasks, and webhooks under /hooks let outside systems trigger bots with per-hook secrets.
Connected Apps: Gmail, Slack, GitHub, Notion and Linear connect through Composio, with approval cards before actions run.

OpenMausBot vs OpenHands (OpenHands Alternative)

Core Focus: OpenHands is a coding agent platform aimed at software tasks.
Team Model: OpenMausBot runs named bots for research, coding and app work in one chat app.

OpenMausBot desktop app vs OpenMausBot on Railway (OpenMausBot Desktop Alternative)

Where It Runs: The desktop app runs on macOS, Windows or Ubuntu and can dictate and control the host desktop.
Always On: Bots on Railway keep working while your laptop is closed.
Limits on Railway: Dictation, host desktop control and Local VMs do not apply on Railway, since Local VMs need Docker or KVM.

How to use OpenMausBot (the OSS AI bot team)?

Wait for the service to go green in the Railway dashboard.
Open https://your-domain/_railway/pair in a browser.
Sign in with the user admin and the OMB_ADMIN_PASSWORD value from the Variables tab. The pairing page fills in a one-time code.
Click Connect. The browser stays paired as admin for 30 days, renewed on use.
Connect an engine in Settings, Engines. For Claude, choose Sign in to Claude. For Codex, choose Connect ChatGPT and finish the device code. Or add a provider key in Settings, Connections, Model providers, though API-key engines are chat only.
Create a bot and start chatting.
Optionally, pair more devices from Settings, Remote access.

To check the server from your terminal, run:

curl https://your-domain/api/health

How to self host OpenMausBot on other VPS Services (OpenMausBot self hosting guide)

If you would rather run OpenMausBot on your own VPS than on Railway, the upstream project supports that path.

Clone the Repository

Upstream's Docker path, documented in docs/deploy-vps.md, uses the deploy folder, which runs the server next to a Caddy edge on ports 80 and 443.

git clone https://github.com/milind-soni/OpenMausBot
cd OpenMausBot/deploy

Install Dependencies

Install Docker with the compose plugin. For the no-Docker paths, install Node 24 or newer and use npx openmausbot serve with --tunnel or --tailscale instead.

docker compose version

Configure Environment Variables

Copy the example env file, then set DOMAIN to your domain and ENGINES to the engine CLIs to bake in, such as the Claude Code and Codex packages.

cp .env.example .env
nano .env

Start the OpenMausBot Application

Pull and start the stack, then pair your first device from inside the container. The /_railway/pair gate only exists in the Railway image.

docker compose pull omb
docker compose up -d
docker compose exec omb node dist-server/openmausbot.js pair --label laptop

Official Pricing of OpenMausBot (OpenMausBot pricing)

OpenMausBot is open-source software released under the Apache-2.0 license, and it is free to download, run and modify. You do not pay the project anything to use it. Your costs are the Railway service and your own Claude or ChatGPT subscription, or API usage if you add a provider key.

OpenMausBot cloud vs self hosted comparison (Pricing, features, costs, and more)

Upstream offers a hosted MausBot Cloud with Starter, Pro and Max plans, but those plans include no AI usage. Self hosting on Railway gives you the same server under your own account, with the volume, logs and upgrade timing in your hands.

Monthly cost of self hosting OpenMausBot on Railway

Railway bills on usage, so your monthly cost depends on how much RAM, CPU and volume space the service consumes. Bots that browse are the heavy part: Railway has no shm-size, so Chrome falls back to /tmp, and you should give the service 2 GB of RAM or more if several bots browse at once.

System Requirements for Hosting OpenMausBot on a VPS

If you self host on a VPS instead, upstream says 2 CPUs and 4 GB of RAM is plenty for a single OpenMausBot server.

Frequently Asked Questions (FAQs)

Where is the admin password?

Copy OMB_ADMIN_PASSWORD from the Variables tab in Railway. Sign in as admin with it on /_railway/pair.

Why is there no normal login page?

OpenMausBot does not use password login on the server. Each device is paired once with a one-time code and stays signed in. The Railway gate at /_railway/pair mints that code behind the generated password, so you never need a terminal.

Do I need an API key to deploy?

No. The template needs no inputs at deploy time.

Why do API keys only give chat?

API-key providers only power chat. Agent tools and computer use need a signed-in engine CLI such as Claude Code or Codex, and that login persists on the /data volume.

What survives a redeploy?

Everything on the /data volume survives a redeploy, including chats, routines, bot workspaces, browser profiles, engine logins and paired sessions.

Can I use email sign-in?

Yes, through the optional variables OMB_SIGNIN_EMAILS for full access and OMB_SIGNIN_MEMBER_EMAILS for chat-only access.