SearchFab · AI-assisted OSINT · In development

Every finding traces back to an archived quote.

SearchFab turns open-source research into evidence. Missions plan their own searches, collect the open web through an isolated chain, archive every page before reading it, and keep only claims whose quote appears word for word in the source.

Crudfab / Products / SearchFab

The model plans. The code writes the evidence. And your analysts hold the gates.

Collect, archive, prove.

Three things happen to everything SearchFab touches, in this order.

Collect

Long-running research missions

A mission takes keywords, sites or a question, builds a search plan across metasearch, search APIs and 52 typed sources, and wakes on a schedule to look for changes.

Archive

Archive first, network second

A request cannot reach the network until its archive record is written; every capture keeps a SHA-256 content hash and a verified replica.

Prove

Claims bound to verbatim quotes

The model only points at a sentence; the code builds the quote and rejects any claim whose subject or object is not in it.

From a question to a signed evidence package.

Each step is a separate process with its own narrow permissions.

01

Plan

The mission turns a question into searches across engines, APIs and typed sources.

02

Fetch

A permit-gated chain fetches pages; only one process owns the outbound socket.

03

Scan

Files pass size limits, type detection, ClamAV and YARA-X before any parser sees them.

04

Extract

Claims are extracted with their verbatim quotes and linked into the graph.

05

Export

Approved findings leave as a signed, replayable evidence package.

Isolated collection

The process that touches the internet never sees the archive or the keys.

Socket ownership, archive writing and address checks are split across separate processes.

  • Host names are resolved once and the address is pinned; private, link-local, metadata and multicast ranges are refused, and every redirect is checked again.
  • The database issues a single-use 256-bit permit for each fetch, valid for at most five minutes.
  • JavaScript-heavy pages and media are rendered in sandboxed browsers that reach the network only through the fetcher.
  • Calls to model endpoints, search APIs and webhooks leave only through an egress gateway that checks the target and the caller's identity.
Evidence

A claim without its quote does not exist.

The raw page is seen only by an extractor with no tools; the evidence itself is built by code.

  • Quotes are matched with Turkish case folding and without fuzzy matching; an optional language-inference check adds a supports or refutes verdict.
  • Derived conclusions come from versioned rules evaluated without the model, so a reviewer can see which rule produced which link.
  • Custody events are hash-chained and rolled into an hourly root signed with Ed25519 by a separate signing process.
  • "Nothing found" is stored with the keywords, sources, languages and time window that were actually searched.
Analysts and gates

A claim-centric graph, with people at the gates.

Every edge on the graph exists only because a quoted claim supports it.

  • Entity resolution merges matching records automatically above a score and sends the uncertain band to a reviewer.
  • Plans, escalations and exports are gates; person-focused plans and every export need a second approver.
  • Findings export as FollowTheMoney, STIX 2.1 or a signed WACZ package that can be replayed and verified without SearchFab.
  • Watches run on a schedule over certificate transparency, RDAP, passive DNS and other infrastructure records, and alert through signed webhooks.
Models and AI

AI is a layer you switch on, not a dependency.

With the AI policy off, missions and the reading pipeline keep working on deterministic paths.

  • Fourteen model roles, from reasoning and embedding to OCR, speech, entity recognition and translation, map to your own OpenAI-compatible or TEI endpoints.
  • Model output is constrained by strict JSON Schema, and the next step is always one of six fixed routes.
  • A project can delegate plan and escalation gates to the model above a confidence floor; four-eyes and export gates are never delegated.

Built to be trusted with sensitive research.

01

Open interfaces

A REST API with a published contract of 160 paths, live event streams and an MCP server with ten tools.

02

Row-level isolation

Projects are separated inside the database with row-level security and a signed session context.

03

Unchangeable audit

The audit log is a hash chain, and database triggers block updates, deletes and truncation.

04

Strong sign-in

Argon2id passwords, TOTP with recovery codes, WebAuthn and scoped, expiring API keys.

05

Encrypted secrets

Stored secrets use AES-256-GCM, and services talk over the installation's own certificate authority with mutual TLS.

06

Hardened containers

Services drop every Linux capability, model and browser services run read-only, and browsers run under gVisor.

07

Signed supply chain

Images are signed and shipped with an SBOM, and deployment refuses any image without a valid signature and provenance.

08

No outside calls

The web app loads no external CDN, font or script, and the map uses a local basemap.

Put SearchFab on your own servers.

Request a briefing
Mobile and WhatsApp
+90 540 278 33 22
Email
hello@crudfab.com