Exact-version checking
Every decision stays bound to the document bytes that were checked. If the file changes, the new version needs its own scan.
Document security checkpoint for AI systems
Control which documents become reusable AI context.
Built for people operating RAG, knowledge bases and document-using agents, .mdSiren checks outside documents before reuse. Scan each incoming version, follow its handling decision and retrieve the current Approved copy as sources change.
Product overview
See the checkpoint in action.
See how .mdSiren checks new documents and updated versions, then keeps current Approved copies ready for knowledge bases and agents. The workflow shown remains current.
Launch update: the recording predates public signup. Free signup, Pro billing and scoped Pro API access are now available.
Read video transcript
Building AI systems with third-party documents? The more context the better, but the risk of hidden prompts and instructions scales with every document you add. That’s why we’re building .mdSiren: a security checkpoint for your AI projects. Upload Markdown files, PDFs or Word documents. Get a clear decision—Approved, Needs review or Quarantine—and keep the current Approved copy ready for use whenever you need it. Every new document—and every updated version—gets the check it needs before your AI uses it. And bring that same checkpoint to your AI agents, with Pro API access coming soon. Your projects. Your instructions. Check what gets in. Join the waitlist today.
The complete workflow
Check. Decide. Retrieve.
Check the incoming source, follow its handling decision and retrieve the current Approved file. The detailed record stays bound to the version that was actually checked.
- 01
Receive
Add the outside document
Bring a reference document, research source or client file into .mdSiren before it becomes AI context.
- 02
Check
Scan the exact version
Standard Scan checks the version supplied for supported prompt-injection and document-borne risks.
- 03
Route
Follow the decision
The completed scan routes that version to Approved, Needs review or Quarantine, with a reason and next action.
- 04
Organise
Place the record in a Collection
Choose a Collection for the client or project. Every status can be organised there; membership never grants approval or retrieval.
- 05
Use
Retrieve into the workflow
Download the current Approved file from your private Library, or use the Pro API for scoped submission, status and eligible Approved retrieval.
An accepted replacement needs its own approval. While it is pending or held, retrieval pauses; the earlier version is not supplied instead.
Core product
A consistent checkpoint as your sources change.
Use the workspace to inspect results, organise sources and handle findings. The Library keeps current Approved copies ready for the systems that need them.
Three clear destinations
Approved is ready for eligible reuse. Needs review calls for investigation, replacement or recheck. Quarantine keeps a hard-stop version out.
Collections and Library
Collections organise document records by client or project. The Library makes current Approved versions easy to find again.
Controlled retrieval
Adding a file to a Collection does not approve it. .mdSiren checks that the current version still meets its approval rules whenever it is retrieved.
What changes
Safer intake. Clearer decisions. Dependable reuse.
.mdSiren supports repeated document intake, revised sources and the systems that depend on them.
- 01
Control what enters AI context.
Put a deliberate checkpoint between an outside source and the agents, knowledge bases or AI projects that may use it.
- 02
Know what to do next.
Move from a scan finding to a clear handling decision: use the version, review the concern or keep it out.
- 03
Return to the checked version.
Supply the current Approved version to your workflow instead of trusting a filename or an unchecked duplicate.
Security and scope
Clear decisions, with explicit coverage.
Approved means the required supported checks completed without a stop or review finding for that exact version under the current policy.
Every result is limited to the reported checks and coverage; it is not a universal safety guarantee.
Before documents become AI context
Build AI projects on documents you have checked.
Start with five Standard Scans, once per account. No card required.