Question 1

How long does implementation take?

Accepted Answer

Most institutions complete core deployment within 4–8 weeks. Timeline depends on data migration scope, the number of modules activated, and integration complexity with existing systems.

Question 2

Does OrvexCore require full system replacement?

Accepted Answer

No. OrvexCore is designed for phased adoption. Institutions can begin with one or two modules — for example, OrvexPay and OrvexAdmin — and expand incrementally while legacy tools remain active during transition.

Question 3

How does OrvexCore handle multi-campus or multi-school operations?

Accepted Answer

OrvexCore is built on a multi-tenant architecture. Each campus or school operates in an isolated data context while administrators with appropriate permissions can access cross-campus reporting, budgets, and analytics from a unified dashboard.

Question 4

Is OrvexCore a SaaS platform or an on-premise installation?

Accepted Answer

OrvexCore is a cloud-hosted SaaS platform, managed and operated by the OrvexCore team. Institutions access it over HTTPS with no local server infrastructure required. Enterprise customers can discuss dedicated instance options.

Question 5

Can OrvexCore connect with our existing accounting or ERP system?

Accepted Answer

Yes. OrvexCore exposes structured API endpoints and supports webhook-based event publishing. Your team or an integration partner can connect external accounting tools, ERPs, or communication systems using the documented API surface.

Question 6

Does OrvexCore support importing historical institutional data?

Accepted Answer

Yes. We provide data migration tooling and dedicated support during onboarding. Historical student records, payment histories, and enrollment data can be imported through a structured migration process with validation at each step.

Question 7

What uptime guarantees does OrvexCore provide?

Accepted Answer

OrvexCore targets 99.9% uptime. The infrastructure is deployed on multi-region cloud infrastructure with automated failover. Health metrics, uptime history, and incident communication are available via our status page.

Question 8

How is student and financial data protected?

Accepted Answer

All data is encrypted in transit and at rest. Role-based access control restricts data visibility per staff role and per institutional boundary. Audit logs record every access and mutation event across the system.

Question 9

Can OrvexCore handle institutions with over 5,000 students?

Accepted Answer

Yes. OrvexCore is built on an event-driven, horizontally scalable architecture. Institutions with thousands of students and staff generate hundreds of thousands of monthly events — the system is load-tested and designed for this scale.

Question 10

How does the event-driven architecture benefit large institutions?

Accepted Answer

Rather than synchronous, blocking API calls, OrvexCore processes institutional operations as durable events. This means payment completions, enrollment updates, and grade postings propagate reliably across modules even during high-volume periods.

Question 11

Is pricing based on the number of students?

Accepted Answer

Pricing is influenced by multiple factors: institutional scale (number of students and staff), active modules, event volume, and integration complexity. We do not charge per-student for every tier — contact us for a scoped institutional estimate.

Question 12

Can small schools use OrvexCore affordably?

Accepted Answer

Yes. The modular architecture means smaller institutions can start with OrvexAdmin and OrvexPay at a lower tier. You're not forced to purchase the full platform — cost scales with the operational footprint you actually need.

Question 13

Does OrvexCore provide training for staff?

Accepted Answer

Yes. All new institutional clients receive onboarding training for relevant staff roles. We provide role-specific documentation, video walkthroughs, and live Q&A sessions during the deployment phase.

Question 14

What happens if we want to add a new module later?

Accepted Answer

Modules can be activated at any time without downtime. Because all modules share the same underlying data layer and event bus, enabling a new module (e.g., OrvexFlow or OrvexInsight) immediately connects to your existing institutional data.

TheOperatingSystemforModernAfricanSchools.