> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/readme.md).

# Introduction

Your starting point for Pharos, the observability platform built natively for Salesforce — follow the journey from first signal to AI-assisted resolution.

Pharos is the observability platform built natively for Salesforce. It unifies logs, issues, alerting, tracing, monitoring, and org insight into one native system, layers **AI** on top to explain and help resolve what it finds, and stays **open**—so Salesforce telemetry can flow to the tools your teams already run. The result turns reactive troubleshooting into proactive, intelligent system stewardship.

{% hint style="info" %}
**Why "Pharos"?** Like the legendary Lighthouse of Alexandria, Pharos guides teams through the complexity of modern Salesforce implementations—illuminating hidden failures and pointing the way toward reliable systems.
{% endhint %}

## Explore the Docs

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🔭 Platform Overview</strong></td><td>What Pharos is, the methodology behind it, and the full architecture.</td><td><a href="https://docs.pharos.ai/platform-overview/overview.md">Platform Overview</a></td></tr><tr><td><strong>⚙️ Configuration Guide</strong></td><td>Install, configure, and tune Pharos in your Salesforce environment.</td><td><a href="https://docs.pharos.ai/configuration-guide/configuration-guide.md">Configuration Guide</a></td></tr><tr><td><strong>🧩 Integrations</strong></td><td>Connect Slack, Teams, Jira, Azure DevOps, GitHub, and AI providers.</td><td><a href="https://github.com/Pharos-AI/pharos-docs/tree/main/integrations/README.md">https://github.com/Pharos-AI/pharos-docs/tree/main/integrations/README.md</a></td></tr><tr><td><strong>🛰️ Open Telemetry</strong></td><td>Stream Salesforce telemetry to any OpenTelemetry-compatible backend.</td><td><a href="https://docs.pharos.ai/open-telemetry/open-telemetry.md">Open Telemetry</a></td></tr></tbody></table>

***

## Why Teams Need Pharos

Salesforce error reporting is scattered and ephemeral—spread across exception emails, platform events, bulk API queues, and debug logs that expire in hours. Teams end up working reactively, learning about problems from frustrated users rather than from their tools.

{% hint style="danger" %}
**The cost of the black box:** one company's invoice automation quietly broke for two weeks—emails stopped going out and nobody noticed until customers did. Observability is the difference between catching that in minutes and hearing about it from a customer.
{% endhint %}

[Why Pharos →](https://docs.pharos.ai/platform-overview/why-pharos.md) makes the full case, including how Pharos compares to off-platform tools like Datadog and Splunk.

***

## Your Pharos Journey

Every signal follows the same path through Pharos—from the moment it's captured to a verified fix—with **AI accelerating every step** and the whole loop staying **open and extensible**.

![The Pharos loop — Tracking (Issues, Logs), Awareness (Slack, Teams, Email), Action and Collaboration (Jira, Azure DevOps), and Resolution (AI-powered issue analysis)](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-9679605e740c50e6ac265da8897839cbc9dfbf2b%2Fpharos-loop-funnel.png?alt=media)

Follow the journey through the docs:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>1 · 📡 Capture</strong></td><td>Every signal, automatically—Apex, Flow, Bulk API, and custom Triton instrumentation—captured as enriched logs.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs.md">Logs</a></td></tr><tr><td><strong>2 · 🎯 Understand</strong></td><td>Logs are fingerprinted and grouped into de-duplicated Issues with impact statistics.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker.md">Issue Tracker</a></td></tr><tr><td><strong>3 · 🔔 Be Aware</strong></td><td>Context-rich alerts reach the right people through Slack, Teams, PagerDuty, and more.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting.md">Alerting</a></td></tr><tr><td><strong>4 · 🤝 Act</strong></td><td>Triage by real impact and sync to Jira or Azure DevOps to coordinate the fix.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ticketing-and-bugtracking.md">Ticketing and Bugtracking</a></td></tr><tr><td><strong>5 · 🧠 Resolve with AI</strong></td><td>Org Genie proposes root cause and remediation—or investigate in plain language with an AI agent.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/ai-analysis.md">AI Analysis</a></td></tr><tr><td><strong>6 · 🧩 Extend</strong></td><td>Open standards, APIs, webhooks, and AI-agent operability connect Pharos to the rest of your stack.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/extensibility.md">Extensibility &amp; Integrations</a></td></tr></tbody></table>

{% hint style="info" %}
See [How Pharos Does It](https://docs.pharos.ai/platform-overview/how-pharos-does-it.md) for the methodology behind this loop, and [Intelligence](https://docs.pharos.ai/platform-overview/how-pharos-does-it/intelligence.md) for how AI runs through every stage.
{% endhint %}

***

## The Architecture Behind It

Pharos operates on a **bottom-up** data flow—everything derives from logs. Logs roll up into Issues, Issues drive alerts and tickets, and every layer is a native Salesforce object, so your observability data inherits Salesforce security and is queryable, reportable, and exportable with the tools you already use.

![Pharos platform architecture — log ingestion flowing up through enrichment, the issue tracker, and analytics, with notification channels and external systems on either side](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-3037494d4448107fc5c841262e480066b2e40abd%2Fpharos-platform-architecture.png?alt=media)

[Explore the full architecture →](https://docs.pharos.ai/platform-overview/pharos-platform-architecture.md)

***

## Get Started

New to Pharos? The typical path is fast: install the managed package, get automated error capture in minutes, then progressively instrument critical processes, wire up integrations, and establish a triage rhythm.

{% hint style="success" %}
**Next step:** head to the [Configuration Guide](https://docs.pharos.ai/configuration-guide/configuration-guide.md) to install and set up Pharos, or start with the [Quick Start](https://docs.pharos.ai/configuration-guide/quick-start.md) wizard to get running fast.
{% endhint %}
