> 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/wemmodeler/wem-runtime/live.md). # Live The WEM Live Runtime Environment - your Application in Production The WEM Live Runtime is the Production Environment for your application. In the Publish feature you can activate both Staging and Live in one go. All settings and features in the Modeler are published first to Staging and updated in Staging Environment, and then to Live and updated in the Live Environment. Publishing is needed when changes are made in the Modeler that need to be implemented in Live Runtime. You want to publish only the finished and tested updates to this environment to make sure you keep a working application exposed to your users. ### Hostnames The default URL for the live environment is https\://\[projectname].live.wem.io. and can be changed in the portal settings. \ More about changing hostnames can be found here: [Portal Settings](/platform/wemmodeler/project-settings/portal-settings.md#manage-hostnames). ### Database Every environment has its own database. When publishing a project to a new environment you publish the data structure not its content. This is necessary to keep the right data in your live environment. When your storage strategy has all portals share the same database you still have a different database for staging and for live used by both portals. More about this here: [Project Configuration](/platform/wemmodeler/project-settings/project-configuration.md#storage-strategy). ### License Before you publish your project to the live environment you need a license. This is a license from WEM giving you permission to publish to live. You can find out more about licenses [here](https://wem.io/wem-licensing-program/). --- # 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/wemmodeler/wem-runtime/live.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.