Synaplan
開源 AI 平台,供企業使用:自行託管的 AI 代理、符合 GDPR 的聊天機器人小工具、RAG 知識庫、WhatsApp 與 Outlook AI、MCP、多模型路由。Docker、Kubernetes 或託管於 Germ
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Operations system for independent studios — knows when a project is going over scope while you can still bill for it.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗An operations system for independent studios and solo consultants, built around one idea most project tools miss: scope is a contract, and it leaks.
Freelancers and small studios don't usually lose money on projects they priced wrong. They lose it on projects they priced correctly and then quietly over-delivered. The extra revision, the "quick call", the feature that wasn't in the statement of work — each one is small enough to absorb, and collectively they turn a profitable engagement into a break-even one. By the time it's visible in a time report, the money is already spent.
Harvest tracks hours. Notion tracks tasks. Bonsai sends invoices. None of them watch the gap between what you contracted to deliver and what you are actually delivering, and tell you while you can still do something about it.
Every project in Keel carries an explicit scope: deliverables with estimates, and a contracted value. As time is logged, Keel continuously compares burned value against contracted value, and completion against estimate. When a project starts consuming budget faster than it produces deliverables, it gets flagged — with an explanation of why, and a one-click path to turn the overage into a change order you can actually send.
The pitch is one sentence: know a project is going over while you can still bill for it.
https://keel-beige-seven.vercel.app — redeployed automatically after each day's commit.
Data pages return 500 in production until a hosted database is attached.
Vercel's filesystem is read-only, so the file:./keel.db fallback has nothing
to open. Create a free Turso database and run
./scripts/set-database.sh <libsql-url> <auth-token> to fix it. Local
development and CI are unaffected — tests run against an in-memory database.
Under construction, one increment per day, on the plan in
ROADMAP.md. Progress is visible in the commit history — the
build is autonomous, so each commit is a single roadmap task.
npm install
cp .env.example .env
npm run db:generate && npm run db:migrate
npm run dev
Tests: npm test. Production build: npm run build.
Next.js 16 (App Router), TypeScript, Tailwind v4, Drizzle ORM over libSQL (a local SQLite file in development, Turso in production without a driver change), Vitest.