We install it.You run it, with real documentation behind you.
Kenii is implemented by our team, not shipped as a self-serve trial you configure alone. Every catalog year, credential structure, and brand setting is in place before your staff logs in, and your catalog coordinator gets a documentation library built for someone who edits a catalog, not a developer, backed by real people when a page does not have the answer.
Every Kenii site starts with a real person configuring it, not a self-serve trial you configure alone.
That is how implementation actually goes.
We install it and configure it. Then we hand you a system you already know how to run.
-
Migration
We import your existing catalog into Kenii's structure, program by program and course by course, so your team's first login is to real content, not an empty admin.
-
Configuration
Your catalog years, your branding, your credential structure, and your taxonomies are set up before anyone on your staff opens the dashboard for the first time.
-
Training
A single guided session walks your catalog coordinator through publishing a change, adding a credential, and finding an answer in the documentation before they need it.
-
Go live and support
Your catalog opens to students backed by a documentation library and a support team that answers, not a ticket queue that goes quiet.
Every answer is one search away,
written for a coordinator.
Kenii’s documentation is organized the way you actually think about the catalog: get started, complete a task, look up a field, or understand why something works the way it does. No API reference to translate and no developer detour.
Programs
48 programs in the catalog · 2026 to 2027
Edit a course yourself.
Publish it without a ticket.
The same admin your team trains on is the one they use every day. Update a description, add a credential, or change a prerequisite in a form built for plain language, then publish it, with the documentation open in the next tab if you want a reminder.
Associate in Nursing
WHERE IT LEADS
Four kinds of answers, not one wall of text.
Learn the admin by doing, start to finish, the first time you log in.
One task, one answer: publish a catalog year, add a credential, export a PDF.
Every field, every setting, every shortcode, described exactly as it appears in your admin.
Why the connected data model works the way it does, so a change you make behaves the way you expect it to everywhere else.
The commitment behind the documentation.
Installed and configured by us
Your Kenii site does not arrive as a blank plugin waiting to be assembled. We migrate your catalog, set your branding, and configure your catalog years before your team’s first login.
One training session, not a semester
Editing a course, adding a credential, or changing a plan of study takes a few clicks in an interface built for a catalog coordinator. Most institutions are self-sufficient after a single session.
Real people behind the documentation
When the documentation does not answer it, a real person on our team does. Ongoing support is part of implementation, not an upsell you discover later.
A library that grows with the platform
As Kenii adds capability, the documentation adds the how-to guide, the reference entry, and the explanation with it, so your team is never running ahead of the manual.
We have had so much positive feedback about the catalog. Kudos to you.Erica Caracoglia Catalog Coordinator Martin Community College
Questions institutions ask.
- How long does implementation take?
- Implementation scales with the size of your catalog. Most institutions are live within a few weeks of signing, with your existing content migrated and your branding configured before day one.
- Who does the migration, us or you?
- We do. Your existing catalog content comes into Kenii’s structure, program by program and course by course, so your team’s first login is to a working system, not a blank one.
- Is the documentation public, or only for customers?
- The documentation library ships inside your Kenii admin and stays with your license, organized as tutorials, how-to guides, reference entries, and explanations, so the answer to how you do this is always in the same tab as the work.
- What happens after training, if we get stuck?
- You reach a real person. Ongoing support is part of every Kenii package, not a separate line item you discover later.
- Does our team need to be technical?
- No. The documentation and the admin are both built for a catalog coordinator, not a developer. Most institutions are self-sufficient after a single training session.
You install nothing.You run everything.
Request a demo and we will stand up a Kenii site with your logo and your colors, running on demo catalog content, yours for fourteen days, with the same documentation library your team would use on day one. At the end we talk, then send a written quote your purchasing office can act on.
Nothing to sign to get the demo site.