Digital Exposure Assessment
A product opportunity: versioned assessment documents about a company’s public digital exposure, built on reusable document infrastructure — not a shipped scanning product.
A credible next product based on capabilities already built. Not a shipped product.
Problem
Exposure reviews often live in slide decks and inboxes. There is no productised way to store versions, attachments and a client-ready PDF around that review.
Users
Consultancies and operators who already do OSINT-style or security-adjacent reviews. No customers are claimed.
Current solution
Use the existing document engine (documents, collections, files, immutable versions, tags, PDF generate/upload) as the backbone of an assessment product. Scanning, scoring and automated OSINT are not claimed as implemented product features.
Workflow
An assessment would be a document with versions. Files live in object storage. PDFs can be generated or uploaded. A seed example in the engine is titled as an exposure assessment for a fictional company. That seed is not a live customer report.
01
Open an assessment document for an organisation
02
Attach evidence files
03
Issue a new immutable version
04
Export or upload a PDF for the client
Product architecture · Not a live product screenshot
Assessment as a versioned document
Organisation
The assessed company is a record, not a folder of emails.
Document
One assessment with immutable versions v1, v2, v3.
Files
Evidence stored as files, not as database blobs.
PDF output
A client-ready artefact generated or uploaded from the same object.
What exists today
A standalone document engine MVP exists: documents, nestable collections, storage, versions, tags, search and PDF generate/upload.
Webbylon can treat professional documents as versioned product objects, not as files in email.
Next milestone
No Digital Exposure Assessment consumer app is shipped. No automated exposure scan is claimed. The engine is not a compliance or MDR platform.
Define the assessment schema and a synthetic ACME-style report flow on top of the document engine.
No public production URL.
Evidence
- Document engine README and domain model describe Digital Exposure Assessment as a future consumer and seed example
- Engine MVP implements the document core only
Commercial opportunity
A packaged document product next to consulting reviews. No market size or pipeline is published.
Reusable capabilities
- Versioned documents and files
- PDF as an output, not as the system of record
- Multi-product document core
Current limitations
- Product opportunity, not a live product
- Seed data is fictional
- No public assessment UI to screenshot
What this shows about Webbylon
Webbylon can separate reusable infrastructure from a vertical product that has not been built yet — and say so.
Investment relevance
Shows how an internal document core can become more than one product without rewriting storage and versioning each time.
Use fictional organisation names only.
A credible next product based on capabilities already built. Not a shipped product.
Implementation note
- Document engine: Next.js with Postgres/storage; PDF via pdf-lib
Discuss this direction
The next step is a short conversation about the problem, the maturity, and the next credible milestone.