> For the complete documentation index, see [llms.txt](https://docs.kostacloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kostacloud.com/quick-start-guide/1.0-kostacloud-user-interfaces.md).

# 1.0 KostaCLOUD User Interfaces

Overview of KostaCLOUD User Interface

Welcome to KostaCLOUD Docs!

<figure><img src="https://2927895027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvzB1GHTV5xshI62EhkCW%2Fuploads%2FBEwdc09EtxUHA6LL2Z0d%2Fimage.png?alt=media&amp;token=f5b9826b-34b3-48fd-9ff3-70631c0394a5" alt="" width="563"><figcaption><p>Example Michelson Interferometer with labels</p></figcaption></figure>

We are quite excited that you are here and now reading our documentation. KostaCLOUD has been developed with you, the user, in mind to ensure a smooth experience in developing optical designs.

First, we have a few things to discuss regarding our two different, interconnected User Interfaces (UIs):

1. **CLOUD Portal**: This UI is dedicated to Project Management. It helps you organize, track, and manage all your optical design projects efficiently. With the CLOUD Portal, you can collaborate with your team, set permissions, and ensure your projects stay on track.
2. **KostaCLOUD Optical Design Software (ODS)**: This UI is focused on Simulation and Engineering Systems. It provides robust tools and features for simulating optical designs and engineering complex systems. KostaCLOUD ODS is designed to help you streamline your workflow, from initial design concepts to final simulations.

By integrating these two UIs, we aim to provide a comprehensive platform that supports every aspect of your optical design process. Explore the documentation to learn more about how to make the most of KostaCLOUD ODS and CLOUD Portal.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kostacloud.com/quick-start-guide/1.0-kostacloud-user-interfaces.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.