Self-hosting
Availability
Open core · self-host + all Splyntra Cloud plans
The source-available Splyntra core runs with a single command. It brings up the full pipeline — collector, security and evaluation services, dashboard, and their datastores — so you can send your first trace locally in minutes.
Start the stack
git clone https://github.com/splyntra/splyntra
cd splyntra
docker compose up
Migrations are applied automatically on first start, so a fresh database is never missing a table.
Services and ports
docker compose up starts the application services and their backing
infrastructure:
| Service | Port | Role |
|---|---|---|
collector | 4318 | OTLP/HTTP ingest and query API |
security | 8001 | Detection (secrets, PII, moderation, injection) |
evaluation | 8002 | Scorers and evaluation runs |
web | 3000 | Dashboard |
Backing infrastructure:
| Service | Role |
|---|---|
postgres (16) | Metadata |
clickhouse (24.3) | Traces, logs, metrics |
valkey (7.2) | Cache / queue |
nats (2.10, JetStream) | Messaging |
minio | S3-compatible storage for evaluation datasets |
First run
- Open the dashboard at
http://localhost:3000. - The collector accepts OTLP/HTTP at
http://localhost:4318(paths/v1/tracesand/v1/logs). - In development, the fallback ingest key
splyntra_dev_keyis accepted. It is rejected in production — setENV/NODE_ENVto anything other thandevelopmentand it fails closed. Mint a real key from the dashboard for any non-local use.
Send your first trace
Point an SDK (or your OTLP exporter) at the local collector:
export SPLYNTRA_ENDPOINT="http://localhost:4318"
export SPLYNTRA_API_KEY="splyntra_dev_key" # dev only
Run an instrumented agent once, then open Traces in the dashboard to see the span tree, its risk score, and cost. The Quickstart walks through instrumenting an agent end to end.
Next steps
- Configuration — the collector and dashboard environment reference.
- Kubernetes & Helm — deploy the stack on a cluster.
- Enterprise (self-hosted) — add governance, identity, and SSO under a license.