Plan the environment before installation
Plan workstations, network licensing, databases, shared storage, user access, backups and operational support before production deployment. Exact requirements depend on the product, version, license type, data volume and infrastructure selected by your organization.
Select the simplest architecture that meets collaboration, performance, access and governance requirements.
The application, license and working data are used from one managed Windows computer.
Client workstations connect to organization-managed licensing, database and shared-data resources.
Applications and supporting services may be deployed in managed Windows virtual machines or remote-desktop environments, subject to testing.
Local clients may connect to selected remote resources. Latency, database performance, file paths and backup ownership require particular attention.
A technically possible design is not automatically the best production design. Test the actual product, dataset, network path and user workflow before approving a distributed or virtualized rollout.
A network deployment involves more than installing the desktop application.
| Component | Purpose | IT planning questions |
|---|---|---|
| Client workstations | Run the GAEA applications used by staff. | Windows version, hardware, display, permissions, installation and updates |
| License service | Provides concurrent licenses in a network deployment. | Host availability, service account, firewall rules, addressing and recovery |
| Database service | Stores structured project and module data where applicable. | Supported release, capacity, authentication, performance, maintenance and backup |
| Datastore and shared files | Holds documents, images and project-related files where configured. | Paths, permissions, capacity, retention, replication and restore testing |
| User administration | Controls accounts and permitted application actions. | Account approval, privilege assignment, removal and periodic review |
| Backup and monitoring | Protects availability and recoverability. | Scope, frequency, retention, off-site copies, monitoring and recovery objectives |
For the documented GaeaSynergy network-license workflow, clients communicate with the Network License Service using TCP port 3000 and the applicable server name or IP address.
Firewall rules should follow organizational policy and be limited to necessary hosts, networks and profiles. Internal client-to-server communication does not imply Internet exposure.
Verify ports against the current documentation and installed version, especially when defaults have been changed.
Security depends on application configuration and the customer-managed environment working together.
This page is not a compliance attestation, penetration-test report or guarantee that a customer configuration meets a regulatory framework. Request current product-specific information for formal reviews.
Assign ownership explicitly instead of assuming that another party controls it.
| Area | GAEA Technologies | Customer organization |
|---|---|---|
| Installation guidance | Provide applicable documentation and entitled technical support. | Approve the environment, administrator access and production change. |
| Accounts and privileges | Provide available application account and privilege capabilities. | Create, approve, review and remove access under internal policy. |
| Servers and networks | Identify product connectivity and supported configuration needs. | Secure, patch, monitor and maintain operating systems, firewalls, VPNs and hosting. |
| Databases and files | Provide supported workflows and product configuration guidance. | Control permissions, administration, retention, backup and recovery. |
| Updates | Publish applicable software updates and release information. | Evaluate, test, approve, deploy and retain recovery capability. |
| Incident response | Investigate reported product behavior and provide available guidance. | Operate the incident process, preserve evidence and control infrastructure. |
Use a controlled rollout for multi-user, hosted or business-critical environments.
Confirm products, versions, licenses, users, locations, data volumes and integrations.
Document clients, servers, databases, storage, network flows, accounts and backups.
Complete security, infrastructure, procurement and data-governance review.
Test licensing, representative data, performance, permissions, reports and recovery.
Release the approved configuration, migrate data and record the production baseline.
Monitor services, manage access, maintain backups and test upgrades.
Protect every component needed to reconstruct a usable environment.
A successful backup job does not prove that projects, templates, attachments and services can be restored into a usable state.
Define recovery objectives and periodically test the recovery order for database, datastore, licensing and client components.
Common questions from IT administrators and procurement reviewers.
A network license service manages available concurrent licenses. Clients request a license when the application starts and release it when the application closes.
The documented GaeaSynergy network-license workflow uses TCP port 3000. Verify this against the installed version and restrict access to approved network scopes.
Managed Windows virtual machines, hosted databases and hybrid configurations may be possible. Suitability depends on product, licensing, latency, storage and security controls and should be tested.
Do not assume hosting from the license alone. Data location depends on the architecture operated by the customer or an explicitly agreed service arrangement.
The customer should approve and administer access under its policies, using the account and privilege controls available in the installed product version.
Back up applicable databases, datastores, documents, images, templates, libraries, configuration records and information needed to restore application versions and licensing.
Send the questionnaire with product names, versions, intended architecture and due date. Many infrastructure controls require answers from the customer’s IT team.
Review release information, back up affected components, test with representative projects, and release through the organization’s approved change process.
Use current product documentation and request assistance when the intended environment differs from the documented configuration.
Tell GAEA which products, license types, user counts, locations and hosting pattern you are considering. We can help identify product-specific questions for your IT review.
GAEA Technologies develops and distributes geoscience and engineering solutions worldwide. Our solutions have been used for over 30 years by companies and organizations around the world.
© 2026 GAEA Technologies. All Rights Reserved.