# Best way to package & deploy Kibana?

**URL:** <https://discuss.elastic.co/t/best-way-to-package-deploy-kibana/45775>\
**Category:** Kibana\
**Created:** [March 30, 2016, 10:00am UTC](https://discuss.elastic.co/t/best-way-to-package-deploy-kibana/45775 "2016-03-30T10:00:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![motty.green](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@motty.green](https://discuss.elastic.co/u/motty.green)\
**Post date:** [March 30, 2016, 10:00am UTC](https://discuss.elastic.co/t/best-way-to-package-deploy-kibana/45775/1 "2016-03-30T10:00:49Z")

</div>

Hi All,

I have a running Kibana application that i would like to deploy to customer with my own setup.

What are the best practice ways to package & deploy Kibana?

Thanks

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [March 30, 2016, 4:51pm UTC](https://discuss.elastic.co/t/best-way-to-package-deploy-kibana/45775/2 "2016-03-30T16:51:29Z")

</div>

Kibana is really just packaged as an archive. You should be able to archive the entire install directory and ship it to another computer without any issue (assuming they use the same OS/architecture as you).

For more detailed descriptions of how the build process works I suggest checking out the source of the grunt `build` command [https://github.com/elastic/kibana/tree/master/tasks/build](https://github.com/elastic/kibana/tree/master/tasks/build)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:57pm UTC](https://discuss.elastic.co/t/best-way-to-package-deploy-kibana/45775/3 "2017-07-06T13:57:24Z")

</div>