> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/apps/about.md).

# About

Build interactive PowerShell Universal web apps using prebuilt cmdlets and components for tables, data grids, onboarding tools, and management interfaces.

Apps are individual websites created with PowerShell Universal. They take advantage of a large set of pre-defined cmdlets for [all kinds of components](/powershell-universal/apps/components.md) and [interactive features](/powershell-universal/apps/interaction.md). You can use apps to create dynamic websites that meet any need you can think of. Some common apps are:

* Disparate Data Grouped into Tables and Data Grids
* End User Onboarding Tools
* UI Tools for System Management without Elevated Credentials

For a full list of real-life examples, [click here](https://forum.devolutions.net/product/powershell-universal).

Apps should be considered an advanced feature and require both knowledge of the PowerShell Universal app cmdlets as well as a decent knowledge of PowerShell itself. With that said, they provide the greatest level of customization for web apps in PowerShell.


---

# 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://docs.devolutions.net/powershell-universal/apps/about.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 `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.