How to Get Started with ProjectDiscovery Documentation

Start at the documentation home page (docs.projectdiscovery.io), where a search box and a Documentation Index give you two ways in: type a product or task into search, or browse the index to see everything the docs cover. From there, pick the entry point that matches what you're trying to do — exposure discovery, custom vulnerability automation, or organizational setup — rather than reading linearly. The sections below map each goal to the right starting point.

Find the right entry point

The home page organizes content around a few primary paths:

The Get Started entry is the general on-ramp; the three topic blocks above it are task-specific. If you already know which product you're using, search is faster than browsing.

If you're working as an individual or on a single task

Use the topic blocks on the home page:

• Advanced Exposure Discovery — for mapping internet-exposed assets and understanding your attack surface.
• Automate Custom Vulnerability — for building and automating custom security templates that detect vulnerabilities at scale.
• Vulnerability Feed — for staying current with trending vulnerabilities and exploits in real time.

Each block links into the relevant documentation set, so you can go from the home page to working instructions without detouring through organizational material.

If you're setting up for an organization

The For Organizations → Get Started path covers the cloud platform and automation. From there, the documented setup areas are:

• Cloud Monitoring — connect and monitor AWS, GCP, Cloudflare, and Azure accounts for security vulnerabilities.
• Team Integrations — integrate with your existing ticketing and alerting tools.
• API Integration — build and automate custom security workflows using the REST APIs.
• Internal Network Security — automated vulnerability assessment and monitoring for internal networks.
• Enterprise Security Setup — configure SAML SSO, IP whitelisting, custom headers, and similar organization-level controls.

A practical order: connect cloud accounts first (Cloud Monitoring), then wire alerts into your existing tools (Team Integrations), then add API automation once the manual flow works. Enterprise Security Setup is worth doing before rolling out to a wider team, since SSO and IP whitelisting affect how everyone signs in.

Find advanced topics and integrations

Two entry points cover most "how do I connect this to something else" questions:

• API Integration — the REST APIs for building and automating custom security workflows. Use this when the built-in integrations don't cover your stack.
• Team Integrations — ticketing and alerting tools, for routing findings into where your team already works.

Both are reachable from the For Organizations section of the home page.

Get help from security experts

The home page includes a Talk to Our Security Experts option for personalized guidance on implementing security workflows for your organization. Use it when you need help scoping a rollout rather than looking up a specific feature — for example, deciding how to structure cloud monitoring across multiple accounts before you configure anything.

Common sticking points

• Search vs. browse: the search box (with a ⌘K shortcut) is the fastest route when you know the product or feature name; the Documentation Index is better when you're surveying what exists.
• Individual vs. organization content: exposure discovery and template automation live in their own blocks, while cloud monitoring, integrations, and enterprise setup sit under For Organizations. Starting in the wrong one is the most likely reason a topic seems missing.
• Setup order matters: integrations and API automation assume you already have accounts or monitoring connected, so do those first.