diff --git a/docs/root/install/building.rst b/docs/root/install/building.rst
index 143f236c6b3e..56b13ee1f20c 100644
--- a/docs/root/install/building.rst
+++ b/docs/root/install/building.rst
@@ -68,9 +68,12 @@ tests.
   organizations track and deploy master in production. We encourage you to do the same so that
   issues can be reported as early as possible in the development process.
 
+Packaged Envoy pre-built binaries for a variety of platforms are available via
+`GetEnvoy.io <https://www.getenvoy.io/>`_.
+
 We will consider producing additional binary types depending on community interest in helping with
-CI, packaging, etc. Please open an `issue <https://github.com/envoyproxy/envoy/issues>`_ in GitHub
-if desired.
+CI, packaging, etc. Please open an `issue in GetEnvoy <https://github.com/tetratelabs/getenvoy/issues>`_
+for pre-built binaries for different platforms.
 
 Modifying Envoy
 ---------------
diff --git a/docs/root/start/start.rst b/docs/root/start/start.rst
index 8754d1c291e2..59a02b741b1e 100644
--- a/docs/root/start/start.rst
+++ b/docs/root/start/start.rst
@@ -5,9 +5,8 @@ Getting Started
 
 This section gets you started with a very simple configuration and provides some example configurations.
 
-Envoy does not currently provide separate pre-built binaries, but does provide Docker images. This is
-the fastest way to get started using Envoy. Should you wish to use Envoy outside of a
-Docker container, you will need to :ref:`build it <building>`.
+The fastest way to get started using Envoy is :ref:`installing pre-built binaries <install_binaries>`.
+You can also :ref:`build it <building>` from source.
 
 These examples use the :ref:`v2 Envoy API <envoy_api_reference>`, but use only the static configuration
 feature of the API, which is most useful for simple requirements. For more complex requirements