Building the operating layer for the billions campus software left behind.
The operations layer for a modern campus: attendance, meals, and payments, unified.
A unified app, web interfaces and operational dashboards now run on one source of truth. Every check-in, every charge and every allowance is accounted for in real time, while the remaining user-facing web roles are being consolidated into the cross-platform client.
These figures are the case as of August 2026, counted from February 2026 when Concourser entered daily production use. They are refreshed periodically rather than live, so treat them as a floor and not a live counter.
Students, teachers, store staff and administrators work through role-specific views of the same real-time campus ledger.
The app in every student's pocket: check in, pay, and see exactly where the day's allowance stands.
Start a session, scan the room, watch the counter climb. Morning and afternoon, if the class runs twice.
A shared-device point of sale for store counter staff, built for the busiest hour, accountable by design.
The web dashboard where administrators run the entire lifecycle: people, programs, money, and the paper trail.
| Role | Program | Status | Action |
|---|---|---|---|
| Student | AI Cohort 3 | Active | Reset · Move |
| Teacher | Robotics | Active | Reset · Cards |
| Student | AI Cohort 2 | Inactive | Reactivate |
| Store staff | Store | Active | Reset |
The store's own control room: what's selling, who's running low, and how the week is really going.
Concourser handles identity, attendance, and financial activity for hundreds of people a day, so the security concern is not an afterthought.
All traffic between every app, dashboard, and the server is encrypted end to end in transit. Logging out clears the device session.
Meal and attendance QR codes rotate and expire in seconds; attendance codes are single-use. A screenshot is worthless a moment later, and lost printed cards are revoked centrally.
Each app keeps its session in isolated local storage; one surface can never read another's session. POS customer details are shown only at the moment of a charge, never retained on the device.
Concourser supports lightweight, institution-controlled and self-hosted deployment as well as lower-cost managed hosting. Each institution can select the configuration that best fits its infrastructure, budget, data-residency and protection requirements.
Concourser runs the everyday rhythm of a working campus: morning check-ins, busy store hours and end-of-day reporting. Since entering production in February 2026, the platform has processed more than 30,000 meal transactions and more than 13,000 attendance records while supporting a paid founding deployment.
It also pays for itself. Before Concourser, the piloting campus ran on hand-signed paper coupons: unverifiable at a busy store counter, four times the staff work, and money quietly leaking with every service. Short-lived rotating QRs and per-program cost-center reconciliation closed that gap, recovering an estimated several thousand dollars as savings every month since February 2026.
These are the directions we are building with founding campuses, not a shipped feature list. Each one extends something already running in daily service, and pilot partners help decide the order.
The ledger is live. Now we make it think and act. Concourser already holds structured context for programs, attendance, allowances, payments and reporting. We are building natural-language analytics, automated operational briefs, smarter imports and configurable workflow automation, followed by anomaly detection, forecasting and approval-based operations agents.
Attendance sessions already run every morning. The same system building block extends to guest lectures, seminars, orientation and exam halls: one-off attendance lists, walk-in registration, and catering drawn against the event's own cost center rather than a student's program allowance.
Concourser began as three role-specific web apps, passed through a native iOS build that carried every role at once, and is now consolidating into a single cross-platform client. That client is publicly available through Apple's App Store. The next step is extending the same one across Android and additional platforms, so a campus deploys one app rather than one per role.
Every entry in the ledger already carries a timestamp. Surfaced as a shared calendar, that becomes something each role can plan against: when an allowance refreshes or expires, when attendance is required, when a store settles, when a term closes and the books have to balance.
The role model already decides what each surface is allowed to see. Opening it wider brings in the people around a campus: sponsors funding a program, guardians following a student's balance, and partner institutions running a joint course or event, each with a wisely limited view and aggregate figures where privacy requires them.
If your campus coordinates attendance, allowances and payments through spreadsheets, printed coupons and portals that do not talk to each other, that is not a local failure. It is the ordinary state of campus operations almost everywhere, and it is why the workflows Concourser replaces have stayed manual for so long.
still rely on paper-based information systems for education planning and management, according to UNESCO.
are connected to the internet worldwide. For lower-secondary schools the figure is 50%.
are enrolled worldwide, 1.4 billion in primary and secondary education and 269 million in higher education, before counting teachers, administrators and store staff.
Concourser enters through the daily workflows an institution cannot avoid, then expands into the operating layer it would rather not rebuild.
Sources: UNESCO Digital Education and Education Management, and the UNESCO Global Education Monitoring Report. Enrolment figures are for 2024.
Concourser was built, deployed, operated and commercialized by its founders before any institutional funding.
Built Concourser's core production platform. React and TypeScript, FastAPI and PostgreSQL, Swift and iOS. Production architecture, deployment and campus support. Leads the unified client and intelligent-operations engineering.
Former commercial software engineer shipping enterprise client applications. Full-stack and web, APIs, cloud workflows and automation. Product specification, UX and QA, debugging and release review, plus commercialization and institutional coordination.
Six years of production backend and data-platform engineering. Distributed systems, integrations, event pipelines, reliability and rollout tooling. Engaged when Concourser needs to harden scale and accelerate repeatable deployments.
Concourser is the flagship product of Rikoukei Labs.
From the first morning scan to the end-of-day report, one platform keeps the whole operation in motion.
// CONTACT
You can either drop us a message with your questions and our team will quickly get back to you with answers, or ask for an online meeting to talk face-to-face.