Launching today
ArchDocs
Plan software changes. Track the work. Verify the outcome.
2 followers
Plan software changes. Track the work. Verify the outcome.
2 followers
Design it. Build it. Verify it. ArchDocs connects design docs, architecture, decisions, and evidence for each software change. People and coding agents work from the same plan, record progress and changes along the way, and leave handoffs so the next session can pick up where they stopped. Define acceptance criteria and check them automatically with GitHub and PostHog, with more integrations coming very soon. Agents read and update docs through MCP. Free for up to three people.
Free Options
Launch Team / Built With
AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi, I'm Aylon, the creator of ArchDocs.
A software change usually leaves its story scattered across a design doc, pull requests, chat threads, and dashboards.
The implementation changes along the way. Decisions get buried. The next person or coding agent has to reconstruct what happened. And someone still needs to check whether the result meets the original requirements.
ArchDocs keeps that work connected:
Design it: bring architecture, previous decisions, and open questions into the plan.
Build it: people and coding agents record progress, changes of direction, and handoffs against that plan.
Verify it: define acceptance criteria and check them against evidence from GitHub, PostHog, with more coming very soon.
The migration in the screenshots follows one change through that whole workflow: why it's needed, how the implementation progresses, and what the verification results show.
You can try that example here, no signup needed: https://archdocs.io/demo
ArchDocs works alongside your existing coding tools. Agents access the context and record their work through MCP.
Free includes up to three people, one design doc, work logs, and MCP access. Automated verification is available on Business.
Where does your team lose the most context today: planning the change, handing off the work, or checking the result?