New version 2.0.0
DOCKRBuilt for founders, builders, lean dev teams, and enterprise engineering teams
Dockr connects to your repositories and generates complete, accurate documentation on every commit. No writers. No reviews. No stale wikis.
11 languages supported
A product by Flytebit Technologies · Alongside TESTR and PASSR
# Overview
Comprehensive blogging platform - secure auth, publishing workflows, nested comments, and transactional email delivery.
## Architectural Layers
## Features
• User & Identity Management
• Content Lifecycle Management
• Communication & Notifications
• System Operations & Governance
## Business Domains
## Modules
## Quality
# User & Identity Management
Governs the complete user identity lifecycle - secure registration, token-based auth, and password recovery.
## Feature Flow
## Use Cases
• UC-01: User Registration & Onboarding
• UC-02: Secure Authentication
• UC-03: Password Management
## Architecture · Components
## API Endpoints
## Business Rules
• Passwords bcrypt-hashed, cost factor ≥ 12
• Access tokens expire 15 min; refresh tokens 7 days
• 5 failed logins triggers 15-min account lock
# main.py
Entry point - initialises FastAPI, configures CORS & rate limiting, registers 5 API routers, manages lifecycle events.
## Scope
• Initializes the core FastAPI application instance
• Configures CORS and API request rate limiting
• Registers endpoint routers for all domain features
## Functions
## Routes
## Middleware
• CORSMiddleware - allow_origins: [*.bloggr.io]
• RateLimitMiddleware - 100 req / min per IP
• LoggingMiddleware - structured JSON output
## Key Imports
## Insights
Regenerates on every git push · zero configuration
What is Dockr
Dockr is an AI code documentation generator for engineering teams. You connect your repository once, and every commit automatically triggers a full documentation pass - Dockr reads your codebase, maps its structure and dependencies, and keeps your technical documentation accurate in real time.
It creates developer docs for every file, class, function, and module, plus architecture diagrams your team can actually use. Output includes API documentation, code flow explanations, and six visual formats: file structure maps, UML class diagrams, method flows, activity diagrams, sequence diagrams, and mind maps.
Beyond docs and diagrams, Dockr runs code analysis on every pass: cyclomatic complexity metrics, performance bottleneck flags, and security vulnerability markers. Teams can see what needs attention without running separate tools.
For Enterprise teams, Dockr goes further. Chat with Docs makes your generated documentation interactive - developers, product managers, and non-technical stakeholders can ask questions about the codebase in plain language and get accurate, grounded answers. No hallucinations, no guessing.
The MCP & Skills architecture lets any compatible coding agent query Dockr directly via the Model Context Protocol. Agents retrieve precise, commit-level context from your generated docs instead of inferring from raw code - making Dockr the documentation layer for AI-assisted development.
Your code is never used to train AI models. No credentials are stored beyond what's needed to pull from your repo. Encryption at rest and in transit on every request.
Your codebase
git push origin main
Dockr AI engine
Reads, understands, generates
Prose docs
Functions, classes, modules
6 diagram types
UML, sequence, mind maps
Complexity, performance, security insights
Cyclomatic metrics, bottleneck detection, vulnerability flags
Chat with Docs
Ask anything, get grounded answers
MCP & Skills
Coding agents query docs directly
The Documentation Crisis
A repo can be clean on day one and unreadable by month six. Teams slow down, onboarding stretches for weeks, and critical context gets trapped in a few people's heads.
Engineering hours disappear into writing and fixing docs instead of building features.
5–10 hours per developer, per week spent on documentation maintenance.
100% automated from commits and webhooks. Zero manual documentation overhead.
The docs and the code diverge after every sprint.
Costly bugs when teams follow documentation that no longer matches production behavior.
Documentation stays auto-synced with every commit, branch, and release cycle.
New engineers spend weeks decoding architecture manually.
Months spent understanding flows, modules, and decisions before contributing real value.
Teams report 60–70% faster onboarding, turning months into days for new contributors.
Business logic gets locked in a few engineer's heads.
When key people switch teams or leave, context leaves with them and velocity collapses.
Critical knowledge is preserved continuously in shared docs and diagrams for every repository.
Senior engineers repeat the same explanations every week.
Support threads and Slack pings interrupt execution, fragmenting focus across the team.
Teams see up to 50% fewer repeated support questions once docs become reliable and current.
Each repo follows a different structure, style, and level of detail.
Audit and compliance reviews surface gaps, stale docs, and conflicting implementation details.
Consistent, high-quality documentation standards are generated across repositories by default.
Push code. Docs update. That's it.
Every commit triggers a documentation pass. No backfill, no manual step, no one waiting.
Documentation in the AI Era
AI coding tools are everywhere. Yet documentation quality barely moved. The gap between shipping code and understanding it is wider than ever - and growing with every commit.
doc quality improvement
A 25% surge in AI adoption moved documentation quality by just 7.5%.
Developers are using AI coding assistants and agents every day. They're shipping code faster than ever. But the DORA 2024 report is unambiguous: AI tools are not closing the documentation gap. They improve code output. They do not produce the structured, accurate, commit-level documentation that engineering teams actually rely on.
2024 DORA Accelerate State of DevOps Report →What the gap actually costs your team - Atlassian Developer Experience Report 2024
of developers lose eight or more hours per week to inefficiencies like outdated documentation and unclear architecture
Atlassian 2024 →of the entire working week - one full day, every week - lost to friction that well-maintained documentation would eliminate
Atlassian 2024 →of developers report losing significant time to these inefficiencies - yet less than half believe their leaders are even aware
Atlassian 2024 →AI coding tools ship code faster. But faster shipping without documentation means more undocumented surface area, more hallucination risk, and more onboarding debt - all accumulating with every commit.
AI coding assistants and agents read your code - but they infer intent from what's documented, not what's implied. Stale or missing docs mean AI tools confidently suggest the wrong architecture, call deprecated methods, and invent interfaces that don't exist. Dockr keeps the documentation current so every AI tool in your stack has accurate ground truth on every commit.
Dockr generates
commit-level docs
AI can rely on
A new hire can't ask an AI coding agent why a system was designed a certain way three years ago. Architectural decisions, tradeoffs, and system relationships live in documentation - or nowhere. Dockr generates prose documentation, file structure diagrams, and class relationship maps so new engineers ramp up in days, not months.
Prose docs +
6 diagram types
on every commit
AI coding tools increase output velocity by 30-40%. That same multiplier applies to undocumented code when documentation isn't automated. Every sprint adds more surface area no one can safely touch. Dockr triggers on every push - so documentation scales with code, not against it.
Webhook-triggered
on every push
zero manual work
AI-assisted review tools see syntax. They can't evaluate whether a change aligns with the architecture decisions made six months ago. Reviewers without documented context approve changes they don't fully understand. Dockr's sequence diagrams and architecture docs give reviewers the context they need at the moment they need it.
Sequence diagrams
+ architecture maps
per commit
What your team is waiting for
According to the Stack Overflow 2024 Developer Survey of 65,000+ respondents, developers overwhelmingly rely on structured documentation - the exact kind that no one has time to write and AI tools don't produce automatically.
rely on API documents and SDK documentation as their primary way to understand how code works
Dockr generates this. Automatically. Per commit.
prefer user guides and README files to understand project functionality and architecture
Dockr generates prose documentation for every module and function.
fall back to search engines when documentation is missing - a sign the source of truth simply isn't there
With Dockr, the source of truth updates itself on every push.
Why Dockr exists
AI accelerates code. Dockr makes sure your team can understand it.
Dockr connects to your repositories and generates complete prose documentation, file diagrams, class maps, sequence diagrams, mind maps, and activity diagrams on every commit - automatically, in minutes, with no human input required.
Features
Six pillars that turn documentation from a chore into a byproduct of shipping - and the source of truth for your coding agents.
AI Intelligence
Dockr reads your codebase as a connected system, not file by file. It traces how modules depend on each other, identifies structural patterns, and documents what's actually implemented across your entire codebase.
The engine reads your entire codebase as a system - not individual files in isolation. It traces dependencies, identifies service boundaries, and understands how layers communicate before writing a single word.
Readable prose - not parameter dumps. Written the way senior engineers explain things.
Auto-generated Q&A for every file - purpose, usage, edge cases, and gotchas.
Usage patterns, optimisation hints, and alternative approaches surfaced automatically.
Design patterns, architectural decisions, and conventions identified and documented automatically.
Encrypted at rest & in transit
Encrypted at rest and in transit via TLS 1.3. Your code is stored only to serve your docs - never exposed.
Never used for training
Your code never trains our models or any third-party AI. Your IP stays yours, always.
Org-level data isolation
Separate encryption keys and dedicated storage per organisation. Your data never shares infrastructure with another tenant.
Your source code security is our top priority.
Full security detailsVisual Diagrams
Every documentation pass generates a full set of visual diagrams automatically - no Mermaid syntax to write, no diagramming tools to maintain. Always in sync with the latest commit.
Automation
Register a webhook once and never think about documentation again. Every push triggers a full analysis cycle - only changed files are re-processed, keeping runs fast even on large monorepos.
git push
3 files changed
Webhook fired
POST /webhook
Diff analysis
3 files queued
AI analysis
context + patterns
Diagrams
6 types generated
Docs published
done in minutes
Only changed files re-processed. New, modified, and deleted all handled correctly.
Configure exactly which branches trigger docs. Main, release, or all.
Include/exclude patterns, wildcards, and directory rules to focus on what matters.
Team gets notified on doc updates based on membership - zero manual subscriptions.
Collaboration
Invite your entire engineering team, set granular permissions, and give everyone a shared portal that stays current without anyone maintaining it.
ACTIVE NOW
bloggr-backend
updated 2s ago
payments-service
updated 14m ago
frontend-web
updated 1h ago
infra-terraform
updated 3h ago
mobile-rn-app
updated 5h ago
Admin, Editor, Viewer - or custom roles. Permissions cascade from org to team to repo. Change a role once, propagate everywhere.
Works across time zones. Everyone reads the same source of truth - onboarding, code reviews, incident response - all off the same live docs.
Browse docs alongside source code without needing an IDE. Useful for PMs, architects, and new joiners who need context fast.
Encryption at rest & in transit
Encrypted at rest and in transit via TLS 1.3. Each organisation gets separate encryption keys and dedicated storage - your data never shares infrastructure with another tenant.
Comprehensive audit logging
Every action logged with timestamp and user. Immutable audit trail ready for compliance reviews and incident forensics.
MCP & Skills · Enterprise
With Dockr's MCP (Model Context Protocol) and skill-based architecture, any compatible coding agent can query your generated documentation directly - getting accurate, commit-level context instead of inferring from raw code or hallucinating.
Docs as the source of truth
Every push keeps docs current. Coding agents always query the latest version - no stale context, no outdated snapshots.
MCP server - plug in, not locked in
Add Dockr as an MCP server in any compatible coding agent. Query by file, function, module, or natural language.
Pre-built skills
Retrieve architecture overviews, function signatures, dependency maps, and business rules - no custom prompts needed.
No hallucinations
Agents ground every answer in documentation generated from your actual code - not general knowledge or guesswork.
{
"mcpServers": {
"dockr": {
"command": "npx",
"args": ["@dockr/mcp-server"],
"env": {
"DOCKR_API_KEY": "dk_live_..."
}
}
}
}How coding agents query Dockr
Chat with Docs · Enterprise
Chat with Docs makes your generated documentation interactive. Whether you're a developer using a coding agent or a non-technical team member in the Dockr portal - anyone can ask questions and get accurate, documentation-grounded answers instantly.
For developers & coding agents
Coding agents use Chat with Docs to get function-level context without reading raw source code - faster, more accurate, no guesswork.
For non-technical users
Product managers, QA, and stakeholders can ask about features and flows in plain language - directly inside the Dockr portal.
Grounded in your docs
Every answer is sourced from documentation Dockr generated from your actual code - not from a model's general training data.
Always up to date
As your code evolves, so do the docs - and so do the chat answers. No manual re-training or prompt maintenance required.
How does the email notification system work?
The EmailService in email_service.py handles all outbound transactional emails. It uses dynamic templates to dispatch messages for:
Sourced from generated documentation
Which files handle authentication?
How it works
Manual upload or Git integration. GitHub, GitLab, and Bitbucket supported. Public or private - no complex setup, connect in seconds.
Set your branch, language, and file scope. Include or exclude extensions, folders, and wildcard patterns. Skip build artifacts and focus on core business logic. A webhook is registered automatically.
Commit and push as you always do. Dockr receives the webhook, identifies changed files, and begins analysis immediately. Incremental - only changed files are re-processed.
Deep code structure analysis across your entire codebase. Pattern and best practice detection, multi-language support, performance and security analysis, secret detection, and error handling review. Code is encrypted at rest and in transit - never used for training.
Comprehensive prose docs for every file, class, function, and module. Six diagram types. FAQs, tips, and notes per file. All generated automatically within minutes of every push.
Multi-level hierarchy - Org, BU, and Team. Role-based access control. Advanced search and filtering. Email notifications on updates, shareable links, and version tracking. Always reflects the latest commit.
Outcomes
more code shipped per sprint
Developers spend 5 to 10 hours every week writing documentation, updating wikis, and searching for context that should already be written down. Dockr eliminates all of that. Documentation is generated automatically on every commit. Your team gets that time back and can use it to ship.
of docs stay current, always
Every commit triggers a full documentation pass. Not just the changed files - Dockr re-evaluates context across everything the commit touches. Your docs reflect the codebase as it exists right now, not two sprints ago. Stale wikis and outdated diagrams stop being a problem you manage.
faster onboarding for new hires
Most of the 3 to 6 month onboarding window is spent chasing context - reading code to understand what it does, asking questions that interrupt senior engineers, and waiting for someone to have time to explain the architecture. With Dockr, every answer is already written. New engineers start contributing faster. Senior engineers stop being interrupted.
more visual context on your codebase
Dockr generates six types of visual documentation for every repository: file structure maps, class relationship diagrams, method flow charts, activity diagrams, sequence diagrams, and mind maps. Architecture reviews that used to take days of Lucidchart work are ready before your next standup. Every diagram stays in sync with the code.
same standard across every project
Hand-written docs produce inconsistent coverage - some repos are thorough, most are not. Dockr applies the same structure and depth to every repository in your organisation. Every file, class, and function gets documented to the same standard. Compliance requirements get met as a side effect of shipping.
documentation PRs or review cycles
There's no documentation PR to approve, no draft to revise, no one waiting on sign-off. Every commit produces final-quality docs immediately. Quality stays consistent because the process runs the same way every time, not because someone reviewed it carefully.
These numbers come from teams in beta. Two weeks in, the pattern holds across every repo size and language.
Start free - 7 daysPricing
Choose the plan that fits your team's needs
Adjust the sliders to match your repository size and change frequency
Actual credit consumption may vary by ±10% based on code complexity and structure
No credit card required • See your codebase documented instantly
Compare Professional vs Enterprise Features →Only pay for the code you actually use. Annual subscription adjusts to your needs.
Track your usage with detailed dashboards and receive proactive alerts.
Transparent pricing with no surprise charges or commitments.
Custom pricing · Dedicated support · Built for large organizations
| Feature | Pro | Enterprise |
|---|---|---|
| Usage Limits | ||
| Users | Up to 50 | Unlimited |
| Teams | Up to 20 | Unlimited |
| Business Units | Up to 10 | Unlimited |
| Organizations | 1 | 1 |
| Core Features | ||
| Repo Linking & Webhooks | ||
| Source Code Viewer | ||
| Search & Filtering | ||
| FAQs, Tips & Notes | ||
| Complexity Analysis | ||
| Manual Code Upload | ||
| Repository Summary | ||
| Diagrams & Insights | ||
| File, Class, Method, Activity, Sequence | ||
| Mind Maps & Business Rules | - | |
| Performance & Security Insights | Basic | Advanced |
| Enterprise Features | ||
| Custom Templates | - | |
| Compliance-Ready Docs | - | |
| Shareable Links | - | |
| Version History & Audit Logs | - | |
| SSO & API Access | - | |
| Private Cloud Deployment | - | |
| Complete Data Control | - | |
| Chat with Docs | - | |
| MCP & Skills for Coding Agents | - | |
| Support | ||
| Support Level | Priority Email | Dedicated Manager |
FAQ
Everything you need to know about Dockr.
Dockr connects to your Git repository and generates documentation automatically on every push. It produces text explanations, class diagrams, sequence diagrams, and activity diagrams for every file and function. Nothing is manual.
Dockr supports 11 programming languages: C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Rust, and TypeScript. More languages are coming soon.
You add a webhook to your repo once. After that, every push triggers Dockr to analyze what changed and update the docs. New files get documented, changed functions get regenerated, deleted code gets removed. You never touch it again.
There's a 7-day free trial with no credit card required. You get full Professional feature access and can upload up to 2 MB of code manually to test it out. After the trial, Professional and Enterprise plans are available on yearly prepaid billing.
Confluence and Notion require developers to write and maintain documentation manually. Dockr reads your actual source code and generates it. The docs stay accurate because they regenerate on every push, not whenever a developer finds time to update a wiki page.
Yes. Dockr never uses your code to train AI models. Each organisation gets dedicated storage and separate encryption keys - your data never shares infrastructure with another customer. All data is encrypted at rest and in transit via TLS 1.3, with CSRF protection and full audit logging. Enterprise customers can also deploy Dockr in their own private cloud so code never leaves their environment.
Dockr generates file diagrams, class diagrams, method diagrams, activity diagrams, and sequence diagrams. Enterprise plans also include mind maps and business rules visualizations.
Setup takes under 10 minutes: connect your repository, add a webhook, and Dockr generates your first documentation automatically. New team members can typically get up to speed 60-70% faster compared to projects without structured documentation.
Yes. Dockr supports both public and private repositories on GitHub, GitLab, and Bitbucket. Enterprise customers can also deploy Dockr in their own private cloud so code never leaves their infrastructure.
7-day free trial. No credit card. Connect your repo and see docs generated in minutes.
Start free - 7 daysMay 31, 2026