Bring your team and collaborators.
Move as much data as the work demands.
Use the bandwidth you already pay for.
The files are big. The connection is anyone’s guess.
Camera originals, image sequences, entire project folders: VOTPort is built for the deliveries that keep a facility busy. Native clients use QUIC to move data through packet loss and long round trips, preserving recoverable progress when a connection breaks.
Current browser and desktop clients send small files in parallel, so a frame sequence does not have to move one file at a time. Native clients overlap reading and hashing large source files during preparation, making use of multiple CPU cores without creating a staging copy. Files can arrive directly on a qualified Linux NAS without reserving space for a second copy or waiting for a final copy step.
There is no faster license to buy. Your network and storage set the pace. For an occasional collaborator, a browser link offers a handoff without an installation.
Delivered means verified.
VOT gives the content a cryptographic identity before transfer. The receiver checks incoming ranges against it and publishes the verified result. Changed or incomplete content fails verification.
A signed receipt records each published file’s identity, length, and publication assurance. Recipient verification and explicit acceptance add separate signed statements bound to the exact package. Production can tell whether the files were verified and the handoff was accepted; operations gets evidence it can retain.
Give incoming work a place to land.
Create a request, choose its destination, and send the link. Collaborators can submit files or folders through their browser or a native client. Add passwords, expiry, and byte limits when the project calls for them.
Files arrive directly in your configured storage, including qualified NAS shares, without overwriting existing files. A reception project can check the completed package, hold it for approval, and send verified copies to S3, a shared folder, or another VOTPort. Incoming work can reach the next team without someone watching an upload and moving the files by hand.
Send the project with access you control.
Share files from your library or prepare a new delivery. The recipient gets an expiring link for browser downloads or a verified native receive into a local folder.
Add a password or download limit, follow the delivery activity, and revoke the link if plans change. Your files stay in your infrastructure.
Let the next handoff happen on its own.
Set the project’s requirements once: metadata, complete sequences, media properties, recipient enrollment, and approval. A persistent job carries the package through those checks and scheduled preparation. Choose whether release waits for every destination or your team can use the local delivery while copies continue in the background. Optional malware scanning can hold suspect files back.
Your team can manage deliveries and project rules in Workflows, connect and test S3 storage from the browser, and issue scoped agent access from Automation. The macOS and Windows apps also manage jobs, while the API, JSON CLI, and 15 MCP tools connect your pipeline. Jobs survive restarts, failed work can be retried, and signed webhooks can be replayed. Acceptance deadlines bring overdue handoffs back to your attention. Slack, Teams, Google Chat, and Discord notifications bring transfer updates into the places your team already works. The whole workflow comes with the port license.
Trade routes carry the work forward, with the proof attached.
Connect your studio, finishing facility, and delivery partner with trade routes. A port is one licensed VOTPort installation; each can serve multiple storage destinations. Routes move packages between ports using accelerated QUIC where available, with recoverable progress when a connection breaks. A package can pass to the next team without losing its delivery history. Each receiving port verifies the files and signs its own custody record; forwarding preserves the signed ancestry. Your team can export the evidence instead of reconstructing the handoff from emails and progress screens.
Attach a reception project at the next port to apply that team’s checks, approval, and onward destinations as files arrive. Successful destinations stay complete when another needs a retry. Every port keeps its own access rules, quotas, and project policy. Signed revocation stops further route-managed sharing and forwarding, with acknowledgment from the destination. Copies already downloaded or exported remain outside that recall.
Your identity provider is already invited.
OIDC single sign-on, SCIM provisioning, administrator/viewer/auditor roles, tenant quotas, and audit exports are included. Give your team the access they need and your collaborators a link for the work they are involved in.
One port license covers the full product, without seat fees, transfer-volume charges, or licensed speed tiers.