Aller au contenu principal
Home›Support›CIO & CISO Technical Guide
IT Architecture & Information Systems Security

Technical & Security Guide for CIOs and CISOs.

Sovereign Architecture Summary

How does INARA RH sovereign software architecture operate?

INARA RH is a native desktop client suite (Windows x64) engineered under a strict local confinement paradigm. Candidate files, scoring rubrics, and organizational charts are stored locally on the client workstation in encrypted formats. AI processing runs either via the zero-token internal deterministic algorithmic engine or through a fully disconnected local Ollama instance, eliminating cross-border data transfers and ensuring native compliance with Algerian Law 18-07.

Encrypted local on-disk storage with zero shared cloud infrastructure.
100% offline AI inference via Ollama (Llama 3, Mistral, Gemma).
3-source PII anonymization triangulation engine and anti-leak Guardrail.
Strict adherence to Law 18-07 Articles 32 and 36 regarding ANPDP data transfer rules.
Inara RH — AI Center Console & Local InferenceOllama model manager on port 11434
Console Centre IA INARA RH
Local architecture supervision: disconnected execution via Ollama (port 11434) with zero cloud reliance or external traffic.

4 Pillars of Secure Enterprise Architecture

1. Autonomous Desktop Client

Windows x64 software installed locally on the recruiter’s PC. Unlike public SaaS web apps exposed to the Internet, it has no shared multitenant backend and no exposed public APIs vulnerable to network injection vectors.

Verified installer binary with code integrity signature.

2. Offline Disconnected Ollama Inference

Native integration with the open-source Ollama engine running on http://localhost:11434. Open-weight models leverage local hardware compute (CPU/GPU) without transmitting a single data packet outside the machine.

Compatible with Llama 3, Mistral, Gemma, and local models.

3. PII Engine & Pre-Flight Guardrail

3-source triangulation detection engine identifying and masking personal identifiers (Latin/Arabic names, 18-digit NIN, social security NSS, banking coordinates) with visual inspection prior to deep inference.

Systematic visual audit ensuring zero inadvertent data leakage.

4. Zero-Token Deterministic Engine

Massive batch screening module built on deterministic local algorithms (regular expressions, weighted score matrices). Rank 1,000 resumes locally without network latency or external API costs.

Zero API expense and total operational independence.

Hardware Specifications and Network Prerequisites

ComponentMinimum RequirementRecommended (Ollama Local)Network Impact
Operating System (OS)Windows 10 (64-bit) build 1903+ or Windows 11Windows 10 or Windows 11 (64-bit)Zero network impact (native client system)
Processor (CPU)Intel Core i3 or AMD Ryzen 3 (64-bit)Intel Core i5/i7 or AMD Ryzen 5/7Zero network impact (local CPU computation)
System Memory (RAM)4 GB RAM8 GB to 16 GB for running local LLM instancesDedicated memory allocation to local process
Disk Storage250 MB free space for the desktop app4 GB SSD space for local models (Llama 3, Mistral)Encrypted local SSD storage
Graphics Card (GPU)Integrated standard GPU (CPU inference)Optional dedicated GPU or standard accelerationPurely on-device mathematical execution
Outbound Network TrafficZero outbound traffic in Exclusive Local Mode (Ollama)Optional HTTPS 443 outbound if using remote API keysRoutable and filterable by corporate proxy/firewall
Inbound Open PortsZero open inbound ports requiredZero inbound ports required (internal loopback 11434)Zero external network attack surface

Security and Regulatory Compliance Matrix

Security RequirementINARA RH Technical ImplementationLegal / Regulatory Compliance
Candidate data protection (Law 18-07)Encrypted confinement on client workstation. Zero transfer to unauthorized offshore servers.Compliant with Law 18-07 Articles 32 and 36 (exempt from ANPDP transborder transfer permits).
Sensitive identifier masking (PII)3-source triangulation engine neutralizing names (Latin/Arabic), 18-digit NIN, NSS, ID cards, passport numbers, and bank details.Full adherence to data minimization principles.
Preventive outbound control (Guardrail)Pre-Flight Inspector enabling HR operators to audit and redact anonymized text before any deep inference step.Absolute technical safeguard against inadvertent data exposure.
Internal auditability and loggingLocal event log (LogViewer) tracing requests, timestamps, and execution statuses with full JSON export capability.Straightforward verification for enterprise CISO and audit teams.
Licensing and software integrityCryptographic machine-bound locking (hardware UUID), without intrusive telemetry or candidate data telemetry.Respect of enterprise digital sovereignty and corporate privacy.
Enterprise Deployment Protocol

3-Step Rollout on Your Corporate Workstations

1

Install the Official Binary

Download and run Inara_2.1.0_x64-setup.exe on targeted HR workstations. Setup completes in under 2 minutes and does not interfere with existing corporate software.

2

Configure Inference (Local or Remote)

According to your internal security policy: connect the software to an Ollama instance (http://localhost:11434) for 100% disconnected work, or input your secured API keys in the AI Center.

3

Hardware-Bound License Activation

The software generates a unique hardware identifier (machine UUID). When upgrading from the 7-day trial to the perpetual license, enter your permanent key provided by LeapDz with no recurring internet check.

Frequently Asked Questions from CIO & CISO Teams

How do you roll out INARA RH across dozens of company workstations?
The official installer Inara_2.1.0_x64-setup.exe can be deployed using standard enterprise distribution tools (Microsoft Intune, SCCM, or administrative PowerShell scripts). Silent installation is supported via the /S flag.
What network connectivity is required between Inara and Ollama?
Inara communicates with Ollama through a local HTTP loopback on http://localhost:11434. No traffic passes through the external network adapter. For intranet-shared Ollama servers, a private IP and Bearer token can be configured.
Does the application require administrator privileges for daily use?
Administrator privileges are required solely during initial installation to register the executable in system directories. Routine operation runs under standard non-elevated user accounts.
How can security teams audit the absence of outbound traffic?
CISOs can enable Exclusive Local Mode in Inara and monitor network packets using packet sniffers (Wireshark, Sysinternals TCPView, or Windows Defender Firewall rules). The client generates zero outbound packets in this mode.
How are data backup and restoration handled?
All application data (applications, job profiles, screening scorecards) is stored locally in the Windows user profile (%APPDATA%\Inara). These directories can be seamlessly integrated into existing enterprise backup workflows.

Validate INARA RH technical compliance on your corporate infrastructure

Questions about enterprise deployment or an official quote?

Chat on WhatsApp