Self-Hosting

Overview

You can run Agent OS entirely on your own machine or server. Optionally, you can point it at a skill store (registry URL) that you host or use. This page gives a short checklist; for deployment details see Deployment.

Architecture (self-hosted)

[Users / devices]
       │
       ▼
[Agent OS server]  ← ~/.agent-os (config, DB, agents, skills)
       │            ← PORT=3010, HOST=127.0.0.1 (or reverse proxy)
       │
       ├──► [Channels]  Telegram, Slack, Discord, Signal, Viber
       │     (webhooks; server must be HTTPS in production)
       │
       └──► [Optional store]  Registry URL in config
                 (GET registry + GET skill content)

• Agent OS runs on one machine. All data (config, DB, agents, skills) lives under AGENT_OS_HOME (default ~/.agent-os). No separate “Integrations” service in this repo; channels are built in (webhooks + config).
• Channels — For production, expose the server over HTTPS (reverse proxy) and set each channel’s webhook URL on the platform. Tokens and default agents are in config.
• Store — Optional. If you run or use a skill store, set its registry URL in Settings so the dashboard and API can list and install skills by slug.

Checklist

Agent OS

• Install and run (e.g. bun run dev or sulala start). See Deployment.
• Run sulala onboard once to create config and seed agents/skills.
• Set PORT and HOST if not default. For remote access, use a reverse proxy and HTTPS.
• Set AI API keys in Settings or ~/.agent-os/config.json (OpenAI, OpenRouter, etc.).
• (Optional) Set registry URL to your store’s registry so you can install skills from the store.
• (Optional) Configure channels in Settings (tokens, default agents). For webhooks, ensure the server is reachable over HTTPS and webhook URLs are set on each platform.

Optional store

• If you run a store app, deploy it (e.g. Vercel or your server). Set its base URL and any admin/auth env. Point Agent OS at its registry URL as above.

Summary

Agent OS is a single server (Bun). Self-hosting means running that server on your own host or VPS, with config and DB under ~/.agent-os. Channels and an optional store are configured via config and Settings; no separate Integrations server is required in this repo.