Vlaander

Trust

What you can check, and what is not ready yet.

Vlaander does not pay for audits. What it offers instead is evidence you can check yourself: figures labelled as measured or stated, open review findings published on each engine's page, and the SHA-256 of every source archive. Public proof repositories with attested results are in preparation. This page says which of these exist today.

Proof repositories In preparation

Each proof repository will hold an engine's interfaces (declarations only), a black-box acceptance suite, the benchmark harness and workloads, attested benchmark results, and a list of open findings. The engine's source code is not published there. The first three are below. None is public yet, so there is nothing to link to; until one is, the engine's page is the record.

EngineProof repositoryEvaluation before purchase (planned)
SOVIn preparationCapped evaluation image that expires after 30 days
MOBIn preparationCapped evaluation image that expires after 30 days
PRIIn preparationHosted evaluation sandbox

Until these exist, nothing can be run before purchase. Each engine's page says how its figures were measured.

Attestations and SBOMs

Today

In preparation

Scorecard and scanners

Each proof repository will run OpenSSF Scorecard, CodeQL and OSV-Scanner on its public files and publish the results. No score exists yet, because no proof repository is public.

Open findings

Every engine has been through Vlaander's own review. Each engine's page lists what is fixed in the source you receive and what is still open, under Scope and maturity. Where an engine has a maturity notice, read that first. Questions about a finding: ask on the support page.

Reporting a vulnerability

Email sales@vlaander.com. The same contact is in security.txt, and each proof repository will carry this policy as its SECURITY.md.

Scope

  • The website www.vlaander.com and the API at api.vlaander.com.
  • The public files of Vlaander's proof repositories (tests, benchmark harness, workflows), once they are published.
  • The source code of an engine, if you are a licensee or have found an issue in a published evaluation build.

How to report

  • Email the contact above with the subject line "Security", or, once a proof repository is public, use GitHub's private vulnerability reporting on that repository (Security tab, "Report a vulnerability").
  • Include what you found, where, how to reproduce it, and the impact you expect. Do not include anyone else's personal data.
  • Please do not open a public issue or pull request for a vulnerability.

What we do

  • We acknowledge a report within one business day.
  • We tell you whether we can reproduce it, and agree a fix and a disclosure date with you before anything is published.
  • Fixed and open findings are listed in the engine's open findings, with the date.

Please

  • Test only against your own accounts and data, or a local copy.
  • Do not degrade the service for others (no denial-of-service or load testing against vlaander.com).
  • Stop and report as soon as you reach data that is not yours.

Recognition. Recognition only: with your permission we credit you by name in the open findings and the release notes. Vlaander does not pay bounties.

Refund policy

Assets are supplied exclusively to verified business purchasers. Once an Asset has been delivered, it cannot be returned, recalled or treated as unused because the Buyer may retain, copy, inspect, disclose or deploy the source code and associated information. Accordingly, except to the extent a remedy cannot lawfully be excluded, no refund, credit, cancellation or return is available after Delivery.

The full policy, including when a payment is refunded before delivery and how, is on the Refunds page.