> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/platform/platform-services/connector/deployment.md).

# Deployment

Runtime roles of the Connector image, how they scale, what the connector depends on, and how each role is monitored.

The connector ships as a single image and runs in one of several roles, chosen at start.

| Role          | Runs                                                 |
| ------------- | ---------------------------------------------------- |
| API           | The Service API and the endpoints the Admin UI uses. |
| Fetch worker  | Reads from sources.                                  |
| Push worker   | Sends signed batches to the registry.                |
| Job scheduler | Starts both workers at their intervals.              |

## Scaling

A production deployment runs the API, the two workers, and the scheduler as separate workloads. Both worker roles scale horizontally by running more instances, and they scale independently, since the pressure on one has nothing to do with the pressure on the other. Small environments can combine the workers and the scheduler in a single workload, at the cost of having to restart them together.

## Dependencies

The connector depends on:

* a relational database for its own data
* a broker for the task queue
* network access to the registry Partner API

## Health checks

The API role exposes liveness and readiness endpoints for health checks. The worker and scheduler roles serve no HTTP traffic and are monitored through process health, logs, and queue depth.


---

# 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.openg2p.org/platform/platform-services/connector/deployment.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.