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.