Work with us›Talk to usEnterprise · deployment shapes on the table
Enterprise and Regulated · Talk to us

Auditable verification, deployed inside your compliance perimeter.

Same engine. Same evidence. Wired into the workflow you already run, at the posture your compliance function will accept. Hosted, private cloud, or on-prem.

Talk to us
Deployment shapes · at a glanceChoose one
Hosted
Lens infrastructure

Calls over TLS. Fastest to first score. Region choice at contract time.

Private VPC
Your cloud tenant

The engine runs in your account. Traffic never leaves your VPC. Same models, same evidence.

On-prem
Your infrastructure

Air-gap-friendly. No outbound calls at serving time. Model bundle updates on your cadence.

Same engine · same evidence · same version discipline
01Why the document-level layer matters here

Regulated workflows need something citable.

A model’s say-so is not evidence. A domain list is not evidence. A calibrated per-document score with the flagged passage and a plain reason is evidence a compliance function can bring into an audit and a court can cross-examine.

What compliance usually tries
Where it falls short
What Lens returns instead
Domain reputation listsA rolling blocklist of publishers.
Rates the site, not the article. A bad piece on a good site slips through. A strong piece on a weaker site gets excluded.
A per-document score. Every flag anchored to the passage that earned it and the plain-English reason.
Model self-assessmentAsking the LLM to grade its own output or citations.
The model cannot reliably see its own blind spots. Verdicts flip between identical runs.
Independent scoring path on separate in-house models. Deterministic against the recorded release.
Brand-safety filterCategory and keyword blocking on inventory.
Category signal, not editorial quality. A page can be on-brand and still thin, misleading, or conflicted.
Document quality that runs alongside your existing filter, not underneath it.
Human review poolEditors and analysts spot-check output.
Does not scale to production volume. Not reproducible for audit. Slow to defend under scrutiny.
Scored at production volume, cited to the passage, reproducible on demand for finance, legal, or regulator review.
02The three deployment shapes

Pick the posture. The engine is the same.

Hosted

Lens infrastructure

The default. Fastest to first score, no infrastructure work on your side, region choice at contract time.

  • Calls over TLS 1.3
  • Region selectable at signing
  • Named account contact
  • Volume pricing, negotiated flat or metered
  • Same API surface as the API partner track
Private cloud

Your VPC tenant

The engine runs inside your cloud account. Traffic does not leave your network perimeter. Managed release cadence.

  • Deploys to your AWS, GCP, or Azure account
  • No outbound calls at serving time
  • Model bundle updates on a scheduled window
  • Ownership of logs and metrics stays with you
  • Priced per instance, not per call
On-prem

Your infrastructure

The engine bundle installs on your metal. Air-gap-friendly. Updates delivered as signed artifacts on the cadence you choose.

  • No network dependency at serving time
  • Signed model bundle, verifiable install
  • Update cadence set by you
  • Support delivered on your terms
  • Priced per site, negotiated at contract
03Integration surfaces

The engine, three ways in.

Surface
Best for
What ships with it
Direct APIStateless, auditable scoring calls into your pipeline.
Any pipeline that can make an HTTPS call. Batch, streaming, or on-request.
Full request and response shape. Rate policy per environment.
Agent-framework toolRegisters into agent frameworks and copilots.
Frameworks that already handle third-party tool calls.
Tool definition, permission scopes, sample calls, integration support.
Platform adaptersDrop-in slots for editorial and gateway workflows.
Editorial workstations, publishing platforms, and gateway pre-checks.
Reference adapter, admin surface, ops runbook. Adapter list expands with cohort work.
04Compliance posture

What we commit to today.

Data segregation

Customer inputs are not used to train or tune models. Where segregation matters more than convenience, the private VPC and on-prem shapes remove the question entirely.

Retention windows

Set at contract, not at defaults. Logs held for the operational minimum, and the operational minimum is negotiated, not assumed.

Version discipline

Every score carries the engine version. Version bumps are gated and released on a schedule you can plan against, not pushed silently.

Audit trail

Score, evidence, version, and timestamp travel together. What was scored, when, and against which engine, all reproducible on demand.

Access controls

Role-based access on the admin surface. SSO on the enterprise plan through your existing IdP.

Deletion on request

Written into every contract. Verifiable on the hosted shape. Immediate on the private shapes because the data never left your perimeter.

Certifications underwaySOC 2 Type II in progress. Current status and target dates provided on the intro call, quoted against real gates, not aspirational ones.
05What we will not do

Four lines named up front.

01
Political filtering.Lens does not carry a lean signal. Enterprise deployment does not add one. Quality and integrity measurement only.
02
Verdicts on truth.The engine returns a measurement with evidence. The truth call is your reviewer's, your editor's, your compliance officer's.
03
Third-party AI in the serving path.Scoring runs on in-house models. Enterprise deployment does not change that. Your data does not pass through anyone else's model at scoring time.
04
Domain-only reputation.Deployment shape does not change how the engine judges. The document is the unit, everywhere.
06How the conversation goes

Three calls, one contract.

Intro

Thirty minutes. The workflow you want verified. Where the check would sit. What compliance is asking for.

Technical

Your engineers and ours. Deployment shape, integration surface, data path, version discipline, ops runbook.

Contract

MSA and order form. Retention, deletion, and audit terms written explicit. Sign path, not a sales cycle.

Live

Deploy on the agreed shape. First real traffic. Named engineering contact on standby.

07Questions we get

Direct answers.

Can you deploy inside our VPC?

Yes. The engine runs inside your account, traffic does not leave your perimeter, release cadence is scheduled against your change window.

Do you support SSO?

On the enterprise plan, yes. SAML and OIDC through your existing identity provider. Role-based access on the admin surface.

What is the pricing model?

Terms are negotiated per client and set in the technical call, not the intro.

Can we cite scores in a regulatory filing?

Yes. Every score reproduces against the recorded release. That reproducibility is the property regulators and courts require in an evidentiary signal.

Do you replace our existing content quality tools?

Rarely. Lens usually sits alongside them. Domain reputation, brand safety, and content moderation answer different questions. Document-level quality is what this layer answers.

Who signs off on the enterprise agreement?

The Lens applied research and legal teams jointly, on every enterprise contract.

08Talk to us

The workflow, the shape, and the question.

Enterprise intro request

Fill this in and it goes straight to the Lens inbox. Next step is a thirty-minute intro call.

Not enterprise yet?

Two other lanes are open. Get early access to Lens for AI, or send a campaign log and get a scored audit back.

Join the programRequest a pilot audit