About Secure Raven

A security layer that shows its work.

Secure Raven inspects what a team has shipped, a Supabase or Postgres database and public websites, for the mistakes that leak customer data. It works from fixed rules, keeps names and flags instead of your rows, and publishes the claims it does not make.

Part of
The Olyron framework, as its security layer
Built by
Olyron
Inspects
Supabase or Postgres databases, and public websites
Works from
13 Ravens on fixed rules, 3 inspection stages in a fixed order
Status
Private early access · invite-only
Running today
Web Headers, Web Surface and Login Flow. The other 10 Ravens do not run for customers yet.
First commit
· Changelog
  1. CompanyOlyronolyron.com
  2. FrameworkThe Olyron frameworkOlyron’s apps and services
  3. Security layerSecure Ravensecureraven.app
  • DatabaseSupabase or Postgres
  • WebPublic websites
Olyron builds the Olyron framework. Secure Raven is the framework’s security layer, and it inspects Supabase or Postgres databases and public websites.

Scope

What it is, and what it is not.

Secure Raven does one job: it checks what you have shipped. Its scope is written down, and so are the decisions about what it will not become.

It is

in scope
  • An inspection of what you ship.Your Supabase or Postgres database and your public websites.
  • 13 checks called Ravens.Each one built on fixed rules. Meet them
  • An ordered database inspection.Connect, Static posture, Detector. A stage that cannot finish is reported as incomplete, never as a pass.
  • Evidence you can hand over.An evidence export and an append-only, hash-chained audit log.

It is not

by design
  • A firewall or a proxy.No WAF and no proxy between you and your users.sitsInFrontOfSubscriberApi: false
  • Endpoint protection.It does not detect or stop attacks on laptops and servers.Decided 2 September 2026
  • A device lab.It does not test apps on phones.Decided 8 September 2026
  • An AI scanner.No AI model reads your data, and findings, events and credentials are never sent to an AI vendor.
  • A certification.HIPAA Hawk maps technical safeguards and cites the rule behind each check. It does not certify.hipaaCertified: false

The record

The record so far.

Milestones from Secure Raven’s own history, newest first. The changelog has every entry, in plain words.

Read the changelog
  1. A fresh database, closed by default, with Ed25519 request signing.

    Entry from 16 October 2026
  2. Push-probe mode and Customer API v1.

    Entry from 27 August 2026
  3. MFA step-up, the hash-chained audit log and an isolated broker.

    Entry from 26 August 2026
  4. HIPAA Hawk and the ordered inspection.

    Entry from 25 August 2026
  5. The Web Ravens: Web Headers, Web Surface and Login Flow.

    Entry from 19 May 2026
  6. Sign in with Olyron.

    Entry from 23 February 2026
  7. First commit: a control plane, a probe and a worker.

    Entry from 5 February 2026

The mark

Inspected. Never certified.

The mark is the Sentinel’s head, drawn as one solid shape with a glare for an eye. Its evidence stamp says only what Secure Raven can stand behind: inspected, which run, which day.

Drawn from
The Sentinel, the Raven that runs Watch
Geometry
14 points and 4 radii on a 64-unit grid, with the eye as its one counter
Small sizes
16 px drawn by hand, 32 px snapped to the pixel grid
Stamp
The Fail-Closed Seal: the stop shape, with the head knocked out

Contact

Talk to us.

Secure Raven is private and invite-only today. Request early access, or write to the address that fits.