©2026 Gozie Victor Ene. All Rights Reserved
Senior .NET engineer and solution architect building scalable enterprise, cloud, mobile, data-intensive, and distributed systems.
Kobzira is a school safety and attendance platform designed around a simple idea: attendance should provide more trustworthy information than a checkbox beside a student’s name.
The platform is intended to connect identity verification, school arrival and departure, class or activity attendance where required, authorized pickup, guardian permissions, and real-time communication so schools and parents have a clearer record of who arrived, who left, when it happened, and who was involved in the handover.
Technology: C# · .NET · ASP.NET Core · Blazor Server · .NET MAUI · Android verification client/API · SQL Server · Entity Framework Core · Azure Blob Storage · Azure Service Bus · CQRS/MediatR where justified · Biometric facial verification · ASP.NET Core Identity
Facial verification is an important part of Kobzira, but it should not be the only way a school can safely verify a pickup.
The platform is designed to support guardian-controlled fallback or additional verification factors. For example, a guardian can generate a short pickup code that an authorized person presents to school staff. Staff can enter the code during the handover workflow, and the system validates that the code belongs to the expected child or children and is still valid.
The purpose is not to weaken biometric verification. It is to provide explicit, auditable alternatives for real-world situations where a face cannot be reliably verified or a guardian wants an additional factor.
Kobzira is being designed as a modular monolith with strong domain boundaries rather than a microservices-first system.
That gives the product a simpler deployment and operational model while the domains are still evolving, without giving up separation between attendance, identity, guardians, pickup authorization, notifications, subscriptions, and school administration.
Asynchronous messaging can still be used selectively for events such as notifications, audit workflows, or integrations where decoupling is useful. The architecture should become distributed only where independent scale, fault isolation, or deployment boundaries justify the cost.
A child-safety workflow should degrade safely when technology is uncertain.
©2026 Gozie Victor Ene. All Rights Reserved