This document maps each of Nesto’s seven Worker Onboarding Portal requirements to the Nexus component that fulfils it. No gaps. No custom-code workarounds.
Nesto’s Worker Onboarding Portal requires automated multi-jurisdiction compliance, RBAC approval gates, a tamper-proof audit trail, and two white-label portals — without ongoing engineering spend for each regulatory change. Every one of those requirements is delivered by four platform components: Nexus (pipeline orchestration — this is the platform name), deltaPrism (data governance and audit), Chameleon (white-label portals), and Atlas (intelligence and document understanding layer). Compliance branches, document validation rules, and regulatory API endpoints are all pipeline configuration. When Gulf regulators update their requirements, Nesto updates a config file. No developer. No sprint. No release.
Atlas Strategic Position: Atlas is the intelligence layer above Wormwood, deltaPrism, and Chameleon. It does not replace any component — it adds capabilities that belong above the pipeline: document understanding at scale, cross-record consistency enforcement, exception explanation, CV pre-qualification before pipeline entry, evidence pack assembly for regulatory inspection, and SuccessFactors handoff integrity gate. Atlas observes the entire pipeline, extracts meaning from documents, flags inconsistencies, and generates intelligence outputs the other components rely on but cannot produce themselves.
| Ref | Requirement | Delivered by | How |
|---|---|---|---|
| R-01 | Multi-jurisdiction compliance rules | Nexus rule engine | Per-jurisdiction pipeline branches. Config, not code. No sprint per regulatory change. |
| R-02 | Document validation & routing | Nexus + Atlas | Required fields enforced at intake. Atlas OCR extracts structured fields from all uploaded documents with confidence scores. Cross-document consistency checking catches name/date/nationality mismatches before submission. Routing is pipeline config. |
| R-03 | HR approval gate | Nexus — Human Gate node | RBAC pause. Approve / Reject / Request More Info. Decision logged with user ID and timestamp. |
| R-04 | Immutable audit log | deltaPrism | AES-256 event store. Every pipeline event written. Export-ready for Gulf regulatory evidence. |
| R-05 | Employer Portal | Chameleon | White-label portal. Nesto branding and layout. |
| R-06 | Worker Self-Service Portal | Chameleon | Worker uploads, document status, read-only access. |
| R-07 | Regulatory API integration | Nexus pipeline config | Endpoint, auth, and payload format are config. Change takes minutes, not a sprint. |
| Atlas — Intelligence Layer (7 capabilities included): (1) Document OCR with field extraction and confidence scoring; (2) Cross-document consistency checking across worker file; (3) Exception identification and persona-based routing; (4) Operator readiness narratives for HR dashboards; (5) Evidence pack assembly for regulatory inspection; (6) SuccessFactors handoff integrity gate; (7) CV pre-screening API for candidate eligibility evaluation. Full capability specification documented in Nesto commercial pack (ATLAS_FIT.html, DOC-009). | |||
Nationality = IN.Nationality = PH. Configurable — no engineering involvement."No code" does not mean zero effort. Configuration changes still require internal resources. When a regulatory body updates its requirements, someone on Nesto’s team must update the config file and test the change. The efficiency gain is that this work takes hours, not weeks — and requires no developer sprint, no release cycle, and no ongoing vendor dependency.
Building a multi-jurisdiction compliance system from scratch requires three parallel engineering projects: a rule engine, an audit system with Gulf-standard immutability and evidence export, and two white-label portals. Every regulatory change requires a developer sprint. Every new jurisdiction requires code changes, testing, and deployment.
The platform delivers all of this on day one — rule engine (Nexus), audit log (deltaPrism), both portals (Chameleon), and intelligence layer (Atlas). Atlas handles document understanding, cross-record consistency, exception routing, evidence assembly, and SuccessFactors integrity gates. Regulatory changes become config file updates. New jurisdictions become new pipeline branches. Nesto’s team owns the configuration, not a development partner.
Disclaimer: Estimated costs are approximate and vary by region, vendor rates, and project scope. Development partner rates may differ significantly from market averages. The comparison illustrates the efficiency advantage of a platform approach, not a precise cost guarantee.
Priority incident response. Up to six regulatory config changes per year included. Additional capacity available on request. Nesto retains full operational control.
What's included: Platform support and maintenance (infrastructure, security patches, core feature updates). Service desk support (user training, how-to questions, operational guidance) is separate, optional, and recommended from a service ticket perspective.
| # | Source | URL |
|---|---|---|
| 1 | Clutch 2025 Custom Enterprise Software Development Cost Guide | clutch.co/resources/cost-build-web-application |
| 2 | Gartner IT Key Metrics Data 2024 — Application Maintenance as percentage of Development Cost | Proprietary research report (subscription required) |
| 3 | Atlas equivalent custom build estimate: 7 capabilities × 4–6 weeks per capability at mid-market development rates. Composite estimate for document intelligence platform with OCR, consistency checking, exception classification, evidence assembly, integration gates, and pre-screening API. | Derived from Clutch 2025 enterprise ML/AI development cost guide + AWS Textract/Comprehend pricing tiers |
| 4 | CZ-NST-2026-04-001 Commercial Proposal — Uued Viljapuuaiad OÜ / Code Zero | This document |