Sensitive network files deserve a local-first workflow.
How DeepCodeAgent handles firewall matrices and FortiGate configuration files in the current beta.
Local-first by design
DeepCodeAgent is designed so the firewall matrix and supported plain-text FortiGate configuration files selected in the current application are parsed by JavaScript in the browser. The tool does not need to upload those selected files to a DeepCodeAgent application backend in order to perform the current audit and generation workflow.
What stays local
Matrix rows, parsed FortiGate address objects, custom services, selected policy fields, generated delta CLI and generated rollback are processed in the browser for the current beta workflow.
No automatic firewall access
DeepCodeAgent does not connect to your FortiGate, log in to a device, push configuration or execute generated CLI. Deployment remains an administrator action.
Dependencies
The beta may load third-party front-end libraries required by the interface or spreadsheet parser. Loading a library is different from uploading the selected firewall file, but organizations with strict requirements should review browser network activity and the published architecture before use.
Security limits you should understand
Local processing does not make generated configuration automatically safe. Existing configuration can change after export, policy order matters, and the current engine does not fully model NAT, security profiles, VDOMs, zones, groups, VIPs, IPv6 or every FortiOS feature. Always review the target firewall immediately before deployment.
Handling configuration backups
Use a plain-text FortiOS configuration only when permitted by your organization. Prefer password-masked exports where possible. Do not upload a configuration to any service unless you are authorized to handle that data.