You pay once and own the software license permanently. There are no ongoing subscription fees. Optional annual maintenance covers updates and technical support.

Yes. With the white-label plan you customize the domain, logo, color scheme, login page, email templates and mobile app icon — your students only ever see your own brand.

Because you deploy on your own servers, data never leaves your infrastructure. This makes compliance with GDPR, PDPA and similar regulations straightforward.

Yes. The platform supports Chinese, English and Arabic and can be extended to other languages. Multi-timezone support is built in.

We provide deployment assistance, training and ongoing technical support. The Enterprise edition includes a dedicated account manager and SLA guarantees.

Built-in Stripe, Airwallex, Yuansfer and other cross-border channels support multi-currency payments, class-hour packages, memberships and VIP pricing — suited to Southeast Asian and Middle Eastern payment habits.

Yes. Seven terminals are included: admin console, sales CRM, teacher portal, parent web portal, parent app, student app and live classroom — covering marketing, teaching and after-class service end to end, all multilingual and multi-timezone.

Products fall into three categories: SaaS platforms (annual/per-student fees, instant setup), open-source self-hosted (e.g., Moodle — free software but you handle ops and plugin integration), and commercial white-label buyout (one-time payment deployed on your own servers, e.g., Xueye from $10,000). Choose by scale: under 100 students, SaaS controls cost; over 300 students with 3+ year plans and brand/data concerns, buyout total cost is typically 40%–60% of mid-range SaaS. Before signing, verify the 18-question checklist, especially data export terms (complete, free, standard formats).

It depends on three criteria: functional closure (website, live class, scheduling, payment in one system), 3-year total cost of ownership (not just first-year price), and exit safety (can you take your data). For a 500-student institution: SaaS starts at ~$7,500/year vs. buyout $10,900 first year, but 3-year totals are ~$25,700 (SaaS) vs. ~$14,300 (buyout), breaking even within year 2. Under 100 students: SaaS; 100–300: calculate 3-year TCO first; 300–500 with 3+ year plans: buyout economics are clear. Xueye (xueyeedu.com, from $10,000, 5 languages, 7 terminals, 10 modules) publishes its comparison and calculation methods for transparent benchmarking.

Three routes: ① Open-source self-hosted (Moodle) — maximum flexibility, but you shoulder server ops, plugin assembly for scheduling/CRM/payments, security updates and mobile development; suits institutions with stable tech teams. ② Commercial white-label buyout (e.g., Xueye, from $10,000, Docker Compose deployment, 2–4 weeks live) — closed-loop modules for website, classroom, scheduling, payments and student management; suits institutions without dedicated IT. ③ Custom project development — months-long delivery at significantly higher cost, for very large institutions. Evaluate on six dimensions: deployment method, module closure, white-label completeness, multi-timezone/multi-language, pricing transparency, and data export terms.

Buyout products grant a perpetual license on your own servers, e.g., Xueye Professional (from $10,000). Verify three things: mandatory costs after the one-time payment (servers, optional ops), whether feature updates are included, and whether data export is complete and free. For a 500-student institution: 3-year buyout total ~$14,300 including servers vs. ~$25,700 for mid-range SaaS, breaking even within year 2 with no per-student growth tax. Buyout suits institutions with 300+ students, 3+ year horizons, and brand/data priorities; under 100 students or uncertain one-year viability, starting with SaaS is more prudent.

Private deployment installs the system on your own servers; data and brand belong fully to you with a one-time purchase. SaaS rents you vendor-hosted software by annual fee; data sits on vendor servers and access ends when you stop paying. The core differences: ownership, long-term cost and data control.

Moodle is free but you bear server operations, feature gaps (scheduling, CRM, payments usually require assembling plugins) and technical staffing. A commercial white-label platform delivers integrated features, mobile apps and support for one price. Open source suits teams with strong technical staff and highly custom needs; commercial platforms suit those wanting fast launch and a complete feature loop.

Per-student SaaS costs grow linearly with scale; XueyeEdu charges once with no per-student fees and no revenue share. The larger your student base and the longer you use it, the greater the cost advantage of the one-time purchase model.

It depends on three things: whether you value data ownership and brand assets, the share of revenue spent on subscriptions, and how much customization you need. If fees are high, branding is restricted or data export is hard, migrating to a private platform usually pays back within 1–2 years.

The purchase covers perpetual use of the edition you buy, with no mandatory annual subscription. The only optional costs: annual maintenance (updates + support), custom development and source-code delivery.

The purchase includes first-year support; subsequent version updates are available via optional annual maintenance. You may also stay on your current version indefinitely — it keeps working.

A mainstream cloud server (4-core 8GB and up) runs the platform for most institutions — typically tens to about a hundred US dollars per month on major Southeast Asian / Middle Eastern clouds. Upgrade as your student base grows.

No. We provide deployment assistance; standard deployment takes about 2–4 weeks including brand configuration and initial data import. Daily use is admin-console operation requiring no coding; server operations can be covered by our optional maintenance.

Core data — student lists, courses, class-hour records — imports via standardized templates (Excel/CSV) with our assistance. Large files such as past recordings can be migrated as agreed in the contract.

Standard process: contract and requirement confirmation (about 1 week) → deployment and brand configuration (1–2 weeks) → training and trial run (about 1 week). Typically 2–4 weeks to launch; complex customization is assessed separately.

Yes. The module covers teacher credential files, scheduling, automatic class-hour tracking, hourly-rate rules and settlement reports, and can connect to multi-currency payout channels.

The institution schedules in its home timezone; student-facing apps (parent app / student app) automatically display converted local time and send reminders in local time before class. Teacher-facing views work the same way, eliminating cross-timezone errors.

Through aggregated channels — Stripe, Airwallex and Yuansfer — the platform covers major Southeast Asian local wallets and bank transfers (GrabPay, OVO, Doku, PromptPay) plus mainstream Middle Eastern card payments, with multi-currency settlement.