# Escolia

> Escolia is a school management SaaS with full source code, built for multiple educational institutions with isolated records.

Source page: https://saascode.ai/products/escolia
Machine-readable record: https://saascode.ai/products/escolia.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $249 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

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.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/escolia — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://escolia.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

6 roles seeded on the demo (of the 8 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Guardian** (`guardian`) — `guardian@demo.com` / `see the page`
  Reviews linked students' schedules, results and messages.
- **School director** (`org_admin`) — `org-admin@demo.com` / `see the page`
  Runs one institution across academics, staff and settings.
- **School secretary** (`secretary`) — `secretary@demo.com` / `see the page`
  Manages enrollment, attendance, tuition and family records.
- **Student** (`student`) — `student@demo.com` / `see the page`
  Reviews their own timetable, results and allowed messages.
- **Teacher** (`teacher`) — `teacher@demo.com` / `see the page`
  Captures attendance and grades for assigned classes.
- **Platform owner** (`super_admin`) — `admin@demo.com` / `see the page`
  Runs institutions, plans, integrations and cross-school oversight.

Or open a role directly: https://saascode.ai/demo/escolia?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 8** — distinct roles accepted by the role CHECK constraint: admin, guardian, member, org_admin, secretary, student, super_admin, teacher
- **tables: 94** — distinct CREATE TABLE statements across every applied migration
- **migrations: 118** — .sql files in supabase/migrations
- **page modules: 107** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 200,394** — lines of code (comments and blank lines excluded) across 1265 TypeScript files (174,945) and 145 SQL files (25,449); node_modules and .next excluded
- **api route files: 251** — files named route.ts under src/app/api
- **http operations: 347** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 94 tables, 198 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-21

## Complete capability inventory

13 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### School records & access

- **Core student/guardian/staff record** — 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.

### Academic operations

- **Academic structure, enrollment, attendance and grading** — Years, terms, levels, courses, divisions and subjects, each with capacity. This is the skeleton every other academic feature hangs from — a division is what a teacher is assigned to, and what a timetable entry and an attendance session belong to.
- **Manual timetable + collision detection** — The timetable can be built by hand, with collisions flagged immediately as you edit — a teacher in two places at once, a room double-booked, a division scheduled against itself.
- **Timetable suggestions** *(seller-authored)* — Runs timetable suggestions as persisted jobs that keep their constraint version, seed, state and best result so far. Staff can leave a run, return later, compare alternatives and inspect the remaining violations before choosing a result.

### Tuition & collections

- **Tuition subledger + cash/transfer recording** *(seller-authored)* — Records charges, fee plans, installments, late fees, waivers, receipts, allocations and family statements in the product's receivables subledger. A payment provider remains a collection rail rather than the source of truth for what a family owes.
- **Pending-balance staged import** — Institutions that arrive mid-year already have families who owe money. This product includes a staged import for pending balances on every plan: upload, preview, see per-row errors, then commit explicitly. Collections cannot start safely without opening receivables, so this is not treated as a premium migration feature. Importing historical grades, attendance and other legacy records is a depth feature of the middle and top plans.

### Communications & portals

- **Family/student portals, communications, standard reports** — Institution and course announcements go to an audience and track acknowledgement, so a director can see who has actually seen a notice rather than assuming. Teachers and families hold authorized threads about a specific student, and only the people connected to that student can take part.

### Reports & integrations

- **Advanced reports** *(seller-authored)* — Adds cohort comparisons, scheduled exports and advanced reporting dimensions for institutions on higher plans. It extends the standard reports already included across the product without changing the underlying academic and financial records or their access rules.
- **History imports** *(seller-authored)* — Brings historical grades, attendance and other legacy records into the institution through staged adapters. It is separate from the pending-balance import that every plan receives and is available as a higher-plan depth capability.

### Privacy & audit

- **Advanced audit exports** *(seller-authored)* — Extends audit and rights-case export depth for institutions on the top plan. The base audit remains available below it, while sensitive operator reads continue to require a stated purpose and produce immutable access evidence.

### Academic operations — structure, enrollment, attendance, grading, report cards, timetable

- **Custom report cards (Report cards from configured institution templates with immutable issue snapshots)** *(seller-authored)* — Report cards from configured institution templates with immutable issue snapshots

### Other

- **Online tuition payments (Online tuition payment reconciliation through configured provider callbacks)** *(seller-authored)* — Online tuition payment reconciliation through configured provider callbacks
- **SSO integrations (OAuth sign-in with native providers and gateway-backed OIDC providers)** *(seller-authored)* — OAuth sign-in with native providers and gateway-backed OIDC providers

## What each system gives the operator

*stated.*

- **School records & access** — Keep each institution's people connected without crossing school or family boundaries.
- **Academic operations** — Run the academic year from enrollment through published records without losing history.
- **Tuition & collections** — Track what families owe and reconcile every payment against the institution ledger.
- **Communications & portals** — Give staff and families a shared record of notices, conversations and reports.
- **Reports & integrations** — Extend reporting and access as institutions grow into higher operating tiers.
- **Privacy & audit** — Make sensitive access and rights-case outcomes explainable from immutable evidence.
- **Academic operations — structure, enrollment, attendance, grading, report cards, timetable** — 

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### 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.

### 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.

### 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.

### 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.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **A Node host and a Supabase project** (required) — The application declares Next 16.2.10 and React 19.2.3. Supabase supplies its database, authentication and storage.
- **A scheduled runner** (required) — Six jobs are declared in `vercel.json`. On another host, those schedules must be wired to the shipped endpoints.
- **An email delivery provider** (required) — Choose one of the shipped Brevo, Mailgun, Resend, SendGrid or SMTP providers for transactional email.
- **Upstash** (optional) — The example environment exposes Upstash configuration for deployments that use the hosted integration.
- **Sentry** (optional) — The example environment exposes Sentry configuration for deployments that want external error monitoring.

## FAQ

**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.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Escolia: an operating system for educational institutions](https://saascode.ai/inside/road-to-escolia.md)
- [Escolia vs PowerSchool: Own the Product or Use the Managed SIS](https://saascode.ai/inside/escolia-vs-powerschool-source-ownership-managed-sis.md)
- [School Management Software in 2026, Organized by the Record at the Centre](https://saascode.ai/inside/school-management-software-2026-record-ownership.md)

## Links

- Catalog page: https://saascode.ai/products/escolia
- Product record: https://saascode.ai/inside/products/escolia
- Live demo: https://escolia.saascode.ai
- Every product: https://saascode.ai/llms.txt