KOVR · 2025–2026

KOVR

closed source
  • Marketplace
  • Mobile
  • NestJS
  • Realtime
kovr existing
www.kovr.app
2025–2026

A city-based shift marketplace for multi-location employers and flexible workers: post public or private jobs, build a vetted roster, auto-schedule by reliability and distance, track live shifts and approve timesheets, with a worker mobile app and AI assistants that answer from live data.

read how it was built ↓
about.txt
role
Founder & Full-Stack
for
KOVR
stack
Marketplace, Mobile, NestJS, Realtime
when
2025–2026

How KOVR was built01 / 08

Crewly, week one

The repo began on 6 Nov 2025 as a monorepo with a Next.js employer dashboard, an Expo worker app and a NestJS API. Within days it had job creation with a map picker, map and list discovery, shift giveaways and swaps, an auto-scheduler, chat over WebSockets and a timesheets view.

scroll ↓ or click a card

The brief

Shift hiring still runs on agencies, group chats and spreadsheets. Agencies are slow and expensive, manual coordination double-books people, and workers cannot see what is nearby. KOVR is a technology platform rather than a staffing company: employers keep the relationship with their workers, and KOVR handles matching, scheduling and the operations tooling.

facts.txt
Problem
Shift staffing scattered across agencies and chats
Audience
Multi-location employers and flexible workers
Surfaces
Employer web dashboard and a worker mobile app
Launch market
Edmonton first, built for more cities
Role
Founder and full-stack
Timeline
Nov 2025 to spring 2026

How I approached it

  1. 01
    Two sides, one system

    Employers work on the web and workers on their phones, but both talk to the same API, so a change on one side shows up on the other in real time.

  2. 02
    Public and private jobs

    A public job is open to everyone nearby. A private job is visible only to a vetted roster, so regular staff and new hires are handled in the same tool.

  3. 03
    Prevent the mess up front

    Role and time validation blocks overlapping or illegal assignments, so double-booking is stopped by the system instead of found on the day.

  4. 04
    Explain the match

    The auto-scheduler ranks workers and shows the reasons: availability, rating, distance, reliability, skills and past performance. The employer can override and invite.

  5. 05
    Make live shifts visible

    Clock-ins, breaks, tasks, photos and guest counts feed one operations view, and timesheets can be approved with edits and notes.

  6. 06
    Grow one city at a time

    Billing is per city, permissions are scoped to locations, and a city that is not live yet takes a waitlist instead of an empty map.

A look at the product

dashboard and app (test data)
dashboard and app (test data)
kovr.app
kovr.app
live ops, analytics, access control
live ops, analytics, access control

How it is different

Staffing agencies fill shifts for you, slowly and at a markup, and they sit between you and your own workers. Group chats and spreadsheets are free but double-book people and leave no record. General job boards help you find candidates, but stop before scheduling, attendance and pay.

KOVR is built around the shift itself:

  • A technology platform, not an agency. The employer owns the relationship with their workers.
  • Private rosters for repeat staff next to public jobs for new hires.
  • Scheduling, live attendance and timesheets in the same tool as the job post.
  • Per-city and per-location control for operators who run teams in several places.

What it runs on

What got in the way

What came out of it

KOVR runs as a web dashboard and a mobile app on one API, launching in Edmonton. These numbers describe what was built. There are no usage figures on this page.

What I learned

  1. A marketplace is two products sharing one backend. The employer and worker experiences needed different design and the same source of truth.
  2. Enforce the rules in the API. Validation on the server held up when new screens were added.
  3. Explain automated decisions. Showing why a worker was ranked first is what makes people trust the auto-scheduler enough to use it.
  4. Treat money as its own system. Payouts had different risks and rules from scheduling, so they became their own project.
  5. Open a city only when it can work. Waitlists turned an empty map into a signal about where to launch next.

KOVR: workforce infrastructure for flexible hiring

A shift marketplace so multi-location employers can source, schedule and pay workers without a staffing agency in the middle.

See KOVR

Launching in Edmonton and built to add cities. The payout engine is its own project.

up next →
KovrPay payout infrastructure

KovrPay

2026
closed source

Fintech · Stripe · Java

White-label contractor payout infrastructure for shift platforms. Stripe moves the money; KovrPay orchestrates onboarding, batch payroll, T4A, and CRA — Kovr is client #1.

say-hi.txt

Want something like KOVR?

Tell me what you're making and I'll tell you how I'd build it.

Overview