System Requirements

Everything You Need
Before Evaluating

Agent specs, browser support, ECM compatibility, network rules, and performance benchmarks — all in one place for enterprise IT evaluation.

Windows Server
Agent OS
8
Production Connectors
Chrome 90+
Browsers
50K+
Docs/Hour Peak
Start Free TrialTalk to Sales
1. AetherFlow Agent (On-Premise)

Agent Server Specs

Runs entirely on your infrastructure. Minimal footprint, outbound-only connections.

Operating System

Windows Server 2016, 2019, or 2022 (64-bit required)

Runtime

.NET Framework 4.8 or higher

RAM

4GB minimum, 8GB recommended for large migrations

Disk

500MB installation + temp space for document processing

Network

HTTPS outbound to AetherFlow cloud (port 443). WebSocket for real-time communication.

Permissions

Service account with read access to source ECM, write to target ECM

2. Web Dashboard (Cloud-Hosted)

Browser & Device Support

No downloads, plugins, or extensions. Works everywhere modern browsers do.

Browsers

  • Chrome 90+
  • Edge 90+
  • Firefox 90+
  • Safari 15+

No Client Software

No plugins or extensions required. Fully responsive on desktop and tablet viewports.

3. Supported ECM Systems

Production Connectors

Bidirectional support — any connector can be source or target.

SystemVersionsConnector Type
Hyland OnBase18+, 20+, 21+On-premise agent
SharePoint OnlineCurrentCloud (Graph API)
SharePoint Server2016, 2019On-premise agent (REST/NTLM)
Square 9 GlobalSearchCurrentOn-premise agent
FileHoldCurrentOn-premise agent
OneDrive for BusinessCurrentCloud (Graph API)
FilesystemAnyOn-premise agent
SQL Server2016+On-premise agent (ODBC)
4. Network & Firewall

Outbound-Only. Proxy-Friendly.

No inbound ports. Agent initiates all connections.

  • Agent → Cloud: HTTPS (443) to app.aetherflow.com, WebSocket upgrade
  • Agent → Source ECM: Varies by connector (SQL ports, CIFS shares, API endpoints)
  • Agent → Target ECM: Same as source
  • No inbound ports required on agent machine
  • HTTP/HTTPS proxy support via environment variables
5. Performance Guidelines

Real-World Throughput

Scales with hardware, network, and workload. No fixed limits.

  • Throughput depends on document size, network bandwidth, ECM API limits
  • Typical: 500-5,000 docs/hour for metadata-heavy migrations
  • Peak: 50,000+ docs/hour for lightweight file copies
  • Recommended: Dedicated network segment for large migrations

Scaling Factors

Agent Hardware: More RAM/CPU = higher concurrency
Network: 1Gbps+ recommended for large volumes
Parallelism: Configurable worker pools per flow
Enterprise Ready

Ready to Test in Your Environment?

Start a free trial. Deploy the agent in minutes and connect your first migration flow.

Start Free TrialContact Engineering