# Getting Overcharged Using Docker with WSE

**URL:** https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932
**Category:** Wowza Streaming Engine
**Created:** [May 16, 2016, 3:53pm UTC](https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932 "2016-05-16T15:53:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Matt\_Dev](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Matt\_Dev](https://community.wowza.com/u/Matt_Dev)
#### Post date: [May 16, 2016, 3:53pm UTC](https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932/1 "2016-05-16T15:53:28Z")

</div>

We are using Wowza Streaming Engine on Google Cloud Compute Engine in conjunction with Docker: [https://cloud.google.com/compute/docs/containers/container\_vms](https://cloud.google.com/compute/docs/containers/container_vms).

We set up a really nice system to build and deploy new Wowza code using Docker and soon realized that Wowza licensing does not work well in this system. When a new version is rolled out a fresh new set of instances are created and we point our users to this new cluster. As you probably already know, WSE contacts Wowza Corporate to let them know a new server is running. This action charges your account for a new license for a month.

This system of creating a new set of instances is typical of a cloud Docker service.

**So every time we push code a new Docker container is built and we are charged a new month of billing for that instance.** This seems unreasonably inflexible to me.

Is there anyone else out there that is using WSE with Docker in a similar manner that has worked around this problem?

---

<div class="post-metadata">

### Author: ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)
#### Post date: [May 20, 2016, 6:08am UTC](https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932/2 "2016-05-20T06:08:14Z")

</div>

If you have not done so already, you may want to [raise a ticket with support](https://www.wowza.com/support/open-ticket)and get their thoughts on this issue.

Best,

Salvadore

---

<div class="post-metadata">

### Author: ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)
#### Post date: [May 27, 2016, 10:00am UTC](https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932/3 "2016-05-27T10:00:52Z")

</div>

Thank you for the update. Glad you were able to get this issue resolved.

Regards,

Salvadore

---

<div class="post-metadata">

### Author: ![Matt\_Dev](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Matt\_Dev](https://community.wowza.com/u/Matt_Dev)
#### Post date: [May 27, 2016, 10:58am UTC](https://community.wowza.com/t/getting-overcharged-using-docker-with-wse/46932/4 "2016-05-27T10:58:58Z")

</div>

Thanks! Yes I opened a ticket and they refunded the overcharging. They also explained the licensing structure; how it tracks current installs etc. I’ve never used a piece of software charges your account when you launch an instance before. I was also made aware of the developer license: [https://www.wowza.com/media-server/developers/license](https://www.wowza.com/media-server/developers/license).
