Backend and security foundation
Authentication, MFA challenge, JWT sessions, refresh/logout, BCrypt hashing, tenant/school access guards, audit logging, and production fail-fast checks exist.
Public brand: MyCloudCampus · Product: CloudCampus
AI-ready multi-tenant School ERP SaaS for controlled demos and staging validation.
CloudCampus is the School ERP product by MyCloudCampus, built with a Spring Boot backend, React/Vite web portal, PostgreSQL, Docker deployment assets, role-based access, tenant isolation, audit logging, and school operations workflows.
Honest status: CloudCampus is staging-ready for controlled deployment recreation and internal demo use. It is not yet paid-production ready. Stable HTTPS staging, SMTP delivery, object storage, payment gateway integration, monitoring, backup/restore proof, and production hardening are still pending.
Platform
Built as a serious School ERP product, with boundaries clearly marked.
The product has real backend and frontend implementation evidence, but the page intentionally separates verified functionality from partial workflows and production hardening work.
API-backed web portal
The React/Vite portal connects role navigation to real APIs through a shared HTTP client instead of presenting fake production data.
Deployment-oriented repository
Dockerfiles, local/staging/production Compose files, Nginx config, health checks, rollback docs, and staging runbooks are present.
Modules
School ERP scope without inflated claims.
These modules are taken from the CloudCampus README and audit reports. Verified means the repo has stronger proof; partial means API-backed foundation exists but UX or production readiness still needs work.
Verified foundation
Authentication, tenant onboarding, school access, academic setup, staff/teacher provisioning, student import, dashboards, and audit logs have stronger repo proof.
School Admin workflows
Students, parents, staff, academic setup, fees, attendance, homework, exams, notices, reports, documents, website content, settings, and imports are represented in the portal.
Teacher and classroom flows
Teacher dashboard, assignments, attendance, homework, exams, marks, timetable, and notices are API-backed, with UX polish still needed in places.
Parent and student portals
Child-linked attendance, homework, results, fees, notices, timetable, leave, profile, and student self-service foundations exist.
Finance and reporting
Fee demands, payments, receipts, finance reports, report export foundation, and revenue views exist, while payment gateway and durable file delivery remain pending.
AI-ready foundation
AI entitlement, usage audit, and scoped retrieval foundations exist; advanced AI/RAG execution is still roadmap work.
Source proof
The proof today is the CloudCampus repository and audit docs.
No fake screenshots, customer logos, testimonials, or paid-production usage claims are shown here. Screenshots are planned in the CloudCampus repo but not committed as real assets yet.
README
Product source
CloudCampus README documents stack, roles, feature matrix, readiness status, staging smoke evidence, and roadmap.
Audit
Feature completion report
The audit lists verified, partial, hardening-needed, and not-production-ready areas with validation command evidence.
Smoke
Staging smoke evidence
Disposable EC2 HTTP smoke verified health, frontend, Super Admin login/MFA, onboarding, invitation acceptance, academic setup, student import, and logout.
Readiness
Production readiness
The readiness report marks CloudCampus as staging-ready for recreation, not paid-production-ready.
Status
Clear implemented-vs-roadmap language.
This product page mirrors CloudCampus README and audit reports instead of presenting controlled-demo features as paid-production software.
Local and internal demo
CloudCampus is suitable for local demos and controlled internal validation with demo data.
EC2 HTTP staging smoke
A disposable EC2 HTTP smoke passed and was then terminated to avoid ongoing cost; there is no permanent public staging URL claimed here.
Before pilot
Stable HTTPS staging, rotated secrets, disabled shared bootstrap, SMTP, backup/restore proof, monitoring, and School Admin UX hardening are still needed.
Paid production
Payment gateway, object storage, managed database, provider delivery, observability, production secrets, and customer-grade UX are not complete.
Contact
Email About CloudCampus
Discuss a controlled demo, school workflow, or pilot-readiness path.
Use email for CloudCampus product questions, school workflow feedback, architecture discussion, or future pilot interest after stable staging proof is complete.