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 is product observability: one clear picture of how your product works today, and how it changes with each release. It reads your codebase and turns it into a business-level view of the product, every feature, how it behaves, and how it all connects. Read by everyone from support to the CEO, and written by nobody.
No. Specsight reads code, but nothing about using it is technical. It is a product tool, not a developer tool: you open it and read your product in plain language.
Observability is how you see what a running system is doing without stopping to ask it. Teams have had that for their infrastructure for years. Product observability points the same idea at the product: what it does today, what changed in the last release, who that change affects. More in the glossary.
Product and business people: product, support, sales, marketing, leadership. Engineers can pipe the same data into the AI tools they already use. One source of truth for the whole company.
Two minutes to set up. You create your organisation, connect your product through GitHub or GitLab, and Specsight runs a first analysis. After that it updates itself every time your team releases a new version. Nothing to configure, nothing to maintain.
Confluence and Notion hold what someone meant to build. Specsight shows what actually shipped, read from the code itself. It is not another page to keep up to date, it is an instrument you watch, so what you read today matches what is live today.
Tickets record what you planned. They are written before the work and almost nobody goes back to correct them when the build turns out differently. Specsight records what actually shipped, read from the code afterwards. Reading the two side by side is the interesting part, which is why connecting Jira and Linear sits on the roadmap.
No. It covers what a wiki cannot: how every feature actually behaves, read from the code. Strategy, design rationale, help articles and onboarding guides still belong in Notion or Confluence. Specsight is what they can all point at.
Any of them. Specsight reads for behaviour, not for syntax, so there is no supported-languages list to check yourself against. JavaScript, TypeScript, Python, Go, Ruby, Java, Rust, PHP, C# and Elixir all work the same way.
Yes. You can open the live demo, which is Specsight running on its own codebase. Or watch Specsight in 3 minutes.
You can, but it is one question at a time. You write the prompt, wait while it reads the code, and get back a wall of text nobody else sees. There is no shared view, and the next person starts from scratch. Specsight is one picture the whole company reads, already written when you open it.
At the moment one project is one repository, so a product split across several repositories becomes several projects in the same organisation. We are working on multi-repo projects, where one spec covers several repositories.
Yes. You choose which changes are worth announcing, Specsight drafts them in your product’s voice, you edit the draft, then publish to a public page. Nothing goes out that you have not approved.
Not yet, but all of them are on the roadmap. Connecting Jira and Linear unlocks gap analysis: a side by side of what you planned versus what actually shipped. Confluence and Notion would feed Specsight more context about your product. If one would unblock you, get in touch and we will prioritise what real teams need first.
Nobody updates anything. Specsight reads the code on every release, so the picture moves with the product.
It reads your actual code, so there is nothing to invent: every scenario comes from something that exists in the product. A second pass then re-reads everything the first one wrote and corrects it, and every scenario goes through automatic quality checks before it is saved. Anything that still reads wrong, your team can fix.
Most projects finish their first analysis in under an hour. After that, every release updates the spec in minutes.
Security & data
The repositories you connect. Specsight reads your code and never writes to it. 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. Specsight reads source code to understand behaviour and skips everything that is not code. Media, binaries, data files, lockfiles and `.env` files of every kind are excluded before analysis.
No. Specsight reads your code, it does not keep it. For an analysis the repository is copied to a temporary environment, read, and deleted in the same job. What stays afterwards is only what Specsight wrote: features, scenarios and connections. On every release only the changed code is read, and that 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, digests, and release notes.
Read-only, and nothing else. Specsight connects through a GitHub App with fine-grained permissions to read repository contents, file trees, commits and code changes. It cannot write to your repositories, merge anything, or change them in any way. It subscribes to push and installation events so it knows when a release has landed.
Through an access token you create in GitLab and paste into Specsight with your instance URL, so gitlab.com and self-managed GitLab both work. Specsight stores it encrypted and never writes to your code. The permissions the token needs and what happens when it expires are in connect GitLab and on the security page.
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.
BYOK is an older plan Specsight no longer offers, so this only applies to organisations still on it (older plans). The key is encrypted in Supabase Vault and decrypted only at the moment of use, never logged. 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 7 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
One plan, Standard: €150 a month with every Specsight feature, for up to 3 projects and 50 members. For more projects, members or syncs, a Custom plan sets the limits and the price for your company, book a call.
Yes, by application on the plan step during setup: teams that fit get 7 days free straight away, and everyone else hears back the same day. The trial needs a card, but nothing is charged until it ends. If you'd rather pay straight away, your first payment comes with a 14-day money-back guarantee.
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.
Your first payment comes with a 14-day money-back guarantee, unless you started with a free trial. Email ola@specsight.app within 14 days for a full refund, which ends your subscription straight away. Later payments aren't refunded, but if something has gone wrong, write to us and we'll sort it.
Team & access
Four roles: Admin, Developer, Editor and Viewer. Full breakdown in members and roles.
Standard includes up to 50 members. For more, a Custom plan raises the limit, book a call.
Company
Ola Piętka, an AI engineer shaped by early-stage startups across the EU and US, who built Specsight after watching every team she joined lose track of its own product. The Founder section on the homepage has more, or book a call to talk to her directly.
Continuously. Every commitment with a status and a date is on our public roadmap: what is live, what is shipping this month, what is next, and the eventual vision. You can react to any card to tell us what matters most.
Not yet, but the hiring process starts soon. If you would like to collaborate, reach out to ola@specsight.app.
Yes. We are raising a pre-seed to grow Specsight. If you would like to know more, the investor page is where you can book a call or get access to the deck.
The team is based in Poland.