Enter password to view the HorixOS illustration page.
This page explains how all major HorixOS technologies connect to each other using simple language and relationship diagrams. Think of it like a city map: users enter from the front gate, tasks are routed to departments, work gets processed, and reports come back to leaders.
How all major parts connect from left to right.
They sign up, choose a plan, and get their own private tenant space.
Owner adds managers and recruiters, then connects email and calling tools.
Jobs are posted, candidates are sourced, and matching ranks best fits.
Calls/emails are analyzed so team quality and candidate engagement are visible.
When placements happen, metrics improve and AI learns to recommend better next actions.
The website (Next.js) sends requests to the NestJS API. Heavy tasks (scraping, transcription, AI batch jobs) are handed to worker services through Redis queues so the main app stays fast.
Every action writes data to storage and emits events. Those events feed analytics and dashboards so leaders see live business impact.
How access control and money control work together.
Owner controls tenant-wide settings and billing. Manager controls team operations. Recruiter executes hiring tasks. Platform Admin controls system-wide health.
Every costly action (AI calls, call minutes, storage, APIs) is counted. Plan limits are checked before processing. Stripe handles payment lifecycle.
They get smarter daily suggestions (who to call, follow-up timing, risk alerts).
They see team quality signals (engagement, conversion, burnout risks).
They track ROI, cost efficiency, and where automation creates savings.
| Term | Simple Meaning |
|---|---|
| Tenant | One customer company with its own isolated data and settings. |
| API Gateway | Main gatekeeper that checks identity, company, and access before work starts. |
| RBAC | Role-based rules that decide who can do what (Owner/Manager/Recruiter). |
| Worker | Background helper process for heavy tasks so main app stays fast. |
| Event Bus | A stream of “what just happened” messages across the system. |
| Vector DB | Special database for similarity search (matching candidates to jobs). |
| Metering | Counting paid usage like AI tokens, call minutes, and storage. |
| Closed Loop | System learns from past outcomes and improves future recommendations. |
Page generated for illustration from HorixOS architecture, workflow, directory, RBAC, and API requirement documents.