IT / systems integrators
Bundle LiveSchools365 with networking, biometric attendance, or campus Wi‑Fi projects as the operational SIS.
OEM Partner plan
LiveSchools365 OEM Partner Plan
Re-brand and re-sell LiveSchools365 in your geography under your pricing and terms — with a partner portal to invite schools, assign packages, and issue signed licenses.
What is the OEM program?
Embed LiveSchools365 into your education offering
OEM Partners are organisations that take LiveSchools365 — feature-rich modules, role-aware screens, and signed licensing — and sell it as part of their own product or services package to schools and colleges.
You leverage a UI and workflow set already proven for Pakistani campuses (admissions through payroll and parent portals), then localise commercial terms, branding, and go-live support for your territory. Trend Developers keeps engineering, releases, and the license signing model current so you can focus on sales and implementation.
Reach more customers
Sell LiveSchools365 as part of your stack
OEM is not only a logo swap. It is a commercial layer above schools (SaleCustomers) and campuses — so your team owns the relationship while the product stays one maintainable codebase.
Education consultants
Move from advice-only engagements to a recurring platform you implement and support for each school board.
Regional SaaS brands
Offer hosted school ERP under your domain with MultiTenant host binding to each SaleCustomer.
On-prem specialists
Deliver Windows Setup or Docker SingleTenant packs with the same license.json activation story.
OEM toolkit
What the LiveSchools365 OEM Partner receives
- Partner Portal (
/partner) Invite schools, assign Core / Standard / Premium or marketplace modules, issue signed licenses. - Wholesale pricing Partner-specific monthly list prices for components — set with Trend Developers, visible read-only in your portal.
- School branding & hosts SaleCustomer colours, favicon, and custom hostnames so each school (or your brand) feels native.
- Campus ownership model Campuses hang under SaleCustomer; school admins get customer-scoped access without a separate TenantId rewrite.
- Settlement stubs Period reporting rows for territory finance (Stripe Connect payouts can follow when you are ready).
- Enablement Solution tour, User Guide, Trial Journey, and Implementation Guide — the same paths schools already use.
Operating model
How OEM differs from buying for one school
A single school buys a package on Pricing or modules on Modules. An OEM partner owns a portfolio of schools: you create and link SaleCustomers, keep wholesale margins, and run activations from the Partner Portal after Trend Developers provisions your OemPartner account and portal users.
liveschools365.com remains the whole-product SaaS face; school-automation.com remains the module marketplace. Your OEM layer sits above both as the reseller channel — not a fork of the codebase.
Apply for the OEM Partner plan
Re-brand. Re-sell. Keep shipping.
Send your company profile, target cities, and preferred delivery model (hosted, Windows, or Docker). We will schedule a partner briefing and outline wholesale terms.
OEM Partner plan — white-label school ERP
The LiveSchools365 OEM Partner plan is for organisations that re-brand and re-sell the product under their own pricing and terms. You embed a feature-rich school ERP — role-aware modules, signed licensing, cloud and self-host packs — into your education offering without forking the codebase.
Commercially, OEM partners own OemPartner → SaleCustomer → Campus. Operational rows still filter by CampusID. Branding (school name, primary/secondary colours, favicon, custom hosts) attaches to SaleCustomer so each school or your regional brand feels native. The Partner Portal is where you invite schools, assign packages, and issue licenses after SuperAdmin links your portal users.
Delivery options OEM partners can sell
- Hosted cloud — schools on LiveSchools365 / school-automation hosting with optional custom hostnames.
- Windows Setup — shared installer plus license.json for on-premises campuses.
- Docker SingleTenant — customer compose pack with Hosting:Mode=SingleTenant for appliance-style installs.
Not included yet
Automated Stripe Connect payouts and partner-specific signing keys are planned after the portal foundation. Settlement stub rows already exist for territory reporting. Until Connect is live, Trend Developers and the partner agree payout terms offline while licenses still issue from the portal.
Compare school-facing pricing, read Why partner?, or contact Trend Developers to apply for the OEM plan.