> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/operation-mode.md). # Cloud App vs. Installed App Understanding the difference between the cloud and installed versions of ENERCALC SEL and where project data is saved. ## What is meant by Cloud App versus Installed App? ENERCALC SEL now exists as both an installed application and as a cloud application. The installed application is software that is located on the user's computer. This is the historical usage method of nearly all software. The cloud application is launched using an Internet link, and it runs within the user's web browser. The cloud app is no different than the installed app that runs on your local computer. ## Where is my project data being saved? When using the cloud application, project data is saved in the cloud. When running the installed application, the user has the option of saving project data as local project files, or in the cloud. This provides the flexibility to work with local project files when an Internet connection is not available, and to work with cloud based files when an Internet connection ***is*** available. In this way the application can be run from anywhere and use the same set of data files for ultimate usability. Cloud based files offer significant benefits: * Data is secure, * Data is continuously backed up, * Data can be shared among other members of the team. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/operation-mode.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.