Your existing tests
test("blocks unknown user")
expect(status).toBe(401)One source of truth
Readable evidence, derived from running code
Teams can author structured or BDD cases directly, import existing suites and collections, and connect execution results back to requirements. Vaettir keeps the readable view and the source evidence together.
Readable behavior
Given an unknown user
When access is requested
Then the request is denied
When access is requested
Then the request is denied
Release evidence
SOC 2CC6.1
Current source passing
Evidence graph
Follow any claim all the way back
Every test case retains a path to its source, latest result, repository, owner, and compliance mapping.
- Framework-agnostic ingestion
- Given, When, Then documentation
- Freshness and drift signals
- Control coverage at a glance
Evidence explorerLive graph
auth.spec.tsUnknown user deniedSOC 2 CC6.137 / 37 passing
Compliance mapping
Controls become a living view, not an audit-season scramble
Working platform
Not a diagram pretending to be a product
Vaettir already has a multi-tenant SaaS foundation, organization-scoped roles, and a live AI reverse-engineering pipeline.
Platformv1 working
AccessOrganization RBAC
PipelineAI extraction live
ScopeFramework agnostic
The difference
Evidence should be derived, not authored
Write the same truth twice
Manual cases become another artifact for engineers to remember, review, and eventually distrust.
Connect documentation to reality
Readable cases and compliance evidence come from the source that already decides whether software ships.
The name
Why Vaettir?
VNamed for the vættir, old Norse spirits said to watch over a place whether anyone noticed them or not. Vaettir keeps watch over test coverage, making it visible before something breaks instead of after.