Skip to main content

Self-hosting

The Splyntra Community edition is fully open source and self-hostable. It gives you traces, cost analytics, and baseline secret/PII detection with nothing to pay and nothing to phone home. Enterprise features (governance, agent identity, advanced scorers) are added on top of the same core — see Cloud for the managed option.

Quick start​

git clone https://github.com/splyntra/splyntra
cd splyntra
docker compose up

This brings up the core stack:

  • collector — OpenTelemetry ingest (OTLP/HTTP on :4318) plus detection and cost computation.
  • dashboard — the web UI on http://localhost:3000.
  • storage — Postgres for traces, findings, and metadata.

Point your agent at http://localhost:4318 (see the Quickstart) and open the dashboard.

Architecture​

The open core is a single OpenTelemetry-native pipeline: spans arrive at the collector, detectors run per span to produce findings, model spans are costed, and everything is written to Postgres and served by the dashboard. There are no runtime calls out to any hosted service — the community stack is self-contained.

agent ──OTLP──▶ collector ──▶ Postgres ──▶ dashboard
                   │
                   └─ detection (secrets/PII) + cost

Configuration​

Configure the collector and dashboard via environment variables:

# collector
SPLYNTRA_DB_DSN=postgres://splyntra:secret@postgres:5432/splyntra?sslmode=disable
SPLYNTRA_OTLP_HTTP_ADDR=:4318

# dashboard
SPLYNTRA_API_URL=http://collector:8080
note

API keys are stored as SHA-256 hashes, and the dashboard talks to the collector with a trusted service token — the browser never holds a replayable per-org key. Keep these secrets out of source control.

Migrations​

Database schema is managed by ordered migration files applied at startup. When running locally with docker compose up, migrations are applied automatically before the services start, so a fresh database is never missing a table.

Upgrading​

Pull the latest images and re-run compose:

git pull
docker compose pull
docker compose up -d

Migrations are idempotent, so upgrades apply cleanly against an existing database.

When to choose Cloud instead​

Self-host when you want full control and data residency. Choose Splyntra Cloud when you'd rather not run infrastructure and want SSO/SCIM, per-org plan gating, and the managed Enterprise feature set.

Next steps​