Ecoscope Desktop stores templates, workflow configurations, and workflow outputs locally on your computer. This allows workflows to run directly on your system without requiring cloud processing.

Most files created by Ecoscope Desktop are stored automatically and managed by the application. Users typically do not need to manually interact with these files, but understanding how data is stored can help when reviewing workflow outputs or managing disk space.

Workflow Templates

Workflow templates added to Ecoscope Desktop are stored locally after they are imported from a repository, catalog, or local folder.

During the initial setup of a template, Ecoscope Desktop downloads the runtime environment and dependencies required to execute workflows made from the workflow template.

This initialization process may download up to approximately 1.7 GB of data, depending on the template. Note that even if you create multiple workflows from a given template, that amount of data stays at that size.

Once installed, the template and its environment remain available for future workflows without requiring additional downloads.

Workflow Results

When a workflow runs successfully, Ecoscope Desktop generates output files that contain the workflow results.

These outputs may include:

• Interactive dashboards (HTML)
• Data files (JSON or other formats)
• Exported datasets produced by download workflows

These files are stored locally so they can be reviewed, shared, or used in other analysis tools.

Workflow results are not encrypted, since they are intended to be accessed directly by users.

Data Source Credentials

Credentials used to connect to external data sources are never stored at rest. 

Sensitive information such as usernames and passwords, service account credentials, and authentication tokens are held in memory only while Ecoscope Desktop is running and are not written to disk.

Disk Usage Considerations

Because workflows run locally, Ecoscope Desktop may use disk space for:

• workflow templates and runtime environments
• generated dashboards and result files
• exported datasets

Over time, workflows that generate large outputs or download datasets may increase the amount of storage used by the application.

Users can manage disk usage by removing unused workflow templates or deleting unneeded workflows. Note that selectively deleting individual workflow output files is not recommended, as this can cause result dashboards to break when they are next loaded.