Your file stays in one place. Your team works it from everywhere.

Why it matters

Most review platforms still operate on a download-and-edit model. Files are sent. Users open them locally. Comments are added in the user's local copy. Comments are sent back. Versions multiply. Security is compromised the moment the file leaves the platform.

This model breaks down on three dimensions:

• Security. Once a file is downloaded, the platform cannot enforce who sees it. Regulated content (PHI, PII, financial confidentials, regulated marketing) needs to stay in a controlled environment. Downloads create a perimeter that the platform cannot defend.
• Concurrency. A 300-page file or a multi-asset campaign cannot be reviewed by twenty people in parallel if each person is downloading their own copy and merging comments after the fact. The merge problem alone breaks the model.
• Performance. Multi-gigabyte files take meaningful time to download. Reviewers wait. If the file is large enough, some reviewers cannot review it from where they are working.

Performant File Streaming was designed to remove all three constraints at once, giving regulated teams a safer model for secure file sharing. The file is processed once and streamed on demand. Reviewers see it instantly, regardless of size. Hundreds of reviewers can collaborate on the same file simultaneously, with their comments and annotations appearing in real time. The file itself never leaves the secure environment.

This is what makes compliance-grade review at scale possible.

The streaming architecture

The architecture has three layers:

1. Process and tile. At upload, the Processing Agent does the heavy work. It RIPs the file (rasterizes it for web display), processes it through the format-appropriate provider (Adobe PDF Library for PDFs, dedicated providers for video, images, HTML5, CAD, and Office formats), and generates tiles at multiple zoom levels using Aproove's proprietary tiling engine. The tiles are what make deep zoom possible. Reviewers can move from page-level to pixel-level without re-downloading or rerendering. The tiles are generated once and reused for every reviewer.

2. Host securely. Processed tiles and the original file are stored on encrypted infrastructure (encryption at rest, tenant isolation, TLS 1.2+ in transit). The original is preserved alongside the tiles for forensic and audit purposes, but the original is not what reviewers interact with. Reviewers interact with the streamed tiles.

3. Stream to the reviewer. When a reviewer opens a proof, the right tiles for the right zoom level are streamed to their browser on demand. Pan, zoom, jump to a page: Aproove streams the relevant tiles in real time. The reviewer's device never holds a complete copy of the file. The streaming is fast because tiles are small and pre-generated; it is secure because each request is authenticated and permissioned.

This is what allows a multi-gigabyte CAD drawing or a 400-page PDF to load instantly in a reviewer's browser, regardless of their bandwidth or device, and regardless of how many other reviewers are doing the same.

Real-time collaboration

Streaming does not just deliver the file. It synchronizes the work happening on it.

Live annotation push. When one reviewer adds a Note, marks a region, highlights text, or applies a Tag, the change is pushed to every other reviewer looking at the same proof in real time. Reviewers see their colleagues' work as it happens. There is no refresh, no merge, no late-arriving comments after the fact.

Project Chat. Every project includes a chat room accessible from the Project Dashboard, the Task Welcome screen, the Review Interface, and the User Dashboard. Reviewers and stakeholders communicate in context, with @mentions creating tasks and notifications. Chat messages are part of the project audit trail, with originals preserved if a message is later edited or deleted.

Task Chat. Specific tasks can carry their own chat rooms, either visible only to task assignees (private) or threaded into the broader Project Chat. This lets specialist conversations (a regulatory escalation, a brand decision discussion) stay scoped to the people who need them, without polluting the main project conversation.

Decision support. When a step requires multiple decision-makers, real-time annotation and chat let those decisions converge quickly. A team voting on a step decision can see each other's notes and chat exchanges as they form their answers. Conflict Manager review sees the full thread when escalation arrives.

The throughput of decisions, especially decisions involving multiple stakeholders or large input pools, depends on this real-time visibility. Streaming makes it possible.

Concurrent reviewers at scale

Because the file is streamed rather than distributed, the number of concurrent reviewers is bounded by infrastructure capacity, not by the model itself. Aproove customers regularly run review programs with hundreds of concurrent reviewers across multiple projects.

Practical implications:

• A campaign asset can be opened simultaneously by legal, brand, regulatory, marketing operations, and external agency reviewers, all viewing the same proof, all seeing each other's work.
• A 300-page document with multiple specialist reviewers can have those reviewers working in parallel, focusing on different sections, with the platform routing each reviewer to their assigned components.
• Decision steps with multi-assignee voting (unanimous, majority, conflict-managed) work because every assignee sees the same source of truth.

The constraint that traditionally limited concurrent review (everyone needed their own copy of the file, then their copies needed to be merged) is removed. Streaming makes concurrency a non-issue.

Component-level streaming and access control

Because the platform streams the file rather than distributing it, the platform controls what each reviewer sees in their stream. This makes component-level permissions enforceable, not just notional.

A few practical patterns:

• Risk-tagged components route to specific reviewers. A page tagged as high-severity regulatory streams to legal and regulatory reviewers; the same page does not appear in the stream for marketing reviewers. Same file, different views, all from the same source.
• Sensitive content gated by role. PHI, PII, or restricted material can be configured to stream only to roles with appropriate clearance. Other reviewers see the file with the sensitive components excluded from their stream.
• Decision-driven visibility. When a workflow decision routes specific components to a specialist, those components are what the specialist receives in their stream. The rest of the file is not part of their view.
• Stage-based access. Components might be visible to certain reviewers at one stage of the workflow and not at another. The streaming layer enforces these state-based gates per reviewer.

This is permission enforcement that holds at the file level. There is no copy of the full file on a reviewer's device that contains content they are not supposed to see. The view is the file.

Deployment choices: Aproove-hosted, self-hosted, on-premise

Performant File Streaming runs in the deployment model that fits your security and operational requirements:

• Aproove-hosted on Microsoft Azure. The default deployment. Aproove runs the platform in dedicated Azure infrastructure, with HIPAA-aligned configuration, ongoing SOC and HIPAA compliance evidence collection, encryption at rest, tenant isolation, and TLS 1.2+ in transit. Suitable for most regulated and enterprise customers.
• Self-hosted in your cloud. For organizations that require full control over their infrastructure, Aproove can be deployed inside your cloud environment, on infrastructure you provision and govern. The platform runs on your network. Data residency, network isolation, and access controls are in your hands.
• On-premise. For environments where cloud is not an option (sovereign environments, air-gapped deployments, regulated industries with strict residency requirements), Aproove can be deployed in your on-premise data center. The streaming architecture works the same way: process, tile, host, stream, all happening within your physical infrastructure.

In every deployment mode, the streaming layer behaves the same. The file is processed once, tiled, stored securely, and streamed to authenticated reviewers on demand. Reviewers do not download. The platform's behavior is consistent; what changes is who owns the infrastructure and where the data resides.

Benefits

• Files load instantly, regardless of size. Multi-gigabyte CAD drawings and 400-page PDFs open in the reviewer's browser at the speed of the first tile. Deep zoom to pixel without waiting.
• Hundreds of concurrent reviewers, one source of truth. Streaming removes the merge problem. Every reviewer sees the same file in real time, with each other's annotations appearing as they happen.
• Real-time collaboration accelerates decisions. Project Chat, Task Chat, live annotation push, and @mention-driven notifications keep multi-stakeholder review moving without external coordination tools.
• Secure file sharing without downloads. The file never leaves the platform. Downloads are not part of the review model. Sensitive content stays in controlled infrastructure.
• Permission enforcement is structural. Component-level access is enforced at the streaming layer. There is no full-file copy on a reviewer's device that contains content they should not see.
• Three deployment models. Aproove-hosted on Azure (HIPAA-aligned), self-hosted in your cloud, or on-premise. The streaming behavior is consistent; the infrastructure ownership is your choice.‍
• One file, many views. Components route to the right reviewers based on tags, permissions, and workflow state. The same file serves marketing, legal, regulatory, brand, and production teams, each seeing what they should.

Who it's for

• Compliance and regulatory teams in industries where downloaded files are a security and audit problem.
• Production and prepress teams working with multi-gigabyte CAD, prepress, or video files that traditional review tools cannot handle.
• Operations leaders running review programs that involve hundreds of stakeholders across legal, brand, regulatory, agency, and production functions.
• IT and security teams evaluating the security model of review platforms against their data residency, access control, and compliance requirements.
• Customers in regulated industries (pharma, healthcare, financial services, government) where deployment flexibility is a procurement requirement.

Under the hood

Performant File Streaming is implemented through Aproove's Processing Agent, tiling engine, and secure delivery layer. The Processing Agent ingests source files, processes them through format-specific providers (Adobe PDF Library for PDFs, dedicated providers for images, video, HTML5, CAD, and Office formats), and generates rendered proofs at multiple resolution tiers (configurable from 120 DPI for fast review up to 768 DPI for high-quality print proofing). The tiling engine produces zoom-level tiles from the rendered proofs, enabling deep-zoom navigation without per-zoom rerender. Tiles and source files are stored on encrypted infrastructure with tenant isolation; transit is TLS 1.2+. The Review Interface streams tiles to authenticated reviewers on demand based on their viewport and zoom level, with permissions enforced per-tile-request to support component-level access control. Real-time collaboration is delivered through push-based channels that synchronize annotations, Notes, Tags, and chat across concurrent reviewers in the same proof. Aproove-hosted deployments run on Microsoft Azure with HIPAA-aligned configuration and ongoing SOC and HIPAA compliance evidence collection; self-hosted and on-premise deployments use the same software stack on infrastructure provisioned by the customer. The audit trail captures every annotation, chat message, and decision event in the project record.