Your data never leaves your network.
Trust and security
eva runs on your infrastructure, inside your permission model. By design, not as an option.
- On premise index
- Built and read inside your network.
- Access is role and grade gated
- Enforced in code, not in a policy doc.
- Every model call is audited
- One central key, full logging.
- No training on your data
- Providers never see your content twice.
- Managed runtime
- You pin the version the fleet runs.
- Privacy blur
- One toggle hides numbers and client names.
- One governed gateway
- Every model call, one central key. Revoke once.
- Central connector rollout
- Enabled once, live on every laptop.
- Runtime version control
- Updates ship only after conformance tests pass.
- Full activity log
- Who asked what, and which sources answered.
- Per team enablement
- Pilot one function before you widen it.
- Spend visibility
- Usage and limits set centrally.
At a glance
Where does your data actually sit?
The short version your IT team will ask for first.
- Index location
- On premise
- Training on your data
- Never
- Permissions
- Mirrored from your systems
- Model traffic
- Your governed gateway
- Writes to systems of record
- Opt in, logged
- Activity log
- Exportable
An operating layer the whole company runs on.
Built for enterprise
- One layer, not ten tools
- Every system read once, every project role served.
- Six domain agents
- Preconstruction, design, delivery, commercial, finance, legal.
- Permission aware
- People see what they are already entitled to see.
- On your infrastructure
- eva runs next to the systems it reads.
- Measured workflow by workflow
- Before and after time on every workflow.
- Six weeks to daily use
- Zero to company wide, seven systems live.
Intelligence and time are money. Save all.
0
Systems read in place
0
Workflows already collapsed
0 wks
Zero to company wide