Controlled content, in any form.
CUI and export-controlled content get caught by meaning, whether it sits in a CAD file, a notebook, or a results directory, not just where a pattern matches.
Inside discovery and classification →Secuvy learns your research data itself, in place, and gets more accurate as the data changes, exactly when pattern rules break.
Every AI project on research data stalls at one question: what is in the files, and who can prove it?
“Two thirds of organizations report having a formal tagging system in place. Only half describe their approach as comprehensive or automated.”
Classifying files by hand cannot reach a petabyte. Pattern rules only catch data that repeats; simulation outputs, instrument data, and files from collaborators almost never do.
At petabyte scale, classification breaks first—the GPUs were never the bottleneck.
Secuvy classifies your data unsupervised, in place, across your sources. It builds its own model of your data from content and context, not from rule sets.
It proposes a classification. Your stewards confirm. Every confirmation teaches the engine, and every new run gives it more to learn from.
What breaks a rule set trains Secuvy.
Inside non-pattern classification →CUI and export-controlled content get caught by meaning, whether it sits in a CAD file, a notebook, or a results directory, not just where a pattern matches.
Inside discovery and classification →Your data stewards confirm Secuvy's classifications instead of searching project shares by hand, and the queue shrinks as the engine learns your data.
Why the engine learns →Every pipeline carries a Data Bill of Materials: what fed it, what was held out, and when the record last changed.
The DBOM in depth →
Simulation runs leave large outputs no one has classified. Secuvy discovers and classifies them in place, so teams know what each result holds before it is shared.

Telescopes, sequencers, and beamlines write data faster than anyone can review it. Secuvy tags it as it lands, so researchers find what they need.

Export-controlled results hide in CAD files, notebooks, and results directories. Secuvy finds them by content and tags them, so stewards can check access.

Partners and sponsors share data under different terms. Secuvy tags each source, and a data bill of materials shows a sponsor what fed each model.
Thirty minutes on your own environment. Bring your export-control officer.
Request a demo →Yes. It runs fully disconnected, and what the engine learns from your data never leaves the environment it learned in.
Yes. Secuvy classifies files from content and context, including how they relate to the surrounding project data. It tags which data fits a pipeline, while your research and export-control teams make the final decision.
Yes, that is the design. It learns meaning from context instead of matching patterns, so unfamiliar formats are exactly what it handles.
Yes. Each pipeline carries a Data Bill of Materials listing what fed it, what was held out, and when it last changed.
Confidently fuel every AI pipeline.