Korsys

The operating system for facilities teams. Built AI-native from the ground up — not bolted on top.
Request pilot access → See Hopper live →
AI-native CMMS Work order AI Operational memory Autonomous tools Monitoring twin Predictive maintenance AI-native CMMS Work order AI Operational memory Autonomous tools Monitoring twin Predictive maintenance
// The AI inside Korsys Live

Meet Hopper.

The chat surface inside Korsys. Speaks plain English, confirms before it acts.

What Hopper does →
// Architecture

Three layers. Built on top of each other.

Korsys isn’t a feature list bolted onto a CRUD app. Three reinforcing systems — each ships a real product, each makes the next one stronger.

I.
Layer one
The Brain
Institutional memory the model speaks with.
Every conversation builds an operational knowledge graph. Confidence grows with corroboration. Stale facts decay. New techs onboard against decades of memory from day one — and senior techs retire without taking it with them.
II.
Layer two
The Twin
A digital model running in parallel with the real plant.
Watches sensor streams, ticket throughput, and PM compliance — and flags developing problems before they surface as failures. A chiller drifting. A building running hot. An asset overdue by enough days to matter.
III.
Layer three
The CMMS
Maintenance software designed for the model, not the form.
From "AI on top of your CMMS" to AI-native CMMS itself — tickets, assets, PMs, contracts, time, parts, all chat-first. Existing integrations stay. The destination is software that fits how maintenance actually runs.
Brain accumulates → Twin acts → CMMS records
// Why we’re building this

Facilities ops still runs on systems built before the cloud.

Universities, hospitals, and campuses run on software designed before AI existed — tickets, portals, spreadsheets, knowledge locked in one person’s head. The next platform isn’t a CMMS with AI bolted on top. It’s AI-native from the ground up.

Built by the people who do the work. Decades on the trades side of facilities ops — not vendors writing about a job they’ve never done.

// Roadmap

From assistant to operating system.

Seven milestones. Four shipped, one shipping now, two on deck. Each one makes the next one possible.

// 01 Shipped
Hopper Chat
2026 · Q1 / Q2
// 03 Shipped
Native CMMS shell
2026 · Q2
// 05 Next
Vendors & Contracts
2026 · Q4
// 07 Future
Monitoring Twin
2027 +
// 02 Shipped
Operational Memory
2026 · Q2
// 04 Shipping
Mobile + Polish
2026 · Q2 / Q3
// 06 Next
Multi-CMMS Connectors
2027
// 01
Tenant-isolated
Each customer’s data lives in its own scope. Cross-tenant queries aren’t possible.
// 02
Audit-logged
Every state change writes an immutable record — user, time, before, after.
// 03
Confirm-first AI
Hopper never edits your system of record without an explicit OK.
// 04
FERPA-aware
Higher-ed data sensitivity baked in from day one. Per-tenant gating where it matters.
// Pilot Access

Have a pilot key?

Enter it to reach the live build. Don’t have one? Pilots are running with select higher-ed facilities teams — talk to us.

// AUTH_FAILED · INVALID KEY
Korsys · Pilot build · v1