Request a branded demo

Modules

Catalog Pathways Curriculum Board Essentials Free Assist Coming soon

Catalog

Digital catalog Program pages Courses Search Publishing workflow

Pathways

Career exploration Wage data Program outcomes Student discovery Transfer articulation

Curriculum

Proposals Approvals Vote records Evidence archive Catalog year lifecycle
Capabilities MCP Coming soon API and exports Integrations College branding
Platform overview How the modules share one record, and why that matters at publish time.
Packages Compare Catalog Pathways Curriculum Academics
Academic Affairs Catalog governance Curriculum approvals Accreditation evidence
Catalog & Curriculum Teams Publishing workflow Course and program updates Version control
Enrollment & Marketing Program discovery Career outcomes Search and conversion
Information Technology WordPress ownership Data exports SIS compatibility AI and API readiness
Need help choosing? Tell us what is hardest to manage today and we will recommend a package and setup path. See it in your own colors Request a demo We stand up a full Kenii site carrying your logo and colors, loaded with demo catalog content, so your team can click through the real thing instead of watching a slide deck.

Proof

Why colleges choose Kenii Compare with incumbents Customer stories
Documentation

3.15.2

The groundwork for letting a site make its own record numbers is now tested end to end, and the data layer has a test that any storage engine must pass. Nothing a visitor or an editor sees changes.

  • Changed **Kenii can now be tested with a site making its own record numbers for 35 kinds of record.** A new check creates, reads, changes, trashes, restores and deletes each kind both ways and compares the two. Sites keep their current WordPress numbers; the setting stays off.
  • Changed **Looking up a contact or role that has no record answers "none" instead of hiding a real storage error.** Only a missing entry in the identity map is treated as "none" now.
  • Changed **A shared storage test now runs against the WordPress store and a standalone SQLite store.** It records four places where the WordPress store would silently shorten or zero a bad value, so they can be fixed in a later release.