🛡️ Self-hosted · GitHub-native · Event-sourced

The OS of OSS people.

OpenSquire is a self-hosted, opinionated open-source company companion for maintainers, founders, and contributors — a shared operational brain across chat, GitHub, and the web.

View on GitHub How it works

● MVP0 shipped — first dogfood ecosystem: Gno / Gnoland

What it is

Not a chatbot with GitHub tools.

A shared OSS operating layer where three surfaces are lenses over the same canonical state.

💬 Chat

Telegram / Slack / CLI — private conversation, digests, and approvals for the humans running the project.

🐙 GitHub

The public operational surface. GitHub App, fine-grained short-lived tokens, every write approval-gated.

🖥️ Web cockpit

The persistent mission-control surface. Live view of the ecosystem, powered by SSE.

How it works

One canonical event log. Everything else is a projection.

No surface owns truth. The raw log is canonical; every projection is rebuildable.

append-only event log  +  versioned config  +  rebuildable projections

Chat ── GitHub ── Web → Core → Event Store → Projections → Agents / Skills / Workers

Design principles

Boring on purpose. Trustworthy by construction.

The ecosystem is the core abstraction — one instance, many ecosystems. Not the repo.
Approval-gated writes — intent → policy → visibility → draft → approval → exec → event → notify.
Rebuildable state — replay the log to reconstruct any projection. The log is the source of truth.
Self-hosted & inspectable — Go, SQLite (WAL) for v0, Postgres later. Your data stays yours.
Multi-tenant from day one — tenant and ecosystem fields baked into every event.

Quickstart

Run it in one command.

make run                    # start stewardd — web on :8080, SSE live stream
go run ./cmd/steward doctor # health check
go run ./cmd/steward replay # rebuild projections from the event log
go run ./cmd/steward export # dump the raw event log as JSONL

Then open http://localhost:8080/ for the mission-control shell.

Read the docs