> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/integrating/integrating-value-stream-delivery.md).
# Integrating with pipelines
Akamas can integrate virtually with any pipeline tools to support the ability to optimize systems as part of a Continuous Integration / Continuous Delivery (CI/CD) process.
When integrated into a CI/CD process, Akamas optimization ensures that new releases don't cause incidents due to misconfigured parameters pushed to production without proper review and tuning.
By integrating Akamas into the CI/CD pipeline, you ensure the new release not only passes functional and security tests but also that:
* performance regressions in key performance indicators (or SLOs) such as service response time or resource consumption are avoided;
Reactive optimization: in-the-pipe remediation (optimization task is triggered by quality gate)
* configuration settings are properly tailored for the new release, thus avoiding configuration bottlenecks (e.g. wrong JVM settings or smaller Kubernetes pod resources for the new release) and decreasing the risk of performance or availability incidents.
Proactive optimization in-the-pipe
---
# 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.akamas.io/akamas-docs/integrating/integrating-value-stream-delivery.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.