Documents and notes decision

Kibu

A capable developer can reproduce a usable subset (notes, voice capture, reports, exports) in about a week, but Kibu's certified compliance posture and proprietary lesson-content are durable advantages that make a full replacement impractical for an individual.

Visit website
SubscriptionCustom pricing
Initial build38 hours
Monthly upkeep6 hours + $100
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Kibu alternatives, with the arithmetic →

What a replacement has to do

  • Capture staff input (text or voice) → auto-generate structured case notes → store notes per member → generate exportable reports and state-compliant forms → admins review and track compliance/metrics.

What it still won’t have

  • SOC 2 attestation and documented HIPAA compliance (formal certifications)
  • Kibu's pre-built lesson/content library and tailored lesson plans
  • Enterprise onboarding, support, and polished usability for non-technical staff
  • Uptime/SLA guarantees and managed hosting/ops

What remains hard

  • Compliance and regulationHIPAA Compliant. Fully Encrypted.
Read the build prompt

First-year cost

No published price

Kibu does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal self-hosted Kibu-like service using React for the frontend, Node.js + Express for the API, and Postgres for storage; deploy on AWS (ECS/Fargate or Elastic Beanstalk) with S3 for file storage and CloudFront for assets. Core features in scope: (1) staff login and role-based permissions, (2) member profiles and CRUD for notes, (3) voice capture UI that uploads audio and a background job using an open speech-to-text model or API (configurable) to produce transcripts, (4) a report generator that scans stored notes to render exportable PDFs and state-form templates, (5) a small lesson-content library with tagging and attach-to-member functionality, (6) audit logs, basic time-tracking, and CSV/PDF export. Out of scope: pursuing SOC 2 or HIPAA certification, advanced analytics, multi-tenant billing, and managed onboarding. Include input validation, error handling, role/permission tests, API tests, and basic end-to-end tests for note creation → report export. Provide README with deployment steps, environment variables, and a script to seed demo content.
How we checked6 sources · 2/3 runs agreed · evidence score 22

How the score was reached

  • Pay verdict base20
  • An open-source build was found+5
  • 6 cited sources+3
  • Hard moats found in the evidence-6
  • Evidence score22

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat quoted from the page