# Work on this is now being tracked over at https://gitlab.com/groups/gitlab-org/-/epics/2960 <details> <summary>Original epic description</summary> ## Overview GitLab plans to go public on 18 November 2020. To hit that goal, we need to get more efficient at our go-to-market model. See [efficiency improvements meetings agenda](https://docs.google.com/document/d/10zaXBXkX31wfc0DUsRb5mzFswe7nxUNCthUggwGQvsc/edit#) for more details. One way to do this is to reduce costs incurred when selling our product. This include pre-sales and sales time incurred answering technical questions and support time incurred assisting customers with high-availability and scaling solutions. Additional context from `@dstanley`: > My take-away from this conversation was that we need to continue with the efforts we already identified, namely to offer customers prescribed installation scenarios for some basic configurations from single-node to multi-node, even including HA and GEO. The best result in my mind would be to make it self-serve as much as possible. Something like we gather some basic data: number of users, repository data size, preferred installation (GCP, AWS, K8s, etc), HA, GEO, and we hand them something preconfigured and easy to install, based on the reference architectures we've developed. Link: https://gitlab.com/gitlab-com/www-gitlab-com/issues/6700#note_298389291 Additional context available in [Scaling and Availability Documentation meeting minutes](https://docs.google.com/document/d/1XatsGYGepUx4l6Jpfx3b3XCKHn3vgJiI_A4wNNVp_mc/edit#heading=h.954v91mukl7r). GitLab Support's role in these efforts is to use the knowledge gained from interacting with our customers and supporting our customer's infrastructure to enhance these documents such that internal (SALs, SAs, etc.) and external customers are able to self-serve for most queries, reducing support case load and increasing efficiency for the sales organisation. ## Deliverables * [AWS HA documentation](https://gitlab.com/groups/gitlab-org/-/epics/912) (epic) `@collen` * [Better separation of scaling and HA concerns](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28179) `@weimeng` ## Notes * These efforts may also dovetail with efforts in the wider GitLab community to improve HA documentation. For those, please see: https://gitlab.com/groups/gitlab-org/-/epics/151 * If you have a Geo or HA related documentation issue or MR that lives in the `gitlab-org` group, for now please add it to this tracking issue: https://gitlab.com/gitlab-com/support/support-team-meta/-/issues/2202 * This may be an interim epic as it seems that docs issues should naturally live in the `gitlab-org/gitlab` project rather than in the `gitlab-com` group. For more see this comment in the parent epic: https://gitlab.com/groups/gitlab-com/support/-/epics/52#note_307647862 </details>