Read-only verification
Explore the public verify path and see how Vraimony keeps the verification layer light, constrained, and easier to trust.
One clear demo front door · Read-only by design
Understand Vraimony before you download, install, or onboard.
This demo is the fastest way to understand how read-only verification, sample evidence bundles, and widget-style display look in practice. It is built for understanding first, trust second, and next-step decisions third.
No upload is required for the first impression. This page combines an interactive verify path, a guided widget walkthrough, and a sample evidence bundle explanation.
What this demo shows
See the product without a heavy setup.
Sample evidence bundle
See how a bundle can bring together PDF, proof card, JSON, and official guidance without turning into a confusing workflow wall.
Widget-style display
Preview how a site or partner page can expose a visible verification surface with a lightweight, iframe-first approach.
Choose a demo path
Start with the path that matches your question.
Verification demo
Best for: users who want to understand what Vraimony checks publicly.
Open the public verify surface and review what read-only verification looks like before you install anything.
Widget demo
Best for: sites, stores, and partner portals that want visible verification without a heavy integration.
See the widget, understand the iframe-first model, and decide whether the widget or the plugin is the better first step.
Sample bundle demo
Best for: merchants and operations teams who need to understand the output structure first.
Walk through the Evidence Bundle Structure and see how PDF, proof card, JSON, and helper paths fit together.
What is simulated vs what is real
Know what you are seeing.
What you can test now
Read-only verification, guided tool pages, widget display, sample bundle structure, and public trust wording.
What requires official package or final state
Official release state, final signature publication, and certain stronger authoritative states depend on the official package, channel, and release wording.
What stays read-only
The public verify path is for integrity and reference checks. It is not a workflow platform, court opinion, or legal guarantee.
Next step
Move from demo to the right real path.
Download a tool
Go to the Downloads hub to choose the right helper for browser, site, document, or local workflows.
Open DownloadsStart with WooCommerce
Use the flagship wedge when you want to see how the Dispute Evidence Bundle fits a store workflow.
Start with WooCommerceRequest guided onboarding
Use contact if your next step is rollout, pack choice, or partner onboarding rather than self-serve exploration.
Contact VraimonyThree fast answers
What am I seeing, why does it help, and what should I do next?
See how verification looks before you install anything
The demo lowers friction for the first impression and shows what the public verify surface is actually for.
Explore a sample evidence bundle
You do not need to imagine the structure. The demo points you to a concrete bundle-style path and output explanation.
Understand what stays read-only and why
This makes the trust model easier to explain and reduces confusion between verification, workflows, and legal meaning.