1EDU.app

№ 01 — The Platform

A whole technology office, for schools that can't hire one.

Small educational institutions run on spreadsheets, memory, and one overworked administrator. 1EDU is the operating platform that replaces the patchwork — with AI working the desk.

Start with an assessment →
Cutaway illustration of a small schoolhouse, each room a working department
01 Advancement Donors, grants, and the CRM — the whole development office in one view.
02 Learning Staff training, knowledge base, and video — with expiry-aware certifications.
03 Curriculum Versioned units mapped to outcomes; the accreditation evidence pack, always current.
04 Operations SOPs, forms, automations, and documents — how the school actually runs.
05 Reporting KPIs and board packets computed from the record, not rebuilt for it.
06 AI Grant drafts, policy watch, and a staff assistant that cites its sources.

№ 02 — The Method

Software second.
Assessment first.

Every engagement begins the same way: we sit with how your institution actually works, and we write it down. What comes back is not a sales pitch — it's a plan.

Line illustration of a surveyor's folded map with a plotted route
  1. Current-state technology assessment
  2. Business process assessment
  3. AI opportunity assessment
  4. Systems architecture — current and target
  5. Software recommendations, alternatives included
  6. Implementation priorities
  7. Integration plan
  8. Budget estimates in ranges, not false precision
  9. Multi-year technology strategy
  10. Board-ready executive summary

If the roadmap recommends our platform, you'll see the scoring that got it there. If it recommends someone else's — or keeping what you have — it says so. The fee is never contingent on choosing us.

Request an assessment

№ 03 — The Architecture

API-first. AI-first.
Self-describing.

Every capability on this platform exists as a versioned API before it gets a screen. Your data is never trapped behind our interface — anything you can click, your systems (and your agents) can call.

The MCP surface ships alongside the API, so the assistants your staff already use can drive the same records, under the same permissions, with every action audited.

  • Interface REST, versioned at /v1
  • Agents MCP, same auth, same audit trail
  • Tenancy per-institution, never per-seat
  • Exit full export — CSV, PDF, JSON

GET /.well-known/1edu.json — live now, generated from platform config:

{
    "name": "1EDU",
    "tagline": "The technology office for small educational institutions",
    "api": {
        "base": "https://www.1edu.app/v1",
        "health": "https://www.1edu.app/v1/meta/health",
        "intake": "https://www.1edu.app/v1/intake"
    },
    "modules": [
        "advancement",
        "learning",
        "curriculum",
        "operations",
        "reporting",
        "ai"
    ],
    "mcp": {
        "endpoint": null,
        "status": "planned"
    }
}