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 release archive, its checksum manifest, and the detached signature — all published as separate files.

3

Verify

Check the archive checksum and Ed25519 signature before extracting. The verification files are served alongside the archive, not inside it.

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, Helm chart material, and security evidence pack. The checksum manifest and detached signature are published as separate files for pre-extraction verification.

The release download is not available from this page yet. The licence request is separate and does not start a bundle download.

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, including the source-available and open-code terms — are published in the legal centre; 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.
# Step 1: download the archive and its two detached verification files.
# The companion filenames append to the FULL archive name, so the checksum
# manifest names the .tar.gz itself and can be checked before extracting.
V=X.Y.Z
curl -LO https://downloads.tessallite.io/tessallite-community-$V.tar.gz
curl -LO https://downloads.tessallite.io/tessallite-community-$V.tar.gz.SHA256SUMS
curl -LO https://downloads.tessallite.io/tessallite-community-$V.tar.gz.SHA256SUMS.sig

# Step 2: verify the archive integrity BEFORE extracting.
# The manifest is a single `sha256sum -c` line covering the archive itself.
sha256sum -c tessallite-community-$V.tar.gz.SHA256SUMS

# Step 3: verify the release signature over the exact manifest bytes.
# Prerequisite: pip install cryptography
# The .sig file is two lines: the signing key id, then the base64 signature.
pip install cryptography
python3 - "$V" <<'PY'
import base64, sys
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PublicKey
V = sys.argv[1]
PUB = "/by3PGaeLD425bBkMrAbD2NeHROHyjLHVA37pS5w3+0="
sig = base64.b64decode(
    open(f"tessallite-community-{V}.tar.gz.SHA256SUMS.sig").read().splitlines()[1])
Ed25519PublicKey.from_public_bytes(base64.b64decode(PUB)).verify(
    sig,
    open(f"tessallite-community-{V}.tar.gz.SHA256SUMS", "rb").read(),
)
print("signature OK -- safe to extract")
PY

# Step 4: extract only after both checks pass.
tar -xzf tessallite-community-$V.tar.gz

Signed artifacts

Two detached files are published alongside the archive: <archive>.tar.gz.SHA256SUMS (a checksum manifest of the archive itself) and its Ed25519 signature .tar.gz.SHA256SUMS.sig. Both are named after the full archive, so teams verify integrity and authenticity before extraction.

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.

Verify the archive first, then 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.

Capability maturity

Stable, beta, and preview capabilities.

Core semantic modelling, BI access via the JDBC and XMLA protocols, query acceleration, row-level security, multi-tenant isolation, the AI conversational agent, and the Excel task-pane add-in are stable and acceptance-tested. The Headless REST API, column-level security, and several other capabilities are implemented and available but are Beta — unit-tested, with acceptance testing still in progress. The cards below list exactly what is stable and what carries a maturity qualification. Both Community and Enterprise share the same codebase and the same maturity status for every feature.

Beta

Implemented end to end and unit-tested, but acceptance testing is in progress. Includes: the Headless REST API, column-level security (data tags), SSO (SAML/OIDC), comprehensive audit logging, the KPI system, multi-calendar support, semi-additive measures, the webhook event system, the embed API, and YAML/dbt model import. Evaluate these; do not rely on them contractually for production until they are promoted to stable.

Preview connectors

PostgreSQL and BigQuery are stable. Snowflake, Redshift, SQL Server, and Spark/Hive are implemented and available but require environment-specific acceptance validation. Connect and evaluate; report issues.

Integrations (dry-run only)

Collibra and Solidatus integrations support mapping, schema, admin UI, and dry-run export. Live synchronisation is not yet available; the connectors will indicate this clearly.

Stable core

Semantic modelling, dimension and measure definitions, aggregate and pocket-table acceleration, BI access via the JDBC and XMLA protocols, row-level security, multi-tenant isolation, the model builder UI, the AI conversational agent, and the Excel task-pane add-in are stable and acceptance-tested. The Headless REST API and column-level security are Beta (see the Beta card); they are available but not yet acceptance-tested.

Need the licence first?

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