system4us/salamandr-worker repository overview

⁠Salamandr

A self-hosted-first support-ticket helpdesk — Zendesk/Freshdesk-shaped, but you keep the database.

Source: https://github.com/system4us/salamandr⁠ · License: AGPL-3.0

⁠Two images, always deployed together

• system4us/salamandr-backend — the API + the web UI (the compiled frontend is embedded into this same binary, so there's no separate frontend container to run).
• system4us/salamandr-worker — background jobs: email polling, SLA breach detection, scheduled reports, chat listeners, webhook delivery, billing reconciliation.

Both come from the same build, share the same tag, and expect the same .env.

⁠Quick start

The deploy/production/ directory in the source repo is the actual deployment — one docker-compose.yml that pulls these images, plus a .env.example with every setting documented in place:

git clone https://github.com/system4us/salamandr.git
cd salamandr/deploy/production
cp .env.example .env
# set IMAGE_NAMESPACE=system4us, IMAGE_TAG=<a tag below>, and the REQUIRED
# values .env.example marks — passwords, SESSION_SECRET, ADMIN_EMAIL/PASSWORD
docker compose up -d

Postgres, Redis and object storage each sit behind a Compose profile, so the same file covers "everything on one box" (COMPOSE_PROFILES=bundled-db,bundled-cache) and "point it at a database/cache you already run" — remove a profile and set the matching URL instead. See the repo's docs/deployment.md for what a managed Postgres/Redis/object-storage provider needs to support.

⁠Tags

There is one edition of this image: the same binary always links every module this project ships — SSO, chat-platform mirroring, calendar sync, e-commerce and CRM/issue-tracker connectors, custom RBAC roles, and more. "Community" isn't a smaller build — it's what this image looks like with no license installed. Upload a signed license file from the Admin Panel's License tab to unlock the gated modules; nothing else changes, no redeploy needed.

• vX.Y — a released version. Pin one for anything but a quick trial.
• latest — the most recent release.

⁠What's free vs. licensed

Everything in the open-source repository — the full ticketing core, email/web-form/live-chat channels, bot flows, Mattermost/Discord chat mirroring, community-authored WASM plugins — runs with no license at all, capped at 5 staff seats. A license removes the seat cap and unlocks SSO, Slack/Zulip/Microsoft Teams mirroring, calendar sync, e-commerce and CRM/issue-tracker connectors, custom roles, outbound webhooks, API keys, audit-log viewing, white-label branding and advanced reporting. Full breakdown: https://github.com/system4us/salamandr#community-vs-enterprise⁠

⁠Why self-hosted

Nothing in this codebase phones home — no telemetry, no usage reporting, no license server; verification is fully offline. Third-party integrations (AI providers, chat platforms, e-commerce) are opt-in per tenant, never on by default. Every Meta-backed integration connects through your own Meta App and credentials, never a shared vendor-owned intermediary sitting in the middle of your customer conversations.

⁠Links

• Source & full documentation: https://github.com/system4us/salamandr⁠
• Deployment guide (managed databases, object storage, backups, reverse proxies): see docs/deployment.md in the repo
• Kubernetes: deploy/helm/salamandr/ in the repo
• Issues: https://github.com/system4us/salamandr/issues⁠