MiddleOut is a compression-first video streaming pipeline. The public repository is the front door: product summary, non-confidential proof notes, licensing boundary, and access request process.
The engine is not in this repository.
This public repository contains:
- product and access-request documentation
- non-confidential public proof notes
- links to public smoke fixtures
- licensing, trademark, and security boundaries
This public repository does not contain:
- MiddleOut engine source code
- benchmark harness source code
- buyer data-room ZIP files
- production-readiness bundles
- real customer videos
- private release evidence
- private deployment configuration
- credentials, API keys, or provider accounts
The private engine repository remains private. Evaluation access may be granted only after written approval and, where appropriate, a signed NDA.
MiddleOut is a system for evaluating and packaging bandwidth-saving video delivery evidence. It focuses on:
- real video intake
- adaptive streaming ladder generation
- quality-gated compression comparisons
- buyer-readable economic proof
- deployment-readiness evidence
- tamper-evident release and data-room packaging
The public material is intentionally high-level. It is meant to show the product boundary without disclosing implementation details that would allow cloning the engine.
The public smoke fixture repository is separate:
https://github.com/Martin123132/MiddleOut-public-smoke
That repository is fixture-only. It exists to host public HLS smoke artifacts and prove that a generated public stream can be inspected without exposing the private engine.
Private access is not automatic. Start here:
Do not post confidential business information, proprietary videos, credentials, or private datasets in public issues. Public requests should only identify who is asking and what kind of evaluation is being requested.
MiddleOut is not open source. Public materials are source-available/evaluation materials under the repository licence. Commercial use, commercial integration, hosted service use, benchmarking-as-a-service, or incorporation into a video platform requires written permission from TWO HANDS NETWORK LTD. Commercial licensing discussions should be directed to the COO/licensing contact through the private access or licensing route.
See:
MiddleOut has a private engine and private evidence chain. The public project is parked behind a controlled access gate until there is an appropriate evaluation path. The current public boundary is summarized in docs/current-status.md.
GitHub Actions are intentionally not configured in this public access repo. The project avoids paid CI dependencies and avoids exposing private implementation details for public build logs.