Most AI tools reset every session. DocPro is a persistent development team — four members with memory, opinions, and the ability to build real things while you're not there.
Every session is indexed. Standing preferences are loaded into every new session. Important mistakes are logged so they don't become recurring failure patterns. The context that disappears every time you open a new chat window? It lives here permanently. The team knows your stack, your standards, and the argument you had about the database schema in March.
Most AI code review is a treadmill — the same findings on every pass because the reviewer has no memory of what was already settled. DocPro's review reads its own history before flagging anything, drives every finding to a terminal state instead of skimming the top, and audits its own past judgments to make sure they still hold. Four buttons in the sidebar. The count goes down and stays down.
You click Run Code Review. DocPro reads its own ledger history, flags only what's genuinely new, and writes every finding to a durable ledger. You stay in control — nothing is auto-committed; you decide what gets fixed and what gets kept on the record with a reason.
The first time the team reviewed this codebase cold — no ledger, no history — it surfaced around 110 findings across roughly 150,000 lines and drove every single one to a terminal state: fixed, or deliberately kept with a reason on record. From then on, each review reads that ledger before it flags anything. It never re-derives a settled problem. It only looks at what actually changed — so the count collapses and stays collapsed.
Every bar is a real entry in the review history. The tall one on the left is what a reviewer sees when it has no idea what was already settled. Everything after it is what the same review finds once it remembers — a handful of genuinely new issues in the code that actually changed, each one driven closed. No treadmill. No re-litigating fixed work. The count goes down and stays down because the memory is real.
Source: the team's own archived review ledgers (docs/review_history/) — first whole-repo pass 2026-05-23 (~110 findings, 0 deferrals); most recent pass 2026-06-20 (1 finding, fixed & verified). Counts above are verbatim from each pass's ledger summary.
Build Mode runs the team through a project one milestone at a time, on its own — plan, build, QA gate, commit, deploy, document, repeat. You define the milestones and approve the plan. DocPro works the queue with the same memory and the same review loop it uses when you're watching, logging every turn so the next session knows exactly where it stopped. You keep the controls: it works on a branch, commits are yours to read, and nothing reaches production without passing the gate first.
One command and the team stands up real infrastructure — an AWS Lightsail instance, static IP, firewall, Cloudflare DNS, and an SSL certificate — then hands back a live URL. Under three minutes. No tickets. No ops team. Today it runs on DocPro's cloud, billed in good faith as the AWS line in your plan. Bring-your-own AWS and Cloudflare API keys are planned for September 2026 — move it all onto your own accounts whenever you're ready.
See Security for cloud ownership, credential handling, and deletion boundaries.
Carl reviews every line of code before it ships. Diana counts pixels. Anthony builds fast and stays up too late. Abish keeps a journal. Each one is a persistent behavioral context — domain expertise, working style, and memory compressed into a model that activates the same way, every session. Not a prompt. A development context that compounds.
And you don't only read their output — you can call them. One click in the sidebar and the team is on the line with your project already loaded. Meet the team · how the calls work.
Real session — Saturday Night cron debug — recorded 2026-04-26
Security and For IT explain exactly what code, credentials, and project context are sent, stored, and deleted. Security — For IT
We are taking on a small number of new projects. If something on this page made you want to know more, that is the right instinct.
Say helloinfo@docpro.cloud — we respond personally.