> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/enterprise-it-setup/web-application-platform-configuration.md).

# Web Application Platform Configuration

Enterprise configuration for running mods as a web app or embedded frame (IFrame)

{% hint style="info" %}
The Web Application platform is currently only available to Enterprise customers. To receive access, contact your Account Manager.
{% endhint %}

The Web Application platform is a way to deploy PixieBrix mods anywhere a web application can run, as a standalone web page or as an embedded frame (iframe)

## Custom Domain Name

See section "Custom Domain and White-Labelling" under [Custom Branding and Themes](/enterprise-it-setup/custom-branding-and-themes.md)

## Third-Party API Configuration

### Cross-origin resource sharing (CORS)

API requests made from the browser to third-party APIs originate from `app.pixiebrix.com` or your custom domain name. If your API has cross-origin resource sharing (CORS) controls configured, you must allowlist `app.pixiebrix.com` or your [#custom-domain-name](#custom-domain-name "mention")

* [Access-Control-Allow-Origin Header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Allow-Origin)

### OAuth2 Redirect URL

To support OAuth2 integrations, you must add web application platform's URL to the URL redirect allowlist of your OAuth2 provider:

```
https://app.pixiebrix.com/oauth2-callback/
```

If you are using a [#custom-domain-name](#custom-domain-name "mention"), use your custom domain in the redirect URL:

```
https://<your-custom-domain>/oauth2-callback/
```


---

# 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.pixiebrix.com/enterprise-it-setup/web-application-platform-configuration.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.