Operational control
Structured records, permissions, audit trails, and reporting support accountable daily work.
Request a demoOne operational foundation
PitCore organizes the workflows that begin at the casino entrance and provides a modular foundation for planned operational expansion. Each phase is presented according to its real delivery status.
Structured records, permissions, audit trails, and reporting support accountable daily work.
Reception and Cage & Cashier are complete. Pit, accounting, and loyalty remain clearly identified as planned phases.
Windows reception workflows are designed to support connected identification and membership-card hardware.
Completed phases
PitCore now includes two completed operational phases: Reception and Cage & Cashier, each designed for controlled day-to-day casino operations.
Reception features
Eight available capabilities support reception teams today. Future-module capabilities are not presented as complete.
Product workspace
Product roadmap
Two completed phases. Three planned operational modules. No inflated delivery claims.
Customer registration, identification, profile photos and documents, membership cards, visitor check-in and check-out, user permissions, audit records, dashboards, reporting, and casino and terminal configuration.
Completed cage and cashier workflows for controlled financial operations.
Planned pit and table-management workflows.
Planned accounting and financial reporting capabilities.
Planned loyalty, player engagement, and rewards capabilities.
Technology foundation
The operational PitCore platform is developed primarily in C# and .NET, with ASP.NET Core backend services and Microsoft SQL Server. It uses role-based security, audit controls, an API-based client-server architecture, Windows support for reception and connected hardware, and a modular expansion strategy.
This public website runs on a separate modern web stack and a separate PostgreSQL database. It does not connect to the operational casino database.
Why PitCore
Product status is explicit, with completed capabilities separated from planned development.
Roles, permissions, audit controls, and controlled configuration support responsible operations.
A modular architecture supports measured growth without overstating future capability.
Deployment model
Reception and connected hardware workflows are supported through Windows clients, API-based services, and controlled operational data access.
Start a conversation
Request a product demonstration or discuss implementation, hardware integration, distribution, technology partnership, or investment.