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
AI restaurant operating system — VAPI voice ordering, Clover/Square POS integration, real-time order management, WebGPU analytics dashboard
Translation pending
BusinessTypeScript · PLpgSQLGitHub @SashreekMallemOnlineOwner 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
Loading the full README. The saved excerpt is shown below.
Heyloo is a multi-tenant voice-AI answering/booking SaaS: small businesses
across eight verticals (auto shops, veterinary clinics, law firms, dental
practices, real estate, motels, restaurants, and a generic front-desk
template) forward their business line to a Heyloo number. A Retell-powered
AI agent, compiled from a canonical per-vertical conversation template,
answers, triages, and books — with every call backed by real-time
availability, a real booking record, and a compliant AI/recording
disclosure.Read the full README ↗Heyloo is a multi-tenant voice-AI answering/booking SaaS: small businesses across eight verticals (auto shops, veterinary clinics, law firms, dental practices, real estate, motels, restaurants, and a generic front-desk template) forward their business line to a Heyloo number. A Retell-powered AI agent, compiled from a canonical per-vertical conversation template, answers, triages, and books — with every call backed by real-time availability, a real booking record, and a compliant AI/recording disclosure.
The complete spec is docs/SYSTEM_DESIGN.md
(authoritative). See also docs/MASTER_PLAN.md
(business decisions), docs/BUILD_PLAN.md (the
agent build waves this repo is being assembled from), and
CLAUDE.md (binding rules for anyone — human or agent —
building against this repo).
apps/ Frontend apps — empty until T5 (frontend stack
decision doc), see apps/README.md
packages/
canonical-types/ Provider-agnostic types: agent state graph, tool
contracts, domain model — the only thing core
code is allowed to depend on
adapters/ Provider isolation boundary — every third-party
SDK (Retell, Twilio, Stripe, PayPal, ...) lives
in its own packages/adapters/<provider>; see
packages/adapters/README.md for the rule and why
ui/ Shared components for the dashboard/admin/portal
templates/ The 8 vertical agent templates (T6)
supabase/
migrations/ Postgres schema + RLS (T1)
functions/ Edge functions: voice hot path (T3), billing/
lifecycle (T4)
config.toml Supabase CLI project config
.github/workflows/ci.yml typecheck · lint · test · build · migrations
check · RLS cross-tenant probe
Requires Node.js ≥ 22 and pnpm (pinned via packageManager — enable
Corepack or install the matching pnpm version yourself).
pnpm install
pnpm run typecheck # tsc -b across every package, via Turborepo
pnpm run lint # biome check . (formatter + linter + import rules)
pnpm run build # tsc -b build output for every package
pnpm run test # vitest, per package
pnpm run dev # turbo run dev (once an app exists — see apps/README.md)
pnpm run lint:fix and pnpm run format apply Biome's automatic fixes.
Copy .env.example to .env and fill in real values —
every variable is commented with what it's for and which task wires it up.
Never commit a file with real secrets in it.
Everything else — architecture, data model, security/compliance,
reliability, the vertical conversation designs, the admin panel, and the
full build order — lives in docs/. Start with
docs/SYSTEM_DESIGN.md.