Local models
Inference runs on the computer hosting the model. Conversations are stored on your disk. Connected tools can still use the network; local inference does not make every action offline.
Trust & evaluation
Evaluate PriestAI
on your own work.
Give PriestAI one useful job. Choose the data it can see, the tools it can use and the result you expect. Evaluate the work before expanding its responsibility.
Know the destination
Where your data goes
Cloud models & tools
The providers and tools you configure receive the data needed for their requests. Review the destination, permissions and provider terms before using company information. Provider charges are separate.
Downloads & updates
Setup, model downloads and release checks use the network. The app checks for releases every six hours while open; downloading and installing an update requires confirmation.
Support reports
Review the report before sending it. Remove customer information, credentials and sensitive attachments. Reports sent by email pass through your mail provider and the support mailbox.
Plan a pilot
Choose a workflow and agree how to measure it.
01 / Define
Choose the work
Bring a development task, a repeatable support problem or a security review of systems you own or are authorised to assess. Agree the scope and a named decision maker.
02 / Evaluate
Keep the evidence
Use a separate evaluation workspace and non-sensitive sample data. Record setup time, completion quality, tool approvals, model cost and the recovery steps when something fails.
03 / Decide
Review before expanding
Review the output and unresolved issues together. Confirm deployment requirements, licensing, support arrangements and ownership before a wider rollout.
Prepare an evaluation
Create a
pilot brief.
Choose a workflow and a data boundary. Get an evaluation plan with the evidence to collect and a clear decision at the end.
The planner runs in this page. Your entries are not submitted or saved. Download your brief to keep it; an email draft is yours to review and send.
Download the blank briefSuggested acceptance criteria
A proposed scope, not a quote or a production approval.
Security with a defined scope
Find the issue. Verify the fix.
Viriditas is PriestAI's security workbench. Evaluate it through authorised testing, reproducible findings and remediation evidence. Security testing needs an agreed target, permission from its owner and a clear stop condition.
Verify the software you receive
The releases page publishes version information and checksums. Check the downloaded file against the published SHA-256 before running it. A checksum verifies the file against that published value; it is not a code-signing certificate or an independent security audit.
Report a vulnerability privately
Email support@priest.locker with “Security report” in the subject. Include the affected version, expected and actual behaviour, and minimal reproduction steps. Omit credentials and personal data. Support is best-effort; no response-time commitment is advertised.
Before production
Check your production requirements.
PriestAI is in beta. Enterprise evaluation should confirm identity integration, tenant isolation, data handling, deployment support and recovery against your requirements. Record any gaps before making a deployment decision.
Current assurance status
No independent penetration-test result, compliance certification, production SLA or code-signing certificate is claimed here. OpenAI Daybreak partnership and specialised model access are not claimed. Those require separate approval and evidence.
Current release status
The release page lists the current public version and verified download hashes. Read the release status for validation scope and work still in development.