NESTING SOLVER
Data and security
An operating environment suited to your workflow, with clear control over design files.
Choose where your data is processed.
Production files carry design knowledge, part details and planning choices. Nesting Solver offers desktop and server deployments so you can clearly decide where this information is processed. File location, computing environment and access to results depend on the deployment you choose.
Offline: files and computation on your computer.
The desktop version opens part models locally and runs the placement search on the same device. You do not need to upload designs to an external computing service for optimization. Searches can run without internet, supporting workflows on closed networks or where design data stays within the organization.
Saved jobs, placements and shared geometry caches are stored on your computer. These records support resuming jobs and comparing results. Protecting local files also involves the computer’s user account and your organization’s device policies.
Server: controlled access and continuing computation.
The browser is the interface for submitting jobs and reviewing results. Placement computation runs in the selected server environment, not in the browser. Closing your computer or browser does not automatically stop a job already running on the server. Jobs and results are managed within that server’s operating and retention policies.
The application uses account-based access and job authorization. Standard users access their own jobs; broader permissions to view and manage other users’ jobs are assigned separately. This separation helps control who can access files and results within the application.
On-premise deployment and network access.
An on-premise server processes files within the infrastructure selected by the organization. Network access is determined by that organization’s own environment, including private-network or VPN access where appropriate.
Connection protection, server access and system updates are considered together. Safeguards such as HTTPS, network restrictions and permissions are configured within each deployment’s infrastructure. Application-level access control and server-level protections then complement each other.
Records, results and caches.
Placement history, saved results and caches serve different purposes. History supports comparing discovered options. Job records support resuming an unchanged search. Geometry caches preserve reusable preprocessing that can save time in later operations.
Deleting a job and clearing shared caches are different actions. Some desktop cache data can remain after a job is deleted. Server retention, backup and cleanup policies are defined separately for the deployment.
Establish an appropriate operating setup.
Choosing a deployment involves data management as well as computing power. Before setup, consider where files live, which users can access which jobs, how long records are retained and how recovery from backups works. Local and on-premise options are useful considerations for teams handling sensitive designs.
Application permissions control access to part files, while the organization’s network, device and operating policies protect the infrastructure. A setup suited to the workflow supports both continued production planning and controlled data management.
Security and deployment enquiries.
Contact us about desktop use, on-premise server deployment or data-management requirements. We can review options suited to your existing workflow.
alperen@nestingsolver.com