Technical intelligence · Public sources only

Any software product.
What is it made of?

Paste a URL. Get an evidence-backed report on the product's architecture, stack, and complexity — cited like a research paper.

Free during beta · Research takes a few minutes

Technical Intelligence Report

Kurrent Capacitor

capacitor.kurrent.io · researched from 21 public sources

8.4/10
Complexity

Highly complex system: broad agent compatibility, live capture, event sourcing, MCP recall, permission-sensitive team workflows.

C# / .NET 10 · NativeAOTconfirmed[3]
KurrentDB event streamsconfirmed[1, 11]
ASP.NET Core serverstrongly supported[3, 6]

Prepared from public sources only. Excludes reimplementation guidance.

The deliverable

A standardized fourteen-section dossier

Every report follows the same structure, so two products — or the same product six months apart — can be compared line for line.

01

Reconstructed architecture

Components, data flow, and an architecture diagram for how the product appears to work end to end — confirmed and probable details kept strictly apart.

02

Confirmed vs. probable stack

Technologies proven by first-party evidence — project files, official docs, package metadata — listed separately from well-supported inference.

03

Complexity score

A weighted 1.0–10.0 score across eight engineering dimensions, each with its own rationale.

04

Open-source equivalents

Closest, partial, and adjacent alternatives — with license, activity, overlap, gaps, and a similarity score for each.

05

Evidence ledger

Material claims carry a classification — confirmed, strongly supported, likely, possible — and numbered citations that resolve to a full source list.

06

Unknowns, stated plainly

What public evidence cannot establish is listed explicitly. Uncertainty is preserved, never papered over.

Full report contents

  1. 01Executive summary
  2. 02Product overview
  3. 03How the product works
  4. 04Reconstructed architecture
  5. 05Confirmed technology stack
  6. 06Probable technology stack
  7. 07Component-by-component analysis
  8. 08Technical advantages
  9. 09Disadvantages and tradeoffs
  10. 10Complexity score
  11. 11Open-source equivalents
  12. 12Unknowns and limitations
  13. 13Evidence ledger
  14. 14Sources

How it works

Three steps. The rest is our problem.

  1. 01

    Submit a URL

    Any public software product. That's all we need.

  2. 02

    We research the public record

    Deep, bounded research across the product's public footprint — never behind a login.

  3. 03

    You get a cited dossier

    Fourteen standardized sections. Every material claim classified and cited, delivered in minutes.

Pricing

Pay per report. No subscription required.

Beta — all reports free right now

Free Preview

$0

Proof the research worked before you unlock anything.

  • Product summary & identity
  • Complexity score teaser
  • One sample finding
  • Count of public sources reviewed
  • A glimpse of the architecture
Try it
Most popular

Full Report

$79per report

The complete standardized dossier. Nothing held back.

  • All fourteen sections, complete
  • Evidence ledger with citations
  • Full numbered source list
  • PDF & Markdown downloads
  • Typically 8–15 pages
Run a full report

Extended Report

$149per report

Same structure, substantially deeper research.

  • Everything in Full
  • Up to ~2.5× the source coverage
  • Broader repository & package research
  • Expanded equivalents: direct, partial & adjacent
  • Deeper contradiction & historical review
  • Typically 15–25 pages
Go extended

Five Full Reports — $299

Effectively $59.80 per report. Reports never expire.

Get the pack

Report depth depends on the product's public footprint — a product with a thin public record produces a shorter report at any tier. Same-product requests within 30 days are served from your report library at no charge.

Ground rules

Research you can defend

01

Public sources only

Pages are read exactly as a visitor sees them — never signed in, never behind a paywall, and downloaded code is never executed.

02

Every claim cited

Material statements reference numbered sources. Nothing can be marked confirmed without first-party evidence.

03

Explains, never duplicates

Reports describe how a product works. They never include reimplementation plans, schemas, or clone-building guidance.

04

Honestly dated

Reports carry their true research date. Repeat requests within 30 days reuse the same dated report.

Run your first report

Free during beta. Results in a few minutes, dated and sourced.