wikipls.
Documentation that maintains itself

Yourdocs,alwaysuptodate.

When a PR merges, Wikipls reads the diff, the Jira ticket, and your docs — then opens a documentation PR with the right changes.

github.com / acme / api / pulls
live
PR #842 · Add rate limiting middleware
merged · 2s ago
Wikipls evaluates 3 sections across README.md, docs/api.md
claude-sonnet-4 · 2.1s
docs: update from PR #842
opened · #843
README.md## Rate limiting
## Rate limiting
 
The API is unbounded — calls are processed first-come, first-served.
The API enforces a token bucket of 60 requests / minute / IP.
Requests exceeding the budget receive a 429 response.
 
Authenticated requests use a separate budget.
How it works

Four steps. Then it's invisible.

No new tools to teach the team. Connect a repo, drop a manifest, and documentation starts updating itself.

  1. 01
    1. Connect

    Install the GitHub App.

    One click on the repos you want Wikipls to watch. Read-only on code; writes only ever happen as pull requests — never silent commits.

  2. 02
    2. Drop a manifest

    Wikipls proposes the manifest.

    It scans your repo and opens a PR with a .wikipls/manifest.yml that maps doc sections to the source files that should keep them honest. Review, tweak, merge.

  3. 03
    3. Merge a PR

    Your normal flow, unchanged.

    Wikipls listens for merged PRs in the background, reads the diff, the linked Jira ticket, and your existing docs — then figures out which sections need to move.

  4. 04
    4. Review the doc PR

    Surgical edits, ready to ship.

    Wikipls opens a focused doc PR with edits only to the affected sections. You read the diff, approve, merge. Nothing auto-merges, ever.

What's in the box

Everything you need.
Nothing you don't.

Set it up once. The defaults are sensible. Most teams never open the Wikipls dashboard after the first manifest merges.

  • Manifest-driven

    You declare which docs watch which files. The manifest lives in your repo and evolves with your team.

  • Jira-aware

    Reads the ticket that drove the change — title, description, acceptance criteria — so docs reflect intent.

  • Stoney integration

    Understands enforced acceptance criteria from .stoney/. Your docs match the contract your CI already keeps.

  • Surgical edits

    Rewrites only the section that needs updating. Tone, structure, and adjacent content stay untouched.

  • Always reviewed

    Wikipls opens PRs, humans approve, nothing auto-merges. Docs change at the speed of your normal review.

  • Full audit trail

    Every doc PR is traced back to the merged PR and ticket that caused it. Replay or regenerate anytime.

Pricing

Pay for the docs you don't have to write.

One repo is free, forever. Add more when your team grows.

Free
starter
$0/ month

Try Wikipls on a single repo, with no card.

  • 1 repo
  • 25 doc events/month
  • Public repos only
  • Jira integration
Most popular
Pro
growing
$19/ month

For small teams shipping fast across a few repos.

  • 5 repos
  • 300 doc events/month
  • Private repos
  • Jira integration
  • Stoney integration
  • Priority support
Team
scaling
$49/ month

For engineering orgs with many repos and many merges.

  • Unlimited repos
  • Unlimited doc events
  • Private repos
  • Jira integration
  • Stoney integration
  • Priority support

All plans include unlimited team members, audit logs, and priority bug fixes. Cancel anytime.