Keep your files close to the work
We help shape the deployment around your work: one port connected to multiple storage destinations, or separately licensed ports at different sites. A port is one VOTPort installation, with its own storage, access policies, and operating responsibilities. Trade routes connect those installations when a package needs to move between teams.
Start with the path the files already take
Camera originals might arrive from a location, an image sequence might come out of a render farm, and a finished project might need to reach a client before the next shift. VOTPort gives each handoff a controlled route into or out of your facility.
Create incoming requests with project destinations, passwords, expiry, and byte limits. Prepare outgoing deliveries from your library. Use tenant namespaces when teams or clients need separate content and access boundaries.
The result stays useful to the rest of your pipeline: ordinary files and folders, with cryptographic verification and signed receipts attached to the handoff.
Build the repeat work into the system
Have a renderer finish a package in your library, import it from S3, or start the workflow automatically when an incoming upload completes. VOTPort can check the sequence, metadata, and configured media properties, hold it for approval, and distribute verified copies to S3, shared folders, or other VOTPort deployments. Decide whether local release waits for every destination or copies continue in the background. Schedule preparation and set an acceptance deadline so the handoff stays visible after the transfer.
VOTPort includes those automation tools in the port license. Persistent jobs, 15 MCP tools, APIs, and signed webhooks with retries and replay give your technical team practical ways to connect the workflow. Recipient verification and explicit acceptance produce evidence tied to the exact files, ready to feed back into your production system.
Trade routes preserve a signed custody record at each handoff between ports while each site keeps its own permissions and policies. The receiving port can apply its own reception workflow and send the package onward without someone repeating the upload. Built-in Slack, Teams, Google Chat, and Discord connections keep people informed; replayable workflow webhooks connect the systems doing the work.
We can work through custom integration requirements with you. The scope of any integration work is agreed around the systems you actually use.
Use the identity system your team already knows
SSO is included. Connect an OIDC identity provider, map groups to roles, and use SCIM provisioning where appropriate. Tenant controls, quotas, and audit exports help the facility keep access organized as people and projects change.
Occasional senders and recipients can use a controlled browser link without being issued a seat. Your busiest teams can use the native clients for large files and difficult network paths.
Set up the whole route
We work through the deployment with your technical team so the network and storage support the workload from the start.
| Part of the deployment | What we work through |
|---|---|
| Servers and storage | Host capacity, incoming and outgoing roots, mounted-storage requirements, and file retention |
| Network | HTTPS, public addresses, firewalls, and UDP forwarding for native transfers in both directions |
| Identity | OIDC, provisioning, roles, tenant boundaries, and recovery access |
| Integrations | Project checks, S3 import/export, APIs and MCP, signed webhooks, and acceptance tracking |
| Operation | Monitoring, updates, backups, recovery, maintenance, and support responsibilities |
A port license includes the full VOTPort feature set. Infrastructure and operating arrangements are scoped with your deployment; they do not require a speed upgrade or an SSO add-on.