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
Your team's job hunt, together.
Translation pending
BusinessTypeScript · JavaScriptGitHub @iamankooOnlineOwner 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
Apply karde bhai
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗A private job-tracking web app shared by three members: Anni (blue), Lukky (yellow) and Rishii (red). Screens: Login, Dashboard, All Jobs, Add Job, My Applications, Analytics.
Status: Phases 1 (secure login), 2 (Google Sheets data layer) and 3 (All Jobs, Add Job, My Applications) are implemented, and the live Google connection is verified for all three members. Phases 1-4 are done and Phase 5 (deployment) is complete: production is live at https://jobsbyarillabs.vercel.app (see docs/deployment). Work proceeds one phase at a time with explicit owner approval.
npm install
cp .env.example .env.local # add GOOGLE_* values for data routes; see docs/setup/README.md
npm run dev # http://localhost:3000
Without env vars, development uses documented prototype access codes and a dev-only session secret. Production refuses to start sessions without SESSION_SECRET and fails closed without access codes.
npm run dev, npm run build, npm start, npm run lint, npm run typecheck, npm test, npm run test:e2e, npm run test:e2e:isolated (browser workflow + responsive suites on an in-memory backend), npm run sheets:test-setup (prepare a disposable test spreadsheet).
assets/ – original reference screenshots and photos (never modified)public/assets/ – browser-served copies of the profile photossrc/app – pages and route handlers; src/components; src/lib (auth, validation); src/configtests/ – unit, integration, e2eAll data comes from the Google spreadsheet; an empty sheet shows an empty state with an Add New Job button, never sample data.
GET/POST /api/jobs, GET /api/applications, PUT /api/applications/[jobId], GET /api/sheets/status. Jobs are shared; each member has an independent application status. Identity always comes from the session. Without Google configuration these routes return a safe 503; there is no sample data. Details: architecture.md.
Access codes are verified on the server only. Sessions are signed, HTTP-only cookies; identity is always taken from the validated session, never from browser-supplied names or IDs. Never commit .env* files or service-account JSON.