For Engineering Teams

Docs in the same
flow as code

No context switching. No stale wikis. Write architecture docs, onboarding guides, and API references in the same repo, with AI that actually knows your codebase.

Architecture Decision Records

— document the why, next to the code

adr-007-redis-over-kafka.md

Accepted

docs/adrs

adr-006-monorepo.md

adr-007-redis.md

adr-template.md

src/workers

1# ADR-007: Redis over Kafka

3Status: **Accepted** (2026-03-12)

5## Context

6Async jobs in `src/workers/` use polling.Sarah

7We need pub/sub for event-driven flows.

9## Decision

10Redis Streams: already in our stack,

11lower ops burden than Kafka.

13## Consequences

14- Max throughput ~100k msg/s- No multi-region replay

Onboarding guides

References real file paths, env vars, and commands. Always up to date.

API documentation

Endpoints documented alongside the code. Changes ship in the same PR.

Runbooks & playbooks

Collaborate in real-time during incidents. Merge improvements after.

Migration guides

Ship the migration guide in the same PR as the breaking change.

The docs-as-code workflow

Write

In the same repo as code

AI assist

Codebase-aware suggestions

Review

Same PR process as code

Merge

Docs ship with the feature

Why verso.md for engineering?

Live mode for engineers who think in prose, not raw markdown

AI autocomplete that knows real function names, file paths, and configs

Code review workflow built in. Docs go through the same PR process.

Real-time collab for pairing on post-mortems and design docs

Ready to try it?

Get started, it's free

Docs in the sameflow as code