Where your data goes
Investigations involve data that cannot leave your control. Here is exactly what OpsBuilder does with it in each deployment, and what it does not do.
On your own hardware
- Runs entirely inside your network; needs no internet after install
- Models are fine-tuned for your deployment and installed with the software
- No API keys, no license server, no update checks, no telemetry
- Prompts, generated code, and workspaces stay in your own database
- You set retention, backups, and deletion to match your policies
- Works on isolated networks and single workstations
Run by Optimatech Labs
- Each customer gets a separate workspace and admin-managed accounts
- Your prompts and generated code are used only to provide the service
- The same fine-tuned models, served from our inference hosts
- Export your workspace at any time and move to self-hosting
- Tell us what you plan to upload and we say plainly whether hosted fits
Controls that are in the code today
Roles and sign-in
Admin and analyst roles. Admins create accounts; there is no self-signup. Passwords are hashed and sessions expire after eight hours.
Protected by default
CSRF tokens on every form, parameterized database queries, input validation, and output encoding.
Who did what
An activity log records who generated, ran, exported, or deleted what, and failed logins are recorded with their source address.
A quick check, not a vault
Python and Bash tools run on the OpsBuilder host under a time limit. Treat it as a quick check, and run finished tools on the systems they belong to.
Documented for your team
We provide architecture documentation and walk your security team through every component before a pilot. Nothing exotic to maintain.
Your rules apply
Self-hosted installs sit behind your own authentication, network segmentation, and monitoring, with nothing that needs an exception.
Questions from your security team?
We walk through the architecture, provide documentation, and answer specific compliance questions before any pilot.
Contact us