Escolia
Escolia is a school management SaaS with full source code, built for multiple educational institutions with isolated records.
Escolia is the operating system for an educational institution. One deployment serves many institutions; each institution keeps its people, academic operations, tuition and family communication in a single isolated record. A guardian or student can participate in more than one institution without their records being merged.
Every academic decision stays connected from enrollment to the final record.
A school year becomes fragile when enrollment, attendance, grading and schedules live as separate conversations. Staff spend their time reconciling names, dates and versions instead of running the institution. A move between divisions reaches one team but not another; an attendance correction arrives after a report was prepared; a timetable conflict is discovered when two groups are already waiting. The immediate cost is rework, but the deeper cost is trust: teachers stop relying on the record, families receive conflicting answers and directors cannot tell which version is current when a consequential decision must be made.
- Academic structure, enrollment, attendance and grading
- Manual timetable + collision detection
- Timetable suggestions
- Custom report cards (Report cards from configured institution templates with immutable issue snapshots)
Families see one balance, and every collection closes against the same record.
Collections become contentious when the amount a family sees is different from the amount the office is chasing. A payment may exist in one provider, a cash receipt in a notebook and an opening balance in a spreadsheet, leaving the secretary to explain a number nobody can reconstruct. The disagreement then spreads: reminders go to the wrong family, a paid installment still appears overdue and month-end reporting requires manual reconciliation. The cost is more than administrative time. It weakens confidence in every financial conversation the institution has with families and makes ordinary follow-up feel like a dispute.
- Tuition subledger + cash/transfer recording
- Pending-balance staged import
- Online tuition payments (Online tuition payment reconciliation through configured provider callbacks)
Each person sees the right institution, student and responsibility.
School data is difficult because the same person can stand in several relationships at once. A teacher may also be a guardian, a family may have children in different schools and an operator may support many institutions without belonging to any of them. If those boundaries are only conventions, the product forces staff to choose between blocking legitimate work and exposing records too broadly. The failure is rarely dramatic at first; it appears as a wrong student in a list, an unexplained document view or a director seeing beyond the institution they run. Each one is expensive to investigate and harder to explain after the fact.
- Core student/guardian/staff record
- Family/student portals, communications, standard reports
- Advanced audit exports
Growing schools add operational depth without replacing their system of record.
A school usually outgrows its first reporting process gradually, then all at once. Leadership asks for comparisons across cohorts, historical records arrive from an older system and identity requirements become part of a larger technology policy. Treating each request as a separate side project creates a second operating layer beside the product: spreadsheets that only one person understands, exports with no consistent meaning and access work that drifts from the institution's actual roles. The cost compounds with every new school and every reporting cycle, because the team spends more time maintaining the bridge than using the information it was meant to provide.
- Advanced reports
- History imports
- SSO integrations (OAuth sign-in with native providers and gateway-backed OIDC providers)
There are two planes, and they never overlap.
**The operator plane (/admin/*) belongs to whoever runs this deployment. It provisions institutions, assigns plans, supports them, and holds a cross-institution mirror of every domain area: students, guardian links, academic structure, enrollments, attendance, grading, report cards, timetables, tuition, communications, staff, conduct, school reports and privacy cases. Alongside those sit the platform surfaces — organizations, users, plans, feature flags, analytics, integrations, automation, audit log, translations, content, API keys and the admin assistant.
The institution plane (/app/*)** belongs to the school. Everything here is scoped to one institution, and for families and students it narrows further to the students they are actually connected to.
Suggestions run as persisted jobs rather than as something you wait on in a browser tab. A job keeps its constraint version, its seed, its state and its best result so far, with the remaining violations explained. You can leave it, come back, compare runs and take the best one.
Publishing is a single transactional step that re-checks the current constraints before it commits and creates a new timetable version. Publishing never silently accepts a schedule that stopped being valid while the job was running.
Timetable suggestions are available from the middle plan up. Manual editing with collision detection is available on every plan.
Suggestions run as persisted jobs rather than as something you wait on in a browser tab. A job keeps its constraint version, its seed, its state and its best result so far, with the remaining violations explained. You can leave it, come back, compare runs and take the best one.
Publishing is a single transactional step that re-checks the current constraints before it commits and creates a new timetable version. Publishing never silently accepts a schedule that stopped being valid while the job was running.
Timetable suggestions are available from the middle plan up. Manual editing with collision detection is available on every plan.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 81 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 94 tables, as text
academic_terms · academic_units · academic_years · active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assessment_results · assessments · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · attendance_corrections · attendance_records · attendance_sessions · audit_logs · automation_log · automation_templates · charge_installments · communication_campaigns · communication_recipients · conduct_records · credit_balances · credit_transactions · currencies · data_exports · data_imports · domain_jobs · enrollment_events · enrollments · faq_categories · faq_items · feature_flags · fee_plans · grading_policy_versions · guardian_student_links · inbound_webhook_events · inbound_webhooks · institution_memberships · institution_policy_assignments · languages · marketing_audience_members · marketing_audiences · message_threads · messages · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · payment_allocations · payment_event_inbox · payment_receipts · plans · platform_secrets · platform_settings · privacy_cases · privacy_policy_packs · processing_purposes · product_purchases · products · provider_prices · push_devices · report_card_issues · report_card_templates · report_templates · roles · scheduled_tasks · sensitive_access_events · seo_meta · staff_profiles · student_charges · student_sensitive_records · students · subscriptions · teaching_assignments · theme_page_sections · theme_section_library · theme_sections · timetable_constraint_sets · timetable_entries · timetable_jobs · timetable_versions · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 3 required, 2 optional.
The application declares Next 16.2.10 and React 19.2.3. Supabase supplies its database, authentication and storage.
Six jobs are declared in `vercel.json`. On another host, those schedules must be wired to the shipped endpoints.
Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP providers for transactional email.
The example environment exposes Upstash configuration for deployments that use the hosted integration.
The example environment exposes Sentry configuration for deployments that want external error monitoring.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 200,394 lines across the application and its database, 94 tables defined by 118 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Escolia demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 6 of them: Guardian, School director, School secretary, Student, Teacher, Platform owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 107 page modules and 347 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A scheduled runner, An email delivery provider. Optional: Upstash, Sentry. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 118 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $249?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.