VERIKER OPEN CORE nexiverify.com →NEXIVERIFY →
The open core for AI-output verification

An independent way to check whether an AI's output is what it claims to be — free, open, Veriker™.

Veriker is the permissively-licensed core for verifying AI output: a portable receipt format and a re-derivation check anyone can run, host, or audit. The managed product built on top of it is NEXIVERIFY.

Apache-2.0 · permissive Open core · vendor-neutral by design Patent-pending methods
See the product, NEXIVERIFY
01 · What Veriker is

A receipt for AI output that anyone can re-check.

Three parts, all open. The point is that nobody has to take the verdict on trust — the check is reproducible, and the format is nobody's secret.

The format

A portable receipt

A signed, self-describing record of what was checked and what the verdict was — readable and re-checkable outside the system that produced it.

The check

Independent re-derivation

Rather than trust a claim, Veriker recomputes the result and signs a pass or fail. The producer of a thing is never the verifier of it.

The license

Permissive, forever at the core

Apache-2.0. Free to adopt, fork, host, and embed. Adoption is the whole job of the core; the revenue lives one layer up, in the product.

02 · The structure

Two layers, same hands.

The open standard and the company are different things with the same authors — the model that let a free signing standard sit under a multi-billion-dollar company while staying free.

The core — free, neutral

Veriker

The open, Apache-2.0 verification core. Nobody owns it; the aim is that everyone can trust it because anyone can audit it.

  • Permissive license, vendor-neutral, built to be embedded anywhere.
  • The core wins adoption; charging for it is never its job.
The product — managed, paid

NEXIVERIFY

The managed receipt of record built on Veriker: hosted verification, maintained policy packs, and the independent record enterprises renew.

  • A repeatable product above the core — managed, hosted, kept current.
  • Independence is the product — the same hands, a separate trust boundary.
03 · Principles

What the core will and won't do.

1

The producer is never the verifier

A system cannot vouch for its own output. Veriker exists to give a check that sits outside the thing being checked.

2

The verdict is reproducible

Anyone with the receipt can re-run the check and reach the same pass or fail. No portal, no black box, no "trust us."

3

The core stays permissive

Apache-2.0 at the core, always. If defensive licensing is ever needed, it goes on the product layer — never on Veriker.

4

Soundness before release

An unsound verifier is worse than none. The engine ships open only when its checks are proven correct — not before.

04 · Where this stands

Honestly, today.

This page is the standard's home and its intent. The engine is in development and stays gated until its soundness is proven — that is the one rule a verifier cannot break.

01

The name and the home

veriker.com secured; this page stands up the open-core story and links to the product.

Live
02

The receipt format

The portable, re-checkable receipt spec is being prepared for open publication.

In prep
03

The verifier engine

Source stays private until its soundness is proven and the test suite is green. No false-pass ships.

Gated
04

Neutral governance

A stated path to multi-stakeholder stewardship once the core is adopted — independence is what it sells.

Planned
The shape of it

Free core, paid product, same hands.

Veriker is the open verification core. NEXIVERIFY is the managed product above it. The free layer is how the receipt becomes the default; the product is how the work gets paid for. The discipline that matters is sequence — adoption before revenue, soundness before the source.