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.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證自托管的 MSP 平台,將 PSA、ITSM 與 RMM 結合於同一處。
AI 翻譯
Self-hosted MSP platform combining PSA, ITSM, and RMM in one place.
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
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.檢視完整 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.