CLEARSKY is an OSINT investigation platform. Open a case, collect
from public sources, produce a signed dossier. Anyone you share it
with confirms authenticity in 200ms at a public URL, no account
required. Built by the 79th Unit, a UK intelligence consultancy.
UK/EU jurisdiction.
When you sign a dossier in CLEARSKY, it ships with a public
verification code. Anyone you share it with, the instructing
solicitor, the insurer, the internal compliance reviewer, the
opposing side, pastes the code at a URL and sees this in 200ms.
No account. No printed seal. No chain of phone calls to confirm
provenance.
✓VERIFIEDf9b3a2c1-e7d8-4b6c-...
signed_at
2026-05-04 22:14:03 UTC
kind
DOSSIER
signed_by_role
SENIOR_ANALYST
alg
ECDSA P-256
key_fp
3a:7e:b1:c4:5f:9d:a2:8e
case_id
MP-20260504-A7K
No content disclosed. Only signature, role, timestamp, and
key fingerprint. The verifier proves the document has not
been altered since it was signed by 79th Unit.
Every signal, every decision, every dossier. One signed audit chain.
The cockpit is built around the intelligence cycle, not a dashboard
template. Live event ticker, classification banner that follows the
case, dual-confidence (pipeline vs analyst), proportionality gate
token-locked before sensitive collection runs.
01
Classification follows the case
OFFICIAL-SENSITIVE banner pinned at the top of every workspace. Nothing leaves a tier it shouldn't.
02
Dual confidence, never conflated
Pipeline confidence is amber, statistical noise. Analyst confidence is green, intelligence. Different DB columns.
03
Proportionality token-locked
Sensitive collection refuses to run without a 7-criterion gate. Time-limited token. Audit-logged.
04
Audit append-only at the DB
UPDATE and DELETE on the audit log are blocked by a Postgres RULE. Not policy. Not application code.
The intelligence cycle
A closed loop, not a dashboard.
Every CLEARSKY case enforces six stages with hand-off gates between them.
The platform refuses to skip a step. Click through to see how each
stage works.
Stage 01
Direction sets the scope.
The instructing solicitor or operations lead writes the brief
first. CLEARSKY captures the question, the lawful basis, the
tier ceiling, and the analysts assigned. Without this, no case
opens.
JESIP / METHANE / IIMARCH compiled into the form schema
Tier ceiling locked at case creation, immutable
UK GDPR Article 6 + Article 9 lawful basis recorded inline
EU AI Act Article 5 prohibitions checked at intake
Stage 02
Collection runs only after the gate.
Sensitive techniques are token-gated. Before a worker fetches
from a sensitive source it must present a proportionality
token. The token expires. The collection refuses to run if
the token is missing or stale.
15+ live connectors: AIS, ADS-B, BGP, Tor exits, GNSS, etc.
7-criterion gate enforced server-side, not in UI
Time-limited tokens, one per case + technique
Every fetch audit-logged with token reference
Stage 03
Processing builds the ontology.
Raw signals flow through Elasticsearch fuzzy match plus a
SequenceMatcher dedup pass before they touch the knowledge
graph. Direct INSERTs into ontology objects are blocked by a
CI gate, not a code review convention.
Resolution engine de-duplicates on every ingest path
Apache AGE graph + pgvector kNN over 384-dim embeddings
Pipeline confidence scored per relationship, amber UI
Direct ontology writes blocked by `lint_no_direct_inserts` CI gate
Stage 04
Analysis is human-driven, AI-augmented.
CHAPEL (the AI analyst assistant) drafts. The analyst confirms.
Pipeline confidence becomes analyst confidence only when a human
clicks accept. The two values stay in different columns,
forever, by schema.
CHAPEL fine-tuned weights, tier-scoped per CHAPEL Innovation 10.3
Cross-case pattern hunter runs every 6 hours
Daily / weekly briefing-of-briefings via CHAPEL rollups
Analyst-confidence amber → green only on explicit accept
Stage 05
Dissemination is signed and verifiable.
Every dossier export is rendered, hashed, and signed with an
ECDSA P-256 key by cs-core. The signature lands on the cover
page with a public verification URL. Anyone you share the
dossier with can confirm authenticity in seconds.
Pre-export gate refuses dossiers with missing analyst confidence
ECDSA P-256 signed by cs-core (Rust core engine)
Public verifier at /verifier with no account required
Tier ceiling enforced cryptographically, not by UI filter
Stage 06
Feedback closes the loop.
After Action Reviews are not optional. The case-closure gate
refuses to close a case without an AAR plus an outcome summary
of at least 100 characters. Subjects of investigations get a
Receipt of Evidence and an appeal route.
Every signed dossier carries an ECDSA signature and a public
verification URL. No account required. Anyone you share a
dossier with can confirm it has not been tampered with.
02 · Receipt of Evidence
Subject of an investigation? Request a Receipt of Evidence at
the subject portal. UK GDPR Article 15 by default, not as an
afterthought.
03 · Doctrine compiled to schema
JESIP, METHANE, IIMARCH, EU AI Act Article 5, and the National
Decision Model are compiled into the form schemas. The common
doctrine errors are blocked at form-level, not flagged after
the fact.
04 · Tier-respect by construction
Above-tier data cannot reach lower-tier surfaces. Enforced by
tier-conditioned data paths, model weights, and CRDT sub-docs.
Cryptographic, not declarative.
05 · UK/EU jurisdiction, single-server
OVHcloud bare metal in Roubaix. Not subject to the US CLOUD
Act. Docker Compose, no K3s. One server, fully audited.
Multi-node only when a real customer needs it.
Use cases
Pick the framing that fits your work.
Same platform. Same audit log. Same verifier. Different language
for different buyers. Open the page that matches your operating
context.
01 · Solicitors & litigation support
Evidence that holds up under disclosure. Signed dossiers,
field-level redaction reasoning, audit log per matter.
What your client sees, before you write a line of code.
Two demonstration pages so procurement, counsel, and analysts
can review the experience CLEARSKY produces. Sample dossier in
the platform's signed-PDF layout, plus the verifier verdict the
recipient sees when they paste the document ID.
The Founding Member program is not a discount tier. It's how we fund
the first commercial year while the customer roster fills in. One-off
£499. Lifetime Analyst access. Direct line to the founder.
Capped at 25 seats ever. When 25 are claimed, the program closes
forever.
25 of 25 seats currently
available · pre-launch · UK-regulated controller
Right of access. A copy of the personal data we hold about
you. Submit at subject portal.
Receipt of Evidence
A signed acknowledgement that your data has been queried,
processed, or stored, with a per-event audit trail. Cover
page carries a public verifier URL.
Public verifier
Want to check a dossier mentioning you? Paste its code at the
public verifier. Signature and timestamp,
no account required.
Procurement-ready answers
Frequently asked.
Where does our data live?
OVHcloud bare metal in Roubaix, France. UK/EU jurisdiction, not
exposed to the US CLOUD Act. UK ICO registered (00013660448).
Backups are 6-tier 3-2-1-1 with 14-day immutable Object Lock
copies in OVH SBG.
Can I cancel any time?
Yes. Monthly plans cancel from the next billing cycle inside
the Stripe Customer Portal. Yearly plans run to the end of the
paid period (no pro-rate). Founding Member is a one-off
lifetime payment with no recurring charge.
Do you handle GDPR DSARs?
Yes. The audit log retains object IDs only (never names) under a
DB constraint that blocks UPDATE / DELETE on audit rows. Subject
access requests routed via the subject portal return a structured
export within 30 days per UK GDPR Article 15.
Will I get a VAT invoice?
Every Stripe subscription generates a VAT invoice automatically
and stores it under your billing account. Enterprise contracts
go through a signed MSA with annual invoicing in arrears. VAT is
calculated at checkout for non-UK EU billing addresses.
What is the SLA?
Analyst and Team plans are best-effort 99% monthly availability
with status page updates. Enterprise contracts include a written
SLA with negotiated targets, support response times, and
credit-backed incident handling.
Is anything court-admissible?
Reports are structured, signed, and time-stamped to support a
legal context. Admissibility is for the instructing solicitor to
determine on a case-by-case basis. We do not claim admissibility
on your behalf.