Move critical data in one direction, with control over the path.
qntm is Bayontek’s one-way data movement platform for high-volume feeds across networks with limited or no return path. It moves named byte streams from a sending system to a receiving system, with configurable bandwidth allocation, optional forward error correction, and optional authenticated encryption. Its companion application adds customer-facing ingestion and file delivery workflows.
Designed for demanding one-way links
- Allocate bandwidth deliberately. Give each traffic class a configured minimum rate, while allowing active workloads to borrow unused capacity up to their ceilings.
- Recover eligible loss without a return path. Optional forward error correction sends parity so the receiver can reconstruct losses within the configured limits. There is no retransmission.
- Use more than one network path. Stripe across comparable links for aggregate capacity, or duplicate traffic across separate path groups for redundancy, at a cost to usable bandwidth.
- Protect and observe the transfer. Optional authenticated encryption and key rotation protect frames when configured. Metrics and a separate operator console show throughput, drops, and host-tuning findings.
How qntm works
Ingest → Send → One-way network → Receive → Deliver
qntm-core runs as separate send-mode and receive-mode processes. The sender reads configured socket sources, shapes traffic, and transmits frames in one direction. The receiver reorders the frames and routes named streams to configured destinations. The core transport keeps transferred data in memory and does not write it to disk.
At the edges, qntm-companion can accept authenticated customer connections or watched files and deliver completed files to SFTP, S3, or local directories. Its delivery spool verifies whole transfers and avoids exposing a partial file at a pickup point. qntm-tui is a separate tool for configuration and monitoring; the transfer daemons operate headlessly.
Where it fits
- One-way feeds into protected environments, including architectures that use a data diode.
- Sustained data movement over high-latency or lossy links where retransmission is unavailable or costly.
- Shared links where workloads need configured bandwidth floors.
- Deployments with comparable network paths that benefit from striping or deliberate duplication.
Architecture note: qntm provides transport for a one-way design. An approved cross-domain solution requires separate policy, filtering, accreditation, and deployment review.
Plan your evaluation
qntm is designed for configured data flows. It does not provide a reverse channel, request/response API, sender-side delivery acknowledgments, adaptive congestion control, or a VPN. Configure rates against the actual link capacity. For file workflows, evaluate qntm-companion alongside qntm-core and define how the receiving application confirms completion.
Tell us about the feed, network, throughput target, and delivery endpoint. We can walk through an architecture and arrange a demonstration or evaluation.