Skip to content
Notedigit
Get started

Your server, your notes. Nothing reaches us.

Notedigit runs on your own server. Your notes, accounts and logs stay there, every request an assistant makes is on the record, and the people responsible hear about every change that matters.

  • Self-hosted on your VPS
  • Nothing sent to us
  • Every MCP call logged
  • Email on every significant event

Everything stays on your side.

Notedigit is not a service we run for you. You install it on a server you control, and everything it keeps lives there.

vps.your-company.com

  • Your notes

    Cloned from your git host only while an assistant reads them, and deleted after 15 minutes without activity.

  • Accounts and credentials

    Names, emails, password hashes, two-factor secrets and passkeys.

  • Access rules

    Your team, its roles and invitations, and who is assigned to which repository.

  • Repository settings

    Addresses, branches, IP allowlists and read-only deploy keys, encrypted at rest.

  • The audit log

    Every MCP session and tool call, kept for 90 days by default.

What reaches Well Digit

  • Your name, email and the messages you send us
  • Your license purchase, processed by Paddle

What never does

  • Your notes
  • Your audit log
  • Your accounts and passwords
  • Search queries and note paths

Your instance talks only to your git host, with the read-only key you approved, and to the assistants your people connect.

Every MCP request is on the record.

Each session and each tool call is written to the audit log on your server. Owners and admins review it in the dashboard, filtered by repository, person or date.

  • Which client connected, and its version
  • Which person, signed in with OAuth or a personal access token
  • The IP address the request came from
  • Which tool ran, with its arguments
  • Whether it succeeded, and how long it took

Tool arguments are encrypted and visible to owners and admins only. The log is kept for 90 days by default; you choose the period.

Time Client Person Tool Argument Time taken
09:41:07 Claude maria@your-company.com search expense policy 38 ms
09:41:09 Claude maria@your-company.com read_file kb/policies/expenses.md 12 ms
10:02:44 Cursor dev@your-company.com list_files playbook/ 9 ms
10:15:30 Release agent token nd_7f3a… read_file runbooks/deploy.md 11 ms
Example entries. Your log shows your own clients, people and notes.

See what your assistants can read.

In the dashboard, open any connected repository to see every Markdown file it holds, and read a note exactly as it is on your branch. Check by hand what your assistants can find before they find it.

Notedigit Company Handbook · Files
  • kb/README.md
  • kb/policies/expenses.md
  • kb/policies/leave.md
  • kb/policies/security.md
  • kb/processes/onboarding.md

kb/policies/expenses.md

Expenses

  • Book travel for client visits through the shared travel account.
  • Train tickets are reimbursed in full with the receipt attached.
  • Submit claims within 30 days of the trip.
Example repository and note.

An email for every significant event.

When something changes who can read what, the people responsible hear about it. Emails are sent from your instance, through the mail account you connect.

EventWho is told
A repository is added Owner and admins
A repository is removed Owner and admins
A deploy key is added Owner and admins
A deploy key is removed Owner and admins
An assistant signs in to a repository for the first time Owner, admins and the person who connected it
Someone is given access to a repository That person
Someone is invited to the team The invited person
A new member joins The new member
An email address needs verifying The account owner
A password reset is requested The account owner

Locked down by default.

  • OAuth 2.1 sign-in

    Every assistant connects as a named person. No shared keys.

  • Access per repository

    People read only the repositories they are assigned to, or the ones you open to the whole team.

  • Read-only by design

    Three tools — search, read_file, list_files — and Markdown only. Write tools don’t exist.

  • Read-only deploy keys

    Generated per repository; the private key is encrypted and never shown.

  • Invitation-only accounts

    No public sign-up. Two-factor authentication and passkeys available to every account.

  • Encrypted at rest

    Repository addresses, keys and log arguments are sealed with two separate keys.

  • IP allowlists

    Optionally limit a repository to the networks you trust.

  • Rate limits

    Requests are capped per token, per address and per repository.

Book a demo