Skip to content

License + terms of use

Hivemind is free software under the GNU Affero General Public License v3.0 only (AGPL-3.0-only). You may read, build, run, modify, and redistribute it under those terms — including for commercial and production use — provided you honor the AGPL's obligations, in particular the network-copyleft obligation in section 13.

A commercial license is available if you need terms outside the AGPL-3.0 — contact Info@Seglamater.com. (Formal commercial-license terms are being finalized.)

The authoritative LICENSE file (the verbatim AGPL-3.0 text) lives at the root of every release bundle (<install-dir>/LICENSE), alongside NOTICE, which carries the copyright line and the commercial-license pointer. Both are materialized into every release bundle — the artifact your install actually uses — so a self-hosted install has the full terms on disk. The text in this document is a plain-English summary; the LICENSE text governs in case of any disagreement.

What the AGPL gives you

  • You run Hivemind on your own infrastructure. Self-hosted, on your hardware or VPS of your choice. Seglamater never sees your data, your prompts, your agents' work product, or your users' identities — the product is BYOK and the LLM calls go directly from your host to your chosen provider.
  • You get the source, and you may modify it. You are not dependent on Seglamater continuing to exist, or continuing to agree with you.
  • You may redistribute it, modified or not, under the same AGPL-3.0-only terms, with the source and this license included.
  • Your data is yours. The customer-side Postgres volume, secrets directory, agent profiles, audit log, and integration tokens stay on your host. Seglamater has no access path absent operator-initiated support sessions you authorize.

What the AGPL asks of you

  • Source availability, including over a network. If you modify Hivemind and let users interact with it remotely — a hosted service, a multi-tenant deployment, anything reached over a network — those users must be offered the corresponding source of your modified version. Running an unmodified Hivemind for your own organization triggers nothing here; it is modification plus remote users that does.
  • Same license downstream. Derivative works you distribute or network-serve are AGPL-3.0-only too. You cannot relicense them.
  • Keep the notices. LICENSE, NOTICE, and copyright notices travel with the software.

If any of that is incompatible with what you need to build, that is exactly what the commercial license is for — ask, rather than working around the AGPL.

What your Seglamater agreement covers (separate from the license)

The AGPL is the software license, and it is not something you buy. A master services agreement with Seglamater is a commercial agreement, and it governs things the AGPL says nothing about:

  • Signed updates on a managed channel pinned in your bundle (typically canary, beta, or stable). Each release manifest is cosign-signed, and the updater verifies that signature against the pinned public key before it applies anything; the manifest names the exact image digest and the pull is pinned to it. See upgrade.md.
  • Access to the Seglamater container registry and to per-customer invite bundles.
  • Support per the tier in your agreement (community, business, enterprise, etc.) — channels and SLAs are defined in the MSA.

If your agreement ends, you lose the managed-update channel, registry access, and support. You do not lose your license to the software — that is the AGPL's, not ours to withdraw. You may keep running, modifying, and self-updating the version you have under AGPL-3.0-only.

Third-party components

Hivemind incorporates open-source components under their own licenses:

  • PostgreSQL (PostgreSQL License) for storage.
  • Rust standard library + crate dependencies under their respective open-source licenses (MIT / Apache-2.0 / BSD primarily). The full third-party attribution lives in the release artifact at licenses/THIRD_PARTY.md (forthcoming — currently in flight as a future release artifact).
  • chatalot-crypto, the E2E crypto crate shared with chatalot, linked as a git dependency. It is GPL-3.0-family and shares a single copyright owner with Hivemind; AGPL-3.0 section 13 expressly permits the combination.
  • The chatalot integration otherwise uses chatalot's published HTTP and WebSocket APIs (chatalot is a separate Seglamater product with its own license terms). If you also run a chatalot instance, that software is governed by its own license, not this one.

The third-party attribution list will be a separately rendered file shipped with each release; for the current release, the in-tree Cargo.toml set of dependencies is the authoritative source.

Telemetry

Hivemind transmits no telemetry to Seglamater by default. The managed-update sidecar polls updates.seglamater.app for the latest release on your channel and pulls the manifest-pinned image from registry.seglamater.app when you click Apply — those two endpoints are the only outbound calls Seglamater sees, and they reveal only your channel + the version your bundle is pinned at, not any operational data.

If you want to disable even the update poll (an air-gapped install), bring the stack up without the updater compose profile — the sidecar is profile-gated and is simply not started, so nothing polls. Supply update bundles out-of-band instead. (The server's admin Updates routes then return 503 for apply/applies/snapshots; status and check still respond.)

Contacts

  • Commercial licensing inquiries: Info@Seglamater.com
  • Sales: sales@seglamater.com
  • Support (existing agreement): support@seglamater.com
  • Security disclosure: security@seglamater.com

Your channel and support tier are pinned in your bundle's client_id and support_tier metadata; share those with support when you open a ticket.