Opendray – run Claude Code/Codex agents on your own box, drive from anywhere

Self-hosted gateway for Claude Code, Codex, Antigravity, Grok Build, and OpenCode. Run agent sessions on your own infrastructure. Drive from web, mobile, or chat.

🌐 English · 简体中文 · فارسی · Español · Português · 日本語 · 한국어 · Français · Deutsch · Русский

flowchart LR
    subgraph before ["❌ SSH direct"]
        laptop1[Your laptop] -.->|ssh, dies on sleep| host1[Server + CLI]
    end

    subgraph after ["✅ opendray gateway"]
        web[Web] --> gw[opendray]
        phone[Phone] --> gw
        chat[Telegram / Slack / Discord] --> gw
        gw -->|survives disconnect| cli[Claude Code · Codex · Antigravity · Grok Build · OpenCode · shell]
    end

Running Claude Code or Codex over SSH means the agent dies the moment your laptop closes. opendray runs it on a host that stays awake (a Mac mini under your desk, a NAS, a VPS) and lets you reattach from a web admin, a mobile app, or a chat message. Sessions keep executing whether or not anyone is connected. Multiple accounts get pooled with per-tier balancing and live account-switch. A local-first memory layer keeps every embedding on your network.

opendray wraps the AI coding CLIs you already use (Claude Code, Codex, Antigravity, Grok Build, OpenCode, plus any shell) and turns them into something you can drive from anywhere. Run sessions on your home server, NAS, or VPS. Get notified on Telegram when a session goes idle. Reply from your phone to feed the next prompt back in. All over a self-hosted gateway you control end to end.

• 🛰 One backend, three surfaces. Single Go binary serving a React web admin and a Flutter mobile app, with every action also exposed over a REST + WebSocket API for third-party integrations. - 💬 Six bidirectional channels, no walled gardens. Telegram, Slack, Discord, Feishu (飞书), DingTalk (钉钉), WeCom (企业微信), plus a Bridge adapter for anything custom. Replies on any channel route back into the right session. - 🧠 Local-first memory. ONNX / Ollama / LM Studio embeddings with three-scope retrieval (user, project, session), smart ranking, and cross-layer conflict detection. No vector data leaves your network. - 🔌 Integration-grade API. Scoped API keys, per-call audit log, reverse-proxy mounts. Treat opendray as the gateway behind your own product or just as a personal command centre. - 🔑 Multi-account fleet for Claude, Codex, Antigravity. Drop multiple logged-in credential directories onto the host; opendray auto-discovers them via a filesystem watcher, balances new sessions across enabled accounts, and lets you switch a live session between accountswithout losing the conversation(transcript migrates under the hood). Each account row shows live capacity (subscription tier, rate-limit tier, active sessions, last-used, current login email). - 🔒 Self-hosted, licence-clear. Apache 2.0, one static binary, cosign-signed releases with SPDX SBOM. No telemetry, no cloud account, no subscription.

opendray is a Go binary that serves a web admin at /admin/

and a REST + WebSocket API at /api/v1/*

. Here is what it does, in the shapes you would actually see.

$ opendray sessions ls
ID        PROVIDER      PROJECT              STATE     STARTED
ses_a1f   claude-code   app/web              running   2h ago
ses_b2c   codex         internal/session     idle      5m ago
ses_c9d   grok-build    docs/                running   14m ago
ses_d34   shell         misc/deploy-logs     idle      1h ago
bash
$ opendray providers list
PROVIDER      VERSION     ACCOUNTS   ACTIVE   NOTES
claude-code   1.4.11      3          1        auto-discovered via CLAUDE_CONFIG_DIR
codex         0.29.0      2          1        openai login
antigravity   0.7.2       1          0        agy, HOME-isolated
grok-build    2.5.1       1          1        xai
opencode      0.6.3       -          0        local endpoint required
shell         -           -          1        arbitrary

The web admin embeds xterm.js. You see the same PTY the CLI wrote to. Close the browser tab and the session keeps running on the host. Reopen it hours later and the transcript is where you left it.

[claude-code ses_a1f · app/web · 2h 14m]

> refactor the router to lazy-load the mobile view

I'll look at the current router and figure out the cleanest split.

● Read(app/web/src/router.tsx)
  ⎿ 342 lines
● Grep(pattern: "loadable", path: "app/web/src")
  ⎿ found 3 uses
...
sequenceDiagram
    participant U as You (Telegram)
    participant TG as Telegram Bot
    participant OD as opendray
    participant S as Session ses_a1f

    S->>OD: session emits "review needed on line 42"
    OD->>TG: send message + session tag
    TG->>U: notification with quick-reply
    U->>TG: "yes, ship it"
    TG->>OD: webhook incoming
    OD->>S: inject "yes, ship it" as next PTY input
    S->>OD: agent continues

Same shape for Slack, Discord, Feishu, DingTalk, WeCom, and any Bridge-adapter transport.

flowchart LR
    prompt[Agent asks for context] --> ret[memory retrieve]
    ret --> user[USER scope<br/>preferences, workflows]
    ret --> proj[PROJECT scope<br/>architecture, decisions]
    ret --> sess[SESSION scope<br/>this conversation]
    user --> rank[cross-scope rank]
    proj --> rank
    sess --> rank
    rank --> ctx[injected context]

Every scope stores embeddings from your own provider (ONNX bundled, Ollama, or LM Studio). Nothing leaves your network.

flowchart LR
    a[Claude account A<br/>rate-limited] -->|switch| b[Claude account B<br/>fresh quota]
    a -.->|transcript migrates| b
    b --> cont[Session continues<br/>same conversation]

Same for Codex accounts and Antigravity accounts. Carry-context

is on by default; untick to start clean on the new identity.

Sessions | Attach to a running Claude Code, Codex, Antigravity, Grok Build, OpenCode, or shell session from web, mobile, or chat. Sessions survive client disconnect and host reboot. Live transcript overlay for TUIs that skip wheel input. | Providers | 5 first-class AI coding CLIs plus arbitrary shell. Adding a new CLI is a JSON descriptor drop-in under internal/catalog/builtin/ . Per-provider MCP-server injection (Vault, memory, integrations). | Memory | Three-scope retrieval (user, project, session). Local-first embeddings via ONNX, Ollama, or LM Studio. Cross-layer conflict detection. Global knowledge pages injected at spawn. Compiler flywheel distils episodes into reusable playbooks. | Channels | Telegram, Slack, Discord, Feishu, DingTalk, WeCom. Bridge adapter for custom transports. Bidirectional: sessions notify, replies feed back. | Integrations | REST + WebSocket API with scoped API keys, per-call audit log, reverse-proxy mounts. HashiCorp Vault MCP for secret access. Public docs/integration-guide.md |

Opsopendray update / start / stop / providers update

). Encrypted PostgreSQL backups + data exports. Goreleaser pipeline with cosign-signed releases + SPDX SBOM.SecurityProtectSystem=strict

systemd hardening. Multi-tenant-safe scoped tokens.A single Go binary on your host runs the show. Clients drive sessions through HTTP/WebSocket, the session manager spawns each AI CLI in its own PTY, and the memory layer keeps shared state in Postgres with vector embeddings from your own provider.

flowchart LR
    subgraph clients [Clients]
        web[Web admin<br/>React SPA]
        mob[Mobile app<br/>Flutter]
        chat[Chat<br/>Telegram, Slack,<br/>Discord, Feishu,<br/>DingTalk, WeCom]
        api[Third-party apps<br/>REST + WS]
    end

    subgraph gw [opendray gateway · single Go binary on your host]
        direction TB
        http[HTTP + WS<br/>chi · auth · audit]
        sess[Session manager<br/>PTY · ring buffer]
        mem[Memory layer<br/>three-domain retrieval]
    end

    subgraph cli [AI CLIs · spawned via PTY]
        cc[Claude Code]
        co[Codex]
        ag[Antigravity]
        gb[Grok Build]
        oc[OpenCode]
        sh[Shell]
    end

    subgraph data [Persistence · stays on your network]
        pg[(PostgreSQL<br/>+ pgvector)]
        em[ONNX · Ollama<br/>LM Studio embeddings]
    end

    clients --> http
    http --> sess
    http --> mem
    sess --> cc
    sess --> co
    sess --> ag
    sess --> gb
    sess --> oc
    sess --> sh
    sess -.-> mem
    mem --> pg
    mem --> em

Everything in the diagram runs on your network. No cloud dependencies, no inference outside your control.

opendray	Claude Desktop	Cursor	CLI over SSH	ChatGPT Desktop
Session survives client disconnect	✅	❌	❌	❌
Multi-account pool with live switch	✅	❌	❌	❌	❌
Cross-session memory layer	✅	❌	Partial	❌	Partial
Host filesystem + tool use	✅	Limited	✅	✅	Limited
Mobile client with feature parity	✅	❌	❌	Partial
Chat channel adaptors	✅ (6)	❌	❌	❌	❌
Self-hosted	✅	❌	❌	✅	❌
Licence	Apache 2.0	Proprietary	Proprietary	(varies)	Proprietary

opendray	Open WebUI	LibreChat	Dify
Runs actual agent CLI (not just chat)	✅	❌	❌	Partial
Tool use + file writes on host	✅	❌	❌	Sandboxed
Multiple AI coding CLIs in one gateway	✅ (5)	❌	❌	❌
Cross-session memory	✅	Basic	Basic	✅
PTY session with terminal reattach	✅	❌	❌	❌
Chat channel adaptors	✅ (6)	Partial	Partial	✅
Licence	Apache 2.0	MIT	MIT	Apache 2.0

Solo dev running a homelab. You already have a Mac mini, NAS, or Proxmox box running 24/7. You've been running Claude Code over SSH but the session dies every time your laptop sleeps. You want the CLI to keep going, and you want to reattach from your phone on the train. opendray is the gateway that puts your host between you and the CLI.

Small-team lead standing up shared AI infrastructure. Your team has 3-5 Anthropic accounts spread across work and personal plans. You want to pool them, watch usage per account, and let anyone on the team drive a session from the browser. opendray gives you multi-account pooling, per-account observability, scoped API keys per teammate, and a mobile app they can install without an App Store submission.

Integrator building on top of a session-runner. You are building a product that needs to spawn Claude Code, Codex, or Grok Build sessions with tool use, and you don't want to reimplement session lifecycle, PTY handling, memory, or channel routing. opendray exposes every action over REST + WebSocket with scoped keys, per-call audit logs, and reverse-proxy mounts. Treat it as your agent runtime.

Linux / macOS / WSL2

curl -fsSL https://raw.githubusercontent.com/Opendray/opendray/main/scripts/install.sh | bash

Windows sets up WSL2 first, then runs the Linux installer inside it. details →

irm https://raw.githubusercontent.com/Opendray/opendray/main/scripts/install-windows.ps1 | iex

Walks through Postgres setup, AI-CLI install, admin credentials, and service registration, landing a running gateway in ~5 to 10 minutes. See for what the wizard does, the file layout it creates, options, and troubleshooting.

scripts/README.md

Want the manual walkthrough?Read[, a 15-minute end-to-end guide that mirrors what the wizard does so you can verify each step yourself.]docs/getting-started.md

Install globally and put opendray

on PATH

:

npm install -g opendray

Or run on demand without installing:

npx opendray

This installs just the binary, no wizard, no service, no Postgres. The package pulls the matching opendray-{linux,darwin}-{x64,arm64}

platform binary via optionalDependencies

(the esbuild / Biome pattern, no postinstall

, no network call at install time). Good for scripted environments, ephemeral runners, or when you already run your own Postgres and process supervisor.

You still bring a database and start the gateway yourself:

export OPENDRAY_DATABASE_URL="postgres://opendray:pw@127.0.0.1:5432/opendray?sslmode=disable"
export OPENDRAY_ADMIN_PASSWORD="$(openssl rand -base64 24)"
opendray migrate
opendray serve        # → http://127.0.0.1:8770/admin/

Full walkthrough (pgvector setup, config.toml

, running as a systemd / launchd service, and updating) in docs/install-binary.md.

Default. Stops the gateway and removes the binary, but keeps your config.toml

, data directory (bcrypt keyfile, sessions, notes, vault), logs, and the PostgreSQL database so a re-install resumes where you left off:

curl -fsSL https://raw.githubusercontent.com/Opendray/opendray/main/scripts/uninstall.sh | bash

Full purge. Also drops the PG database + role, deletes config / data / logs, removes the service user. Includes a post-delete verification step that bails loudly if anything survived:

curl -fsSL https://raw.githubusercontent.com/Opendray/opendray/main/scripts/uninstall.sh | OPENDRAY_PURGE=1 bash

After install, the opendray

binary handles its own lifecycle, with no need to remember systemctl

/ launchctl

incantations:

sudo opendray update --restart   # download latest release, verify SHA, atomic replace + restart
sudo opendray providers update   # bump installed AI CLIs (claude / codex / antigravity) to npm-latest
opendray providers list          # see which AI CLIs are installed + their versions
sudo opendray start              # start | stop | restart | status, wraps systemd / launchd

opendray --help

lists the full subcommand set.

Every supported path includes session spawn, AI-CLI access, encrypted backups, and the full integration API. opendray is a host-resident gateway; it spawns AI CLIs via PTYs and shares process state (~/.claude

, ssh-agent, project files) with them. That model is incompatible with the container isolation that production Docker would impose, so Docker is not a supported deployment path for v2.x.

Path	Best for	Jump to
📦 Pre-built binary
"Just run it", Linux / macOS, any supervisor

systemd unitProduction deploy §A** macOS LaunchDaemon**Production deploy §C** Build from source**QuickstartbelowFor a full walkthrough with prereqs and troubleshooting, see docs/quickstart.md. The condensed dev path:

cp config.example.toml config.toml
$EDITOR config.toml          # set [database].url, [admin].password

cd app/web && pnpm install && pnpm build && cd ../..

go run ./cmd/opendray migrate -config config.toml

go run ./cmd/opendray serve -config config.toml

This runs OpenDray in the foreground; Ctrl-C kills it. For a long-running daemon, see Production deploy below.

Four supported deploy paths, pick whichever fits your environment. Each one gives you auto-restart on crash, persistent state, and separation of secrets from config.

The recommended Linux deploy path. Ships a hardened unit at deploy/systemd/opendray.service with sandboxing (

ProtectSystem=strict

, NoNewPrivileges

, MemoryDenyWriteExecute

, capability scrub), migrate

-then-serve

boot, and a 20s graceful-stop window.Get a binary first. Either grab a pre-built archive from the Releases page (opendray_*_linux_<arch>.tar.gz

, which unpacks to a single opendray

binary), or build from source via the Quickstart above (go build ./cmd/opendray

).

sudo install -m 0755 /path/to/opendray /usr/local/bin/opendray

sudo useradd -r -s /usr/sbin/nologin -d /var/lib/opendray opendray
sudo install -d -o opendray -g opendray -m 0700 /var/lib/opendray

sudo install -D -m 0640 config.example.toml /etc/opendray/config.toml
sudo $EDITOR /etc/opendray/config.toml             # set [database].url etc.
sudo install -D -m 0640 -o root -g opendray /dev/null /etc/opendray/env.d/secrets
sudo $EDITOR /etc/opendray/env.d/secrets           # OPENDRAY_ADMIN_PASSWORD=…

sudo cp deploy/systemd/opendray.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now opendray

sudo systemctl status opendray
sudo journalctl -u opendray -f --no-pager

The unit runs opendray migrate

as ExecStartPre

, so the first boot applies all migrations before serve

ever starts. Restarts are on-failure

with a 5s back-off and a 5-burst limit per minute.

For LXC without systemd, FreeBSD rc.d

, OpenRC, or anything else. Build once, run with whatever supervisor you already use:

goreleaser release --clean --snapshot
ls dist/                  # opendray_*_linux_amd64.tar.gz etc.

Then point your supervisor (s6, runit, supervisord, runwhen) at:

/usr/local/bin/opendray serve -config /etc/opendray/config.toml

Pre-flight: run opendray migrate -config /etc/opendray/config.toml

once before the first serve

, or as a pre-start hook in your supervisor of choice.

For Apple Silicon Mac mini / Mac Studio running 24/7. Ships a LaunchDaemon at deploy/launchd/com.opendray.opendray.plist that starts at boot before any user login, restarts on crash with a 5s throttle, and logs to

/usr/local/var/log/opendray/

.

sudo install -m 0755 ./opendray /usr/local/bin/opendray
sudo install -d -m 0755 \
  /usr/local/etc/opendray \
  /usr/local/var/lib/opendray \
  /usr/local/var/log/opendray
sudo install -m 0640 config.example.toml /usr/local/etc/opendray/config.toml
sudo $EDITOR /usr/local/etc/opendray/config.toml    # set [database].url etc.

sudo /usr/local/bin/opendray migrate \
  -config /usr/local/etc/opendray/config.toml

sudo cp deploy/launchd/com.opendray.opendray.plist /Library/LaunchDaemons/
sudo chown root:wheel /Library/LaunchDaemons/com.opendray.opendray.plist
sudo chmod 0644 /Library/LaunchDaemons/com.opendray.opendray.plist
sudo launchctl bootstrap system /Library/LaunchDaemons/com.opendray.opendray.plist

sudo launchctl print system/com.opendray.opendray
tail -f /usr/local/var/log/opendray/opendray.log

Restart with sudo launchctl kickstart -k system/com.opendray.opendray

; unload entirely with sudo launchctl bootout system/com.opendray.opendray

.

Postgres on macOS: install via Homebrew (brew install postgresql@17 && brew services start postgresql@17

) and point [database].url

at postgres://$USER@127.0.0.1:5432/opendray

. Add pgvector

with brew install pgvector

and CREATE EXTENSION vector

inside the opendray database.

For Proxmox-specific LXC notes (PTY in unprivileged containers, networking, cgroup tweaks), see deploy/lxc/proxmox-pty-notes.md.

For reverse-proxy / TLS termination (nginx, Caddy, Traefik, Cloudflare Tunnel), see docs/operator-guide.md §Topology.

export OPENDRAY_BACKUP_KEY="$(openssl rand -base64 32)"
export OPENDRAY_BACKUP_ENABLED=1

export OPENDRAY_BACKUP_PG_DUMP_PATH=/opt/homebrew/opt/postgresql@17/bin/pg_dump
export OPENDRAY_BACKUP_PG_RESTORE_PATH=/opt/homebrew/opt/postgresql@17/bin/pg_restore

Restart opendray; the sidebar grows a Backups page (/backups

) for encrypted PostgreSQL dumps + restore, and /export

for zip-bundle data exports + import. See docs/operator-guide.md §Backup for the full lifecycle.

A single Go binary carries the whole web bundle, so no Node runtime is required at runtime, no separate static-file server, no Caddy/nginx needed. Cloudflare Tunnel terminates TLS in front of :8770

.

cmd/opendray/   binary entry point
internal/       Go backend (gateway, sessions, memory, channels,
                integrations, git, search, one package per domain)
app/web/        React + Vite admin SPA (embedded in the binary)
app/mobile/     Flutter app (iOS + Android)
app/shared*/    cross-surface shared UI + i18n strings
docs/           guides: install, getting-started, integration, ops
deploy/         systemd / launchd / LXC units + install scripts

app/web/

builds a single SPA into internal/web/dist/

, which the Go binary embeds and serves at /admin/*

. The Vite dev server at :5173

proxies /api

to :8770

for HMR-driven development.

cd app/web && pnpm dev               # http://localhost:5173
go run ./cmd/opendray serve -config ../../config.toml   # other terminal

cd app/web && pnpm build              # writes ../../internal/web/dist
cd ../..
go build ./cmd/opendray               # bakes dist into the binary
./opendray serve -config config.toml

See app/web/README.md for the frontend stack (React + Vite + Tailwind v4 + shadcn/ui + TanStack Router/Query + Zustand + xterm.js) and per-W milestone notes.

app/mobile/

is a Flutter app for iOS and Android with feature parity with the web admin. It attaches to a running gateway over HTTPS. Enter the Gateway URL + admin login on first launch and you get the same Sessions / Channels / Integrations / Memory / Git surfaces. There is no App Store / Play Store build by design (self-hosted, single-tenant): you build it yourself and sign it with your own identity.

** → Build & install guide.** Make the gateway reachable from the phone, then sideload an Android APK or install on iPhone via Xcode. (

all 10 languages; switch at the top of the guide.)

opendray is a self-hosted gateway that wraps the AI coding CLIs you already use (Claude Code, Codex, Antigravity, Grok Build, OpenCode, and shell) and turns them into sessions you can drive from a web admin, a Flutter mobile app, or six chat channels (Telegram, Slack, Discord, Feishu, DingTalk, WeCom). One Go binary. Apache 2.0. Your infra, your data, your tokens.

Five first-class providers as of v2.10.x: Claude Code (Anthropic), Codex (OpenAI), Antigravity (Google agy

), Grok Build (xAI), and OpenCode. Plus arbitrary shell for anything else. Adding a new CLI is a JSON descriptor under internal/catalog/builtin/

; no adapter code required for common cases.

Claude Desktop and ChatGPT Desktop are chat clients that run on your laptop and die when the laptop closes. opendray runs the actual agentic CLI on a host that stays awake and lets you reattach from anywhere. Sessions survive client disconnect, laptop sleep, and network drops. Multiple accounts get pooled with live switch between them.

Four things SSH does not give you: (1) session survives when you disconnect (no tmux

gymnastics required, though you can still use tmux inside), (2) attach from a phone or a chat channel, not just a terminal, (3) shared memory layer across every session on the host, (4) multi-account pool with per-tier balancing and live account-switch mid-conversation.

Those are chat frontends against a model API. They send prompts to api.openai.com

(or similar) and render the response. opendray runs the actual agent CLI process on your host, complete with tool use, file writes, memory, and MCP servers. If a task needs Read

/ Edit

/ Bash

on your host filesystem, opendray does it; chat frontends do not.

Yes. Drop the logged-in credential directories on the host (Claude uses CLAUDE_CONFIG_DIR

, Antigravity uses $HOME

isolation) and opendray auto-discovers them via a filesystem watcher. New sessions balance across enabled accounts by tier + capacity. You can switch a live session between accounts without losing the conversation (transcript migrates under the hood). Rate-limit auto-failover carries context by default.

PostgreSQL on your host (bring your own instance, or use the one the installer bootstraps). Embeddings come from your own provider (ONNX bundled, Ollama, or LM Studio). No vector data, transcripts, or memory entries leave your network. No telemetry. No cloud account. opendray

never phones home.

Not currently (v2.x). opendray spawns AI CLIs via PTYs and shares host process state (credential directories, ssh-agent, project files) with them. That is incompatible with the container isolation production Docker imposes. Use the pre-built binary and systemd or launchd (Linux + macOS both have one-line installers). See Production deploy.

NAS: yes on Synology / QNAP / TrueNAS-Scale (anything with Linux + Postgres). Mac mini: yes, this is a common deploy (LaunchDaemon shipped). Raspberry Pi: works on Pi 4 / Pi 5 but underpowered for concurrent sessions; single-user hobby use only.

Apache 2.0. Free forever. No paid tier, no telemetry, no phone-home. Sponsors welcomed (see .github/FUNDING.yml).

Read CONTRIBUTING.md and

. Concrete ways in: (1) translate a README or docs page into a language we already ship, (2) add a provider descriptor for a new AI coding CLI under

CODE_OF_CONDUCT.md

internal/catalog/builtin/

, (3) write a channel adaptor for a chat platform we do not cover, (4) contribute screenshots for the docs, (5) file a bug or a feature request. PRs need CI green; translations are advisory-only; no CLA.:docs/getting-started.md

start here if you're new. Zero to first session in 15 minutes, including installing the wrapped CLIs and bootstrapping Postgres.: install from the npm package or a release binary (bring your own Postgres) and run it as a systemd / launchd service.docs/install-binary.md

: 5-minute dev environment (assumes you already know the moving parts).docs/quickstart.md

: build & install the Flutter mobile app; sideload an Android APK or install on iPhone via Xcode, then point it at your gateway.docs/mobile-app.md

: deploy + ops reference for production-ish setups.docs/operator-guide.md

: how to write an external integration in any language.docs/integration-guide.md

: versioning strategy (major-as-generation).VERSIONING.md

: release history.CHANGELOG.md

Current generation: v2.10.x. See CHANGELOG.md for release history and

for the major-as-generation policy (major = product generation, not strict SemVer "breaking change").

VERSIONING.md

This generation ships:

One-line installer + uninstaller wizards(Linux + macOS; Windows funnels through WSL2). Walks the operator through Postgres bootstrap, AI-CLI install, admin credentials, listen address, binary install, schema migration, and service registration.Self-managing binary.opendray update / start / stop / restart / status / providers list / providers update

so operators don't touchsystemctl

/launchctl

for routine ops.Goreleaser release pipeline. Cross-compiled binaries (linux/darwin × amd64/arm64), cosign keyless signing (Sigstore), SPDX SBOM, atomically verified self-update.

go test -race ./...        # backend
cd app/web && pnpm build   # web (TS strict + vite production build)

End-to-end smoke flows are tracked in commit messages per milestone. A Playwright harness is a planned follow-up.

v1 (Opendray/opendray

) is the legacy codebase, now archived. v2 is the current and active generation, feature-complete and the only branch receiving development. Of the 16 v1 builtins, four migrated into the v2 backend; the rest became client-side features, channel adaptors, or integration-API consumers.

Apache 2.0. See LICENSE. (v1 was MIT; v2 is licensed independently.)

source & further reading

github.com — original article