## Problems to solve We are putting increasing load on our primary Postgres database with new and existing text searching features. Already, new text search features are discouraged from being created due to the load on Postgres, and the existing search experiences that rely on are subpar besides. Additionally, self-managed customers lack efficient support for AI features utilizing embeddings, like Duo, Chat, and later, Agents. Such features depend on embeddable and searchable data, e.g., chatting about GitLab issues and Merge Requests or browsing Docs chat. We don't currently ship with any support for this. ## Proposal Ship GitLab with a search service, initially as an optional component, marking the transition of text searches from Postgres to a search service and introducing a vector store for AI features. Design document MR: https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/13206