Version your product specs in plain English. Capture approvals, sign every generation run, and detect drift the moment your spec and your system disagree.
Spec turns your product decisions into a durable, reviewable, signed record. Not a Slack thread.
Describe the behavior you want in plain English. Upload as a `.md` file. Spec stores it as an immutable, hashed version.
Stakeholders read the diff, leave notes, and approve the version on the record. Nothing ships from a spec no one owns.
Run your agent against the approved spec. Spec records the config and output hashes, pinned to the version that produced them.
Upload a `.md` file, Spec stores an immutable version with a content hash. Compare any two versions side-by-side. No more wondering which Notion doc is canonical.
Growth plan annual discount → 15%
Growth plan annual discount → 10%
Enterprise seat-based volume tiers
Initial public pricing
Every version carries a reviewer list, timestamps, and optional notes. Approvals live in the record. Not buried in a Slack thread or a DM.
@Alex
Product
"Numbers reviewed with finance."
@Sarah
Legal
"Disclosure language is fine."
@Jordan
Engineering
"Awaiting migration plan."
Every generation run is pinned to a specific spec version, agent config hash, and output hash. When the spec moves ahead of your last run, Spec flags the drift, so you can re-run or update.
spec
v4
config
cfg · 7e12aa
output
out · 4b59e3
spec
v4
config
cfg · 7e12aa
output
out · c901fe
spec
v3
config
cfg · 4433bb
output
out · 1aef22
Start free. Upgrade when approvals, signed runs, or drift checks become a requirement.
Free
For solo builders trying out versioned specs
Team
For product teams that need a paper trail
Enterprise
For regulated teams with compliance needs