Skip to content
brnrdbrnrd

Self-hosting brnrd

Self-hosting means keeping the brnrd daemon and coding-agent CLIs on a machine you control. That can be your workstation or an always-on host with access to the repositories and credentials the resident needs. It requires no brnrd account and no payment.

Start with the normal Install, then configure a self-hosted gate:

Terminal window
brnrd gate setup telegram
brnrd daemon install
brnrd daemon status

The installer uses a systemd user service on Linux or a LaunchAgent on macOS. Use brnrd daemon logs for service output and brnrd daemon uninstall to remove it.

What you operate

Section titled “What you operate”
  • the host and its network exposure;
  • the Claude Code or Codex login;
  • gate credentials and authorization choices;
  • repository and resident-state backups;
  • updates to this alpha software.

Project work and runner execution remain local to that host. A self-hosted Telegram, Slack, or GitHub gate still carries messages through the transport’s own service.

Read Security & privacy before exposing a gate. In particular, Telegram and Signal bind authorization to the paired sender (plus an explicit allowlist), and self-hosted GitHub checks the sender’s repository permission; only Slack is channel-scoped, authorizing every member of the configured channel rather than an individual sender.

For managed service availability and pricing, see brnrd.dev. This page makes no parity or hosted-compute claim.