> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/technical-overview/deployment-guide.md).

# Deployment Guide

SeaLights empowers your team to achieve optimal test coverage and deliver high-quality software with confidence. Here's a breakdown of the key deployment steps:

#### **1. Prepare the Environment**

* Ensure your application build is ready for SeaLights integration.
* Verify availability of tests to run against your application.
* Confirm connectivity for SeaLights agents on all target machines.

#### **2. Configure Build Scanner**

* Generate a SeaLights token.
* Install and configure agents and plugins on participating machines.
* Scan your application build to generate code coverage data.

#### **3. Integrate with Your Workflow**

* Choose to integrate SeaLights with your CI/CD pipeline or a non-CI environment.
* Provide essential application and environment details.
* Configure user types and assign permissions for smooth integration.

#### **4. Add Tests**

* Install test listener(s) on relevant machines.
* Run your intended tests to capture coverage data.

***

#### **Additional Notes**

* For each step, consult SeaLights documentation or seek support for tailored guidance.
* Remember, these steps offer a general overview, and adjustments might be necessary for your specific environment and needs.

{% hint style="info" %}
For further details and instructions, contact your SeaLights Customer Success Manager. 
{% 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.sealights.io/knowledgebase/guides/quality-improvement/technical-overview/deployment-guide.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.