> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/introduction/introduction-benefits-of-pmo.md).
# Benefits of PMO
## Developer Self-service
With PMO any user, including developers, are able to quickly and easily build Virtual Machine (VM) instances. Platform9 also enables developers to launch multi-tier applications that are composed of multiple VMs with a single click. Once an application has been deployed, PMO will track the usage as part of leases and quota restrictions ensuring that no sinlge user or tenant exceeds their allocated resources, thus greatly simplifying resource management and enabling agility for greater business productivity.
## Orchestration & Application Stacks
Complex multi-tier applications can be quickly deployed and torn down utilizing out of the box orchestration included with PMO. Self-service users and administrators have access to create custom orchestration stacks that can be integrated in development, testing and production to greatly accelerate development cycles and drive consistency in each environment.
## Enhancing VMware vSphere for Developers
With PMO developers no longer need to log into vCenter to build and maintain virtual machines. And VMware administrators no longer need to manually wrangle virtual machine sprawl with countless spreadsheets.
PMO connects directly to vSphere and creates a self-service portal with leases and quota management that enables developers to get what they want, when they need it and removes the need for VMware administrators to manually manage developer virtual machines.
### Create multiple tenants with specific leases & quotas
### Developers can self manage leases & quota consumption
---
# 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.platform9.com/managed-openstack/introduction/introduction-benefits-of-pmo.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.
