Built for modern engineering stacks
The problem
Engineering knowledge decays faster than code evolves
Every merge request changes your system. Confluence pages, architecture diagrams, and onboarding docs rarely keep up — and nobody notices until something breaks.
3–6 months
Average onboarding time
New engineers spend months tracing dependencies, reading stale wikis, and asking the same questions.
67%
Docs out of sync
Most internal documentation diverges from production within weeks of the last major refactor.
2× MTTR
Incident cost without context
Teams without a living system model take twice as long to diagnose production failures.
How it works
From repository to engineering knowledge in five steps
Connect GitHub
OAuth to your account. Notatkii creates a per-repository webhook with its own secret.
Analyse repository
Structural analysis maps services, databases, APIs, and dependencies — typically under a minute.
Generate Blueprint
Start from a draft or guided wizard, or analyse a connected repo. Layout groups, traffic flow, and cloud context included.
Organise knowledge
Add owners, runbooks, environments, and documentation. Request AI docs when you need them.
Stay synchronised
Every push is detected. Stale assets are flagged — never silently overwritten.
Blueprint
A living model of your software
Not a static diagram — a structured engineering asset you can draft by hand, connect to GitHub, and evolve with every commit.
- Start from a draft or guided wizard — design architecture before connecting GitHub
- Services, databases, queues, and external integrations mapped from your repository
- Layout groups for AWS regions, VPCs, and logical boundaries
- Per-asset metadata: owner, environment, runbook, monitoring links
- On-demand AI documentation — flagged stale when architecture diverges
- Traffic flow simulation and structure linting in the editor
- Export to PNG, SVG, Mermaid, or architecture.json
Payments API Service
Service
payments-team
production
PostgreSQL RDS
Database
platform-team
production
Stripe
External
—
—
Push detected
Per-repository webhook receives the commit. last_event_sha advances — never the analysis baseline.
Structural refresh
Free structural analysis compares the repository against your Blueprint. No AI cost unless you request it.
Changes flagged
Added, removed, or modified services open Sync Review. You accept, reject, or merge each change.
Docs marked stale
Documentation is never silently updated. Stale assets are visible, and your Knowledge Score reflects the gap.
Synchronisation
Documentation that tells you when it's wrong
Most tools regenerate docs on every push — producing confident-sounding content that may be incorrect. Notatkii marks knowledge stale instead of silently overwriting it.
Correctness over convenience
Your Engineering Knowledge Score discounts stale documentation by 50%. A high score means your team genuinely understands the system — not that an AI ran recently.
Engineering Knowledge Score
A score that only rises when knowledge genuinely improves
Eleven weighted dimensions — documentation, ownership, synchronisation, review status, and more. Stale docs drag the score down. Verified assets push it up.
Healthy · Payments API
Plus dependency accuracy, runbook coverage, environment coverage, monitoring coverage, and metadata completeness.
Ownership & reviews
Every asset has an owner, a review state, and a confidence level
Engineering knowledge isn't complete until a human verifies it. Notatkii tracks review workflows, AI confidence scores, and ownership on every component.
Initial state after repository analysis
Flagged for team verification
Human-confirmed by an engineer
Formally approved for production reference
Owner assignment
Team or email on every deployable asset
Review history
Full audit trail of status transitions
Shared org workspaces
Blueprints synced from GitHub organisation membership
Security
Built for engineering teams who take privacy seriously
Your repositories contain your most valuable intellectual property. Notatkii is designed to analyse without persisting source code.
Encrypted tokens
GitHub OAuth tokens encrypted at rest with Fernet. Never stored in plaintext.
Per-repo webhook secrets
Each repository gets a unique HMAC-SHA256 webhook secret. No global secret.
Tenant isolation
Blueprint access enforced via workspace membership. Cross-org access is impossible.
No source code storage
Repository content is read via GitHub API during analysis. Only derived mappings and docs are stored.
Signature verification
Every webhook payload verified before processing. Replay attacks mitigated.
Magic link auth
Single-use authentication tokens with rate limiting. No passwords to leak.
Pricing
Simple pricing. No per-repo charges.
Start free. Upgrade when your team grows.
Testimonials
Trusted by engineering teams
Customer stories coming soon
“Placeholder — customer testimonial coming soon.”
Engineering Manager
Series B SaaS
“Placeholder — customer testimonial coming soon.”
Staff Engineer
Fintech startup
“Placeholder — customer testimonial coming soon.”
VP Engineering
Enterprise platform team
FAQ