Skip to content
finwave Docs

Network Requirements

In this guide you will learn:

  • What network endpoints the desktop client connects to
  • What firewall rules are required
  • That the client sends no telemetry or analytics data

Single API domain

Section titled “Single API domain”

The FinLaunch client communicates with exactly one network endpoint: your configured finwave API server. There are no other outbound connections. The client does not contact:

  • Telemetry or analytics services
  • Third-party APIs or CDNs
  • Crash reporting endpoints

No telemetry

Section titled “No telemetry”

The desktop client collects and transmits no telemetry, analytics, usage metrics, or crash reports. All data the client sends goes to your finwave API server and consists exclusively of API requests for authentication and data operations.

There is no opt-in or opt-out telemetry toggle because there is no telemetry system.

Transport security

Section titled “Transport security”

All communication between the desktop client and the finwave API uses HTTPS. The client does not fall back to unencrypted HTTP.

Authentication

Section titled “Authentication”

The client authenticates using JWT tokens. The sign-in flow is a standard credentials form within the application. The token is refreshed automatically when it expires.

Firewall rules

Section titled “Firewall rules”

If you need to configure your network to allow the desktop client, here are the requirements:

DirectionProtocolPortDestination
OutboundHTTPS443Your finwave API domain

No inbound rules are required. The client does not listen on any ports or accept incoming connections.

Discovery works offline

Section titled “Discovery works offline”

Directory scanning, metadata extraction, and manifest editing all run locally. You only need a network connection for signing in and for future features like onboarding and synchronization.

Section titled “Related”