Box Relay

Name: Box Relay
Brand: Box
Rating: 4 (11 reviews)

Box Relay is an integrated workflow capability within the Box Intelligent Content Management platform that enables business users to create and run visual, no-code workflows to orchestrate tasks, approvals, notifications, metadata-driven routing, and sequential document workflows (form submission, document generation, signature) as part of Box-stored content processes.

Est 2005|Valuation $5.2B|Raised $1.6B

LinkedIn 216K|Website|Web traffic 41.3M|FTEs 2,912|HQ Redwood City, California, US

MarketsWorkflow Automation

01Competitive Landscape

Narrative analysis

Where Box Relay is likely effective: 1. Content-centered automation: When a process is primarily about review, approval, classification, and storage of files in Box, Relay's integration offers operational alignment. 2. Compliance and audit alignment: Relay’s workflow history and ability to trigger governance outcomes (when combined with Box governance modules) are operational advantages in environments already standardized on Box. Where competitors often provide broader capability: 1. Cross-system breadth: Platforms like Power Automate offer a larger connector set, RPA, and broader cross-application orchestration. 2. Community and troubleshooting depth: Larger automation ecosystems tend to have more active community support and a broader set of shared solutions. 3. Advanced orchestration and application building: Dedicated workflow or low-code platforms can provide more extensive orchestration primitives and app-building features when workflows are not primarily document-centric.

Market and press coverage signals

Press coverage and analyst commentary describe product updates that reoriented Relay toward enterprise end users and tighter integration with the Box ecosystem.
Some opinion pieces and vendor-aligned analyses characterize Relay as a strategic capability within Box’s product set; such pieces should be treated as commentary rather than independent validation.

	Box Relay (within Box)	Microsoft Power Automate	Kissflow (workflow/low-code)
Starting Price	Not consistently published as a standalone SKU; often bundled in plans. Enterprise-tier offerings require sales engagement.	Premium: published entry-level pricing available for per-user and per-flow models; RPA and process licensing offered.	Published commercial entry points for entry-level packages; higher tiers offered for enterprise-scale usage.
Most suitable for	Content-centric approvals and routing where files are stored in Box and auditability tied to Box permissions.	Broad cross-application automation across Microsoft and third-party systems; includes RPA options.	Organizations seeking a generalized low-code workflow and app-building environment.
Key Strength	Integration with Box security/governance and audit mechanisms; template-driven workflow creation and metadata-driven routing.	Wide connector ecosystem and extensibility; RPA and extensive community resources.	Packaged low-code app and workflow capabilities aimed at multi-department use.
Key Weakness	Less compelling for complex cross-system orchestration relative to dedicated automation/iPaaS platforms; fewer public peer reviews.	Licensing complexity and potential governance management overhead at scale.	Implementation scope and cost may be higher than integrated content-repository workflows for some use cases.

01Competitive Landscape

Narrative analysis

Where Box Relay is likely effective:

Content-centered automation: When a process is primarily about review, approval, classification, and storage of files in Box, Relay's integration offers operational alignment.
Compliance and audit alignment: Relay’s workflow history and ability to trigger governance outcomes (when combined with Box governance modules) are operational advantages in environments already standardized on Box.

Where competitors often provide broader capability:

Cross-system breadth: Platforms like Power Automate offer a larger connector set, RPA, and broader cross-application orchestration.
Community and troubleshooting depth: Larger automation ecosystems tend to have more active community support and a broader set of shared solutions.
Advanced orchestration and application building: Dedicated workflow or low-code platforms can provide more extensive orchestration primitives and app-building features when workflows are not primarily document-centric.

Market and press coverage signals

Press coverage and analyst commentary describe product updates that reoriented Relay toward enterprise end users and tighter integration with the Box ecosystem.
Some opinion pieces and vendor-aligned analyses characterize Relay as a strategic capability within Box’s product set; such pieces should be treated as commentary rather than independent validation.

	Box Relay (within Box)	Microsoft Power Automate	Kissflow (workflow/low-code)
Starting Price	Not consistently published as a standalone SKU; often bundled in plans. Enterprise-tier offerings require sales engagement.	Premium: published entry-level pricing available for per-user and per-flow models; RPA and process licensing offered.	Published commercial entry points for entry-level packages; higher tiers offered for enterprise-scale usage.
Most suitable for	Content-centric approvals and routing where files are stored in Box and auditability tied to Box permissions.	Broad cross-application automation across Microsoft and third-party systems; includes RPA options.	Organizations seeking a generalized low-code workflow and app-building environment.
Key Strength	Integration with Box security/governance and audit mechanisms; template-driven workflow creation and metadata-driven routing.	Wide connector ecosystem and extensibility; RPA and extensive community resources.	Packaged low-code app and workflow capabilities aimed at multi-department use.
Key Weakness	Less compelling for complex cross-system orchestration relative to dedicated automation/iPaaS platforms; fewer public peer reviews.	Licensing complexity and potential governance management overhead at scale.	Implementation scope and cost may be higher than integrated content-repository workflows for some use cases.