Flowace Whitelisting Requirements

Whitelist Flowace Services


in Antivirus, Firewall, VPN, and Proxy Software


Antivirus, firewall, VPN, and proxy software can interfere with essential Flowace services, leading to tracking failures, missed screenshots, or inaccurate reporting. Whitelisting the hosts, paths, and executables listed below ensures Flowace runs without interruption.


This article is intended primarily for IT administrators configuring company infrastructure. Individuals running Flowace on a personal device should follow the relevant operating system section below.



1. Hosts to Whitelist


Allow the following hosts on the firewall, web proxy, DNS / content filter, and SSL inspection engine. All traffic is outbound HTTPS on port 443/TCP.

Host / EndPoint

Purpose

api.flowace.in

Primary API endpoint. Authentication, activity sync, and agent configuration.

screenshots.flowace.in

Screenshot upload and retrieval.

(tenant).flowace.in

Client tenant URL. Web dashboard, reporting, and administrator access.

production-flowace-reports .s3.ap-south-1.amazonaws.com

Report generation and download.

flowace-resources .s3-ap-southeast-1.amazonaws.com

On-page artifacts. Images and icons served in the dashboard.

de9j6rhbdgsa2.cloudfront.net

CDN for on-page artifacts (images and icons).

s3-ap-southeast-1.amazonaws.com /updates.windows.squirrel/ /updates.windows.squirrel.stealth.generic/

Windows agent builds and updates (Squirrel updater), including the stealth generic build.


Whitelist by host name, not by IP address.

Flowace endpoints are cloud-hosted and the underlying IPs change without notice. Add all hosts above to the SSL/TLS decryption bypass list. The two update paths share a single host: if the proxy cannot match on path, allow s3-ap-southeast-1.amazonaws.com in full.


2. Windows Agent


2.1 Installation Path


All Flowace Windows services install to a single path. Where folder-level exclusions are supported, this one entry covers every executable listed in Section 2.2.


*%LocalAppData%\Flowace*
*Resolves to: C:\Users\AppData\Local\Flowace*


2.2 Services / Executables


Add each of the following executables to antivirus, EDR, and application-control allow lists.


Executable

Function

Applicable To

FlowaceService.exe

Core Windows service. Manages all child processes, authentication, and data sync.

Interactive

FlowaceSSGen.exe

Screenshot generation module.

Interactive

FlowaceRTCHandler.exe

Real-time communication handler for live status and configuration updates.

Interactive

FlowaceApplicationTimer.exe

Application and URL timer. Tracks active window and time spent per application.

Interactive

FlowaceNetworkBandiwidth.exe

Network bandwidth monitor. Measures connectivity and data consumption.

Interactive

NativeMessagingHost.exe

Browser extension bridge for Google Chrome and Microsoft Edge.

Interactive/Silent

FirefoxNativeMessagingHost.exe

Browser extension bridge for Mozilla Firefox.

Interactive/Silent

MoveInstallationDir.exe

Installation utility. Relocates agent files during install, upgrade, and migration.

Interactive

FlowaceActivityTracker.exe

Tracks keyboard & Mouse Activity.

Interactive

WinFApplicationTimer.exe

Application and URL timer. Tracks active window and time spent per application.

Silent

WinFRTCHandler.exe

Real-time communication handler for live status and configuration updates.

Silent

WinFService.exe

Core Windows service. Manages all child processes, authentication, and data sync.

Silent

WinFSSGen.exe

Screenshot generation module.

Silent

WinFActivityTracker.exe

Tracks keyboard & Mouse Activity.

Silent



Best Practices

●Whitelist Flowace services on internal infrastructure (network, proxy, endpoint protection) to guarantee uninterrupted functioning of the Flowace app.
●Monitor antivirus, firewall, VPN, and other security settings on an ongoing basis. Updates to these tools can silently re-block previously whitelisted services.
●If tracking issues persist after whitelisting, check for VPN split-tunneling rules or proxy configurations that may re-route or inspect traffic to the hosts listed in Section 1.


Still Seeing Blocks?

Send the endpoint protection tool name, version, and block log entry to support@flowace.ai.

Updated on: 17/09/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!