Evaluate ClearPoint

This public guide is the evaluation entry point for prospective customers, technical reviewers, and implementation teams who are deciding whether a ClearPoint deployment is ready for their workflow.

What this covers

The guide is public by design. It does not require a tenant account, and it does not expose customer-specific posture, raw evidence artifacts, internal runbooks, or product documentation that has not passed owner sign-off.

How it works

Evaluation begins with the approved public material below. Product destinations appear only after the matching source package completes owner review and publication approval. Held readiness details remain in the internal publication record, not in an empty reader destination.

Limits

The public website and the docs portal have different jobs:

• cpl-web owns marketing, positioning, campaign pages, public conversion journeys, and the first-read Trust Center surface.
• cpl-docs owns technical evaluation and implementation documentation: source-anchored product overviews, security companion docs, getting-started previews, generated references, and audience-gated docs.

This boundary prevents duplicate positioning copy from becoming a second source of truth. If a claim belongs in marketing, it starts in cpl-web. If a fact needs source anchors, owner review, corpus search, or access gating, it belongs in cpl-docs.

Prospective customer audience

The prospective-customer reader is a first-class docs journey, but not a new access tier. Prospective customers read the public tier. Any detail that needs tenant identity, NDA treatment, private evidence, or customer-specific posture must remain behind a customer-approved workflow.

Publishing rules

• Public evaluation pages must carry source anchors and review metadata.
• Product claims must stay tied to canon and source-owner sign-off.
• Product documentation that describes a moving target must stay unpublished until the owning product confirms readiness.
• Customer-only, internal, developer, and partner material must not be linked as public content unless the access gate can enforce the intended audience.

Next steps

• ClearPoint Docs Overview explains the portal source model, audience tiers, and fail-closed publishing discipline.
• Getting Started with ClearPoint Docs explains what is available to anonymous readers and what requires a customer gate.
• Security and Trust Technical Companion collects public implementation-level security, evidence, and data-handling material.