Frequently asked questions
Everything about workload fit, deployment, proof and design-partner access without the usual security-software fog.
- What is a workload in Veritas?
- A workload is the code your team wants to run on sensitive data, typically packaged as a container, job, pipeline or AI execution flow. Veritas governs how that workload executes and produces cryptographic evidence of the conditions under which it ran.
- Do we need to rewrite our applications?
- No. The goal is to bring existing workloads into a verifiable execution model with minimal architectural change, not force a full application rewrite.
- How is this different from observability?
- Observability explains what happened using logs, metrics and traces. Veritas proves what happened correctly by enforcing policy during execution and generating portable attestation evidence.
- Is this a compliance product?
- Not primarily. Veritas is a trust and governance layer for AI and cloud workloads. It supports audits, procurement reviews and defensible compliance evidence, but it is not just another compliance workflow tool.
- Who is this for?
- Security leaders, platform engineering teams, AI infrastructure companies and cloud-native businesses that need stronger proof of how sensitive workloads handle data.
- Can this help us close enterprise deals faster?
- Yes. One of the core outcomes is reducing security review friction by replacing claims, screenshots and interpretation with machine-checkable evidence.
- What does the evidence artifact actually show?
- It can show the workload identity, environment integrity, approval state, policy-constrained execution conditions and the cryptographic attestation material needed to verify those claims.
- Can our customers independently verify the proof?
- That is the point. Veritas is designed to make trust portable, so customers, auditors and regulators can verify how sensitive execution occurred instead of relying solely on internal assurances.
- How does Veritas fit into an enterprise security review?
- Veritas is designed to give security and procurement reviewers a clearer evidence path for sensitive execution claims. Instead of relying only on questionnaires, screenshots, dashboards, or narrative control descriptions, teams can show what policy applied, what runtime executed, what approval occurred, and what evidence was generated.
- What does Veritas actually prove?
- Veritas is designed to prove execution conditions: workload identity, runtime placement, policy checks, approval state, attestation signals, and verification results. It does not claim that every business outcome is correct. It helps prove that a sensitive workload ran under the agreed trust conditions.
- Does Veritas replace observability, compliance, or security tooling?
- No. Observability, compliance, identity, and security tooling remain essential. Veritas adds a verification and evidence layer for cases where customers, auditors, or data owners need portable proof that sensitive execution followed agreed conditions.
- Can a customer or auditor independently verify the evidence?
- That is the direction of the product. Veritas is designed around customer-verifiable proof bundles, verification results, and auditor-facing reports that make execution evidence reviewable outside the internal operator team.
- Does Veritas require confidential compute?
- Confidential compute is an important assurance mechanism for high-trust runtime integrity, but the trust model can vary by use case. Some pilots may begin with a lighter governed runtime model, while higher-assurance workflows may require confidential compute, stronger isolation, or customer-held key boundaries.
- What is included in a design partner engagement?
- A design partner engagement should move from trust concern to reviewable pilot. That can include Trust Fit discovery, architecture and trust-boundary mapping, pilot scoping, approval-flow design, evidence/report design, and walkthrough support for security, product, or procurement stakeholders.
- How does human approval fit into the flow?
- Human approval is used when a sensitive action should not continue automatically. Veritas can model approval checkpoints so the evidence shows who approved, what was approved, why it was required, and whether execution or release continued after that decision.
- What kind of workload is the best first fit?
- The best first fit is a real customer-sensitive workflow where a buyer, auditor, or data owner is asking for more assurance than a standard control narrative provides. Good candidates include enterprise security reviews, regulated AI workflows, external data boundaries, and human-approved sensitive execution.
Still evaluating fit?
Book a demo or contact sales for a proof walkthrough and buyer-fit conversation.