MultiSchool ERP Official Quotation · V3.6.0
← Back to site
ProjectWorlds Parent Company · www.projectworlds.com
Quotation No. PW-ERP-2026-006
Date of Issue 20 August 2026
Valid Until 19 September 2026
Official Sales Quotation

Multi-School ERP SaaS Script
+ Parent, Staff & Driver Mobile Apps

Version 3.6.0 — complete, unencrypted source code for a production-ready multi-tenant school management platform, with three Flutter applications and a Windows biometric sync agent. Published by ProjectWorlds under the Multi School ERP product brand — www.multischoolerp.com.

Prepared By
Yugesh Kumar Verma
Release
V3.6.0 · Aug 2026
Modules
38 + Core Platform
Total Payable
₹ 10,000/-
Delivery
Instant & Automated
01

Product Overview

Technical profile of the delivered package
Product NameMulti School ERP — Multi-School ERP SaaS Script + Mobile App
Product Websitewww.multischoolerp.com
PublisherProjectWorlds (parent company) — www.projectworlds.com
VersionV3.6.0 — Major Feature Release (August 2026). Supersedes V3.5.0 (July 2026).
Backend FrameworkLaravel 12 · PHP 8.3 – 8.4
Mobile FrameworkFlutter 3.x / Dart SDK 3.9+ — three separate applications, iOS & Android
Desktop AgentWindows Biometric Sync Agent (.EXE, .NET 8.0)
ArchitectureMulti-tenant SaaS — single database with school_id isolation and global tenant scoping
DatabaseMySQL 8.0+ / MariaDB 10.6+
SecurityAES-256 encryption at rest, Laravel Sanctum tokens, Spatie role-based access control, full audit logging
AI IntegrationData-grounded AI assistant (Google Gemini & OpenAI) — answers derived from the school's own records, with role-based privacy filtering
PDF EngineNative PHP via Chrome DevTools Protocol — Node.js is no longer required on the server
Licence100% unencrypted source code. No ionCube, no obfuscation, no domain locks, no licence key server, no phone-home calls.
DeploymentUnlimited servers, unlimited schools, unlimited students — no per-seat or per-tenant fee payable to ProjectWorlds
02

What's New in Version 3.6.0

Nine new modules and two major rewrites
About this release. Where V3.5.0 delivered breadth (CRM, website builder, SMS gateway layer, ID-card designer), V3.6.0 delivers the daily-visibility features a school actually notices — engagement & greetings, teacher–parent chat, surveys, gate pass and CCTV — together with real assessment and attendance depth (Online Exam Pro, ZKTeco/eSSL push protocol, QR scanning) and a full rewrite of the transport module into a record of what actually happened on each run. Approximately 490 files changed and 60+ database migrations since V3.5.0.
New Module

Surveys & Feedback Engine

One survey engine for the whole platform — a builder with 9 question shapes, publishing to student / parent / staff audiences, reporting with averages, distribution, NPS and trend lines, a feedback triage board, recurring cycles, anonymous public share links and a 6-template gallery. Full respond parity in both mobile apps.

New Module

Student–Teacher Chat

Direct teacher ↔ student/parent messaging with threads, participants, moderation and reporting. Built on MySQL as the single source of truth with push used only as a wake-up signal — so there is no per-message cost and no third-party chat bill to carry.

New Module

Gate Pass Management

Records every non-routine gate crossing — student early-exit and staff short-leave passes, an approval chain, QR verification, a dedicated gate terminal, automatic attendance write-back and parent notification on exit. A student who left at 11 AM is no longer counted present all day.

New Module

CCTV / Live Surveillance

A control-room camera wall (2×2 / 3×3 / 4×4), cameras assigned to a class or section, a class-scoped wall for teachers and — strictly where the school opts in — parent live-view of their own child's classroom, behind five independent consent and time-window gates.

New Module

Engagement & Creatives

Automatic birthday and festival greetings, thought of the day, tickers, home sliders, stories and pop-ups — one publishable entity with a design gallery and render pipeline, per-school timezone handling, push image support and a full run log.

New Module

Compliance & Governance

Country-specific compliance packs (India-CBSE, India-State, Kenya-CBC, Generic) installable in one click, a statutory document vault with expiry tracking, validation rules that check data before government export, inspection checklists and a readiness dashboard.

New Module

Campus Workers Register

A register for the third campus population — contract and daily third-party workers such as housekeeping, canteen, security and gardeners — with a printable badge and a hook into the gate scanner.

New Module

Datesheet Manager

Build and publish exam datesheets against a defined class scope. Parents see nothing until every unscheduled subject has a date and time and the sheet is deliberately published.

New Module

Dedicated ID Card Module

Student and staff ID cards promoted out of the certificate engine into their own section over the existing canvas designer, with duplex printing and a category split so ID cards and certificates no longer share one bucket.

Major Rewrite

Online Exam — Basic to Pro

The single largest work item in this release. 9 question types with rich attachments (audio / video / image / equation / passage / table); three delivery modes — Exam, Quiz and Practice Set; sectioned papers, blueprints and a balance meter; autosave, resume and auto-submit; a manual review queue for subjective answers; re-grade, item analysis and topic mastery reporting. Built across all four surfaces — admin web, parent portal, parent app and staff app.

Major Rewrite

Transport & Driver App

Transport became a record of what actually happened. Drivers are now real records with a globally unique Driver ID + PIN and QR enrolment; a trip is a real record with GPS pings and stop arrivals bound to it; boarding is recorded per student per trip with an offline queue for dead zones. Adds a Live Operations console, a trip-adherence escalation ladder, hold-to-send SOS, vehicle document expiry tracking and a new Boarding Register report.

Infrastructure

PDF Engine — No More Node.js

Every PDF and PNG now renders by driving Chrome directly from PHP over the DevTools Protocol. Node.js, npm and Puppeteer are no longer required on a customer server, which removes the single most common cause of failed installations. A shared-Chrome mode roughly doubles render speed, and a one-line rollback to the previous engine is retained.

Also included in V3.6.0

AreaEnhancement
Biometric AttendanceReal ZKTeco / eSSL push protocol (iclock / cdata) so devices report in without polling; push-users to devices, a device brand catalog, per-device IP allow-listing and school-level punch modes.
QR AttendanceA staff-app scanner treated as a security surface — gate and classroom scan modes with scoped permissions, a self-mark block, an anti-scan-loop re-arm rule and an evidence-grade scan audit viewer.
Parent AppA new server-decided "Today" home screen, pinnable features per parent, hideable features per school, plus Chat, Surveys, Online Exam Pro, Datesheet and CCTV.
Staff AppChat, Gate Pass, QR Attendance scanner, Surveys and the full Online Exam suite including the paper builder and per-answer marking queue. Firebase push parity added.
White-Label & BrandingPer-school Firebase configuration, and per-app mobile branding — the Driver, Parent and Staff apps each own their own name, logo and colours instead of sharing one config.
BackupPer-school off-site backup with bring-your-own storage — Cloudflare R2, Backblaze B2 or a Telegram bot — with credentials encrypted per school. Backup Management promoted to a top-level item.
SecurityParent API IDOR closed across all parent endpoints; CCTV access consolidated behind a single authority service; CCTV registered in the module registry so it can be disabled per school.
NavigationWebsite Builder, Backup Management and Biometric promoted to top-level modules with their own permissions and menu groups.
03

Complete Module Coverage

38 independently toggleable modules

Every module below is registered in the platform's module registry and can be switched on or off per school, or bundled into a subscription plan. Modules marked in green are new in or substantially rebuilt for V3.6.0.

  • Student Information
  • Academics
  • Fees Collection
  • Human Resource
  • Offline Examinations
  • Certificates & Documents
  • ID Cards
  • School Website
  • Homework
  • Library Management
  • Transport
  • Hostel
  • Inventory
  • Asset Management
  • AI Assistant & Analytics
  • Knowledge Base & Chatbot
  • Study Center
  • Live Classes
  • Accounts & Finance
  • Front Office
  • Lead Management
  • Communications
  • Online Examinations
  • Biometric Attendance
  • CBC / Competency Academics
  • Holistic Progress Card
  • Student Health Records
  • Apps Center
  • Parent–Teacher Meetings
  • Lesson Planner
  • Digital Evaluation (OSM)
  • QR Code Attendance
  • Assessment
  • Surveys & Feedback
  • Student–Teacher Chat
  • Compliance & Governance
  • CCTV / Live Surveillance
  • Engagement & Creatives
Established module New or rebuilt in V3.6.0
Beyond the module list. The following are part of the core platform rather than toggleable modules, and are included regardless of plan: the Super Admin SaaS panel, multi-tenancy and school provisioning, subscription & billing, custom domain mapping, the onboarding wizard, role and permission management, the settings command centre, dashboard themes, audit logging, the export hub, storage centre, backup centre, server health centre, infrastructure centre, API documentation centre and the ERP navigator.
04

Key Feature Highlights

A representative selection
Core SaaS & Admin Academic & Student Finance & Operations High-Tech Features
Multi-tenancy360° student profilesStripe / Razorpay / PayPalGrounded AI assistant
Custom domain mappingBulk CSV / Excel importUPI QR code paymentsLive GPS driver app
6+ dashboard themesVisual timetable builderAutomated payroll & slipsBiometric cloud sync
Flexible subscription billingStudent promotion logicExpense & income ledgerWindows desktop agent
White-label settingsOnline CBT exams (9 types)Hostel & room allocationWhatsApp API notify
Role-based permissionsSyllabus & study centerLibrary (barcode / ISBN)ZKTeco / eSSL ADMS push
SaaS analyticsDigital admit cardsInventory & stock alertsAES-256 data security
Audit logsCertificate generatorFee carry-forwardMulti-language support
Per-school off-site backupSurveys & NPS reportingTransport boarding registerParent-consented CCTV
Support ticket systemTeacher–parent chatGate pass & approvals32+ SMS / 7 WhatsApp gateways
05

Deliverables Included

Everything supplied on payment confirmation
#Deliverable ItemPlatformStatus
1Multi-School ERP SaaS Web Panel — complete Laravel 12 source code, unencryptedWeb (PHP)Included
2Super Admin SaaS Panel — unlimited schools, plans, billing and provisioningWeb (PHP)Included
3Student & Parent Mobile App — full Flutter source codeiOS & AndroidIncluded
4Staff & Admin Mobile App — full Flutter source codeiOS & AndroidIncluded
5Dedicated Driver GPS App — full Flutter source code, rebuilt in V3.6.0iOS & AndroidIncluded
6Windows Biometric Sync Agent — .EXE plus .NET 8.0 sourceWindows DesktopIncluded
7Database schema & seed data — migrations, seeders and demo datasetMySQLIncluded
8Documentation suite — installation guide, update guides, and a full VitePress documentation site covering every user roleAll PlatformsIncluded
9Store publishing guides — Google Play and Apple App Store submission walkthroughsReferenceIncluded
10Client portal access — download library, invoice, update releases and support tickets in one placeWebIncluded
111 Year software updates & bug fixes from date of purchaseAll PlatformsIncluded
121 Year technical support during business hoursWhatsApp / EmailIncluded
13Free installation assistance for one production deploymentRemoteIncluded

Minimum server requirements

PHP8.3 or 8.4 — with mbstring, openssl, pdo_mysql, gd, zip, curl, intl, fileinfo, bcmath
DatabaseMySQL 8.0+ or MariaDB 10.6+
Web ServerApache 2.4+ or Nginx 1.20+, with URL rewriting enabled
OtherComposer 2.x · Chrome / Chromium binary for PDF rendering · a queue worker (supervisor or equivalent) · cron access for scheduled jobs
RecommendedVPS or cloud server with 2 vCPU / 4 GB RAM minimum. Shared hosting is possible but not recommended for multi-tenant use.
Mobile BuildFlutter 3.x with Dart SDK 3.9+ · Android Studio / Xcode for release builds
06

Pricing Summary

One-time payment · no recurring fees
Item DescriptionOriginal PriceQuoted Price
ProjectWorlds Multi-School ERP SaaS V3.6.0
Complete unencrypted source code package — web panel + super admin panel
₹ 11,999 ₹ 10,000
All 3 mobile apps — Student & Parent, Staff & Admin, Driver (full Flutter source)IncludedIncluded
Windows Biometric Sync Agent (.EXE + source)IncludedIncluded
Documentation suite & store publishing guidesIncludedIncluded
1 Year updates, bug fixes & technical supportIncludedIncluded
TOTAL PAYABLE AMOUNT₹ 11,999₹ 10,000
Special discount — save ₹ 1,999 on the original listed price. Limited time offer.
No hidden or recurring charges. This is a one-time purchase. ProjectWorlds charges no royalty, no revenue share, no per-school fee, no per-student fee and no per-server fee, at any point, now or in future. Deploy on as many servers and onboard as many schools as you wish. Third-party services you choose to use — SMS credits, WhatsApp Business, payment gateway charges, Google Maps, Firebase, AI API keys, hosting and domains — are billed by those providers directly to you and are not part of this quotation.
07

How to Buy & Delivery

Two ways to pay — online is instant

Option 1 — Buy online INSTANT

Go to www.multischoolerp.com and use Buy Complete Source Code. Pay ₹10,000 securely by card, UPI, net banking or wallet.

Delivery is fully automated. The moment payment succeeds, the system emails your client-portal login and download link — normally within a minute, no waiting on us and no office hours. The portal also holds your invoice, future updates and support tickets.

Option 2 — Bank transfer / UPI

For buyers who prefer a direct transfer, or need a formal invoice against this quotation, our bank & UPI details are shared on request.

This route is manual: message WhatsApp +91 6263056779 or email contact@projectworlds.com and we'll send the account details. Send the payment screenshot back, and your portal access and download link are issued once the credit is confirmed.

Account HolderProjectWorlds
Bank NameAxis Bank · Current Account
Account & UPIShared on request — WhatsApp +91 6263056779 or email contact@projectworlds.com
Amount Payable₹ 10,000 (Ten Thousand Rupees Only)
Nothing is shipped physically. The complete source code package — web panel, super admin panel, all three mobile apps, the Windows agent and the full documentation suite — is delivered as a download through your client portal. Buy online and it is automated and immediate; pay by transfer and it follows confirmation of the credit. If an automated email has not reached you within a few minutes, check your spam folder, then contact us and we will provision it by hand.
08

Contact & Support

Before and after purchase

Buy Online — Instant

₹ 10,000/-

www.multischoolerp.com → Buy Complete Source Code. Automated delivery, normally within a minute.

  • 100% unencrypted source code
  • All 3 mobile apps (Student, Staff, Driver)
  • Windows biometric sync agent (.EXE)
  • Unlimited servers, schools and students
  • 1 year updates & technical support
  • Free installation for one deployment

Enquiry & Support

WhatsApp / Call+91 6263056779
Emailcontact@projectworlds.com
Product Sitewww.multischoolerp.com
Companywww.projectworlds.com
Live DemoAvailable on request, or at projectworlds.com
Support HoursMonday – Saturday, business hours (IST)

We strongly recommend reviewing the live demo and asking every question you have before making payment — source code is a digital product and cannot be returned once delivered.

09

Licence at a Glance

The full terms follow — this is the short answer

You may

  • Deploy on unlimited servers, for unlimited schools and students
  • Modify the source code freely and keep your modifications
  • Rebrand and white-label — your name, logo, colours and domain
  • Sell it as your own SaaS or install it for paying clients
  • Publish the mobile apps under your own Play Store and App Store accounts
  • Hire any developer you like to work on your copy
  • Keep using it forever — the licence is perpetual

You may not

  • Resell or redistribute the unmodified original source code as your own product
  • Claim authorship or copyright over the original work
  • Remove or alter the licence file in the project directory
  • File any copyright or ownership claim against ProjectWorlds over this work
  • Upload the package to a code marketplace, torrent or public repository
  • Sub-licence the source code itself to other developers or resellers
The distinction in one line: you are free to build and sell an unlimited product and an unlimited service on top of this code. What you may not do is sell the code itself as a competing copy of what you bought.

Terms & Conditions

ProjectWorlds Multi-School ERP SaaS Script + Mobile App V3.6.0 · Quotation PW-ERP-2026-006 · Issued 20 August 2026. These terms, together with the LICENSE file supplied inside the source code package, form the complete agreement between ProjectWorlds and the Buyer.

Section 1 Definitions

1.1 "ProjectWorlds" means ProjectWorlds, proprietor Yugesh Kumar Verma, of www.projectworlds.com — the parent company, publisher, author, copyright holder and licensor of the Software. The Software is published under the Multi School ERP product brand at www.multischoolerp.com, which is owned and operated by ProjectWorlds. References to either name in this agreement mean the same legal entity.

1.2 "Buyer" or "Licensee" means the individual or legal entity that makes payment against this quotation and to whom the Software is delivered.

1.3 "Software" or "Original Work" means the ProjectWorlds Multi-School ERP SaaS Script V3.6.0, comprising the Laravel backend, the Super Admin panel, the three Flutter mobile applications, the Windows Biometric Sync Agent, database migrations and seeders, and all accompanying documentation.

1.4 "Derivative Work" means any version of the Software that the Buyer has modified, extended, rebranded or built upon.

1.5 "End Client" means a school, institution or organisation to whom the Buyer provides access to a deployed instance, whether free of charge or for a fee.

1.6 "Deployment" means one installed, running instance of the Software on a server under the Buyer's control, irrespective of how many End Clients that instance serves.

Section 2 Quotation Validity

2.1 This quotation is valid for 30 days from the date of issue (20 August 2026), expiring on 19 September 2026.

2.2 ProjectWorlds reserves the right to revise pricing, product scope or terms after the validity period expires. A revised quotation will be issued on request.

2.3 The quoted price applies to Version 3.6.0 as described in this document. Subsequent major versions may be priced separately, subject to Section 10 (Support & Updates).

2.4 Feature descriptions in Sections 01–04 of this quotation describe the Software as released. They are a statement of scope, not a warranty of fitness for any specific institutional requirement; the Buyer is responsible for verifying suitability against the live demo before purchase.

Section 3 Payment

3.1 Payment must be made in full before the source code is delivered. Part payment does not create any entitlement to partial delivery.

3.2 Payment may be made either through the secure online checkout at www.multischoolerp.com (card, UPI, net banking or wallet), or by direct bank transfer or UPI to the account detailed in Section 07. The online route triggers automated delivery under clause 4.2.

3.3 Prices are quoted in Indian Rupees (INR) and are inclusive of all applicable taxes unless otherwise stated in writing.

3.4 Any bank charges, currency conversion costs, remittance fees or intermediary charges applicable to an international transfer are borne by the Buyer. The full quoted amount must be received net of such charges.

3.5 ProjectWorlds is not responsible for delivery delays caused by payment that has not been confirmed as received, or by a payment confirmation that has not been sent to ProjectWorlds by the Buyer.

Section 4 Delivery

4.1 The Software is delivered digitally, as a download issued through the Buyer's client portal. Nothing is shipped physically and no delivery charge applies.

4.2 Online purchase (www.multischoolerp.com) — automated delivery. Where payment is made through the website checkout, delivery is automatic and immediate: on successful payment the system issues the Buyer's client-portal credentials and download link by email without manual intervention, typically within one minute and independently of business hours.

4.3 Bank transfer or UPI — delivery on confirmation. Where payment is made by direct transfer, the Buyer must send a payment confirmation screenshot to WhatsApp (+91 6263056779) or email (contact@projectworlds.com). Portal access and the download link are issued once the credit is confirmed, and in any event within 24 hours of confirmation.

4.4 Automated delivery depends on the email address supplied at checkout being correct and able to receive mail. Delivery emails occasionally reach a spam or promotions folder. If nothing has arrived within a few minutes, the Buyer should check those folders and then contact ProjectWorlds, who will provision access manually without undue delay. A delivery email filtered, bounced or rejected by the Buyer's own mail provider is not a failure of delivery by ProjectWorlds.

4.5 Delivery is deemed complete when the download link and portal credentials have been issued to the Buyer, regardless of when the Buyer chooses to download the package.

4.6 The client portal also provides the Buyer's invoice, subsequent update releases during the support period, and the support ticket channel. ProjectWorlds may change or replace the portal, provided the Buyer's access to their purchased downloads and entitlements is preserved.

4.7 The Buyer is responsible for downloading and securely storing the delivered package. ProjectWorlds will re-issue a download link on request during the support period, but does not act as a permanent archive or escrow service for the Buyer's copy.

Section 5 Licence Grant

5.1 Upon receipt of full payment, ProjectWorlds grants the Buyer a non-exclusive, perpetual, worldwide, royalty-free licence to use, install, deploy, modify and create Derivative Works based on the Software.

5.2 The licence is perpetual. It does not expire, cannot be revoked for non-renewal, and is not contingent on any continuing payment. Expiry of the support and update period under Section 10 does not affect the Buyer's right to keep using the Software indefinitely.

5.3 The Software contains no licence key, activation server, domain lock, expiry timer, remote kill switch, telemetry or phone-home mechanism. It will continue to function on the Buyer's servers without any dependency on ProjectWorlds' infrastructure, and its continued operation is not affected if ProjectWorlds ceases to trade.

5.4 The Software is delivered as complete, unencrypted, non-obfuscated source code. No component is encoded with ionCube, SourceGuardian, Zend Guard or any equivalent, and no compiled-only files are substituted for source.

5.5 The licence is granted to the Buyer as a single legal entity, and extends to the Buyer's employees, contractors and agents acting on the Buyer's behalf.

5.6 The licence may be transferred once, in whole and not in part, in the event of a genuine sale, merger or transfer of the Buyer's business, provided ProjectWorlds is notified in writing and the transferee accepts these terms in full. The Buyer must cease all use and destroy retained copies upon transfer.

Section 6 Permitted Use — Expressly Granted Rights

6.1 Unlimited deployments. The Buyer may install and operate the Software on an unlimited number of servers, virtual machines, containers and hosting environments, in any country, with no additional payment to ProjectWorlds.

6.2 Unlimited tenants and users. There is no cap on the number of schools, branches, staff members, students, parents or concurrent users. No per-school, per-seat, per-student or per-transaction fee is payable to ProjectWorlds at any time.

6.3 Non-production copies. The Buyer may maintain unlimited additional copies for development, staging, testing, training, demonstration, disaster recovery and backup purposes.

6.4 Commercial use. The Buyer may use the Software, modified or unmodified, for commercial purposes — including operating a paid SaaS platform, delivering client projects, and charging End Clients subscription, setup, hosting or maintenance fees. All such revenue belongs entirely to the Buyer.

6.5 Rebranding and white-labelling. The Buyer may replace the product name, logo, colour scheme, domain, email templates, application identifiers, app store listings and all user-facing branding with their own. There is no obligation to display "Powered by ProjectWorlds" anywhere in the user interface.

6.6 Mobile application publishing. The Buyer may compile, sign and publish the three mobile applications to the Google Play Store, Apple App Store and any other distribution channel under the Buyer's own developer accounts and their own application identifiers, using their own branding. Developer account fees, store review and store compliance are the Buyer's responsibility.

6.7 Third-party developers. The Buyer may engage any employee, freelancer, agency or third-party developer to install, host, customise, extend or maintain the Buyer's copy, and may grant them the source access required to do so. Such parties act on the Buyer's behalf and acquire no independent licence of their own.

6.8 Ownership of modifications. The Buyer owns outright all original code, modules, integrations, designs and content that the Buyer creates on top of the Software, and may licence or commercialise those additions as they see fit. This ownership does not extend to the underlying Original Work.

6.9 Sector flexibility. Although the Software is designed for schools, the Buyer may adapt and deploy it for colleges, universities, coaching centres, training institutes or any other educational or organisational context without seeking further permission.

Section 7 Restrictions

7.1 The Buyer may not resell, sub-licence, rent, lease, lend, publish or otherwise redistribute the original unmodified source code to any third party as their own product, or as a stand-alone code product, without prior written permission from ProjectWorlds.

7.2 The Buyer may not list, upload or distribute the Software — in whole or in substantial part, modified or unmodified — on any code marketplace (including but not limited to CodeCanyon, Envato, Gumroad or similar), public code repository, file-sharing service, torrent network or nulled-script site.

7.3 The Buyer may not remove, alter, conceal or relocate the LICENSE file from the project directory, nor strip copyright headers from source files. This obligation applies to the code repository only, and does not restrict the Buyer's white-labelling rights in the user interface under clause 6.5.

7.4 The Buyer may not claim authorship or copyright over the unmodified Original Work, nor represent themselves as its creator.

7.5 The Buyer may not file, support or assist any copyright, intellectual property, trademark or ownership claim against ProjectWorlds in relation to the Original Work.

7.6 The Buyer may not grant an End Client any right to redistribute the source code. An End Client receives the use of a running service, not a code licence.

7.7 The Buyer may not use the ProjectWorlds name, logo or trademarks to market, endorse or imply endorsement of the Buyer's Derivative Work, except for factual attribution as required by clause 8.4.

7.8 Each purchase licenses one Buyer entity. Purchasing a single licence to distribute the source code to multiple independent businesses, partners or resellers is not permitted; each such entity requires its own licence.

Section 8 Derivative Works, White-Labelling & Resale

8.1 The Buyer may build and sell their own product, platform or SaaS service based on a modified version of the Software. Such Derivative Works are entirely the Buyer's own product and responsibility.

8.2 ProjectWorlds places no restriction on the Buyer using the Software to build client projects, white-label products or commercial SaaS platforms, and claims no share of the resulting revenue.

8.3 ProjectWorlds has no obligation, liability, warranty or involvement whatsoever in respect of any Derivative Work, including its performance, security, legality, availability or commercial success.

8.4 Any redistribution of the unmodified source code that ProjectWorlds has expressly permitted in writing must retain acknowledgment that the original work belongs to ProjectWorlds (www.projectworlds.com).

8.5 Where the Buyer resells access to a deployed instance, the contractual relationship is exclusively between the Buyer and their End Client. ProjectWorlds is not a party to it, offers no support to End Clients, and accepts no liability toward them.

8.6 The Buyer is solely responsible for the terms of service, privacy policy, refund policy, service levels and regulatory compliance offered to their own End Clients.

Section 9 Third-Party Components & External Services

9.1 The Software incorporates open-source components — including the Laravel framework, the Flutter SDK and a number of PHP and Dart packages — each governed by its own licence (predominantly MIT). Those licences continue to apply to those components, and nothing in this agreement overrides them.

9.2 The Software integrates with external commercial services which the Buyer must obtain and pay for independently. These include, without limitation: payment gateways (Stripe, Razorpay, PayPal and others), SMS and WhatsApp gateways, Google Maps, Firebase Cloud Messaging, AI providers (Google Gemini, OpenAI), email delivery services and cloud storage providers.

9.3 All third-party service accounts, API keys, credits and charges are the Buyer's own. ProjectWorlds supplies the integration code only. No service credits, API keys or trial accounts are included in the quoted price.

9.4 ProjectWorlds is not liable for any change, deprecation, price increase, outage or termination of a third-party service, nor for any resulting loss of functionality. Adapting the Software to a third party's breaking API change is treated as a maintenance update where reasonably practicable during the update period, and as custom development thereafter.

9.5 Hardware integrations (ZKTeco / eSSL biometric devices, IP cameras, GPS trackers, barcode scanners and printers) are supported at protocol level. ProjectWorlds does not supply hardware and cannot guarantee compatibility with every manufacturer, firmware version or model variant.

Section 10 Support & Updates

10.1 The Buyer receives one (1) year of software updates and bug fixes from the date of purchase, covering the web panel, all three mobile applications and the Windows agent.

10.2 Updates are supplied as source code packages together with a written update guide. Applying an update to the Buyer's servers is the Buyer's responsibility.

10.3 Support is provided via WhatsApp and email during business hours (Monday – Saturday, Indian Standard Time). No specific response-time service level is committed to or implied.

10.4 Support covers: defects in the Original Work as delivered, installation guidance for the one included deployment, update guidance, and clarification of documented functionality.

10.5 Support does not cover: custom feature development; code the Buyer or a third party has written or modified; server administration, hosting, DNS, SSL or email deliverability configuration; third-party service configuration or costs; training of the Buyer's staff or End Clients; data entry or migration from another system; or app store submission and review handling. These are available as separately billed services.

10.6 Free installation assistance covers one (1) production deployment only. Assistance with additional deployments is available at a chargeable cost.

10.7 Where the Buyer has modified the Software, ProjectWorlds may require the reported issue to be reproduced on an unmodified copy of the Original Work before investigating. Debugging the Buyer's own modifications is chargeable custom work.

10.8 After the one-year period, the Software continues to work in perpetuity under Section 5, but the Buyer is no longer entitled to new updates or support. Renewal, where offered, is priced separately and at ProjectWorlds' discretion.

10.9 Updates released during the period are made available for the Buyer to collect; ProjectWorlds does not guarantee that every future release will be backward-compatible with modifications the Buyer has made to the original files.

Section 11 Data Ownership, Privacy & Compliance

11.1 All data entered into a Buyer's deployment belongs to the Buyer and their End Clients. ProjectWorlds has no access to it, does not receive it, does not process it, and cannot retrieve it.

11.2 The Software transmits no data to ProjectWorlds. It runs entirely on infrastructure the Buyer controls.

11.3 Where ProjectWorlds is granted temporary server or database access by the Buyer for installation or support purposes, such access is used solely for that purpose, is treated as confidential under Section 12, and is relinquished on completion.

11.4 The Software handles personal data relating to children. The Buyer is the data controller (and their End Clients may be joint or independent controllers) for all such data. ProjectWorlds is neither a controller nor a processor of that data.

11.5 Compliance with applicable data protection law — including India's Digital Personal Data Protection Act, the EU/UK GDPR, and any local education-sector regulation — is the Buyer's sole responsibility. This includes obtaining lawful consent, issuing privacy notices, honouring data subject rights, configuring retention, and — critically — governing use of the CCTV and location-tracking features, which are supplied with technical safeguards but are configured and operated entirely by the Buyer.

11.6 The Buyer is responsible for maintaining backups of their own deployments. The Software includes backup tooling; configuring, verifying and testing restores is the Buyer's responsibility.

Section 12 Confidentiality

12.1 The source code, architecture and documentation supplied under this agreement are confidential to ProjectWorlds. The Buyer will not disclose them to any party other than those permitted under clause 6.7.

12.2 The Buyer will take reasonable measures to protect the source code from unauthorised access, including securing repositories, servers and credentials.

12.3 This quotation and its commercial terms are confidential between the parties.

12.4 ProjectWorlds will keep confidential any Buyer information, credentials or data it encounters in the course of providing installation or support assistance.

Section 13 Intellectual Property & Copyright

13.1 ProjectWorlds retains full copyright and intellectual property ownership of the Original Work. No part of this agreement transfers copyright ownership to the Buyer; the Buyer receives a licence to use, modify and deploy, not ownership of the original codebase.

13.2 Originality of this Software is established and evidenced through ProjectWorlds' publicly available GitHub repository history, YouTube channel publications, and website content at projectworlds.com and multischoolerp.com — all of which carry timestamps predating any sale or distribution.

13.3 The Buyer may modify the source code and claim ownership of their own modifications and additions only. The underlying original codebase remains the intellectual property of ProjectWorlds.

13.4 The Buyer acknowledges that ProjectWorlds is the original creator of this Software and agrees not to file any copyright, intellectual property or ownership claim against ProjectWorlds in relation to the Original Work.

13.5 ProjectWorlds' originality is verifiable through publicly timestamped records including, but not limited to, GitHub commit history, YouTube video uploads, and publication dates on projectworlds.com and multischoolerp.com.

13.6 ProjectWorlds warrants that, to the best of its knowledge, it is the author of the Original Work and is entitled to grant this licence, and that the Original Work does not knowingly infringe the intellectual property rights of any third party.

Section 14 Disclaimer of Warranty

14.1 The Software is provided "as is" without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, title or non-infringement, save as expressly stated in clause 13.6.

14.2 ProjectWorlds does not warrant that the Software will be error-free, uninterrupted, or suitable for every use case, jurisdiction, curriculum, board or regulatory regime.

14.3 The Buyer assumes full responsibility for testing and validating the Software in their specific deployment environment before relying on it in production.

14.4 No advice, information or statement — whether given verbally, by WhatsApp, by email or in marketing material — creates any warranty not expressly stated in this agreement.

Section 15 Limitation of Liability

15.1 ProjectWorlds shall not be liable for any direct, indirect, incidental, special, punitive or consequential damages arising from the use, modification or deployment of the Software.

15.2 This includes, without limitation: data loss or corruption, financial loss, loss of profit or business, security breaches, unauthorised access, regulatory penalties, legal disputes, reputational harm and service downtime.

15.3 Where liability cannot lawfully be excluded, ProjectWorlds' total aggregate liability under this agreement is limited to the amount actually paid by the Buyer for the Software (₹ 10,000).

15.4 ProjectWorlds is not responsible for any modification made to the Original Work by the Buyer or any third party after delivery. Any modified version is solely the responsibility of the party who made those modifications.

15.5 If the Buyer modifies the code and it causes errors, security issues, data loss, financial loss, legal issues or any other damage, ProjectWorlds bears no responsibility for the outcome.

15.6 Any third party who receives a modified version of this Software from a Buyer cannot hold ProjectWorlds liable for that version's performance, security or legality.

Section 16 Indemnification

16.1 The Buyer agrees to indemnify and hold ProjectWorlds, its owner and its team harmless from any claims, damages, disputes, penalties, costs or legal proceedings arising from the Buyer's use, modification, deployment, hosting or distribution of the Software.

16.2 This indemnity extends to claims brought by the Buyer's End Clients, their staff, students, parents or any regulatory authority in respect of a deployment operated by the Buyer.

16.3 This indemnity survives termination or expiry of this agreement.

Section 17 Refund Policy

17.1 No refund will be issued once the source code has been delivered. As a digital product, source code cannot be returned or un-received.

17.2 The Buyer is strongly advised to review the live demonstration, inspect the documentation and raise every question — technical, commercial and licensing — before making payment. ProjectWorlds will answer such questions without obligation.

17.3 Where payment has been received but the source code has not yet been delivered, a full refund may be requested and will be processed within a reasonable period.

17.4 A change of mind, a change in the Buyer's business plans, a lack of technical capability to install or operate the Software, or the discovery of a feature the Buyer assumed was present but did not verify, are not grounds for refund.

Section 18 Termination

18.1 The perpetual licence granted under Section 5 may be terminated by ProjectWorlds only in the event of a material breach of Section 7 (Restrictions) — in particular the unauthorised redistribution or public publication of the source code.

18.2 ProjectWorlds will give written notice of the alleged breach and allow 30 days for the Buyer to remedy it before terminating.

18.3 On termination for breach, the Buyer must cease all use of the Software and destroy all copies. No refund is payable.

18.4 Sections 12, 13, 15, 16 and 19 survive termination.

Section 19 General

19.1 This agreement is governed by the laws of India.

19.2 Any disputes shall be subject to the exclusive jurisdiction of the courts of India.

19.3 The parties will attempt in good faith to resolve any dispute by direct discussion before commencing proceedings.

19.4 Neither party is liable for failure to perform due to causes beyond reasonable control, including natural disaster, war, civil unrest, government action, internet or power failure, or the outage of a third-party service.

19.5 If any provision of this agreement is held invalid or unenforceable, that provision will be severed and the remainder will continue in full force.

19.6 A failure to enforce any provision is not a waiver of the right to enforce it later.

19.7 This quotation together with the LICENSE file supplied inside the source code package constitutes the entire agreement between the parties and supersedes all prior discussions, proposals and representations. Where the two documents differ, this quotation prevails for commercial matters and the LICENSE file prevails for code-level obligations.

19.8 Nothing in this agreement creates a partnership, joint venture, agency or employment relationship between ProjectWorlds and the Buyer.

19.9 By making payment and using this Software, the Buyer confirms they have read, understood and agreed to all terms and conditions listed here.

Licensing FAQ — In Plain English

The questions buyers ask most often, answered directly. This section is explanatory and is intended to help you understand the terms above. Where any wording here appears to conflict with Sections 1–19, those Sections govern.

Do I own the code after buying it?
You own a perpetual licence to use, modify and deploy it however you like — not the copyright to the original work. Practically, this means nobody can ever take it away from you or charge you again, but you also cannot claim you wrote it. Everything you add on top is 100% yours. (Sections 5, 6.8, 13)
Can I sell this to schools as my own product or SaaS?
YesThat is exactly what the licence is for. Rebrand it, put your own name and logo on it, host it, and charge schools whatever you want — monthly, yearly or one-time. The revenue is entirely yours. (Sections 6.4, 6.5, 8.1, 8.2)
Do I pay you a royalty, revenue share or per-school fee?
NoNever. There is no royalty, no revenue share, no per-school fee, no per-student fee and no per-server fee. The ₹10,000 is the only money that ever comes to ProjectWorlds, whether you run one school or ten thousand. (Section 6.2)
Can I remove all your branding?
YesCompletely. Product name, logo, colours, domain, emails, app names — all of it. There is no "Powered by ProjectWorlds" requirement anywhere in the interface. The only thing you must leave in place is the LICENSE file inside the code folder, which your users never see. (Sections 6.5, 7.3)
How many servers can I install it on?
Unlimited. Production, staging, development, testing, demo, disaster recovery — as many as you want, in any country. Note that free installation help covers one production deployment; further installations are chargeable, but the licence itself has no limit. (Sections 6.1, 6.3, 10.6)
Is the code encrypted, locked to a domain, or does it phone home?
NoThe source is delivered fully unencrypted and unobfuscated — no ionCube, no SourceGuardian, no compiled-only files. There is no licence key, no activation server, no domain lock, no expiry timer and no telemetry. Nothing in the Software ever contacts ProjectWorlds. (Sections 5.3, 5.4)
What happens after one year — does it stop working?
NoThe licence is perpetual. After a year you simply stop receiving new updates and support. Everything you already have keeps running forever, exactly as it did on day 365. (Sections 5.2, 10.8)
Can I resell the source code itself to another developer?
NoThis is the one real restriction. You may sell an unlimited product and an unlimited service built on the code — but not the code itself as a competing copy of what you bought. Each business that wants the source needs its own licence. (Sections 7.1, 7.2, 7.8)
Can I hire my own developer to change it?
YesAny employee, freelancer or agency you like. Give them the code access they need. They work for you and gain no licence of their own from doing so. (Section 6.7)
Do I get the mobile app source too, and can I publish under my own account?
YesAll three Flutter applications — Parent/Student, Staff/Admin and Driver — are delivered as full source. Publish them to Google Play and the Apple App Store under your own developer accounts, with your own app IDs and branding. Store fees, review and compliance are yours to handle; publishing guides are included. (Section 6.6)
Who pays for SMS, WhatsApp, Google Maps, Firebase and AI keys?
You do, directly to those providers. We supply the integration code for all of them — 32+ SMS gateways, 7 WhatsApp providers, Stripe / Razorpay / PayPal, Google Maps, Firebase, Gemini and OpenAI — but no credits or API keys are included in the price, and you connect your own accounts. (Sections 9.2, 9.3)
Who owns the school data, and can you see it?
The data belongs to you and your schools. We cannot see it. The Software runs entirely on your servers, sends nothing to us, and we have no access unless you deliberately give us temporary credentials for support — which we then use only for that purpose. (Sections 11.1, 11.2, 11.3)
Who is responsible for GDPR / DPDP compliance?
You are. Since the data never reaches us, you (and your schools) are the data controllers. That includes consent, privacy notices, retention and — most importantly — how you configure and operate the CCTV and GPS-tracking features. The Software ships with strong technical safeguards built in; the policy decisions are yours. (Sections 11.4, 11.5)
What if ProjectWorlds stops operating one day?
Nothing breaks. Because there is no licence server and no phone-home, your deployments carry on running indefinitely with no dependency on us. You would simply stop receiving updates. (Section 5.3)
How quickly do I get the code after paying?
InstantlyIf you buy online at multischoolerp.com, delivery is fully automated — the moment payment succeeds you are emailed your client-portal login and download link, normally within a minute, at any hour of the day. Nobody has to be at a desk to release it. If you pay by bank transfer instead, send us the confirmation screenshot and we release access once the credit shows. (Sections 4.2, 4.3)
What if the delivery email never arrives?
Check your spam and promotions folders first — that is where it goes in almost every case. If it is genuinely not there, message us on WhatsApp and we will provision your portal access by hand straight away. (Section 4.4)
Can I get a refund?
Before delivery, yes. After the source code has been sent, no — it is a digital product and cannot be un-delivered. Please use the live demo and ask us everything you need to know beforehand; we would much rather answer twenty questions than take a sale you regret. (Section 17)
What if I find a bug after the support year ends?
You have the complete source code, so you or your developer can fix it directly. We also offer paid support and renewal where available. Note that within the support year, if you have modified the code we may ask you to reproduce the issue on a clean copy first — otherwise we would be debugging your work rather than ours. (Sections 10.7, 10.8)
Is there a limit on schools, students or users?
NoNone whatsoever from a licensing point of view. The only limits are what your server hardware can handle. (Section 6.2)
Can I use it for colleges or coaching institutes instead of schools?
YesAdapt it for colleges, universities, coaching centres, training institutes or anything else. No further permission needed. (Section 6.9)
What if I sell my business — can the licence go with it?
YesThe licence can be transferred once, in full, as part of a genuine sale or merger of your business. Just notify us in writing, have the buyer accept these terms, and stop using your own retained copies. (Section 5.6)
Does buying this mean you'll build custom features for me?
Not as part of this price. Support covers bugs in what we shipped plus update guidance. Custom modules, integrations and design work are quoted and billed separately — and we are happy to do them. (Sections 10.4, 10.5)
10

Acceptance

Signature confirms agreement to all terms above
By signing below, or by making payment against this quotation, the Buyer confirms that they have read, understood and accepted the full Terms & Conditions set out in Sections 1 to 19 of this document, and the licence terms supplied with the source code package.

For ProjectWorlds

Yugesh Kumar Verma
Proprietor & Authorised Signatory
ProjectWorlds · contact@projectworlds.com
+91 6263056779 · www.projectworlds.com
Product: www.multischoolerp.com

Buyer Acceptance

Authorised signature
Name & designation
Company / institution & date
Quotation No.PW-ERP-2026-006
ProductProjectWorlds Multi-School ERP SaaS Script + Mobile App V3.6.0
Date of Issue20 August 2026
Valid Until19 September 2026
Total Payable₹ 10,000 (Ten Thousand Rupees Only)
DeliveryDigital download via client portal — automated and immediate on online purchase; on confirmation of credit for bank transfer

Thank you for choosing ProjectWorlds

YOUR EDTECH EMPIRE STARTS HERE · WWW.MULTISCHOOLERP.COM · WWW.PROJECTWORLDS.COM
Chat with us