Correct markings.
Less work.
Marque checks classification markings and returns corrections with the rules behind them. Live, Sentry, and Steward bring that work to three situations: creating information, moving it, and maintaining what you already hold.
The product lines
Where do markings need to work?
As you work
Marque Live
Focus on the mission, not gray checkboxes.
Corrects and checks portion markings as you type, generating and updating your banner as you go. No checkboxes or clunky menus, just correct, consistent markings, authority blocks, warnings. Instantly.
As information moves
Marque Sentry
Catch mismarked and undermarked data in databases and in transit. Without adding to your workload.
Identifies and resolves classification and control markings on documents, data, and data labels. Correct them in milliseconds, quantine and inspect, or both.
Across existing holdings
Marque Steward
Identify and correct the actual marking metadata for your holdings.
Check and generate resolved correct markings across your current and historical holdings. At over 300,000 pages per minute per CPU core.
Tell us which workflow you need to support. A briefing is the place to confirm fit, integration, and availability for your environment.
Where Marque fits
Where intent becomes a marking.
Marque fits wherever classification intent becomes a marking: during live work, across a collection, or downstream of another system. Its inputs come from a classifier, existing documents, or AI and natural-language-processing tools.
The responsible authority or accredited upstream tool owns the semantic classification determination. Marque checks and corrects the portion markings, banners, labels, and metadata that express that determination, bringing them into compliance with the governing marking rules.
The division of work
What Marque does—and what stays upstream.
Marque decides
Rule-bound marking outcomes
Marque resolves classification and control markings, authority blocks, warning statements against governing policies and rules, resolving conflicts, applying forgotten rules, and catching that stray controlled portion on page 23.
Eligible corrections
You don't have to trust Marque's corrections. When it makes or suggests a correction, it will tell you exactly where to look the rule up... and show you the policy's text if you want.
Upstream authority
The semantic classification determination
People make classification decisions. Marque automates applying them.
The controlling facts
A person or upstream system supplies the applicable classification and SCG facts. Marque checks those inputs and automates the marking consequences.
How it deploys
Local integration
Marque runs inside an application, browser, or web app, or directly on the command line.
REST API and batch processing
Marque integrates through a REST API or runs as a deterministic stage in automated batch and extract-transform-load (ETL) pipelines.
Deployment stays under customer control
Marque does not phone home. The customer controls network isolation, audit routing, persistence, retention, and access.
Marque keeps checking, correction, and write-back separate. The caller chooses which step to request and whether returned text replaces the source. Marque returns machine-readable records when the caller reports a fix as applied and when the available inputs do not determine one correction.
Finding errors adds work. Correcting them removes it.
Marque is sold through resellers, distributors, and integrators.
Briefings demonstrate Marque against agreed test inputs.