Recognise & expand
ShippingContent-based identity and bounded recursive traversal.
Roadmap & maturity
Turn the evidence engine into deployable decision products.
PayloadGlass is moving from breadth to productisation. The local analysis engine, evidence graph, risk projections and supported transforms already ship. The next milestone is one coverage-aware, intended-use decision contract shared by the CLI, Guardian, Gateway, Cleanroom and future integrations.
Decide, transform, and prove how untrusted content may be used. “Prove” means inspectable evidence, coverage, policy identity, transformation records and explicit limits — never a guarantee that content is universally safe.
One product spine
The maturity boundary is explicit.
Evidence
ShippingTyped findings, spans, source identity and explicit uncertainty.
Asset graph
ShippingNested members and cross-format relationships in one graph.
Risk
ShippingSecurity projections plus advisory governance context.
Coverage
Partial / hardeningWhat ran, what completed and what remains uninspected.
Decision
Partial / hardeningIntended-use guidance today; unified enforcement is being built.
Derivative
Partial / hardeningSafe text and supported sanitisation ship; support varies by format.
Live routing
RoadmapCustomer-deployed connectors and destination writeback.
Current priorities
The work that unlocks the product family.
- Evidence authority and support truth Expose provider participation, analysis obligations, support state, decision traces and explicit incomplete coverage.
- Shared Content Trust contract Accept content plus intended use and return one structured decision, evidence summary, coverage summary, policy identity and derivative references.
- AI Context profile Secure the content-to-context boundary before files, messages and bundles enter RAG, memory, tools or agents.
- Cleanroom workflows Quarantine raw content, produce supported safe derivatives, verify the result and emit residual-risk evidence.
- Thin customer-deployed connectors Filesystem, object storage, HTTP intake, RAG, SharePoint and message adapters must all exercise the same decision vocabulary.
Product direction
Surfaces, and how far each one actually is.
Every surface runs the same engine through shared contracts. AI Context is a profile, Support Bundle Cleanroom is a solution, and email or SharePoint are connectors — not separate products. Maturity is stated per surface rather than averaged into a claim.
sis CLI
ShippingLocal native analysis, investigation, reporting, querying, explanation and sanitisation — with machine output, batch and directory scanning, diagnostics and shell integration.
GitHub Action
ShippingRuns the public binary release in CI over repository or build artifacts, emitting JSON, JSONL and SARIF from a single pass. Release and action provenance continue to harden.
Browser Investigation Workbench
ShippingThe production engine compiled to WebAssembly, running in a local Worker and projected into real investigation areas. Your file's content is never uploaded.
Guardian
Partial / hardeningLocal monitored-folder and operator workflows with desktop and service surfaces, MCP integration, snapshot-bound acquisition, audit records and a transactional vault. Persisted automation authority and cross-platform polish are incomplete.
Content Trust API & gateways
RoadmapCustomer-deployed decision and transformation services for ingestion, transfer, collaboration, email or RAG flows. Not a shared hosted endpoint.
Enterprise control plane
LaterMulti-tenant policy, fleet, lifecycle and reporting surfaces built over the same narrow semantic contracts.
Deliberate boundaries
What PayloadGlass is not becoming.
Not a universal CDR Not antivirus or EDR Not a DLP replacement Not an email-security replacement Not a runtime LLM firewall Not a hosted public scanner Not a full SharePoint security suite Not enterprise case management