Software that survives the shift

I build the systems behind the service.

I am Lukas Slivka — a product engineer and hospitality operator. I turn the awkward, time-sensitive parts of real service into software that staff can trust when the venue is busy.

See QRelia Browse the work
01

Not an agency portfolio. Not a collection of mock-ups. These are products shaped by live operations, built end-to-end, and taken into real environments.

Lukas Slivka in a hospitality setting The operator became the engineer.
Current build QRelia Hospitality operating layer
Method Observe → structure → ship
Discipline Product engineering
Domain Hospitality operations
Core stack .NET / Razor / SignalR
Difference Software + physical devices
Find the friction. ◆ Understand the room. ◆ Build the complete system. ◆ Watch it work under pressure. ◆

Selected system / 01

QRelia is where the whole practice comes together.

Guest ordering, live staff workflow, management control, QR print design, analytics and connected ambient hardware — designed as one operational ecosystem rather than a pile of features.

live operational data
QRelia analytics showing live order performance

Order state leaves the screen and becomes visible in the room.

Q / 01

A real-time service layer, built from the inside of hospitality.

QRelia started with a practical problem: service requests are only useful when the right people notice them, understand them and act at the right moment. The platform connects those moments across guests, staff, managers and devices.

Guest
Branded mobile ordering with location context.
Team
Live receiver workflow built for active service.
Management
Menus, print, access, performance and forecasting.
Room
Ambient hardware translating state into light.
Product overview Live case study Visit QRelia

How the work happens

No theatre. A clear route from operational problem to working product.

  1. 01

    Stand in the operation

    I start with what actually happens: interruptions, handovers, delays, workarounds and decisions.

    OBSERVE
  2. 02

    Model the behaviour

    The workflow becomes explicit: roles, states, timing, edge cases, permissions and consequences.

    STRUCTURE
  3. 03

    Build the complete loop

    Interface, backend, real-time events, infrastructure and hardware are treated as one product.

    ENGINEER
  4. 04

    Put it under pressure

    Live use exposes the truth. I watch, correct, simplify and keep the system accountable.

    PROVE

Supporting work / selected

Different products. The same instinct for operational clarity.

All work
InnControl dashboard
02 / Hospitality operations

InnControl

Internal visibility and coordination for hospitality teams.
BarberCore booking interface
03 / Service SaaS

BarberCore

Booking, payments and day-to-day service operations.
Room service QR ordering project
04 / Early hospitality system

Room Service

The earlier experiment that made the pattern visible.
2019 First serious build

The route here

I did not arrive through the usual door.

Hospitality taught me to read systems before I knew how to code them. Software gave me a way to redesign what I had spent years observing. That combination — practical service experience and self-taught engineering — is now the centre of my work.

Read the full journey
“The useful question is not whether a screen looks modern. It is whether the operation behaves better after it exists.”
06 / OPEN LINE

Have a real operational problem worth solving?

Give me the context, the constraints and the awkward parts. That is usually where the strongest product begins.

Start a conversation