A practical guide to using Perplexity AI for real-time research, documentation lookup, and sysadmin investigations. Unlike ChatGPT or Claude, Perplexity searches the live web and cites sources.
Why Perplexity for Sysadmins
Perplexity retrieves current information — patched CVEs, updated package versions, new RFC standards — that static models like GPT-4o or Claude cannot access without tools. Every answer includes numbered citations you can verify immediately.
Focus Filters
| Filter | Best For |
|---|---|
| All (default) | General queries, broad research |
| Academic | Security research, protocol specs, CVE papers |
| Real-world ops experience, r/sysadmin, r/homelab | |
| YouTube | Tutorial walkthroughs, conference talks |
| Custom domain | Focus on docs.ubuntu.com, kubernetes.io, etc. |
Pro Search vs Regular
Pro Search does multi-step research: it breaks your question into sub-queries, searches each, synthesizes results. Use it for:
- Comparing two technologies (e.g., ZFS vs Btrfs in 2025)
- Security posture for a specific stack
- Finding the latest stable release and changelog of any package
Regular Search is faster and sufficient for quick lookups, man-page clarifications, and error message lookups.
Sysadmin Prompt Templates
| Task | Prompt |
|---|---|
| CVE lookup | What is CVE-[ID]? Is a patch available for Ubuntu 22.04? What is the CVSS score and attack vector? |
| Package version | What is the latest stable version of [package] as of today? What are the breaking changes from [old version]? |
| Tool comparison | Compare [tool A] vs [tool B] for [use case] in 2025. Focus on performance, community support, and production readiness. |
| Security check | Are there any known vulnerabilities in [software version] released in the last 90 days? Cite NVD or vendor advisories. |
| r/sysadmin insight | [Filter: Reddit] What does r/sysadmin say about [tool/approach]? Any common pain points or gotchas from real deployments? |
Citation Best Practices
Perplexity adds inline citation numbers like [1][3]. Before acting on any finding:
- Click the source number to verify the claim against the original page.
- For security topics, always cross-check against NVD, CISA, or vendor advisories.
- If citations are GitHub issues or Stack Overflow, check the date and accepted answer.
Best Practices
- Include the date in your query: “as of May 2025” forces recency.
- Use the domain focus field to restrict to docs.docker.com, man7.org, etc.
- Follow up with: “Show me only sources from official documentation.”
- For incident response: ask in plain English, then ask “what CLI commands check this?”
- Perplexity Spaces let you build a knowledge base — useful for team runbooks.