Questions, answered
Common questions about Specsight, grouped by topic. Can’t find what you’re looking for? Email ola@specsight.app and we’ll answer directly
Product
Specsight reads your codebase and translates it into a living product specification. Every Feature, every behaviour, written in plain language and structured into Context, Action, and Outcome scenarios. The codebase is the source of truth; Specsight keeps the rest of your company in sync with it.
Anyone on your team who needs to know how the product actually works without reading code — PMs writing tickets, customer success answering questions, sales preparing demos, managers onboarding new hires, executives reading the product without anyone translating it. Engineers benefit too, but they are not the audience that drives the design. One spec, one source of truth, for the whole company.
Connect a GitHub repository. Specsight runs a Full Analysis of the entire codebase and produces a spec — features, scenarios, connections, all in plain English. From then on, every merge to your tracked branch triggers a Release Sync that updates only the affected scenarios. Nothing to write, nothing to maintain.
A browsable spec organised by Feature, with each Feature broken into Context/Action/Outcome scenarios — happy paths, edge cases, and errors. Alongside it: a changelog of every release, a Feature Graph of how features connect, and reports summarising what changed across any time range you choose. Exportable to XLSX, Markdown, or PDF.
Confluence and Notion document what someone meant to build. Specsight documents what is actually running, drawn from the code itself. Static docs go stale the moment a feature ships; Specsight updates with every release, so what you read today matches what is live today.
It replaces the part that has to stay in sync with the code — the description of how every Feature actually behaves. Strategy docs, design rationale, customer-facing help articles, and onboarding guides still belong in Notion or Confluence. Think of Specsight as the layer underneath: the always-current truth that everything else can reference.
Yes — that is who it is built for. Scenarios are written in plain English, organised by Feature, and read like a product brief, not a technical document. The intended reader is a PM, customer success rep, salesperson, or manager. Engineers use it too, but they are not the audience the design serves.
Any language, any framework. Specsight reads your codebase the way a senior engineer would — understanding business behaviour rather than relying on language-specific rules. JavaScript, TypeScript, Python, Go, Ruby, Java, Rust, PHP, C#, Elixir, anything that lives in a Git repository.
Yes. The live demo is Specsight running on its own codebase — features, scenarios, changelog, reports, and the Feature Graph. No sign-up, no email gate. The product analyses itself in production; you are looking at the actual output.
You can, and many engineers do. The point of Specsight is everyone else — the PM writing tickets, customer success answering questions, sales preparing demos, managers onboarding new hires, executives reading the product without needing a translator. They get a browsable spec organised by Feature, with scenarios, a changelog, and reports — no terminal, no prompt to write, no fresh hallucination each time. Engineers can still wire Specsight into Claude Code or Cursor through the MCP server, so the same source of truth feeds both audiences.
Two different questions. Jira, Linear, and Slack are on the roadmap as native integrations — not shipped yet. If one would unblock you, get in touch and we will prioritise based on what real teams need first. Confluence and Notion are different — Specsight is not designed to sync into them. It replaces the part of your docs that has to stay in sync with the code; the codebase becomes the source of truth, and Specsight keeps a living spec updated with every release.
Someone with access to your GitHub repository connects it to Specsight — a one-time setup. From then on, everyone can use Specsight.
Most specs go stale because someone has to remember to update them. Specsight removes that step. Every release, the changed code is re-analysed and the affected scenarios update automatically through a Release Sync. No one has to maintain it.
Most Projects finish their first analysis in under an hour. After that, every release updates the spec in minutes through a Release Sync.
Every scenario can be edited, annotated, or deleted by your team, and every change is recorded in the changelog. Once your team has edited a scenario, Specsight won’t overwrite it on the next release — if the code conflicts, it flags the scenario for review instead. Specsight writes the first draft; you own the final word.
Security & data
Read-only access to the GitHub repositories you connect. Code is sent to Anthropic Claude for analysis, never stored on Specsight servers, and never used to train AI models. Full detail on the security page.
No. When Specsight analyses your codebase, the repository is cloned to a temporary environment via a shallow Git clone, analysed, and then deleted in the same job. The only things persisted afterwards are the extracted specifications — features, scenarios, and connections — not the source code itself. During Release Syncs, only the diff for the changed files is sent to the AI for analysis, and it is not stored either.
All code analysis and text generation is performed by Anthropic's Claude. Per Anthropic's API privacy policy, inputs sent to their API are not used to train their models. Specsight uses the Claude Agent SDK for Full Analysis and the Claude API for text generation like Feature descriptions and Reports.
Specsight connects via a GitHub App with fine-grained, read-only permissions. It can read repository contents, file trees, commits, and diffs. It cannot write to, merge into, or modify your repositories in any way. The app subscribes to push, installation, and installation_repositories webhook events to trigger Release Syncs.
Every org-scoped table in Specsight's database has Row-Level Security (RLS) policies enforced at the Postgres layer via Supabase. A user authenticated to one organisation cannot read or modify data belonging to another. Multi-tenancy is enforced in the database, not just in the application code.
When you generate an MCP API key, only a SHA-256 hash is stored in the database — never the full key. If the database were ever exposed, existing keys would not be usable. Keys are prefixed with sk_sp_ for identification and are scoped to a single organisation. Revocation is soft-only so the audit trail is preserved.
Encrypted and stored in Supabase Vault — a dedicated secrets manager, not a regular database column. The key is decrypted only at the moment of use and never logged. The underlying database functions that read it run with restricted service-role access. Full detail in the Encryption section of the security page.
Account deletion is processed immediately — your account is removed from the active database via cascading foreign-key constraints, and Supabase backups rotate it out within 30 days. Deleting an Organisation cascades to every Project, Feature, Scenario, and changelog entry inside it; if other Members remain, the Organisation persists and only your account leaves. Billing records are retained for the period required by Polish tax law (5 years from the end of the tax year). Full detail on the security page.
Yes. A DPA is available on request — email ola@specsight.app and we will send you one.
Email ola@specsight.app with "SECURITY" in the subject line. Please describe the issue clearly, include steps to reproduce if possible, and give us a reasonable window to respond before any public disclosure. We take reports seriously and respond as quickly as we can.
Pricing & billing
Two paid plans plus a partnership programme. Standard (€129/mo) — AI usage included, up to 5 projects. BYOK (€49/mo + your Anthropic API key) — same product, unlimited projects, you bring the key and pay Anthropic directly. Partnership (free) is invitation-only for a small number of hand-picked teams shaping the roadmap with us. Every plan includes unlimited Members. Full breakdown on the pricing page.
Yes — that is the BYOK plan. €49/mo flat for the platform, then you pay Anthropic directly for the cost of your analyses and syncs. Because the AI cost sits with you, BYOK has no project cap — connect as many repositories as you like, up to the same 10,000-file / 150 MB ceiling per repo as Standard. The right fit for teams who already have an Anthropic account or want to scale across many products without a per-project Specsight fee.
No trial today — both paid plans start at the regular monthly price. If you are a serious team shaping the roadmap with us, the Partnership programme is free for the right fit — book a call to see if it applies.
Open Organisation Settings → Billing and click into the Stripe customer portal to cancel directly. Paid features stay active until the end of the current billing period; access pauses automatically after that. Data is retained for 90 days so you can resume any time, then permanently deleted. No retention call, no email loop.
If you are in the EU, you may be entitled to a refund under consumer protection rules — email ola@specsight.app and we will handle the request in line with the law. Outside that we do not run a blanket refund policy, but if something has genuinely gone wrong, write to us and we will sort it.
Team & access
Four roles, listed from most to least powerful. Admin has full access — managing the Organisation, Members, billing, and the GitHub connection. Developer manages the GitHub connection, projects, and edits scenarios. Editor adds, edits, and deletes scenarios. Viewer reads every spec and report. Every role — including Viewer — can annotate scenarios.
Admins, Developers, and Editors can add, edit, and delete scenarios. Anyone — including Viewers — can annotate them. Once a scenario has been edited by a person, Specsight will not overwrite it on the next sync — if the code conflicts with the manual edit, the scenario gets flagged for review instead.
No. Every plan — Standard, BYOK, and Partnership — includes unlimited Members. Invite the whole company, give Viewer access to anyone who needs to read the spec, and stop counting seats.
Company
Ola Piętka — engineer with years of startup experience and a long history of watching the same pattern repeat: engineers ship faster than anyone outside engineering can follow. Specsight is the tool she wished existed at every company she has worked at. The Founder section on the homepage has more, or book 15 minutes if you want to talk to her directly.
Continuously. Every commitment with a status and a date is on our public roadmap — what’s live, what’s shipping this month, what’s next, and the eventual vision. You can react to any card to tell us what matters most.
Not yet. Specsight is still small enough that the founder writes the code and ships the marketing. When that changes, open roles will go up here — until then, the most useful way to get involved is to join the Partnership programme.
Bootstrapped today. Open to the right partner — if you are an investor and the timing feels right, email Ola.
Poland. Specsight is operated by Ola Piętka as a registered sole proprietorship at ul. Zawodzie 20, 80-726 Gdańsk. We follow GDPR, and a Data Processing Agreement is available on request.