Skip to content

Promise

Evidence-first. Bounded claims. Source systems stay yours.

The promise Valty makes is not about outcomes we guarantee. It is about how we operate: proof objects before big assertions, financial estimates with method and confidence visible, and a clear line between what Valty owns and what customers already own.

Review the proof surface
01

Product and marketing rule

Evidence beats assertion.

Claims we make about Valty (product claims, financial outputs, security posture) carry source, confidence, and freshness. The proof object is visible before the buyer is asked to believe the outcome. Louder language is not a substitute.

02

Claim-safety rule

Financial claims stay bounded by source, confidence, and freshness.

Cyber-risk dollar figures are decision-support estimates, not warranties. Every financial output carries method, confidence band, source coverage, and limitation. The number should be challenged, not blindly trusted.

03

Platform boundary

Customers keep their source-of-truth systems.

Valty sits above your scanners, GRC, cloud consoles, identity platforms, and financial models. It normalizes what is true, shows what it means, and packages proof. You keep those operational systems as the authoritative record for the controls your team already owns.

04

Commercial posture

We are early stage and say so.

No fabricated customers. No invented case study logos. No dollar prices without a scoped operating motion. We are in a design-partner stage and the site reflects that honestly.

Proof matrix

How each commitment operates in practice

Each promise maps to a specific behavior: what it constrains, what evidence it requires, and how often it is reviewed. The matrix is the accountability layer for the commitments above.

ClaimSourceConfidenceFreshness
Evidence beats assertionProof objects carry source, confidence, and freshness; louder language is not a substitute for a visible proof artifactOperating rule: applies to product, marketing copy, and sales motionReviewed on each content update and product change
Financial outputs are decision-support, not warrantiesEBITDA estimates, risk quantifications, and exposure ranges carry method, confidence band, and limitation inlineModel-based estimate: stated clearly at point of use, not buried in a disclaimer pageReviewed before board pack or buyer delivery
Source systems remain customer-ownedValty is a decision layer that reads and translates; customers keep their scanners, GRC, cloud, identity, and financial systems as systems of recordProduct boundary: VALTY reads and translates; customers retain enforcement and record systemsStated in product boundary, help docs, and procurement documentation
Stage-honest positioningDesign-partner stage; no public logos, no fabricated customers, no hard pricing until operating motion is scopedCommercial fact: updated when stage changesReviewed quarterly or when commercial motion advances
Blocked claims stay blockedPublication gate prevents stale, inferred, or unsupported claims from leaving the productEnforced in proof-pack export logic; mirrored in marketing copy review processChecked before each major content publish

Proof artifacts behind the promise

Inspect the evidence, not just the language.

Each commitment above points to a product behavior or a reviewed artifact. The pages below are where those behaviors surface: security posture, proof anatomy, and platform boundaries.

Security posture
Source
security@valty.ai + trust-center spine
Confidence
Factual, bounded. No claims beyond reviewed evidence
Freshness
Updated on product change or quarterly review
Proof anatomy
Source
Proof pack: claim, source, confidence, freshness, export target
Confidence
Artifact-based: visible in the product, not just described
Freshness
Reviewed before each board or audit delivery
Platform boundary
Source
Platform page: four motions, source-layer architecture
Confidence
Product boundary: you keep your source systems as the system of record
Freshness
Reviewed when platform scope changes
Financial estimate discipline
Source
EBITDA bridge and risk-quantification surfaces
Confidence
Decision-support only: method, confidence band, and limitation inline
Freshness
Reviewed before financial output is published

Where to verify the claim boundary

The security page states the trust-center spine factually: data boundary, tenant isolation, encryption stance, audit logs, subprocessors, and disclosure channel. Security claims stay public only when reviewed evidence exists behind them.

Where to see proof in practice

The proof page shows what a proof artifact looks like: claim, evidence source, confidence, freshness, and export context. Stale or inferred claims surface as blocked, not silently dropped.

Where the platform boundary is drawn

The platform page shows the four operating motions, verify, quantify, prove, operate, and which systems Valty sits above and reads. The evidence spine is additive; enforcement stays customer-owned.

Questions about these commitments

If you see a claim on this site that is not supported by visible evidence, or a boundary that seems inconsistent with the commitments above, reach out at security@valty.ai. The disclosure channel is the same for product security questions and claim-accuracy concerns.

Proof CTA

Start with the evidence, then decide.

The free tools return an artifact, not a lead form. The design-partner path is structured around your operating motion before a commercial number is set.

Review the proof surfaceRequest access