Modliqer is a no-code manufacturing intelligence and machine learning platform that helps factory teams analyze production data, optimize process settings, validate quality, and generate buyer-ready Quality Passports.

Modliqer is for manufacturing companies, factory owners, plant heads, quality managers, process engineers, operations managers, supplier quality teams, and lean improvement teams.

Do I need a data scientist to use Modliqer?

No. Modliqer is designed so manufacturing teams can use analytics and machine learning workflows without hiring a data analyst, data scientist, or ML engineer to get started.

What is a Quality Passport?

A Quality Passport is a buyer-ready report generated by Modliqer that summarizes dataset readiness, process capability, optimization evidence, operations performance, supplier traceability, and improvement actions.

Is Modliqer an AutoML platform?

Modliqer includes no-code AutoML workflows, but it is not a generic AutoML tool. It is designed specifically for manufacturing workflows such as yield optimization, SPC, Cp/Cpk, OEE, supplier risk, and Quality Passport reporting.

Modliq Platform Launch Documentation Pack Index

**Last verified:** 2026-08-04

**Source of truth:** Current codebase inspection

**Status:** Implemented / Launch-Ready

📌 What Modliq Is

Modliq is a universal no-code AI Process Optimization Copilot powered by AutoML, purpose-built for manufacturing and process engineering teams. Developed in Tamil Nadu, India as a flagship manufacturing intelligence product by Qeltrava AI, Modliq translates complex industrial process data into plain-English operating targets, safe parameter windows, statistical quality controls, root-cause driver rankings, and standardized operating procedure (SOP) action plans.

Modliq features a modern aesthetic inspired by Notion × Figma × Vercel, bridging deep machine learning algorithms with an intuitive, role-gated UI across public marketing, user console, and enterprise admin tiers.

🧭 Documentation Map & Organization

The documentation is organized into 12 dedicated functional domains:

text

/docs
├── 00-overview/             # Product vision, feature catalog, launch status, domain glossary
├── 01-architecture/         # System topology, service boundaries, data flows, multi-tenancy, AI & ML design
├── 02-frontend/             # Next.js App Router, routes, UI components, state management, design system
├── 03-backend/              # Express API gateway, route handlers, RBAC authorization, jobs, Quality Passport
├── 04-ml-engine/            # FastAPI ML microservice, AutoML pipelines, goal parser, optimizer, QC stats
├── 05-database/             # MongoDB Atlas + Prisma ORM schema, models, relationships, sync protocols
├── 06-ai/                   # Multi-provider AI Gateway, provider fallbacks, prompt guardrails, kill switch
├── 07-security/             # Zero-trust security model, auth, tenant isolation, file/SSRF protection, incident response
├── 08-deployment/           # Production deployment topology (Vercel + Render + MongoDB Atlas + Redis), env vars
├── 09-testing/              # Build verification, type checks, pytest suite, E2E integration tests, QA checklist
├── 10-launch/               # Go-live readiness, audit signoff, 10-client pilot terms, SEO/AEO/GEO strategy
├── 11-developer-onboarding/ # Local development setup, codebase tour, common developer recipes, troubleshooting
└── archive/                 # Historical system blueprints and implementation guides

🚀 Role-Based Onboarding Paths

Follow the tailored path below based on your role to get productive quickly:

🎨 For Frontend Developers

1. Start with to understand the domain.

2. Read & .

3. Review and .

4. Setup environment: .

⚙️ For Backend Engineers

1. Read .

2. Review & .

3. Inspect Database models: & .

4. Review authorization policies: .

🧪 For ML / Data Engineers

1. Read .

2. Review & .

3. Deep-dive into algorithms: , , and .

🛡️ For Security Reviewers

1. Read .

2. Inspect & .

3. Check pre-launch checklist: & .

🚢 For DevOps / SRE Engineers

1. Review .

2. Verify environment configuration: .

3. Review rollback protocols: .

🧪 For QA Engineers

1. Start with .

2. Run end-to-end suite: .

3. Execute pre-flight verification: .

📈 For Product / Business Stakeholders

1. Read & .

2. Inspect launch readiness: .

3. Review pilot terms: & .

📜 Documentation Maintenance Rule

IMPORTANT

**Mandatory Policy for All Maintainers & Contributors:**

Whenever routes, API endpoints, Prisma database models, environment variables, service boundaries, AI gateway fallbacks, deployment settings, or launch status change in code, the corresponding documentation files in `/docs` **must be updated in the very same pull request**. Code is the source of truth, and documentation drift is treated as a build blocker.

Modliq Platform Launch Documentation Pack Index

**Last verified:** 2026-08-04

**Source of truth:** Current codebase inspection

**Status:** Implemented / Launch-Ready

📌 What Modliq Is

🧭 Documentation Map & Organization

The documentation is organized into 12 dedicated functional domains:

text

/docs
├── 00-overview/             # Product vision, feature catalog, launch status, domain glossary
├── 01-architecture/         # System topology, service boundaries, data flows, multi-tenancy, AI & ML design
├── 02-frontend/             # Next.js App Router, routes, UI components, state management, design system
├── 03-backend/              # Express API gateway, route handlers, RBAC authorization, jobs, Quality Passport
├── 04-ml-engine/            # FastAPI ML microservice, AutoML pipelines, goal parser, optimizer, QC stats
├── 05-database/             # MongoDB Atlas + Prisma ORM schema, models, relationships, sync protocols
├── 06-ai/                   # Multi-provider AI Gateway, provider fallbacks, prompt guardrails, kill switch
├── 07-security/             # Zero-trust security model, auth, tenant isolation, file/SSRF protection, incident response
├── 08-deployment/           # Production deployment topology (Vercel + Render + MongoDB Atlas + Redis), env vars
├── 09-testing/              # Build verification, type checks, pytest suite, E2E integration tests, QA checklist
├── 10-launch/               # Go-live readiness, audit signoff, 10-client pilot terms, SEO/AEO/GEO strategy
├── 11-developer-onboarding/ # Local development setup, codebase tour, common developer recipes, troubleshooting
└── archive/                 # Historical system blueprints and implementation guides

🚀 Role-Based Onboarding Paths

Follow the tailored path below based on your role to get productive quickly:

🎨 For Frontend Developers

1. Start with to understand the domain.

2. Read & .

3. Review and .

4. Setup environment: .

⚙️ For Backend Engineers

1. Read .

2. Review & .

3. Inspect Database models: & .

4. Review authorization policies: .

🧪 For ML / Data Engineers

1. Read .

2. Review & .

3. Deep-dive into algorithms: , , and .

🛡️ For Security Reviewers

1. Read .

2. Inspect & .

3. Check pre-launch checklist: & .

🚢 For DevOps / SRE Engineers

1. Review .

2. Verify environment configuration: .

3. Review rollback protocols: .

🧪 For QA Engineers

1. Start with .

2. Run end-to-end suite: .

3. Execute pre-flight verification: .

📈 For Product / Business Stakeholders

1. Read & .

2. Inspect launch readiness: .

3. Review pilot terms: & .

📜 Documentation Maintenance Rule

IMPORTANT

**Mandatory Policy for All Maintainers & Contributors:**

Whenever routes, API endpoints, Prisma database models, environment variables, service boundaries, AI gateway fallbacks, deployment settings, or launch status change in code, the corresponding documentation files in `/docs` **must be updated in the very same pull request**. Code is the source of truth, and documentation drift is treated as a build blocker.