Build nodes
Search or filter the tool palette; on mobile, jump among Projects, Tools, Canvas, and Inspector before connecting ports with visual wires.
ByteQuant Workstation arranges tools as nodes, passes output to connected input, encrypts projects on-device with AES-GCM, and shares recipes without a database.
Core tool behavior remains unchanged. Workstation coordinates discovery, layout, handoff, and local persistence; every tool run still requires user action.
Search or filter the tool palette; on mobile, jump among Projects, Tools, Canvas, and Inspector before connecting ports with visual wires.
Inspect confidence, selection reasons, and steps before adding a local plan to the canvas.
Projects and inputs stay in an IndexedDB vault with no external database.
Use a 10-minute P2P code, compare the mutual safety code, and enable live sharing separately.
ByteQuant Workstation is loading locally…
ByteQuant Workstation arranges tools as nodes, passes output to connected input, encrypts projects on-device with AES-GCM, and shares recipes without a database.
Read the privacy policy →P2P codes expire after 10 minutes; live sharing stays locked until people compare the safety code through another channel.
Some NAT and firewall combinations cannot connect outside the same local network. ByteQuant never hides that with a server fallback.
URL recipes exclude inputs by default and always exclude output. Including input requires an explicit user choice.
IndexedDB records use AES-GCM at rest; this cannot guarantee safety on a compromised device or against malicious same-origin code.
Core tool behavior remains unchanged. Workstation coordinates discovery, layout, handoff, and local persistence; every tool run still requires user action.
No. The canvas uses lightweight HTML/SVG and Pointer Events, adding no third-party dependency.
No. It helps compare that both DTLS fingerprints belong to the same session; it does not prove a person's identity. Live sharing stays locked until the code is compared through another channel.
No. Encrypted records stay only in this browser's IndexedDB and never leave automatically.
No. It shows plan confidence and selection reasons; file selection, execution, downloads, and result acceptance require user action.