Enterprise
Enterprise deployment and procurement for EVA
The same Ridhics EVA analytical product, packaged for identity, procurement, support, deployment, and compliance review.
If your email app does not open, write to support@ridhics.com.
Enterprise controls
Identity, infrastructure, data, and workflow controls for institutional review.
Identity & Access
- SSO/SAML/OIDC implementation path during customer onboarding
- Role and workspace controls aligned to enterprise setup
- Organization-scoped access controls with database-level row isolation
- IP allow/deny policy support evaluated during deployment scoping
Audit & Governance
- Audit logging for authenticated and security-relevant activity
- Source-level provenance — every structured figure links to its exact SEC/XBRL source fact
- Compliance-ready documentation and policies
- Data Processing Agreement (DPA) available on request
- Subprocessor registry maintained and available
Data Protection
- Encryption in transit (TLS) and at rest (AES-256)
- Data egress controls and DLP evaluated during enterprise deployment scoping
- Data residency and CMEK/BYOK options remain roadmap items for regulated workloads
Certifications (Roadmap)
- SOC 2 evidence collection and audit engagement remain roadmap
- No SOC 2 certification claim is made today
How EVA handles your data
Procurement should be able to see what reaches model providers and what remains controlled by EVA.
What reaches AI providers
- User requests and prompts needed to fulfill the workflow
- Retrieved source passages and structured financial context
- System instructions that do not contain customer data
What stays controlled
- Customer workspaces remain organization-scoped
- Financial calculations use deterministic application paths where available
- Client content is not used to train Ridhics-owned or third-party models
Provider configuration
- OpenAI, Anthropic, Google Gemini, and Voyage AI may be used by workflow
- DeepSeek use is scoped to public SEC/XBRL/internal pipeline work
- Enterprise configurations can be documented during procurement
Readiness status
A plain-language view of the enterprise controls available today, under validation, or on the roadmap.
| Capability | Status | Notes |
|---|
| Per-organization data isolation | Available Now | Organization-scoped access with database-level row isolation enforced in production. |
|---|
| Encryption at rest and TLS in transit | Available Now | Ridhics-hosted infrastructure uses encrypted storage and HTTPS/TLS for service traffic. |
|---|
| Audit logging | Available Now | Authenticated and security-relevant activity is logged for operational review. |
|---|
| Organization-scoped retrieval | Verification in progress | Organization-scoped retrieval is reviewed as part of each enterprise deployment path. |
|---|
| Organization-level deletion tooling | Roadmap | Deletion requests are handled through a controlled support process while self-serve tooling is built. |
|---|
| SOC 2, VPC, PrivateLink | Roadmap | Offered once certified and contracted. |
|---|
Pilot program
Evaluate the full EVA analytical product with usage guardrails before choosing an Advanced usage plan or Institutional deployment path.
Pilot scope
- Full EVA analytical surface under evaluation limits
- Access across the covered-company universe
- Analyst and PM workflows
- Procurement and security review path
Success goals
- Validate filing, valuation, and source-provenance workflows
- Measure usage profile against Advanced usage allowances
- Confirm analyst and PM adoption before production rollout
- Confirm support, procurement, and data-handling requirements
Pilot outcome
- Advanced or Institutional path decision
- Usage allowance and rate-limit model
- Integration priorities
- Security and legal next steps
Enterprise pricing model
Institutional deployments are scoped by platform, seats, and usage.
PlatformEnterprise tenancy, procurement, security review, and deployment configuration.
SeatsNamed analyst access with PM, compliance, and read-only roles configured during onboarding.
UsageReport credits, valuation workflows, connector and workflow volume, retrieval volume, and custom integration scope.
Compliance resources and deployment topology
Customer-specific artifacts are shared during procurement and pilot setup.
Trust resources
- Privacy Policy and Terms of Service
- Data Processing Addendum path
- Subprocessor registry path
- Security questionnaire responses
- Data-isolation architecture notes
- LLM data-handling summary
Deployment options
- Ridhics-hosted cloud deployment
- Enterprise identity setup during onboarding
- VPC / PrivateLink / dedicated deployment options remain roadmap until built and contracted
- Bring-your-own entitlement adapters evaluated per customer workflow
Your data, your rules
Bring your procurement, security, and workflow requirements into the pilot evaluation.
Request PilotIf your email app does not open, write to support@ridhics.com.