Before I get into it, yes, I know FastAPI gives you /docs out of the box. Yes, I know Spring Boot has SpringDoc. That is exactly why I want to explain what DocuPoints actually does differently, because that question comes up every time and it is a fair one.
The actual problem
Every backend project I have worked on has the same graveyard. A Swagger config, a Notion page, a docs folder, full of API documentation that was accurate maybe three months ago and has been a polite lie ever since.
The tools that exist today fall into two categories:
Category 1: Framework built-ins like FastAPI /docs and SpringDoc.
These are great for local development and quick testing. But they are tied to your running server. You cannot share them with a client who does not have your project running locally. You cannot hand them to a new teammate without spinning up the whole stack. You get no history of how your API has changed over time. And if you have multiple services across different frameworks, you are managing multiple separate doc setups.
Category 2: Annotation-based tools like Swagger UI.
These work, but someone still has to write and maintain the annotations. The moment your team is under deadline pressure, the annotations stop getting updated. That is annotation drift, and it is invisible until someone gets burned by it.
DocuPoints is a third option.
What it actually does
It is a desktop app. You point it at your project folder and click Scan. It reads your source code directly and extracts:
- Every endpoint, method and path
- Request body and query parameters with types
- Response shape
- Middleware chain
- Every exception your endpoint can throw with status codes
No server needs to be running. No annotations to add. No config files. Your existing code is all it needs.
The scan runs entirely locally. Your code never leaves your machine.
What you get that /docs does not give you
A hosted public URL. One click publishes your docs to a shareable link. Send it to a client, a contractor, a teammate onboarding remotely, no stack setup required on their end.
Versioned endpoints. Every scan is tracked. You can see exactly what changed between versions of your API. When did that parameter become required? When did that endpoint get deprecated? That history exists now.
A team changelog feed. Your whole team sees API changes as they happen across the project. No more "did someone change the login endpoint?" in Slack.
Per-endpoint notes. Leave context directly on an endpoint for your team. The kind of thing that currently lives in a Slack thread and disappears.
Export to everything. OpenAPI JSON and YAML, Postman collections, Markdown, DOCX, PDF. Whatever your client or team needs.
Cross-framework in one place. If you have a Spring Boot auth service and a FastAPI data service and an Express gateway, one tool covers all of them with one consistent interface.
Supported frameworks
- Spring Boot
- Express.js, with Joi and Zod schema extraction
- FastAPI, reads APIRouter decorators and Pydantic models
- Django REST Framework, scans urlconf patterns, ViewSets, and APIView classes
Coming soon: NestJS, Laravel, and Flask
Who this is for
Freelancers and consultants who need to hand off clean API documentation to clients at the end of a project without spending a day writing it manually.
Small teams moving fast where documentation always ends up on the backlog because there is always something more urgent.
Developers onboarding into an existing codebase who need to understand what endpoints exist without reading through every controller file.
Teams with multiple services on different frameworks who want one consistent place to view and share all their API docs.
If you already have a disciplined CI/CD pipeline that builds and publishes your OpenAPI spec on every tagged release, DocuPoints probably does not add much for you. That is a legitimate workflow and it works well. DocuPoints is for everyone who is not there yet.
Where things stand
I launched recently. Free tier is available with no credit card required. Paid plans start at $9 per month.
If you maintain a backend API and documentation is a constant source of friction, I would appreciate you giving it a try and letting me know what you think.
docupoints.com
SOCIAL SHARE CARD GENERATOR