Synaplan
Open-source AI platform for companies: self-hosted AI agents, GDPR-compliant chatbot widget, RAG knowledge base, WhatsApp and Outlook AI, MCP, multi-model routing. Docker, Kubernetes or hosted in Germ
An employee-initiated shared exit tracker: what you submitted, what HR validated, what is overdue.
BusinessTypeScript · PLpgSQLGitHub @Pri00padOnlineOwner 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
Employee-initiated exit tracking and verification
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗An employee-initiated shared exit tracker for employees leaving small and mid-sized companies that still manage offboarding manually through email, WhatsApp, spreadsheets and HR follow-ups.
The employee tracks each exit item, submits evidence, and sends HR a private verification link. The verifier approves, requests more information, or rejects — no HR account needed. The employee always sees what has been validated and what is overdue.
ExitProof does not provide legal advice and does not calculate F&F entitlement. A verification link proves possession of the link, not the identity of the person who used it.
Next.js 16 (App Router) · TypeScript · Tailwind CSS 4 · Supabase (Auth email + password, Postgres, Storage) · Vercel
cp .env.example .env.local # fill in Supabase values; keep NEXT_PUBLIC_SITE_URL=http://localhost:3000
npm install
npm run dev # http://localhost:3000
Database: run each file in supabase/migrations/ once in the Supabase SQL Editor, in filename order, one file per run (each run must succeed before the next): the initial schema, then the request-workflow enums, then the request workflow (tables, RLS, functions, private evidence and hr-documents buckets and storage policies). In Supabase Auth, enable Email sign-ups and turn Confirm email off.
For local development against a separate Supabase project, put its three values in .env.development.local (git-ignored). npm run dev reads it in preference to .env.local; next build / next start do not.
Import the repository with the default Next.js settings and set these environment variables (Production):
| Variable | Kind |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | config |
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY | config (safe in the browser) |
NEXT_PUBLIC_SITE_URL | config: the production origin, e.g. https://<project>.vercel.app (no trailing slash) |
SUPABASE_SECRET_KEY | secret — server-only, never prefix with NEXT_PUBLIC_ |
NEXT_PUBLIC_* values are inlined at build time, so redeploy after changing them. If NEXT_PUBLIC_SITE_URL is unset on Vercel, verification links fall back to the project's production domain.
See docs/PLAN.md for the approved plan, data model and acceptance criteria.