# Architectual plan Architectural/component plan published as engineering handbook page on how to integrate UnReview into GitLab detailing how we will: * Meet the needs of both gitlab.com and self-hosted customers including plans for data storage components (MongoDb/Neo4J/etc) and compute/storage resource requirements for creating and running models * Replace the small number of libraries with undesirable open-source licenses # PoC demo PoC demo of UnReview working like Reviewer Roulette on the GitLab product codebase using existing UnReview code/architecture. * Move Azure and GitHub-hosted aspects of UnReview to GCP. * Implement UnReview code and dependent components in GitLab managed GCP instance * Demonstrate UnReview on GitLab code base and compare/contrast with existing reviewer-roulette (https://docs.gitlab.com/ee/development/code_review.html#reviewer-roulette). cc @cweaver1 @tmccaslin @david @eliran.mesika @achueshev @Quintasan Milestone 2 is represented in https://gitlab.com/groups/gitlab-org/-/epics/6113