Documentation
These pages are rendered straight from the repository's markdown on every push, so they never drift from the service they describe.
Should you opt in, what is collected, and your rights over your own data.
The frozen HTTP contract and the system design behind it.
Running a backend — on Azure, or anywhere else.
How this repository is run.
What the backend is, the repository layout, and the local build & test commands.
HOWWhere discussion belongs, the quality bar, and the two load-bearing contracts that change only deliberately.
SECHow to report a suspected vulnerability — always via private reporting, never a public issue.
CoCThe standards this community holds itself to.
This is the server half of a two-repository system, alongside the community provider hub and the sample applications.
Live: vouchfx engine v1.0.0-alpha.9 · Vouchfx.Sdk 1.0.0-alpha.9 · community providers listed in the hub registry: 1 (latest: Vouchfx.Community.JsonRpc 1.0.0-alpha.1).
The engine that produces the telemetry this service ingests — its telemetry reference (docs/telemetry.html on the engine site) covers the CLI-side vouchfx telemetry enable/disable commands and configuration.
The community hub for vouchfx step providers — unrelated data path, same ecosystem.
SAMPLESFour production-grade sample applications with complete .e2e.yaml suites — the engine client that would, if you opt in, be the source of the events this service ingests.