> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polycore.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation

> Understand Polycore's control plane, customer-hosted runner, trust boundary, and governed dispatch model.

<div className="poly-doc-home">
  <section className="poly-home-hero">
    <div className="poly-home-inner">
      <div className="poly-home-copy">
        <span className="poly-kicker">
          <span className="poly-kicker-dot" aria-hidden="true" />

          Polycore documentation
        </span>

        <h1 className="poly-home-title">
          <span className="poly-home-title-line">Govern in the cloud.</span>
          <span className="poly-home-title-line">Execute in your infra.</span>
        </h1>

        <p className="poly-home-lead">
          Policy, approval, and audit live in the control plane. Credentials and
          execution stay on your outbound-only runner.
        </p>

        <div className="poly-home-actions">
          <a className="poly-home-button" href="/getting-started/integration-process">
            Start integrating
          </a>

          <a className="poly-home-button poly-home-button-secondary" href="/concepts/architecture">
            Understand the architecture
          </a>
        </div>
      </div>

      <div className="poly-system-frame">
        <div className="poly-frame-label">
          <span aria-hidden="true" />

          <span aria-hidden="true" />

          <span aria-hidden="true" />

          one request, across the trust boundary
        </div>

        <div className="poly-system-map">
          <div className="poly-system-node">
            <div>
              <span className="poly-node-eyebrow">Callers</span>
              <strong>Agents and operators</strong>
              <p>Slack, MCP, and admin dashboards reach the same catalog.</p>
            </div>

            <span className="poly-node-foot">governed request</span>
          </div>

          <div className="poly-system-wire" />

          <div className="poly-system-node poly-system-node-accent">
            <div>
              <span className="poly-node-eyebrow">Polycore cloud</span>
              <strong>Control plane</strong>

              <p>
                Resolves identity, policy, approval, routing, and the audit
                record. It does not hold your execution credentials.
              </p>
            </div>

            <span className="poly-node-foot">signed dispatch</span>
          </div>

          <div className="poly-system-wire" />

          <div className="poly-system-node">
            <div>
              <span className="poly-node-eyebrow">Your infrastructure</span>
              <strong>Polycore runner</strong>

              <p>
                Holds scoped credentials and executes against your databases,
                APIs, and secret manager.
              </p>
            </div>

            <span className="poly-node-foot">outbound connection only</span>
          </div>
        </div>
      </div>
    </div>
  </section>

  <section className="poly-home-section">
    <div className="poly-home-inner">
      <div className="poly-section-heading">
        <span>The operating model</span>
        <h2>Govern the operation, not the conversation.</h2>

        <p>
          The caller receives a typed capability, not the key behind it. Polycore
          applies the same rules whether the request comes from a teammate, an AI
          agent, or an internal dashboard.
        </p>
      </div>

      <div className="poly-principles">
        <div className="poly-principle">
          <span className="poly-principle-index">01 / CREDENTIAL CUSTODY</span>
          <h3>Your production credentials remain in your infrastructure.</h3>

          <p>
            The customer-hosted runner resolves credentials locally. They are not
            sent to Polycore cloud, an agent, Slack, or a browser.
          </p>
        </div>

        <div className="poly-principle">
          <span className="poly-principle-index">02 / HUMAN GATE</span>
          <h3>Governed by your access policy.</h3>

          <p>
            Your policy decides what runs instantly and what waits. Sensitive
            actions require a recorded approval decision before the runner
            executes them.
          </p>
        </div>

        <div className="poly-principle">
          <span className="poly-principle-index">03 / ATTRIBUTION</span>
          <h3>One record across every caller.</h3>

          <p>
            Requests, capability invocations, results, and approval decisions are
            recorded in the same audit model.
          </p>
        </div>
      </div>
    </div>
  </section>

  <section className="poly-home-section">
    <div className="poly-home-inner">
      <div className="poly-section-heading">
        <span>Assisted integration</span>
        <h2>We design the first production path with your team.</h2>

        <p>
          Polycore is not a self-serve connector marketplace. During early access,
          we scope the first workflow, prepare your runner, help deploy it, and
          validate the full path with you.
        </p>
      </div>

      <div className="poly-integration-strip">
        <a className="poly-integration-step" href="/getting-started/integration-process#the-path-to-production">
          <code>01</code>
          <strong>Scope</strong>
          <p>Choose one useful read and one representative governed change.</p>
        </a>

        <a className="poly-integration-step" href="/integrations/overview">
          <code>02</code>
          <strong>Connect</strong>
          <p>Map least-privilege access to Postgres, Firestore, or your API.</p>
        </a>

        <a className="poly-integration-step" href="/concepts/runner">
          <code>03</code>
          <strong>Deploy</strong>
          <p>Run the outbound-only worker next to your systems and secrets.</p>
        </a>

        <a className="poly-integration-step" href="/concepts/approvals-and-audit">
          <code>04</code>
          <strong>Validate</strong>

          <p>
            Prove instant results, approval-gated actions, failures, and audit
            records.
          </p>
        </a>
      </div>
    </div>
  </section>

  <section className="poly-home-cta">
    <h2>Start with the systems you already operate.</h2>

    <p>
      Tell us which production workflow matters. We will map the integration
      and work alongside your engineering and security teams.
    </p>

    <div className="poly-home-actions">
      <a className="poly-home-button" href="https://www.polycore.ai/early-access">
        Request early access
      </a>

      <a className="poly-home-button poly-home-button-secondary" href="/integrations/overview">
        Browse integrations
      </a>
    </div>
  </section>
</div>