Add GitLab.com strategy

Why is this change being made?

Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

This MR adds a direction page for gitlab.com, where we will host the gitlab.com strategy that cascades down to and aligns with other groups direction in SaaS Platforms

Preview link - https://dotcom-strategy.about.gitlab-review.app/direction/saas-platforms/dotcom/

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Init Draft

---

source/direction/saas-platforms/dotcom/index.html.md

@@ -10,21 +10,32 @@ canonical_path: "/direction/saas-platforms/dotcom/"
 ## Overview
-Our multi-tenant SaaS platform, GitLab.com, provides the easiest and quickest way to adopt GitLab and the lowest overall total cost of ownership. GitLab.com should be the default for all customer profiles.
+Our multi-tenant SaaS platform, GitLab.com, provides the easiest and quickest way to adopt GitLab and the lowest overall total cost of ownership. GitLab.com should be the default for most customers.
 Our SaaS offerings make up an [increasing percentage of revenue](https://ir.gitlab.com/financials/quarterly-results/default.aspx) and we see further growth opportunities because of the benefits of SaaS for our customers. 
+## Vision
+
+In the long term, GitLab.com will be the default choice for most customers when selecting a DevSecOps platform to power their business. 
+GitLab.com's best in class availability, regional offerings and industry leading value will lead customers to choose .com over competitors and other deployment options like Self Managed GitLab. 
+We will leverage vertical efficiencies driven by shared and consolidated tool-sets to bring the efficiencies of .com to all product lines (.com, Dedicated, Self Managed).
+
+Customers with strict compliance and single tenant needs will continue to choose GitLab Dedicated for its unique value proposition.
+GitLab.com will be the default option for customers that want a industry leading SaaS solution for a DevSecOps Platform that meets strict availability and disaster recovery targets.
+As more of these needs are met by GitLab.com, we expect that both new and existing customers will choose GitLab.com for it's consistent performance and low total cost of operation.
+Over time, this will mean that more customers choose GitLab.com over self-managed.
+
 ## Challenges
 <!-- Optional section. What are our constraints? (team size, product maturity, lack of brand, GTM challenges, etc). What are our market/competitive challenges? -->
 ### High Operational Load
-Gitlab.com teams are responsible for the continued operations of the systems that are essential to deliver our multi tenant platform. 
+GitLab.com teams are responsible for the continued operations of the systems that are essential to deliver our multi tenant platform. 
 Onboarding, operating, and maintaining these systems have a high cognitive and operational load. 
 As a consequence, project work that could evolve our deployment capabilities and unlock new business opportunities can be deprioritised over “keep the lights on work” which prevents/mitigates user impact.
 Additionally, GitLab.com is operating at the largest edge of what GitLab handles as a product.
-This can reveal subtle, but significant issues that most customers operating GitLab will never experience, but create a large demand on the teams that support GitLab.com.
+This can reveal subtle, but significant issues that most customers operating GitLab will never experience, but create a large demand on the teams that support GitLab.com. The size of the customer base also comes with the varied ways GitLab.com is used, which not only shows up in subtle differences in how the product behaves, but also in how the users interact with the platform.
 ### Ownership of a Shared Platform
@@ -33,6 +44,8 @@ This can be great for the development of features, categories and stages, but ca
 Since stage teams are empowered to make the changes they need and GitLab operates with a bias for action, stage teams may decide that a shared implementation does not fit their requirements and end up building their own. 
 This can lead to redundancy, the inability to share and re-use code and ultimately increases the tech debt of GitLab. It is therefore important to balance the overall velocity and scalability of GitLab with individual stage team's desire to ship value to our customers.
+We are also working to match some parts of the platform that are currently unowned to relevant teams and groups.
+
 ### Staffing & Perception
 Infrastructure teams are typically staffed very lean as a consequence of being understood as a "cost centre" for the business. 
@@ -43,59 +56,64 @@ We are already starting to change the perception of SaaS Platforms into a revenu
 <!-- Where will the product be in 3 years? How will the customer's life/workflow be different in 3 years as a result of our product? -->
-GitLab.com is our multi-tenant SaaS platform, where we are able to offer the most value to the widest set of customers. 
-Whether large enterprises with many thousands of users or small teams solving a specific problem, Gitlab.com represents the solution with the lowest total cost of ownership (TCO) with the most up to date features and fixes. 
-This should make it the most attractive platform for most customers, with other platforms like GitLab Dedicated avaialble for our customers with strict compliance needs or a desire for Dedicated, single tenant GitLab.
+GitLab.com is our multi-tenant SaaS platform, and it should be the default for the widest set of customers because it offers the most value and lowest total cost of ownership (TCO).
+Whether large enterprises with many thousands of users or small teams solving a specific problem, GitLab.com represents the solution with the lowest TCO with the most up to date functionality. 
+This should make it the most attractive platform for most customers, with other platforms like GitLab Dedicated available for our customers with different (strict internal) compliance needs or a desire for Dedicated, single tenant GitLab.
 ### Increase Platform Availability & Reliability to Best in Class
-GitLab currently has an availability target (SLO) of two 9s (99.80%). 
+GitLab currently has no publicly stated SLA. 
 However, based on [3 years of historical data](https://handbook.gitlab.com/handbook/engineering/monitoring/#historical-service-level-availability) from August 2021 to August 2024, we achieve an average of three 9s (99.94%) in our availability SLI. 
-Three 9s is the high end of availability targets set for complex SaaS applications across the industry including applications like GitHub. 
-In order to win against GitHub in the long term, we need to increase our availability to be best in class across the industry. 
+Three 9s is the high end of availability targets set for complex SaaS applications across the industry. 
+In order to win in the long term, we need to increase our availability to be best in class across the industry. 
 Best in class means putting in place an SLO of four 9s as a clear differentiator. 
 This will require a shared effort between many groups within SaaS platforms and some foundational investments and re-architecture of existing systems.
 ### Improve the Quality of our Product Development Practice through Stewardship
-As stewards of GitLab.com, Delivery, Scalability & Production Engineering have a responsibility to ensure that GitLab.com remains operational and reliable every minute of every day. 
-Shifting more things left in the software development lifecycle (SDLC) is commonly accepted practice in software development as the most efficient way to deliver higher quality production systems.
+[Stewardship](https://www.merriam-webster.com/dictionary/stewardship) is defined as "the conducting, supervising, or managing of something" and in many contexts is extended to "the careful and responsible management of something entrusted to one's care".
+In this context SaaS Platforms team members are stewards of GitLab.com. 
+Delivery, Scalability & Production Engineering have a responsibility to ensure that GitLab.com remains operational and reliable every minute of every day. 
 Globally improving our product and software development practice will result in a higher quality product, with fewer errors and incidents. 
 That will enable teams to be more efficient with their time and bias work toward preventative measures rather than reactive measures post incident. 
 In order to do this, we essentially have 2 levers:
-- Manual engagement and approval with all teams building features for Gitlab - Non Scalable
-- Build tools and frameworks to make the right thing the easy thing to do - Scalable
-In FY 25, much of our activity as stewards requires ICs to engage with teams and onboard onto a problem in order to drive towards an optimal outcome.
+- Manual engagement and approval with all teams building features for Gitlab
+- Build tools and frameworks to make the right thing the easy thing to do
+In FY25, much of our activity as stewards requires ICs to engage with teams and onboard onto a problem in order to drive towards an optimal outcome.
 This has two major drawbacks, the first of which is that this process is slow and places a high burden on all team members involved to build context and understanding. 
 The second is that, since this process is not scalable, many items that should have had review from our stewards slip through and eventually impact customers and in some cases impact customers the same way as previous incidents ([INC-18003](https://gitlab.com/gitlab-com/Product/-/issues/13406#note_1936034718), [INC-18548](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18548)).
-In order to reduce the number and impact and increase the quality of our product offerings at the same time, we have to increase the level of investment in shared tools that make it easy for teams at GitLab to build quality in from the first iteration. 
-Since taking on full responsibility for the operations of GitLab's SaaS Platforms, SaaS Platforms has gained full accountability for much of GitLab's infrastructure including provisioning, deploying, operating, logging, metrics, observability, maintenance and disaster recovery. 
+To drive progress in this area, we will:
+- Shift things left
+- Invest in best practice tools and frameworks
+- Create Education programs based on paved roads
+- Drive cultural change & increase ownership on groups
+- Raise the bar for features to hit GA
+
 Many of theses domains, such as logging and rate limiting, require tight integration and collaboration with teams developing GitLab features. 
-For example rate limits are easy to implement as a feature is introduced, but become exponentially harder to introduce as a feature gains adoption.
+For example, rate limits are simpler to implement during feature development, but become exponentially harder to introduce as a feature gains adoption.
 Improvements in this area will likely be driven by having [availability metrics better reflect the user experience](https://about.gitlab.com/direction/saas-platforms/scalability/#availability-metrics-better-reflect-the-user-experience), [enabling experimental deployments](https://about.gitlab.com/direction/saas-platforms/delivery/#enable-experimental-deployments) and [release channels](https://about.gitlab.com/direction/saas-platforms/delivery/#release-channels-on-com) as well as [increasing the number of paved roads](https://about.gitlab.com/direction/saas-platforms/scalability/#paved-roads-are-the-default-for-all-team-members) for team members to traverse.
-### Unlock Faster Innovation through Novel Software Delivery Models
-Runway introduced a new paradigm for delivering software to customers. 
-In FY 25 Runway supported [multi region deployments](https://docs.runway.gitlab.com/guides/multi-region/), in many locations across the world for customers that wanted to use our hosted AI services that power Duo. 
-In FY 26, Runway will GA a new runtime, [aligned with our long term vision](https://docs.runway.gitlab.com/reference/blueprints/satellite-services-vision/), that will allow easy delivery of services built on Runway to Self Managed customers and expand to support more workloads across GitLab.
+### Unlock faster innovation by introducing different software delivery models
+Runway introduced a new paradigm (to GitLab) for delivering software to customers. 
+In FY25 Runway supported [multi region deployments](https://docs.runway.gitlab.com/guides/multi-region/), in many locations across the world for customers that wanted to use our hosted Duo AI powered services. 
+In FY26, Runway will GA a new runtime, [aligned with our long term vision](https://docs.runway.gitlab.com/reference/blueprints/satellite-services-vision/), that will allow easy delivery of services built on Runway to Self Managed customers and expand to support more workloads across GitLab.
 We expect this new paradigm to unlock new possibilites for stage teams and accelerate our time to value for new and innovative products like [GitLab Secrets Manager](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/secret_manager/). 
 This will also drive opportunities to "Land" in categories that previously we looked to "Expand" into.
-Along with this, GitLab.com teams will be responsible for operating and orchestrating [Cells](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/infrastructure/) which presents an opportunity to further innovate on our overall multi tenant product offering. 
+[Cells](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/infrastructure/) also presents an opportunity to further innovate on our software delivery models and overall multi tenant product offering. 
 Growth in this area will likely take the form of product offerings like per cell/customer Geo, exclusive customer cells, private connections and/or private runners. 
 Cells will be the foundation on which these new product offerings are integrated into gitlab.com and SaaS Platforms teams must design future solutions with this in mind.
-### Build it --> Run it
-As mentioned in other places on this page, the groups and teams in SaaS Platforms are responsible for the operations of GitLab.com and all services that support it.
+### In the direction of "Build it --> Run it" model
 We know that this is something that will only scale linearly and with an increased number of services, the number of engineers we need to support those services will grow at an accelerated rate as will the organisational toil and management overhead to serve that increasing number of engineers.
 ![Runway Scale Model](./scale-model.png)
@@ -119,7 +137,7 @@ Early indicators of success here could look like:
 Example of what we are not doing:
-- We're not launching a separate GitLab EU service, this will be delivered as part of our extended Cells work
+- We're not launching a separate GitLab EU service, this will be considered as part of our extended Cells work
 - We're not offering user customisable versions for GitLab.com, GitLab.com will continue to recieve continuous deployments
 ## What's Next
@@ -132,4 +150,8 @@ For a Look at the work in progress and what's next, you can stay up to date with
 - Scalability
     - [Runway](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/969)
     - [Practices](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1202)
-    - [Observability](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1295)
+    - [Observability](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1295)    
+- Production Engineering
+    - [Foundations](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1175)
+    - [Ops](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1176)    
+- [Cells](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1296)