Pay for the docs you don't have to write.
One repo is free, forever. Add more when your team grows.
Try Wikipls on a single repo, with no card.
- 1 repo
- 25 doc events/month
- Public repos only
- Jira integration
For small teams shipping fast across a few repos.
- 5 repos
- 300 doc events/month
- Private repos
- Jira integration
- Stoney integration
- Priority support
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.
Frequently asked.
What is the manifest file?
The manifest is a YAML file at `.wikipls/manifest.yml` in your repo. It declares which doc sections watch which files, with sensitivity levels and plain-English update conditions. Wikipls auto-generates an initial manifest by scanning your repo — you review and tune it.
Does Wikipls work without Jira?
Yes. Jira context makes updates richer because Wikipls can see the business intent behind the change, but it's optional. Without Jira, Wikipls uses only the PR diff, PR description, and your existing docs.
What happens if a doc section doesn't exist yet?
Wikipls appends the new section to the doc. You can also use Wikipls to bootstrap documentation for a repo that has no docs at all — just declare what you want in the manifest.
How does Wikipls handle private repos?
Private repos are supported on Pro and Team plans. Wikipls only accesses repos you explicitly authorize via the GitHub App.
What does 'sensitivity' mean?
Each manifest section has a sensitivity: high (update on any watched change), medium (update when signatures or structure change), or low (only substantial changes). It controls how aggressively Wikipls flags a section for updates.
Can I use Wikipls with GitHub wikis?
Not yet. Wikipls currently works with markdown docs committed to your main repo. GitHub wikis are on the roadmap.