Team

The people shaping Liminal.

Liminal is built by a small founding team focused on practical AI, customer clarity, imagination, and the operating discipline needed to turn ideas into working systems.

NK
Founder & Systems Architect

Nicholas Krut

Leads product direction, software architecture, AI systems, and the technical foundation behind Liminal.

View profile
EK
Chief Imagination Officer

Ezri Krut

Helps keep the product understandable, creative, and welcoming for people who are starting with an idea.

View profile
KK
Chief Operating Officer

Kelsey Krut

Runs operations, customer support, events, follow-up, and the practical process that keeps Liminal moving.

View profile
These profiles describe the founding roles behind Liminal while keeping the operating structure clear for customers who need to understand who owns product, imagination, operations, and delivery.
Leadership

CEO & Founder

Sets product direction, narrative standards, deployment philosophy, and the operating constraints that keep the system aligned to its identity.

Board

5 strategic oversight members

Provides governance, capital discipline, strategic pressure-testing, and long-horizon oversight across growth and infrastructure decisions.

Sales team

Client onboarding and growth

Qualifies inbound demand, shapes deployment expectations, coordinates onboarding, and keeps revenue discussions tied to practical fit.

Development team

Core system engineering

Builds the application layer, interaction behavior, page system, integration surface, and the logic that governs continuity and response quality.

Infrastructure team

Uptime, failover, and deployment

Maintains service reliability, region strategy, deployment health, failover readiness, and performance at the GPU and storage layers.

How the team page is structured

The founder profiles show the people and their contributions. The role groups show the operating coverage customers rely on after a deployment begins.

Next step

The team structure matters when the system is running on your site.

If you need to understand who covers architecture, uptime, onboarding, and product direction, the deployment review is where that mapping becomes specific.

Use Liminal to map out your future