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
An AI assistant that answers from your own listings and company information, hands the chat to a person when needed, and keeps customers, campaigns and reports in one place.
BusinessPython · TypeScriptGitHub @Youssef-Adel91OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
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
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Multi-tenant SaaS for Saudi real-estate agencies: one inbox for WhatsApp / Instagram / Messenger, an AI assistant grounded in the agency's own listings and company profile, customer management with PDPL consent, campaigns, billing in SAR, and a developer API.
| Folder | What |
|---|---|
omniflow-backend/ | FastAPI gateway, Kafka workers, Celery tasks, Alembic migrations, tests, ops scripts |
omniflow-frontend/ | Next.js 16 app (Arabic RTL + English): public site and dashboard |
omniflow-deploy/ | Production compose files, nginx, monitoring, backup/restore, RUNBOOK.md |
docs/ | Architecture, API, env reference, go-live checklist, per-feature notes, night-2 reports |
docs/architecture.md → docs/env-reference.md → omniflow-deploy/RUNBOOK.mddocs/go-live-checklist.md, docs/launch-decisions-and-manual-tests.mddocs/user-guide-ar.mddocs/api.md, docs/comment-replies.md, docs/einvoice.mddocs/retention.md, docs/security-audit.mddocs/ui-quality.md, docs/morning-verification.mdIMPLEMENTATION_STATUS.md# 1. dependencies (Postgres 16 + PgBouncer, Redis, Kafka/Redpanda, Qdrant, MinIO): your docker compose
# 2. backend
cd omniflow-backend && python -m venv .venv && . .venv/bin/activate && pip install -r requirements.txt
cp .env.example .env # fill in; never commit .env
alembic upgrade head
python -m scripts.dev_up # checks ports/dependencies/ngrok, then starts API + workers + celery + frontend
# 3. frontend alone
cd ../omniflow-frontend && npm ci && npm run dev
Windows shortcuts: run-backend.bat, run-workers.bat, run-ngrok.bat.
cd omniflow-backend && python -m unittest discover -s tests -t . # DB-backed tests need OMNIFLOW_TEST_DATABASE_URL / OMNIFLOW_TEST_RLS_URL (scratch DB)
cd omniflow-frontend && npx tsc --noEmit && npx eslint src && node --test tests/*.test.cjs && npx next build
cd omniflow-frontend && E2E_BASE_URL=http://localhost:3100 npx playwright test e2e/public.spec.ts
CI (.github/workflows) runs on a self-hosted runner for pull requests into main.