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
Capture leads, reply on WhatsApp and email, and move every deal forward from one workspace. Flazyn is the conversational CRM for growing teams. Join early access.
BusinessJavaScript · CSSGitHub @ZomicccOnlineOwner 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.
The public website for Flazyn, the CRM that turns conversations into customers.
Live at https://flazyn.com (early access).
React 18 · Vite 5 · Framer Motion · three.js via @react-three/fiber (lazy-loaded) ·
React Router 6 · Vercel (static pages + one serverless function).
Set in Vercel → Project → Settings → Environment Variables (and in .env.local for dev —
see .env.example). Never prefix them with VITE_; they must stay server-side.Read the full README ↗The public website for Flazyn, the CRM that turns conversations into customers. Live at https://flazyn.com (early access).
React 18 · Vite 5 · Framer Motion · three.js via @react-three/fiber (lazy-loaded) · React Router 6 · Vercel (static pages + one serverless function).
npm install
npm run dev # http://localhost:5174 — forms work locally via .env.local
npm run build # client build → SSR build → prerender every route
npm run preview # serve the production build on http://localhost:5175
Set in Vercel → Project → Settings → Environment Variables (and in .env.local for dev —
see .env.example). Never prefix them with VITE_; they must stay server-side.
| Variable | Required | Purpose |
|---|---|---|
RESEND_API_KEY | yes | Sends form submissions through Resend |
CONTACT_TO_EMAIL | yes | Inbox that receives contact and early-access submissions |
CONTACT_FROM_EMAIL | no | Sender on a Resend-verified domain, e.g. Flazyn <[email protected]> |
src/
├─ lib/site.js business facts (name, domain, email) + navigation — edit here first
├─ lib/seo.js title/description for every route → prerender, sitemap, client nav
├─ lib/posts.js blog posts
├─ lib/motion.jsx scroll reveals, 3D tilt, page transitions (reduced-motion aware)
├─ three/Scenes.jsx procedural 3D logo scene + mascot (lazy chunk, loads when idle)
├─ components/ Navbar, Footer, Logo, Stage3D (3D loader), ProductDemo, Forms, sections
├─ pages/ Home, productPages, solutionPages (FeaturePage template), legal/…
├─ entry-server.jsx build-time render entry
api/contact.js Vercel function: validates forms and emails them via Resend
scripts/prerender.mjs writes dist/<route>.html with meta, Open Graph, JSON-LD, sitemap, robots
<title>, description, canonical,
Open Graph/Twitter tags and JSON-LD (Organization, WebSite, BreadcrumbList, FAQPage, BlogPosting).sitemap.xml and robots.txt are generated on each build. A real 404.html is served with 404 status.<Route> in App.jsx and an entry in lib/seo.js.vercel.json).Privacy Policy: /privacy · Terms: /terms · Data deletion instructions: /data-deletion (old /legal/* URLs redirect).
/admin)A built-in CMS for one admin account:
How it works: the site's copy stays in the components as defaults; the admin stores overrides
(src/lib/content.jsx, validated by api/_lib/content.js). Content and media live in Vercel Blob
(api/_lib/storage.js); the build (scripts/prerender.mjs) bakes the published content into every page.
Admin code is lazy-loaded and never shipped to regular visitors.
Setup (Vercel):
BLOB_READ_WRITE_TOKEN).npm run admin:password -- "a-strong-password" → add ADMIN_EMAIL, ADMIN_PASSWORD_HASH,
ADMIN_SESSION_SECRET as environment variables.main, add its URL as VERCEL_DEPLOY_HOOK_URL./admin.Locally (npm run dev) without a Blob token, content and uploads are stored in .cms-local/ (gitignored).