ClockTron — Gozie Victor Ene

Senior Software Engineer · Solution Architect · .NET Specialist

Senior .NET engineer and solution architect building scalable enterprise, cloud, mobile, data-intensive, and distributed systems.

Mail Us [email protected]

Based In Based in Nigeria · Open to international, relocation, and remote opportunities.

ClockTron is a workforce time-and-attendance platform I’m currently designing and building.

The product is intended to give organizations several ways to verify attendance without forcing them into a single proprietary device model: a tenant-managed Android verification kiosk, employee mobile access, facial verification with liveness controls, geofencing, fallback verification methods, real-time attendance dashboards, and reporting.

The goal is to combine reliable attendance evidence with a SaaS experience that a business can set up and operate without a complex on-premise deployment.

Technology: C# · .NET · Blazor · ASP.NET Core Web API · .NET MAUI · Android · SQL Server · Entity Framework Core · ASP.NET Core Identity · Biometric facial recognition · Geofencing · Azure Blob Storage / Service Bus where appropriate

Hosting direction

ClockTron is being designed to remain cost-conscious at the application-hosting layer while still using cloud services where they provide clear value.

The primary web application and SQL Server database can run on myASP.NET shared hosting, while services such as Azure Blob Storage, Service Bus, Functions, or monitoring can be introduced selectively instead of making expensive platform services a prerequisite for the first version.

Product surfaces

Tenant Admin Web — Blazor-based configuration, employee management, dashboards, reporting, subscriptions, and policy controls.
Tenant Verifier — Android kiosk/verification application for face-based attendance and controlled fallback verification.
Employee Mobile — .NET MAUI application for employee-facing attendance and related workflows.
Main Admin Web — SaaS administration, tenant management, plans, support, and platform-level controls.

Current MVP dashboard language

Expected Today
Present
Late
Absent
Needs Attention
On Leave

Verify first, decide second

The verifier should establish who the employee is before asking whether the event is a clock-in, clock-out, or another allowed attendance action.

Liveness matters

Biometric recognition without liveness protection is not sufficient for a serious attendance product.

Fallbacks must be controlled

PIN, manager approval, QR, or similar fallbacks should be explicit, permissioned, logged, and visible in reporting.

Attendance is an event stream

Dashboards and reports should be built from trustworthy attendance events rather than fragile UI state.

Offline operation is a real requirement

Verification devices may lose connectivity. The client should preserve safe local behavior and synchronize without creating duplicate attendance events.

Start simpler than the eventual scale

A modular architecture with clear boundaries is preferable to prematurely splitting every capability into independent services.