Agency resources
Explore the platform, review the proposed deployment, and use practical buyer guidance to define a controlled agency evaluation.
Start here
Product fit, deployment evidence, and procurement requirements should be evaluated together.
See how narrative preparation, fact review, official instructions, policy sources, and warrant preparation connect.
02Review the proposed boundary, data lifecycle, identity model, CJIS responsibilities, and evidence package.
03Bring structured governance, deployment, access, audit, AI-safety, operations, and contract questions into procurement.
Insights & buyer guides
Practical guidance for defining pilot scope, reviewer safeguards, security controls, procurement evidence, and measurable success criteria.
Buyer Guide
A useful pilot tests the full documentation workflow—not just whether a model can produce polished text. Use these questions to evaluate control, quality, security, and operational fit.
Read the guideSecurity & Governance
The important difference is not the chat box. It is the deployment, identity, data, audit, source, and review controls surrounding the model.
Read the guidePrintable buyer resource
Common questions
Evaluate the exact proposed architecture, data flow, model and hosting providers, identity configuration, operating controls, contracts, and evidence package. Responsibility is shared across the agency, LeoPen, and applicable providers.
The current workflow supports reviewable copy and download actions. Direct RMS integration is roadmap work unless it is included and demonstrated in a specific pilot scope.
The intended first live model is a LeoPen-managed Google Cloud deployment with a dedicated single-agency boundary. Region, services, identity, model path, support access, retention, evidence, and CJIS responsibilities require written validation before agency data is used.