Skip to content

The promise on the front page, and the machine that keeps it.

What the school owns, where the files live, whose account the money settles into, and what happens if we stop. Then the drawing: an API-first platform that describes itself, so the systems you buy after us can read it without asking us anything.

← Back to the prospectus

Yours01

Your data belongs to you —
records, address, and the money.

  • Your records export whole — CSV, PDF, JSON — on any ordinary Tuesday.
  • Your web address stays yours, on your own certificate.
  • Payments settle into your school's account. They never pass through ours.
  • Every action is written down — who did it, when, and what it changed.
  • Your documents and your AI keys stay in your account, not pooled in ours.

Privacy is a setting, not a policy page

Every AI capability switches on and off per school, and whole classes of record can be held out of every prompt — a school that never wants a child-linked record in an AI context sets that once. Provider terms are no-training and minimal-retention, sub-processors are published, and document reads are audited.

Your files can live in your own bucket

Documents can be held in the school's own encrypted S3 bucket — AES-256, public access blocked, download links that expire in minutes, an access log stamped with who and from where. Custody is recorded per file, so a school can move where the bytes live without moving what they mean.

Or in your own building

For a school whose board wants the whole thing inside its own account or its own racks, we build that — and we build the maintenance rails with it: patching, backups, monitoring, and a tested restore. It is an engagement rather than a download, and the platform is the same one either way.

And if we stop, you still have it

If 1EDU ever ceased operating, schools get a 90-day export window with a person helping. Deactivation preserves the record; closure schedules a clean, retention-compliant disposal. No lock-in by friction.

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

{
    "name": "1EDU",
    "tagline": "The technology office for small educational institutions",
    "api": {
        "base": "https://1edu.app/v1",
        "access": "private",
        "intake": "https://1edu.app/v1/intake"
    },
    "modules": [
        "advancement",
        "learning",
        "curriculum",
        "operations",
        "reporting",
        "ai",
        "workspace",
        "requests"
    ],
    "mcp": {
        "endpoint": "/mcp",
        "domain": null,
        "url": "https://1edu.app/mcp",
        "status": "live",
        "transport": "streamable-http",
        "auth": "Bearer token (same ApiClient tokens as the REST API)"
    },
    "how_to_get_access": "Provisioned with an engagement — start with a conversation."
}
  • AVersioned REST at /v1 — anything you can click, your systems can call.
  • BAgents drive the same surface over MCP: same permissions, every action audited.
  • CYour data exports whole — CSV, PDF, JSON. Leaving is a feature, not a fight.

General notes

  1. Every capability exists as a versioned API before it gets a screen — the interface is a client, never a cage.
  2. This sheet describes itself: the manifest above is served live by the platform it documents.
  3. The MCP surface ships alongside the API, so the assistants your staff already use can drive the same records.
  4. Tenancy is per-institution, never per-seat — the whole staff works, the price doesn't move.
Project1EDU Platform
Drawn byJ. Connor
Date2026.09
RevB
ApprovedPending your first conversation