> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/gettingstarted/devops-portal.md).

# DevOps Portal

The **DevOps Portal** is the management interface for WEM Runtimes hosted in Kubernetes-powered Private Cloud environments.

It provides administrators with controlled access to environment-level configuration and operational insights that are not managed from the Modeler. Through the DevOps Portal, you can configure runtime settings, manage deployed applications, handle certificates, inspect logs, and monitor technical aspects of the environment.

The portal is built using the WEM No-Code Platform and communicates with the Runtime through dedicated API service calls. Functionality may expand over time as additional DevOps capabilities are introduced.

The devops portal has the following features: 

* Environment Information
* Application Management
* Manage Certificates
* Database Information
* Logging Information
* User management 

{% hint style="info" %}
Devops settings can also be changed by the modeler, this will override the settings set in the devops portal. Disable the setting, "publish to devops" in the modeler to only manage these settings from the devops portal. 
{% endhint %}


---

# 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.wem.io/platform/gettingstarted/devops-portal.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.