agentos
★ 4.9kAbout
Community Ratings
No ratings yetNew this week
Read recap →Features
- built-in agents
- session management
- universal transcript format
- automatic persistence
- framework integrations
- Bash/Node.js/Python execution
- filesystem mounts
- bindings
- cron jobs and webhooks
- multiplayer collaboration
Details
- Last Updated
- Nov 5, 2026
- Created
- Feb 7, 2024
- Install Methods
- package-managersource
- Requirements
- Node.jsnpmRivet Actor runtime (for @rivet-dev/agentos)
- Default Port
- 6420API server / agent runtime
- Authentication
- oauth
- API
- REST
- Backup & Export
- built-in-backup
- Privacy & Independence
- Cloud: Optional
- User Model
- Multi-User
- Deployment
Deployment: Docker Compose ✓Single Container — minimal hosting footprintsingle container
Run agentos yourself
Pick how much you want to manage.
netcupBest match
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
Hetzner
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
DigitalOcean
Full control
A small server, then Docker Compose.
About 20 minutes with Docker
1 more way to host
Some links earn us a commission. netcup pays us one and is our preferred VPS host.
Is this your project? Sponsor a listing
Run agentos with Docker Compose
Compose file from the agentos project repository.
1 service
no resource limits declared
needs persistent storage (8 volumes)
docker/dev/compose.yaml · @ 06db7b1 · scanned Nov 3, 2026
name: agentos-dev
services:
dev:
build:
context: ../..
dockerfile: docker/dev/Dockerfile
working_dir: /build
# Keep the container resident; drive it with `just dev-shell` / `docker compose exec`.
command: ["sleep", "infinity"]
stdin_open: true
tty: true
ports:
# RivetKit engine: actor gateway + /inspector/* + custom-tab assets. The
# hosted dashboard runs in the host browser and points at this port.
- "6420:6420"
# Vite dev server for examples/browser-terminal.
- "5173:5173"
# Docker Desktop's embedded resolver (192.168.65.7) intermittently stops
# answering, which surfaces as EAI_AGAIN storms during `pnpm install`.
dns:
- 1.1.1.1
- 8.8.8.8
environment:
# Unambiguous sidecar resolution; `just dev-bootstrap` builds this path.
AGENTOS_SIDECAR_BIN: /build/target/debug/agentos-sidecar
RUST_BACKTRACE: "1"
# Vite/RivetKit must listen on all interfaces to be reachable from the host.
HOST: 0.0.0.0
# RivetKit binds the engine it spawns to loopback, which a published port
# cannot reach. This is the supported override for that bind address
# (rivetkit's `engineHost`); setting RIVET__GUARD__HOST does not work,
# because RivetKit passes its own value to the engine process.
RIVET_RUN_ENGINE_HOST: 0.0.0.0
volumes:
- ../..:/build:cached
# Host node_modules are darwin-native — mask every bind-mounted tree that
# holds platform binaries or build output with a container-owned volume.
- node_modules:/build/node_modules
- cargo_target:/build/target
- toolchain_target:/build/toolchain/target
# Only `toolchain/c/vendor` is safe to mount: it holds the large wasi-sdk
# and llvm-project downloads and nothing deletes it. `sysroot`, `libs`,
# `.cache`, and `toolchain/vendor` are `rm -rf`'d wholesale by the build,
# which fails with EBUSY on a mount point — leave them on the bind mount.
- toolchain_c_vendor:/build/toolchain/c/vendor
# Caches outside the working tree.
- cargo_registry:/usr/local/cargo/registry
- cargo_git:/usr/local/cargo/git
- pnpm_store:/root/.local/share/pnpm/store
volumes:
node_modules:
cargo_target:
cargo_registry:
cargo_git:
pnpm_store:
toolchain_target:
toolchain_c_vendor:
This file may be out of date. Check the agentos documentation for current setup steps.
Tags
Track your self-hosted stack
Bookmark software to try, rate tools you've used, and keep your collection in one place.