---
title: "How Does Retrace Work with Containers?"
slug: "how-does-retrace-work-with-containers"
updated: 2023-07-05T13:56:16Z
published: 2023-07-05T13:56:16Z
canonical: "docs.stackify.com/how-does-retrace-work-with-containers"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Does Retrace Work with Containers?

The first step to running Retrace in a containerized environment is to install Retrace as a container on your host. See the following installation guides for containerized installations:

- [Kubernetes Install](https://docs.stackify.com/docs/retrace-kubernetes-install)
- [Docker Install](https://docs.stackify.com/docs/retrace-docker-install)

          Note for Host Hour Billing Plans...

          

Our pricing for containers is connected to the underlying host. You can run as many containers as you want on a single host and pair it with 1 agent instance and it would incur normal hours for only that 1 server.

If you integrate logging with Retrace, you would incur additional lite hours from each container on top of the normal hours.

E.g. if you have **5 containers** on a single host, and **3 containers** are sending logs to Retrace the calculation would be:

- **1 prod hour** for all 5 containers on 1 host + **3 non prod hours (lite hours)** for 3 containers sending logs = 1 prod hour equalling 2 prod hours in total.