> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/use-cases/for-platform-engineers/standardized-application-delivery-workflows.md). # Standardized Application Delivery Workflows {% hint style="info" %} As a Platform Engineer, Ozone gives you the ability to standardize your CI/CD workflows into standards that any team can consume. DevOps workflows are comprised of security checks, code quality checks, performance tests, regression tests. Combine all these into a single standard and create your own using Ozone's native pipeline and tasks catalog as a template {% endhint %} ### Problems * Platform engineers need to maintain CI/CD standards at scale within an organization. As the software stacks scale with the advent of microservices that use multiple stacks, there is a need to define a set of standard that fits your organization * Platform engineers need to be able to scale these workflows on demand, ideally across clouds and regions for a host of reasons such as costs, cloud availability, compliance * Platform engineers need to be able to offload as much of Day 1 and Day 2 ops to a system that makes it more on-demand for development teams ### Solutions * Ozone provides a set of workflow templates in the form of a task and a pipeline catalog that can be used to define re-usable deployment templates that can be shared across teams * Ozone workflows are on-demand and can run on any kubernetes clusters. As an additional check, Platform engineers can define which clusters are accessible to a team for executing the workflows * Ozone provides pre-deployment automation by making any steps within the CI/CD workflow completely customizable. In addition, workload visibility is enhanced through Ozone for better analysis through the build and deployment process --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ozone.one/ozone-end-user-guide/use-cases/for-platform-engineers/standardized-application-delivery-workflows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.