Bring your team and collaborators.
Move as much data as the work demands.
Use the bandwidth you already pay for.
License the port. Stop counting the people.
Bring in another editor, another vendor, or an entire production team. VOTPort has no seat fees, no monthly active-user allowance, and no transfer-volume charges. Your facility can do more work without turning every new collaborator or delivery into a licensing calculation.
VOTPort gives your facility accelerated QUIC transfers, cryptographically verified files, signed recipient acceptance, project controls, SSO, and persistent workflows in every port license. A port is one installation; connect it to several storage destinations or run separately licensed ports across your sites. Take full API and CLI control of your delivery workflow, or put an AI assistant to work with 15 built-in MCP tools. It all runs on your infrastructure, without charging you for another user, another terabyte, or a faster connection.
Their upgrade is our standard.
Signiant requires its highest package for SSO and workflow automation APIs. With VOTPort, both come standard. Connect your identity provider, automate your handoffs, and put the full product to work without upgrading your license. [1]
A faster connection should not need a faster license.
IBM offers Aspera Enterprise subscriptions in 500 Mbps, 1 Gbps, and 10 Gbps tiers. License-based Aspera nodes enforce the licensed bandwidth ceiling. VOTPort has no paid speed tiers: use the capacity your network and storage can deliver. [3, 4]
What comes with the license matters.
With VOTPort, bringing in more people, moving more data, or automating the next handoff does not send you back to the pricing page. See where Signiant Media Shuttle and IBM Aspera Faspex attach allowances, upgrades, and extra setup to the work your facility needs to do.
| What your facility gets | VOTPort | Signiant Media Shuttle | IBM Aspera Faspex |
|---|---|---|---|
| Licensing model | Every port gets the whole product. Licensed per installation, with no seat fees, transfer-volume charges, speed tiers, or feature unlocks. | More active users can mean a bigger bill. Monthly user allowances with overage charges. [2, 12] | Increased costs for more speed. Higher licensed speeds require a higher-tier subscription. [3, 4] |
| Data moved | Send more without paying us more. No per-gigabyte fees or transfer-volume allowance. | Cloud transfers come with an allowance. Overage terms apply beyond it. On-premises transfers are unlimited. [1, 12] | Pay by bandwidth or consumption. Licensed nodes avoid volume charges; consumption plans meter transfers. [4, 5] |
| Transfer speed | Full-speed accelerated QUIC. Huge deliveries, resilient transfers, and resumable progress. No licensed speed cap. | No upcharge for speed. No licensed bandwidth cap. [1, 6] | Extra charges to unlock your full bandwidth. FASP speed on licensed nodes is capped at the bandwidth you purchased. [4] |
| Encryption and integrity | Encrypted transport. Automatic file verification. TLS encrypts and authenticates connections. Incoming files and native downloads are also cryptographically checked before publication. | Standard TLS transport protection. Encrypts and authenticates the connection. [6] | File verification requires an extra step. Whole-file checksum reporting is off by default. You must enable it and compare the received file separately. Transport encryption and packet checks are included. [7] |
| Evidence you keep | Proof of the files. Proof of the handoff. Automatic signed file receipts, recipient verification, and separate explicit acceptance bound to the exact package. Trade routes retain signed custody at each port, preserved ancestry, and exportable audit evidence. | Transfer logs and delivery tracking, including proof-of-delivery reporting. [6, 8] | Build your own verification record. Enable checksum reporting, retain the logs or manifests, and compare the received files. [7] |
| Single sign-on | Included from the start. OIDC, SAML through an OIDC bridge, and SCIM provisioning. | Only in the highest package. SSO requires Enterprise. [1] | SAML sign-in supported. Connect your identity provider. [9] |
| Workflow automation | Full API and CLI workflow control. Persistent jobs, schedules, acceptance deadlines, retries, and replayable webhooks. Automatic workflows after upload, checks and approval, and delivery to S3, shared folders, or connected ports through trade routes. Failed destinations retry without repeating completed copies. | Workflow APIs require Enterprise. Lower packages include management APIs, not the workflow APIs or SDK. [1, 6] | Orchestration lives in a separate application. Orchestrator comes in the Enterprise suite; Faspex supplies APIs. [3, 10] |
| AI assistant setup | Connect it from your desktop app. 15 included MCP tools to prepare jobs, track release, and inspect signed acceptance. Scoped permissions and a ready-to-copy configuration; human approval stays with your team. | Professional Services required for setup. MCP integration is not self-serve. [11] | Separate CLI setup required. Install and configure Aspera CLI, then connect its MCP plugin to your assistant. [13] |
| Infrastructure control | Your facility stays in control. Run it on your servers or cloud. Receive directly onto qualified NAS without reserving space for a second copy or waiting for a final copy step. Your storage, identity provider, and access rules. | The control plane stays with Signiant. You choose the storage; Signiant operates the SaaS layer. [6] | Run it on your infrastructure. Customer-managed on-premises or cloud deployment. [3] |
VOTPort connects to SAML identity providers through an OIDC bridge, such as Keycloak; bridge setup is separate from native OIDC sign-in. VOTPort is licensed per port, meaning one installation; a company can run one port connected to several storage destinations or separate ports at different sites. Infrastructure costs remain with your chosen providers. IBM speed tiers refer to license-based nodes and Aspera Enterprise.
A delivery record worth keeping.
When a delivery is questioned, you need more than a status screen. VOTPort gives you a way to establish what actually arrived. Received content must match its cryptographic identity before publication; missing or altered bytes fail verification.
The signed receipt records that identity, the file’s length, and the publication assurance used. Keep it with the project. Recipient verification and explicit acceptance add two separate signed statements tied to that exact package. Your team can distinguish files that arrived from a handoff the recipient accepted, with evidence it can export for a client or an audit.
Make delivery part of the workflow you already have.
Your render finishes. VOTPort checks the expected sequence, required metadata, and configured media properties, then holds release for the right person’s approval. A job can start on a schedule or when an incoming upload finishes, then distribute verified copies to S3, shared folders, and other VOTPort deployments. You decide whether local release waits for every destination.
Jobs survive restarts, retries preserve the original request, and signed webhooks can be replayed when a downstream system misses an event. Track explicit recipient acceptance against a deadline, preserve signed custody between ports, and put the result into your production system. Workplace notifications keep the team informed in Slack, Teams, Google Chat, or Discord. Your team gets the tools to run the handoff, not another feature tier to negotiate.
Make the comparison on a real deadline.
Bring the camera originals, the many-file sequence, and the remote connection that slows everything down. VOTPort’s native transport is built to keep transfers moving through packet loss and long round trips, with resumable progress when the connection breaks. Browser links keep occasional handoffs simple.
We will work through your storage, access requirements, and automation with you. You get a transfer system built around your facility, with the speed, security, and evidence already included.
Sources and comparison scope
Reviewed September 9, 2026. IBM speed tiers refer to Aspera Enterprise and license-based nodes. Signiant’s transfer tracking and VOTPort’s portable signed file receipts are described in their respective product documentation.
- Signiant pricing and packaging. Lists SSO and workflow automation APIs in the highest package, Enterprise.
- Signiant active-user licensing. Active users are a floating usage measure, not named seats.
- IBM Aspera Enterprise datasheet. Lists Faspex in the Enterprise suite and subscription bandwidth tiers of 500 Mbps, 1 Gbps, and 10 Gbps.
- IBM Aspera node types and licensed bandwidth.
- IBM transfer-volume billing.
- Signiant Media Shuttle technical white paper.
- IBM Aspera checksum reporting. The documented HSTS/HSTE checksum-reporting workflow is configurable and disabled by default; the destination compares its own checksum with the source result.
- Signiant reliability and activity reporting.
- IBM SAML configuration in Faspex 5.
- IBM Faspex 5 REST API architecture.
- Signiant MCP Server availability and integration. The August 2026 announcement describes MCP integration through Professional Services.
- Signiant current usage and overage definitions. Defines active users, cloud data, and overages against the limits in the ordering document.
- IBM Aspera CLI 4.27.0 MCP support. Includes an MCP plugin for Aspera CLI commands, including Faspex, using configured commands and presets.
Native recipients automatically queue signed verification after local publication; browser recipients select and hash their saved files. Acceptance is always explicit. Optional media and malware checks require separately installed checker software. VOTPort receipts attest to the signing deployment’s recorded publication result. Checking a file against its receipt establishes matching content; the commit profile describes storage assurance. See verification and storage guarantees for details. Direct NAS receiving requires a qualified Linux SMB3 or NFSv4 mount and administrator-confirmed storage guarantees; see NAS setup. Native QUIC acceleration requires a compatible client and a reachable UDP endpoint. Network and storage capacity determine achievable throughput.