Direct answers. No marketing fluff.

eMada is a cloud-native Student Information System (SIS) built by Human Logic Software LLC. It unifies the entire student lifecycle — admissions, registration, finance, scholarships, academic records, accommodation, and reporting — on a single SaaS platform purpose-built for credit-hour-based universities — American-system, British-system, and medical institutions. eMada features single-tenant architecture, AI-powered analytics and forecasting, full data residency control, and multi-cloud hosting on AWS, Azure, or Google Cloud. It is used by universities and academies across the UAE and Bahrain, and is headquartered in Dubai, UAE.

Three things: it's purpose-built for credit-hour-based universities — American-system, British-system, and medical — so the academic model fits from day one; it's truly modular SaaS so you start with what you need and scale; and it's backed by an independent team with no acquisition-driven roadmap surprises.

Fully. Logo, colours, typography, custom domain — all configured during implementation. Login screens, email templates, transcripts, invoices, and certificates carry your brand, not ours. Students, faculty, and stakeholders interact with your institution throughout. eMada runs underneath.

Single-tenant, by design. Each institution gets its own database and application instance — no two customers share infrastructure.

What that means in practice:

• Institution-specific WAF rules tailored to your traffic patterns
• Network access restricted per module — Finance and Registration locked to campus networks while Admissions stays open to the public internet
• Data residency guaranteed at the institution level — you dictate where your data is hosted, processed, and backed up
• Update schedules around your academic calendar, not a shared release train

SaaS only. No on-premises or hybrid option — deliberate.

• No capital expenditure on servers or data centre infrastructure
• No version lag — every institution runs on the current product
• Continuous security patching, managed by eMada
• Faster implementation — no infrastructure procurement before software work begins

For institutions with strict data sovereignty or network access requirements: single-tenant architecture, configurable in-country hosting, institution-specific WAF rules, and per-module network access controls deliver the isolation that previously required on-premises — without the cost.

Everything a student used to queue at the registrar or finance office for.

Grades, transcripts, full academic history. Degree progress tracked against the study plan with completion percentages. Course schedules, exam timetables, and advisor booking.

Online course registration with real-time section availability. Add, drop, waitlist, semester suspension, withdrawal, and program change requests — all self-service.

Account balance, fee structure, payment history. Online payments through connected gateways. Scholarship and sponsorship status. Installment plan setup where offered.

Update contact info, request official transcripts, enrolment verification letters, and other documents. Track every submitted request through to completion.

Responsive design across every browser and device. SSO through Microsoft 365, Google Workspace, or Oracle Identity Management. UAE Pass available at the admissions stage where enabled.

Tools that give advisors the context they need in the time they actually have — removing the data-gathering work, not the advisor.

• "What-if" scenarios — model how different course choices, program changes, or transfer credits affect the path to graduation before any decision is made
• Per-course reasoning — see exactly why a course is recommended or blocked: prerequisites, credit-hour requirements, holds, probation status, scheduling constraints
• When a course can't be taken, the system explains why — so the advisor discusses alternatives, not just a "blocked" message

• Plan course sequences across remaining terms
• Automatic prerequisite chain validation
• See the cumulative impact on graduation date, cost, and completion

• Advisor-student matching with workload visibility for department heads
• Built-in secure messaging with full conversation history retained — handovers between advisors don't lose context

• Visual dashboards: academic progress, milestone completion, risk indicators based on criteria the institution defines
• Filtering and grouping to identify which students in a caseload need attention this week

eMada uses AI where it produces measurable operational benefit — not as a marketing label on features that don't need it.

Predictive scoring and pre-screening against your admission criteria. Prioritises applications for human reviewers and forecasts which applicants are most likely to convert from offer to enrolment. The final decision stays with the admissions team.

Predicts course enrolment based on historical patterns, study plans, and student progression. Calculates how many sections to schedule to avoid both over-staffing and waitlist bottlenecks. Predictions are inputs to planning, not automatic actions.

Proposes timetable configurations that maximise student access to required courses while minimising conflicts, factoring faculty availability, room capacity, demand patterns, and prerequisite chains.

Handles routine inquiries and transactional tasks: registration questions, payment status, policy questions, document requests. Routine questions get instant answers. Complex situations get routed to the right human team.

OCR and machine learning applied to uploaded documents: transcripts, IDs, financial statements, language certificates. Reads, classifies, extracts structured data, and triggers renewal reminders on expiring documents.

Enterprise AI accounts with zero data retention. Your data is never stored after the response is returned, never used to train or fine-tune any model. Role-based access controls on what data each AI feature can see. AES-256 encryption at rest before any processing. PII anonymisation where AI doesn't require personally identifying information.

Yes. A built-in module covering student housing and non-student campus accommodation — visiting faculty, short-term residents, conference attendees.

Manages room and building inventory, flexible leasing structures (semester, monthly, daily, custom), housing applications and waitlists through the same student portal, automated or manual room allocation, check-in through check-out lifecycle tracking, and occupancy reporting for capacity planning.

Accommodation charges flow directly into the student's account in the Finance module alongside tuition and other fees.

One of the most comprehensive modules — purpose-built around the complexity institutions actually face, particularly in the Gulf where scholarship structures tend to be more varied.

Handles nationality-based scholarships, merit-based (GPA, test scores), need-based grants, sponsor-funded awards, sibling discounts, staff dependant discounts, and multiple awards stacking on a single student — each with its own coverage rules.

• Configurable eligibility rules: GPA, program, nationality, admission year, financial need, any student attribute in eMada
• Self-service scholarship applications routed through approval workflows
• Automated renewal processing — evaluated against renewal criteria each term, renewals and revocations processed without manual intervention
• Fund tracking and budget management in real time
• Automated disbursement — value applied to the student's account, integrated with Finance and connected payment gateways

• Sponsors log in to view funded students, invoices, disbursements, and academic performance
• Consolidated billing per sponsor — one invoice covering all funded students
• Configurable sponsorship templates: full or partial tuition, accommodation, transportation
• Automated revocation for failed courses, withdrawal, or breach of conditions
• Cost centre allocation for financial tracking

A complete Finance and Billing module managing the financial relationship with each student from admission through graduation.

• Credit-hour-based tuition billing with configurable rates per program, nationality, admission year
• Non-academic fees: accommodation, books, parking, labs, events — any configurable fee type
• Multi-currency billing: AED, SAR, BHD, QAR, OMR, KWD, USD, ZAR, and additional currencies configurable
• Cash, credit, and installment-based invoicing
• Financial aid packaging: scholarships, grants, discounts, sponsorships, and installment plans combined into a single coherent student account view
• Built-in cash register for on-campus cashier counters
• Aging and revenue reporting in real time

Online payments through NGenius Online, DubaiPay/Smart Dubai, Magnati, Payfort, and Benefit. Other standards-compliant gateways added through configuration.

Live with Microsoft Dynamics 365, Oracle E-Business Suite, Oracle Fusion, and SAP. Automated GL posting, cost centre and profit centre allocation, and revenue reporting. Automated reconciliation where the connected system exposes a reconciliation API. Other ERPs integrated during implementation via the Open API framework.

Built with UAE PDPL principles in mind — data residency, access control, and auditability.

• In-country data residency. UAE student data hosted in UAE data centres. DR copies outside the UAE only with the institution's explicit consent.
• Consent workflows. Configurable consent collection using the workflow engine, capturing student consent for specific data uses and retaining the record alongside the student file.
• Role-based access with full audit logging. Every data access event logged with user, timestamp, and record accessed — the audit trail needed for regulatory enquiries or internal investigations.

PDPL obligations on the institution as data controller — data subject requests, breach notification, sensitivity classification — are supported through audit logs, configurable workflows, and role-based access. Operational ownership sits with the institution.

Enterprise-grade controls across encryption, authentication, access, and auditability.

• Encryption. AES-256 at rest. TLS 1.3 in transit.
• Authentication. MFA. SAML 2.0 and OAuth 2.0. UAE Pass SSO at admissions. Institutional SSO (Microsoft 365, Google Workspace, Oracle Identity Management) for ongoing access.
• Access control. Granular role-based access with field-level permissions.
• Audit trail. Complete logging of data access, modifications, and administrative actions.
• Penetration testing. Annual third-party pen test included in every customer contract. Institutions can also engage their own independent auditors at any time.
• SOC 2 alignment. Controls aligned with SOC 2 Type II principles. Not currently SOC 2 certified — alignment means the controls exist and are operated; certification is a separate formal audit.
• GDPR readiness. Built-in tooling for institutions with EEA data subjects, including audit logs and access controls for demonstrating lawful processing.

Microsoft Azure, AWS, or Google Cloud — in the data centre region your institution chooses.

Region	Cloud Provider
United Arab Emirates	Azure, AWS
Saudi Arabia	Google Cloud
Bahrain	AWS
Kuwait	Google Cloud
Western Europe	Azure, AWS
United States	Azure, AWS
South Africa	Azure, AWS

Multi-region deployments available for institutions operating across countries. You specify where data is hosted and where DR copies are maintained. Cross-border data transfer for DR only with explicit consent.

eMada operates as part of your technology ecosystem, not a closed silo.

Live integrations with Moodle and Blackboard (Anthology): automatic enrolment sync, grade passback, user provisioning, and real-time status updates. Canvas (Instructure), D2L Brightspace, and Microsoft Teams for Education connect through the standard LMS connector framework, provided the LMS exposes a standard SIS integration API (LTI or REST).

A dedicated Teams App with SSO, calendar sync with Outlook, and direct access to dashboard, timetables, statements, transcripts, payments, and grades inside Teams.

Live with Microsoft Dynamics 365, Oracle E-Business Suite, Oracle Fusion, and SAP. Automated GL posting, cost centre allocation, and revenue reporting.

RESTful APIs covering students, courses, enrolments, grades, and financial accounts. Webhook support for event-driven notifications. OAuth 2.0 and API key authentication. Full API documentation. Integration support during implementation and ongoing.

The principle: wherever a standard API exists at the other end, eMada connects to it.

Built on a configurable gateway framework — any standards-compliant payment gateway connects through configuration, not custom development.

Live integrations: NGenius Online (Network International), DubaiPay/Smart Dubai, Magnati, Payfort, and Benefit (Bahrain). Other gateways added during standard implementation if they expose a standard payment API.

Once connected, the Finance module handles automated invoice generation, payment posting, and reconciliation in real time.

Yes — built as a genuinely bilingual platform, not an English product with an Arabic translation layer.

• Full Arabic UI with native RTL rendering across all modules
• Bilingual data storage — student names, program names, course names, academic records stored and displayed in both Arabic and English simultaneously
• Official documents generated in high-quality Arabic meeting regulator, employer, and institutional standards
• Arabic reporting for regulatory bodies requiring Arabic-language submissions
• Users at the same institution each work in their preferred language, viewing the same underlying records

The bilingual architecture is built into the database schema, application framework, and document generation engine. For institutions outside Arabic-speaking regions, the platform operates fully in English.

Regional support hubs. Responsive, in-context support during your working hours — not someone else's time zone. Primarily in English and Arabic.

Standard support includes:

• Response SLAs aligned with severity — critical production issues same-day
• Ticket portal, email, and scheduled video sessions
• Implementation-to-support handover so institutional context isn't lost
• Annual third-party penetration testing included in every contract
• Product and compliance updates included in the annual subscription

Extended coverage hours, dedicated account management, or named technical contacts available as additional support tiers.

3–6 months, regardless of whether you start with core modules or the full platform.

Actual timeline depends on module count, data migration complexity, integration scope, and your team's availability for requirements workshops, UAT, and training.

Typically faster than comparable legacy SIS platforms: modular architecture supports phased go-live, pre-built integrations remove custom development work, and SaaS delivery eliminates infrastructure procurement timelines.

Annual subscription based on two dimensions: the modules you license and the number of active students (enrolled plus temporary suspensions — not inactive historical records).

• Hosting on your chosen cloud region
• All product updates and feature releases
• Regulatory and compliance updates (CHEDS API changes, Bahrain HEC format changes, etc.)
• Annual third-party penetration testing
• Standard support with severity-based SLAs

• Module configuration to your policies, workflows, and academic calendar
• Data migration from your existing SIS
• Integration with connected systems — identity provider, LMS, ERP, payment gateways
• White-label branding across portal and generated documents
• User training in English or Arabic
• UAT support through go-live
• Post-go-live hypercare during the initial weeks of live operation

• Custom development beyond standard configuration
• Optional add-ons (e.g., Perpetual blockchain credentials)
• Extended support tiers

For a tailored proposal — module selection, student population, integrations, deployment region — contact the eMada team.

Clean cutover from the legacy system to eMada. No parallel-running — deliberate. Running two SIS platforms simultaneously creates divergent data, confused users, and a transition that drags on indefinitely.

• Student records — personal info, contact details, demographics, documents, academic profile
• Academic history — courses completed with grades, including transfer credits
• Program and study plan information — current program, year, completed credits, remaining requirements
• Scholarship and sponsorship records — active awards and histories
• Student financial position as at cutover — outstanding balances, deposits, institutional commitments

• Individual add/drop transactions from previous semesters (final enrolled course list and grades do)
• Receipt-level financial records and historical payment methods (closing student balance does)

The legacy system is retained read-only for audit, regulatory, or historical reporting.

Discovery → field mapping → pre-migration data cleansing → test migration to staging → production cutover (typically during a quiet academic period) → automated reconciliation reports → institution sign-off.

Yes. A built-in CHEDS module that consumes the CHEDS Master API for validated, periodic submissions to the Ministry.

Covers student personal and demographic information, academic records and transcripts, enrolment and registration data, scholarships and financial aid, and fees and student account data.

Scoped to data held within eMada. Staff records, payroll, and accounts-payable data come from your HR/ERP system — institutions that need full CHEDS coverage pair eMada's module with their HR/ERP submission.

Maintained against the current CHEDS API specification. When the Ministry publishes schema updates, the module is updated to match.

eMada captures CHEDS-relevant data correctly at source — during admissions, registration, grading, scholarships, and financial transactions — instead of reconstructing it from spreadsheets before each deadline.

Because the data is already structured against the CHEDS schema, the module extracts, formats, flags incomplete records, and submits through the Master API. CHEDS reporting becomes routine operations, not a deadline-driven data-cleanup exercise.

Yes. For institutions registered with NAPO (National Admissions and Placement Office), eMada provides a native integration in the Admissions module.

NAPO is the UAE's centralised admissions system for Emirati students and children of Emirati mothers applying to federal institutions and government scholarship pathways. Applicants submit one centralised application, upload records, take EmSAT where required, rank preferences, and receive placements.

eMada's integration:

• Receives applicant data from NAPO into the Admissions module with field mapping to eMada's data model
• Maintains alignment between the NAPO process and your internal admissions workflow
• Processes NAPO applicants alongside direct applicants in a single queue

Available only to institutions registered as participating institutions with NAPO.

Yes — as an option for the admissions portal.

When enabled, prospective students sign in with UAE Pass credentials and have government-verified information populated directly into the application: name, Emirates ID, date of birth, nationality, residency and visa status — plus single sign-on.

Reduces data-entry effort, eliminates a category of document-fraud risk, and gives applicants a familiar government-grade sign-in experience. International applicants without UAE Pass can still apply by creating an account manually.

After admission, identity management hands over to the institution's own SSO — typically Microsoft 365, Google Workspace, or Oracle Identity Management.

Built-in reporting modules for:

• UAE — CAA, CHEDS, and MOHESR submissions
• Bahrain — Higher Education Council (HEC) reporting standards

For other GCC countries — Saudi Arabia, Qatar, Oman, Kuwait — the configurable reporting framework extends to support additional regulators as part of implementation. Scope and effort depend on the regulator's data requirements and submission format.

Reports generated on demand or scheduled for automated periodic generation.

Yes — through Perpetual, also built by Human Logic Software, available as an optional add-on.

Perpetual is a blockchain-anchored credential platform built on W3C Verifiable Credentials 2.0 and BlockCerts v3. When a university issues a diploma, transcript, or certificate through Perpetual, the credential is cryptographically signed by the institution, anchored on a public proof-of-stake blockchain, stored permanently on decentralised storage, and verifiable on any compatible third-party tool — not just inside Perpetual.

For graduates: a credential they own, shareable electronically, verified in seconds. For institutions: a tamper-proof, audit-ready record of every credential issued.

Optional — institutions can use eMada's standard transcript and certificate generation without it. Learn more at perpetual.academy.