Meet Mark

Meet the people behind Mark.

Mark was founded and is built by Kenny Allman, with advice, feedback, and pilot support from people who care about teaching, software, security, and fair records.

People behind Mark

Kenny Allman

Kenny Allman

Founder

Assistant Professor of Cybersecurity at Garrett College, with 40+ years of programming, systems, and network experience applied to classroom tools.

For Mark: brought the original classroom problem to Mark and keeps the tool grounded in real teaching workflows.

Quiet superpower: Can actually work on only one thing at a time.

Leo Edmiston-Cyr

Leo Edmiston-Cyr

Informal Advisor

Brings a physics and instrumentation background and decades of software, network engineering, monitoring, and security experience to systems that fit the people who use them.

For Mark: offers occasional advice on architecture, reliability, and user-aware design choices that support different learning and working styles.

Quiet superpower: Spots the one assumption everything else depends on.

Sean Kline

Sean Kline

Feedback Contributor

Came up through a traditional Computer Science B.S. path and has been designing and crafting software daily since the 1990s.

For Mark: has provided feedback on accessibility, user experience, and front-end implementation choices.

Quiet superpower: Builds today's code so tomorrow has fewer surprises.

Zachary Krisher

Zachary Krisher

Pilot Supporter

Associate Dean of Academic Affairs at Garrett College, working on student success, academic scheduling, and programs that connect the college with local schools and the wider community.

For Mark: has supported conversations about institutional fit, pilot planning, and the academic questions programs need answered.

Quiet superpower: Turns fast thinking into words normal humans can use.

Professional affiliations describe individual experience and do not imply institutional endorsement of Mark.

Perspectives that support pilots

A Mark pilot should be easy to understand before anyone commits to a wider rollout. Advice, feedback, and pilot conversations help connect the product mechanics to the teaching, program, and security questions institutions naturally ask.

Teaching fit Does Mark support the way instructors already run classes and assignments?
Program fit What would a small department or multi-section pilot need to prove?
Trust fit What data, sign-in, privacy, and support questions should be answered early?

Want to talk through a pilot?

Tell us what your program needs to verify and what would make a pilot useful.

Request a pilot demo