Skip to content

License + terms of use

Hivemind is proprietary, commercial software. It is licensed (not sold) to Seglamater customers under a master services agreement signed between Seglamater and the licensee organization. Without that agreement on file, you have no license to install, run, modify, or redistribute Hivemind.

The authoritative LICENSE file lives at the root of every release bundle (<install-dir>/LICENSE) and is shipped alongside every signed image. The text in this document is a plain-English summary; the agreement itself governs in case of any disagreement.

What your license covers

Once you have a signed master services agreement and a valid invite from Seglamater:

  • 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 receive signed updates on a channel pinned in your bundle (typically canary, beta, or stable). Update binaries are cosign- signed; the installer verifies the signature against the pinned public key before applying. See upgrade.md.
  • You receive support per the tier in your agreement (community, business, enterprise, etc.) — channels and SLAs are defined in the MSA.
  • 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 your license does not cover

  • Source redistribution. You receive signed binary release images and the installer's compose / scripts. You do not receive a license to re-package, sub-license, or redistribute Hivemind to other parties.
  • Modification for redistribution. You may operate Hivemind as part of internal workflows including downstream agents you build on top of its API. You may not fork the product itself and ship the fork.
  • Reverse engineering the protected internals (signing keys, proprietary algorithms, anti-tamper measures) is out of scope of the license.
  • Use after termination. If the master services agreement ends, you uninstall the product. The on-disk state (database, secrets) is yours to keep or destroy at your discretion; the running software is not.

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).
  • The chatalot integration 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 signed images 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), set HIVEMIND_UPDATER_ENABLED=false and supply update bundles out-of-band.

Contacts

  • Sales / licensing inquiries: sales@seglamater.com
  • Support (existing license): support@seglamater.com
  • Security disclosure: security@seglamater.com

Your license, 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.