FairSpot parking allocation project

I have been working on a side project called FairSpot.

It started with a simple problem: when a company has fewer parking spaces than people who want to use them, email requests and manual decisions quickly become messy. The goal of FairSpot is to make this process more transparent.

Employees request parking for a given day. The system then runs a Draw and allocates available places according to configured rules. People who did not get a place recently should have a better chance next time. HR can see what happened, employees can see their own result, and auditors should be able to trace why a decision was made.

Technically, I use it to try a few ideas in practice:

• .NET services with clear boundaries
• Dapr for state, pub/sub, service calls, and workflow
• role-specific screens for employees, HR, tenant admins, and auditors
• architecture documentation that is useful during implementation, not written after the fact

The product documentation is here:

https://www.vejvoda.net/fairspot/

I also moved the architecture documentation into a separate site:

https://www.vejvoda.net/fairspot-architecture/

That architecture site is where I keep the higher-level view: requirements, decisions, risks, constraints, target architecture, transition states, and the implementation roadmap. The detailed delivery work still belongs to GitHub issues and pull requests.

Source code and architecture repository:

• RobertVejvoda/fairspot
• RobertVejvoda/fairspot-architecture

• 2026 1
• 2023 3
• 2022 1
• 2021 1
• 2020 1