Where can we help you?
What WeaveSpec reads, what it writes, and what it will never touch — answered before you connect a single repository.
Getting started
WeaveSpec connects several GitHub repositories into one project, works out what each of them does, and generates the documents a feature needs across all of them: a repository summary, a system map, a PRD, a technical design, per-repository work items, API and data model changes, test scenarios, and the risks in between.
No. WeaveSpec is a product planning tool, not a developer tool. A product manager should be able to produce an implementable PRD without opening a single repository. Source references — file, line, commit — are shown as evidence: a technical reader can verify them, but you do not have to read them to use the output.
WeaveSpec is in early access and access is granted by request. Send a request from any "Request early access" button on the site, and we read it by hand. You will hear back by email once your request has been reviewed.
Install the GitHub App on the repositories you want to include, create a project and add them to it. The first analysis then runs in the background and its duration depends on the size and number of repositories; you can leave the page while it works.
Repositories & analysis
No. GitHub access is read-only. WeaveSpec never commits, never pushes and never opens a pull request. It reads your repositories, analyses them, and produces documents and — after you approve them — Jira issues.
A project is meant to hold the whole product: backend, web, mobile, workers, infrastructure. The exact ceiling depends on your plan, and it is an account-wide total rather than a per-project one.
Yes. The GitHub App is installed on the repositories you select, private or public, and it sees nothing you have not granted it.
The analysis reflects the state of the repository at the time it ran. When your repositories move on, you can re-run the analysis and regenerate the affected documents; each document records which analysis it was produced from.
The analysis is language-agnostic: it reads structure, configuration, dependencies and code across whatever stacks your repositories use, rather than relying on a single language parser. Polyglot products — a TypeScript web app, a Kotlin mobile app, a Go worker — are the normal case.
Documents & Jira
Product and technical documents are produced separately, so each role can work from its own output: a PRD and a technical design, plus repository-level work items, API and data model changes, test scenarios, and a list of risks and dependencies.
It is a draft written by a model, and it can be wrong. That is why every claim carries its evidence — the files, lines and commits it came from — so the people who know the system can check it quickly instead of taking it on faith. Review before you ship.
You connect a Jira project, review the epics, stories, tasks and sub-tasks WeaveSpec proposes, and only what you approve is created. Nothing is written to Jira automatically.
Yes. Every document can be exported as Markdown, on every plan. Your documents are yours.
No. Your repository content and generated documents are not used to train our models or our providers’ models. They are processed to produce the output you asked for, and nothing else.
Security & access
Isolation is enforced in the database itself, not only in the application: a session belonging to one account cannot read another account’s projects even if the application asked it to. Integration credentials are stored encrypted and are not readable through the API.
Owners and admins manage the account, members do the work, and viewers read everything a member reads without being able to spend anything — a viewer cannot start an analysis, generate a document or open a chat turn. Viewer seats are free and unlimited, so the whole team can stay in the loop.
Yes. Sign-ins, invitations, role changes, analyses, generations and exports are all recorded. The audit log is append-only: entries can be read and exported, but never edited or deleted — by you or by us.
Uninstall the GitHub App or disconnect the repository, and all further access stops immediately. Deleting a project deletes its repositories, analyses and documents with it.
Plans & pricing
Nothing yet. WeaveSpec is in early access, the product is free, and there is no checkout anywhere on the site. Prices will be published before paid plans start, and we will tell you what changes before it affects you.
By consumption, not by visibility. A seat is a person who can spend the account’s budget — owners, admins and members. Viewers do not count as seats and never will, because a planning tool that charges per reader stops being read.
The whole account. Repository counts, seats and monthly document credits are account-wide totals, and every project you create draws from the same pool.
It stays yours. Before paid plans begin, we will tell you what is changing and give you time to export your documents or stop using the product.
Still have a question?
Tell us about your repositories and what you are trying to plan. A person reads every message.