EasySpecs Review (2026): Pricing, Features & Honest Verdict

TLDR

EasySpecs is a spec review platform that maps a Git repo into functional documentation, then helps product and engineering write specs agents can build from. The BYOK plan is a bargain; the credit plan is steep. Best for: small teams adopting spec-driven development. Price: from EUR 5/repo/mo, free plan no. Rating: 6.5/10.

What is EasySpecs?

We found EasySpecs on Product Hunt, where it launched on 11 September 2026 as a platform for spec-driven development. The pitch is simple: if AI assistants write most of the code now, the place to argue about quality is the spec, before any code exists. EasySpecs reads your repository, documents what the software already does, and gives product managers and developers one place to write, review and approve specs.

It is two businesses under one brand. The self-serve product is the web app, a VS Code compatible extension and a read-only feed of approved specs for agent hosts. Around it sits a consultancy selling code audits, “dark factory” delivery, factory buildouts and paid workshops in Barcelona. This review covers the software. The terms name Spaii Edutainment SL, a company based in Barcelona, as the operator, while the site footer says Built by Spaii Labs SL.

What Are EasySpecs’s Key Features?

From Code to Documentation

You connect a repo from GitHub, GitLab, Azure DevOps or Bitbucket using a read-only personal access token. EasySpecs then builds a knowledge tree of features, use cases, scenarios, views, services, methods, data models, relationships, tech stack, infrastructure, components, tests and test cases. The site claims up to 98% of lines of code get assigned to a documented unit. That “up to” is doing a lot of work, and we saw no benchmark behind it.

Change, Intent, Diagram, Spec

The spec flow runs in four stages. A raw change request is expanded into an Intent grounded in your real code and docs, then a diagram of the change, then a detailed spec written with AI help. Reviewers can highlight any passage, comment and mark it resolved. Jira and Linear tickets can be imported as the raw request, and a finished spec can be pushed back as a developer ticket.

Trust Engineering and Specs Readiness

This is the most distinctive part. Every spec gets a companion Trust Spec with an intent statement, an in and out scope boundary, and numbered behavioural claims that each carry a “False if” condition. Unresolved decisions stay blocked rather than passing. Specs Readiness then shows green or red across seven checks: Change, Intent, Diagram, Specs, Open Questions, Trust Engineering and Comments.

IDE extension and agent access

The extension, published on Open VSX under an MIT licence, lets you browse docs and change requests, edit specs and sync them to the cloud. We checked the registry: version 0.4.11, last published 12 August 2026, with 2,650 downloads. Approved specs are also exposed to agent hosts over a read-only connection, so assistants receive only what humans already signed off. If your repo defines Skills, EasySpecs agents inherit them.

What Is It Like to Use EasySpecs?

Signing up asks for name, email and password, with no card required. You tick two consents: the terms, and that your data may be processed by AI providers. That second consent is honest and worth reading, because every Workbench and Factory action sends code context to a model provider through OpenRouter.

The workflow is opinionated. You are pushed to document the repo first, then clarify intent, then spec, then add validators. Teams that already write specs in Markdown files next to the code may find it heavy. Teams where product owners write fuzzy tickets and developers decode them will find the Intent stage the most useful part, because it forces the ask to be grounded in what the code does today.

The marketing site shows signs of a young product. The getting started guide prints an install command that points at a localhost address, a developer URL that leaked into production. The pricing page ships its credit table empty in the static HTML and loads it from an API. The headline on the main page spells platform as “Plattform”. None of these break the product, but they suggest fast iteration over polish.

Where Does EasySpecs Fall Short?

Start with the free trial, which is thinner than it looks. It gives 3 credits once, with no refill. The public credit table, which we pulled from the vendor’s own API, prices “Generate new context” at 8 credits and “Update context” at 5. On those published rates, a trial account cannot pay for the documentation step that the whole product is built on.

Factory credits are expensive. EUR 150 buys 15 credits a month, so each credit costs EUR 10. Extra packs cost EUR 150 for 10 credits, or EUR 15 each. One fresh documentation run eats 8 of your 15 monthly credits, and every “Chat with documentation” action costs 1 credit. Asking the docs ten questions would cost EUR 100 on Factory.

We found no privacy policy. The /privacy address returns the generic marketing page, and the site’s code contains no privacy policy route. For a product that reads your source code with a personal access token, that gap matters, especially under GDPR, which the terms cite. The terms also contain no refund clause and cap liability at the greater of EUR 100 or 12 months of fees.

Naming is inconsistent. The terms list plans called Workbench, Factory and Industrial, while the pricing page calls the top tier Enterprise. The Migration Harness appears on the feature menu next to the self-serve tools, but its own page says it is Enterprise only.

How Much Does EasySpecs Cost?

EasySpecs starts at EUR 5 per repository per month on Workbench. That is a 50% promotional price, struck through from EUR 10, and the site gives no end date for the offer. All prices are in euros and monthly; we found no annual option, and the terms say applicable taxes may be added.

Workbench is bring your own provider key. You add OpenAI, Anthropic, Google or OpenRouter keys in Settings, inference goes on your own bill, and EasySpecs says it adds no markup. Workbench does not use credits at all, so heavy users pay only EUR 5 or EUR 10 per repo plus model costs. That is cheap for what you get.

Factory costs EUR 150 per month for 15 credits on any repo, with EasySpecs managing the model keys. Enterprise is custom and runs on your own servers, VPC or private cloud, and adds the Migration Harness. The Free Trial gives 3 credits once.

For comparison, Kiro, the spec-driven IDE from AWS, has a free tier with 50 credits and Pro at $20 per user per month for 1,000 credits. Tessl has a free plan with 1,000 credits a month and a Team plan at $100 per month. GitHub Spec Kit costs nothing. Workbench undercuts all the paid options; Factory is the priciest per unit of work.

Who is EasySpecs Best For?

Use EasySpecs if you run a small team where product owners and developers keep misreading each other, you already pay for model access, and you want a shared place to turn tickets into reviewed specs. At EUR 5 per repo on Workbench, the downside is small. It also suits teams inheriting an undocumented codebase who want a map before they change anything.

Skip EasySpecs if you are a solo developer happy with specs in Markdown, if your company requires a published privacy policy and subprocessor list before connecting source code, or if you want managed inference without a meter that bills EUR 10 per action. Skip it too if you need the Migration Harness but cannot justify an Enterprise contract.

Best EasySpecs Alternatives

Kiro

Kiro is the AWS IDE built around specs, with a spec mode for refining requirements and running implementation steps inside the editor. It is free with 50 credits, then $20 per user per month for Pro, $40 for Pro+, and up to $200 for Power. It writes the code too, which EasySpecs does not, but it lacks the product owner review flow.

GitHub Spec Kit

Spec Kit is a free, MIT licensed toolkit from GitHub for spec-driven development, with over 139,000 GitHub stars and fresh commits as of today. It lives in your repo and works with the agent you already use. There is no web review space or documentation generation, so it is for developers, not product teams.

Tessl

Tessl focuses on skills, plugins and evals for coding agents. The free plan includes 1,000 credits a month with no card, and Team costs $100 per month with five times the credits. It is stronger on agent evaluation and weaker on the product side of specs.

Final Verdict: Is EasySpecs Worth It?

EasySpecs has a clear idea and a thoughtful workflow. Grounding change requests in the real codebase, then attaching falsifiable claims to every spec, is a smarter answer to agent-written code than piling more reviewers on the output. On Workbench at EUR 5 per repo with your own keys, it is one of the cheapest ways to try spec-driven development with a proper review surface.

The caveats are real, though. The trial cannot cover the core documentation run, Factory credits cost EUR 10 each, and the missing privacy policy should stop any company with a security review. We recommend Workbench for small teams willing to bring their own keys, and waiting on Factory until the credit pricing and legal pages mature. It earns a 6.5 out of 10.