Platform
Built on a first-party spine
How SEOMadman is put together: only data you already own, row-level tenant isolation, read-only Google scopes, and a cost model that stays at zero marginal cost per user.
How it is built
Every choice serves the same thesis: honest data, held with restraint.
First-party spine
Only Search Console and GA4, nothing scraped.
Read-only scopes
We request read access; we never write anything.
Tenant isolation
Row-level security scopes each read to you.
Vaulted secrets
Provider keys live in a vault, off the client.
Durable memory
OKF stored as text in Postgres, no vector DB.
Zero marginal cost
No paid third-party API sits in the hot path.
The data model
Text you can trust, not a black box
Knowledge is stored as OKF: Markdown with structured frontmatter, as plain text in Postgres. You can read it, export it, and reason about it, because there is no opaque embedding in the way.
- OKF: Markdown plus structured data
- Queryable, exportable, inspectable
- No vector database, no hidden state
platform · architecture
RLS
Isolation
R/O
Scopes
$0
Marginal
Why the constraint is the moat
SEOMadman
Crawl-heavy suites
Data sources
Search Console and GA4
Crawlers and scrapers
Marginal cost
Zero per free user
Priced per crawl
Access
Read-only, always
Broad write scopes
Storage
Inspectable OKF text
Opaque indexes