Security
MainframeLore was built for banks, insurers, and government mainframe shops — the most security-conscious buyers there are. Here's exactly what happens to your source code, what deployment options exist, and what we don't do.
The core guarantee
You export your COBOL, copybooks, and JCL — the same PDS export you already produce for source control, audits, or vendor reviews. That export is the only input. There is no agent installed on z/OS, no CICS transaction, no network path opened into your mainframe, and no credentials of any kind requested for your systems. The tool reads files; it does not connect to anything.
Deployment options
| Tier | Where processing happens | Where your source lives |
|---|---|---|
| Assess | Hosted, one-time run | Deleted after the report is delivered |
| Team | Hosted, continuous | Retained only to re-run docs on new drops; deletable on request |
| Enterprise | Inside your own network (container) | Never leaves your infrastructure |
AI and your data
Common questions
On the Assess tier, no — it's deleted once your report is delivered. On Team, only what's needed to re-run documentation on new source drops, and it's deletable on request. On Enterprise, never — everything runs inside your own network.
No. Requests to Anthropic's API are not used to train models per Anthropic's API terms. If your policy requires it, use the Enterprise tier with your own LLM deployment for a fully self-contained pipeline.
Yes, on the Enterprise tier — the parsing and analysis pipeline runs inside your network with no external calls, and either a self-hosted LLM or the deterministic analysis-only mode replaces the hosted AI step.
Start with a sanitized or representative program — the parser works identically on any valid COBOL/JCL. Many customers validate output quality on a non-sensitive program before sending anything production-facing.