Lalabase
Tickets, Doku, Zeiterfassung und Kundengespräche an einem Ort, durchsuchbar per KI. Für Softwarefirmen mit Kundenprojekten. Open Source: auf deinem eigenen Server oder in unserer Cloud in Deutschland.
Translation pending
One MSP platform: assets, support, portal. RMM, ticketing, PSA and scheduling. Open source · AGPL-3.0 · self-hosted.
BusinessJavaScript · CSSGitHub @veritas-mspOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Self-hosted MSP platform combining PSA, ITSM, and RMM in one place.
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Self-hosted MSP platform combining PSA, ITSM, and RMM in one place.
Veritas centralizes day-to-day MSP operations: companies and contacts (PSA), support tickets (ITSM), infrastructure supervision, and RMM. Everything runs on your own infrastructure.
This repository is a monorepo: clone once, then run with Docker or from source.
Ticket views, filters, and assignment for your support team.
Full ticket detail: conversation thread, properties, linked hardware, and resolution workflow.Read the full README ↗Veritas centralizes day-to-day MSP operations: companies and contacts (PSA), support tickets (ITSM), infrastructure supervision, and RMM. Everything runs on your own infrastructure.
| Component | Path |
|---|---|
| API & database | veritas/backend |
| Web UI | veritas/frontend |
| Windows RMM agent | veritas/RMM/Agents/windows |
This repository is a monorepo: clone once, then run with Docker or from source.
Ticket views, filters, and assignment for your support team.
Full ticket detail: conversation thread, properties, linked hardware, and resolution workflow.
Infrastructure inventory by site and device type, including servers, storage, network, workstations, and RMM agents.
Language, timezone, appearance, and organization settings from a single admin area.
Dedicated sign-in for end users: equipment, documents, and tickets from their company portal.
git clone https://github.com/veritas-msp/veritas.git
cd veritas
cp .env.docker.example .env
docker compose up -d --build
Then open http://SERVER_IP:3000/setup (secrets and database are configured in the wizard).
| Service | URL |
|---|---|
| Web UI | http://SERVER_IP:3000 |
| API | http://SERVER_IP:3001 |
Data is stored in Docker volumes veritas-db and veritas-uploads.
If the frontend build runs out of memory on a small VPS, add 2–4 GB of swap, then rebuild:
sudo fallocate -l 4G /swapfile && sudo chmod 600 /swapfile
sudo mkswap /swapfile && sudo swapon /swapfile
docker compose build --no-cache veritas-frontend && docker compose up -d
Requires Node.js 20+, PostgreSQL 15+, npm, Git.
git clone https://github.com/veritas-msp/veritas.git
cd veritas/veritas
cp backend/.env.example backend/.env
cp frontend/.env.example frontend/.env
npm run install:all
npm run dev
Open http://localhost:3000/setup
| Variable | File | Description |
|---|---|---|
JWT_SECRET / ENCRYPTION_KEY | backend/.env | App secrets |
DATABASE_URL | backend/.env | Optional until /setup |
VERITAS_EDITION | backend/.env | community or pro |
REACT_APP_API_BASE_URL | frontend/.env | Default http://localhost:3001 |
REACT_APP_VERITAS_EDITION | frontend/.env | community or pro |
| Service | Port |
|---|---|
| Frontend | 3000 |
| Backend | 3001 |
| PostgreSQL | 5432 |
Put a reverse proxy (nginx, Traefik, Caddy, …) in front of port 3000 for TLS. Set ALLOWED_ORIGINS and FRONTEND_BASE_URL in .env to your public URL.
Community and Pro differ in modules and quotas (companies, contacts, agents, RMM endpoints, etc.). Details: EDITIONS.md.