SovaSpace by NURSOVA
Home/Help Center/IT administrator guide

Help Center

IT administrator guide

Network endpoints, ports, proxy behavior and deployment requirements for SovaSpace on managed Windows and Android networks.

Network model

SovaSpace initiates outbound connections only. It does not require inbound firewall rules, a VPN, LAN discovery or administrator rights after installation. Normal application traffic uses TLS over TCP 443.

Required destinations

DestinationPurposeContent handling
api.nursova.comAccount, session, device, subscription and sync coordination.No plaintext note or attachment content is designed to be sent.
accounts.google.comGoogle identity sign-in.Google authentication data.
oauth2.googleapis.comOAuth token exchange and renewal.Authorization tokens.
www.googleapis.comGoogle Drive API for encrypted Entries and attachments.Encrypted SovaSpace objects and Drive metadata.
drive.google.com
drive.usercontent.google.com		Google Drive download paths.Encrypted objects and provider metadata.
nursova.comHelp, privacy, terms and support information.Normal website requests.
play.google.comAndroid subscription and store management.Google Play account and billing data.

Android notifications

Firebase Cloud Messaging can use TCP 5228, 5229 and 5230 in addition to 443. If those ports are blocked, core app access can continue, but remote session-change detection or notification delivery may be slower and rely on later polling.

Proxy and TLS inspection

SovaSpace does not currently rely on application certificate pinning. A system proxy or approved TLS inspection configuration can work when the organization’s trusted certificate chain is installed correctly. Inspection infrastructure may observe decrypted network traffic and becomes part of the organization’s security boundary.

Deployment notes

  • Allow outbound DNS and TLS to the required destinations.
  • Permit Google authentication pop-up or system browser flows.
  • Confirm organizational Google Workspace policy allows the requested Drive access.
  • Do not redirect SovaSpace storage to a shared Google account unless that is the organization’s deliberate identity and recovery design.
  • Contact support@nursova.com with the platform, build number and exact blocked destination when troubleshooting.