Synaplan
기업을 위한 오픈소스 AI 플랫폼
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.