Verify the bundle.
Do not just trust the logs.
OzRail is a customer-hosted, verifier-backed evidence rail for streamed API delivery. It sits beside an existing gateway, load balancer, or reverse proxy and produces a portable, offline-verifiable proof package for what was actually deliverable on the wire within a narrow machine boundary.
What OzRail is not
- Not a gateway replacement
- Not another observability or logging stack
- Not a generic billing engine
- Not a broad claim of human or business acceptance
Current posture
- STRICT H2 anchor lane
- BOUNDED H3 / WebTransport support
- Customer continuity remains outside OzRail
- Deployment is adjacent, reversible, and intentionally conservative
What OzRail is
OzRail is an evidentiary rail for streamed systems. Its purpose is simple: when delivery, usage, settlement, or partner accountability becomes disputed, it produces a verifier-backed artifact that can be reviewed outside the originating platform.
Portable evidence
Produces a portable, offline-verifiable proof package instead of asking the counterparty to trust provider-side logs or dashboard narratives.
Adjacent by design
Sits beside the existing gateway, load balancer, or reverse proxy rather than trying to become the traffic authority.
Narrow and explicit
Focuses on bounded machine-deliverability within a declared machine boundary instead of making broad or vague claims.
Why OzRail exists
Many systems can count requests, stream tokens, emit logs, and generate invoices. Fewer can produce a portable evidentiary packet that a skeptical counterparty can verify independently.
Delivery disputes
Useful when streamed or variable API delivery becomes hard to reconstruct cleanly later.
Settlement disputes
Useful when delivery and settlement need something stronger than provider-side records or platform-side logs.
Partner accountability
Useful when proof must survive outside the originating system and be reviewed by another party.
How OzRail fits
OzRail is strongest where the disputed fact is machine-boundary deliverability and where counterparties benefit from a portable verifier-backed artifact.
| OzRail does | OzRail does not do |
|---|---|
| Produce a portable, offline-verifiable proof package | Replace the gateway or traffic authority |
| Stay adjacent to an existing gateway, load balancer, or reverse proxy | Take over customer continuity |
| Support delivery, usage, settlement, and partner dispute handling | Act as a generic billing engine or analytics stack |
| Make narrow machine-boundary claims | Claim human consumption, semantic correctness, or business acceptance |
Proof boundary
OzRail is credible because it is narrow. The current strict product line is about bounded machine-deliverability, not broad end-to-end truth claims.
What it does prove
- Portable, machine-verifiable evidence for bounded delivery progression
- What was actually deliverable on the wire within a declared machine boundary
- A verifier-backed artifact that can survive outside the originating system
What it does not prove
- Human consumption
- Semantic correctness
- Business acceptance
- Universal end-to-end truth across every downstream system
Current support and posture
Current claims are intentionally bounded and explicit.
Strict anchor lane
The strict anchor lane today is H2.
Additional support
H3 and WebTransport support also exist, but claims remain bounded and explicit.
Deployment posture
Adjacent, reversible, customer-hosted, and intentionally conservative. Customer continuity remains outside the rail.
Who OzRail is for
OzRail is most relevant to teams that already live with streamed or variable delivery and where counterparties may dispute what was actually deliverable.
AI / API platforms
Where streaming, enterprise delivery, and variable pricing create gray areas later.
Gateway / edge platforms
Where an adjacent evidentiary capability may fit beside existing traffic control surfaces.
Settlement / monetization platforms
Where disputes require something stronger than internal usage records.
Partner ecosystems
Where proof must survive outside the originating system and be reviewed independently.
Contact
For a short technical note or a minimal verifier/report example, email directly.