Frequently asked questions about Nexus
This page is here to answer the questions institutions usually ask before they choose an ERP: pricing, campuses, security, customisation, support, and rollout fit.
If you are comparing products, trying to understand whether Nexus fits your operational model, or preparing internal stakeholders for a buying decision, these are the answers most teams ask for first.
That now includes questions about AI-powered assistance too. We want the AI story to feel trustworthy, useful, and connected to the wider ERP rather than like a detached chatbot pitch.
What institutions usually want to know first
Most ERP questions are not random. They usually cluster around a few practical concerns: commercial fit, operational trust, and whether the system can grow with the institution instead of forcing another change later.
Main FAQ themes
Buying and rollout
Questions about trials, billing, support, and rollout usually come up first because institutions want to understand commercial fit before they commit to system change.
Security and trust
Education ERP decisions involve sensitive data and operational dependence. That is why questions about access, ownership, and exportability matter early in the process.
Flexibility and scale
Multi-campus structure, custom fields, and API access matter because institutions rarely stay static. The product has to support operational growth without forcing a rebuild later.
Questions and answers
Nexus can support multi-campus institutions, including organisations that need central oversight with local campus control. The exact commercial allowance depends on your plan, but the product itself is built with multi-campus operations in mind rather than treating campuses as an afterthought.
Yes. Data isolation, scoped access, and secure handling are core expectations for the platform. Nexus is designed so institutions can manage sensitive student, staff, attendance, and finance records with stronger operational boundaries than ad hoc tools usually provide.
Yes. Nexus offers a 14-day free trial so institutions can understand the product direction before committing commercially. That gives teams a clearer way to evaluate operational fit instead of relying on sales copy alone.
Nexus includes core role-based access for major institutional users such as administrators, teachers, students, guardians, accountants, and superadmin-level control. The goal is to keep each role close to the part of the system it should actually use.
Yes. Nexus includes a custom-fields system so institutions can extend supported records without turning every local data requirement into a development request. That helps the product stay flexible while keeping the core model cleaner.
Arabic and RTL support are on the roadmap. If language support is important for your institution or deployment region, it is worth discussing early so the product conversation reflects that operational need clearly.
Nexus supports both monthly and annual billing, with annual billing offering a lower effective cost for institutions ready for a longer-term commitment. Custom enterprise-style pricing remains available for institutions with broader rollout or procurement requirements.
Yes. Your institution owns its data. Nexus is designed to avoid lock-in and supports exportability so institutions are not trapped in a system they cannot inspect or leave cleanly.
Yes. Nexus is backed by a documented API, which is especially useful for institutions or enterprise buyers that need integration paths beyond the standard product experience.
Support options vary by plan and commercial arrangement, but the broader direction includes email support, stronger help for growth-stage customers, and more tailored support handling for enterprise-style deployments.
Yes. Nexus is positioned as an AI-assisted education ERP, and Nexus AI is the clearest public expression of that today. We use measured language deliberately: the platform already includes AI-powered assistance, and it is evolving toward broader AI-powered insights and smarter operational support across modules.
No. We avoid overclaiming. The direction is AI-assisted rather than AI-first hype. That means practical guidance, smarter visibility, and evolving workflows built on top of connected ERP data, not exaggerated claims about autonomous decision-making.
Still have questions?
If you cannot find the answer you need here, we are happy to talk through your institution's requirements directly and help you map them against Nexus more clearly.