Community Edition download

Install Tessallite from one signed self-hosted bundle.

Download the Community Edition package, verify the release signature, add your licence, and start the full Tessallite stack on your own server.

Install path

Four steps from licence to running stack.

The Community bundle is built for local control: verify it, add your signed licence, and run without needing a managed Tessallite service.

1

Register

Request a free Community licence and keep the signed licence file with your installation material.

2

Download

Get the current signed Tessallite Community release bundle and its checksum manifest.

3

Verify

Check the release checksum and Ed25519 signature before unpacking or installing.

4

Run

Add license.json, run the installer, and open the Tessallite UI on your server.

Downloads

Choose the artifact that matches your job.

Most users need the all-in-one bundle. Platform teams can inspect the included Kubernetes material before moving to Enterprise deployment support.

All-in-one Community bundle

One signed archive containing the product, container images, installer, checksum manifest, signature, Helm chart material, and security evidence pack.

Current release: latest. Free download; you also need a free licence to activate. Requires Docker and Docker Compose v2.

Kubernetes material

The Helm chart ships inside the bundle under helm/ for platform teams planning OpenShift or Kubernetes deployment.

Developer source

Use the source checkout for engineering review and contribution. It is not the recommended production installation path.

Tessallite Community Edition is free under the Tessallite Community Licence. The full terms (and all licence & legal documents) are being finalised; the current licence also ships with your download. Questions? info@tessallite.io.

Security and verification

Everything a reviewer needs is attached to the release.

Tessallite Community is designed for local inspection before it runs. The bundle carries checksums, signatures, deployment material, and the review evidence your IT team needs.

  • Release signing key id: tessallite-prod-2026.
  • Licence checks run locally and support offline evaluation.
  • The evidence pack is included under evidence/ for review before rollout.
# integrity: checksums of every file
sha256sum -c SHA256SUMS

# authenticity: verify the release signature
python3 - <<'PY'
import base64
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PublicKey
PUB = "/by3PGaeLD425bBkMrAbD2NeHROHyjLHVA37pS5w3+0="
sig = base64.b64decode(open("SHA256SUMS.sig").read().splitlines()[1])
Ed25519PublicKey.from_public_bytes(base64.b64decode(PUB)).verify(
    sig,
    open("SHA256SUMS", "rb").read(),
)
print("signature OK")
PY

Signed artifacts

The archive, checksum manifest, and detached signature let teams verify that the release has not been altered.

Offline licence checks

The self-hosted stack verifies the signed licence locally. An evaluation install does not need a licence server to run.

Review evidence

The bundle includes architecture notes, port matrix, image list, SBOM material, and release signatures for IT review.

Evidence pack contents

  • ArchitectureService map, trust boundaries, and deployment assumptions.
  • NetworkPort matrix, container list, and local endpoint summary.
  • Supply chainImage list, SBOM material, checksums, and release signature files.
  • OperationsOffline statement, upgrade notes, and health-check guidance.

Security advisories

Public advisories appear here after a fix is available. The feed is loaded from the issuer service when configured.

The advisory feed will appear here once the service is configured.

Install command flow

Unpack, add your licence, start the stack.

Replace X.Y.Z with the release version shown on this page: latest.

tar -xzf tessallite-community-X.Y.Z.tar.gz
cd tessallite-community-X.Y.Z

cp /path/to/your-license.json ./license.json
# Put LICENSE_PUBLIC_KEYS into .env when provided.

./install.sh

# Open http://localhost:3000
# SYSTEM_ADMIN_EMAIL and SYSTEM_ADMIN_PASSWORD are in .env

Day-2 operations

Keep the installation observable and recoverable.

Health

Run ./healthcheck.sh after installation or upgrade to confirm every service is healthy.

Logs

Use Docker Compose logs to inspect individual services, such as gateway, model-service, or query-router.

Upgrade

Download the new signed bundle, verify it, stop the stack, and run ./install.sh from the new release.

Need the licence first?

Register for Community, then return here to download and verify the signed bundle.