> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt > Use this file to discover all available pages before exploring further. # Modules > Compare Resolve, Review, Optimize, and Cyber: what each module does, what it needs connected, and where to start. CloudThinker groups its work into four modules: **Resolve**, **Review**, **Optimize**, and **Cyber**. Each runs the same [agentic loop](/#how-cloudthinker-works) on a different kind of signal, with the same assistant, memory, and approvals underneath. ## What is a module A module is a complete workflow for one common problem — an incident, a pull request, a cloud bill, or an app's security. CloudThinker runs it end to end, from spotting the problem to bringing you the result to act on. Every module runs on the same [harness](/guide/harness) and shares one memory, so what one module learns helps the others. Each module has its own section in the sidebar and a status line on the **Modules** card on [Home](/guide/activity). ## Why modules * **One signal, one place.** Incidents, pull requests, cloud bills, and app security each get a workspace built for them. * **Shared context.** What CloudThinker learns in one module — your services, your conventions, past incidents — informs the others. * **Start with one.** Each module needs only its own connection, so you can turn them on one at a time. ## At a glance | Module | What it does | What it needs | Start here | | - | - | - | - | | **Resolve** | Investigates every incident, finds the root cause, and proposes the fix | An alert source, or a manually logged incident | [Connect Pulse sources](/guide/pulse/setup) | | **Review** | Reviews every pull request with context from your running infrastructure | A Git connection with a repository added | [Set up Review](/guide/code-review/setup) | | **Optimize** | Ranks cost-saving actions from your cloud bill | An AWS, Google Cloud, or Azure connection with billing access | [Optimize overview](/guide/cost-optimization/overview) | | **Cyber** (Beta) | Pentests a running app and proves each finding with evidence | An app with a target URL you've verified | [Cyber overview](/guide/security/cyber-overview) | ## Resolve Resolve is incident response. [Pulse](/guide/pulse/overview) takes in alerts from sources such as Datadog, PagerDuty, Grafana, or cloud monitoring, strips the noise, and routes real problems into Incidents. CloudThinker investigates each one and hands you a root cause and a proposed fix to approve. Find it under **Resolve**: **Investigation**, **Overview**, **Pulse**, **Insights**, **Integrations**, **On-call**, **Runbooks**, and **Settings**. No alert source yet? Use **Log Incident** on the Investigation page — see the [quickstart](/quickstart). ## Review Review is code review. Every pull request on a connected repository — GitHub, GitLab, Bitbucket, Azure DevOps, or AWS CodeCommit — gets inline comments with severity and a suggested fix. The review bot answers [mention commands](/guide/code-review/mention-commands) such as `@cloudthinker-ai review`. Find it under **Review**, starting with **Overview**, **Reviews**, and **Settings**. ## Optimize Optimize is cloud cost. It reads billing data from one AWS, Google Cloud, or Azure connection and ranks what to fix first: idle resources, oversized instances, unused commitments, and anomalies. Find it under **Optimize**: **Overview**, **Cost Health**, **Cost Explorer**, **Findings**, **Anomalies**, and **Reports**. ## Cyber Cyber is application security, currently in beta. A dedicated security agent pentests one running app at a time, keeps its attack surface and findings between runs, and re-checks each fix on the next scan. You prove you own the app's domain before the first scan. Find it under **Cyber**: **Overview**, **Pentest**, and **Settings**. ## Plan availability Chat is available on every plan. On the Free plan, Review runs only for eligible organizations, and Resolve investigations and Cyber pentests need a paid plan. A new organization starts on a 14-day Team trial with every module available. See [Pricing](/guide/billing/pricing). ## Related See how modules share workspaces, connections, and guardrails Learn who does the work inside each module Run your first investigation in about 10 minutes Add what each module needs This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.