Michał Wiatr

Profile

Michał leads CloudFloo from the systems side. His work sits at the point where product ambition has to become an architecture, a release plan, and a set of engineering choices the team can defend after launch.

Clients usually meet him when the project has more risk than a simple build ticket can carry. The question might be how to modernize a legacy system, how to move a service toward Kubernetes, how to introduce AI without making the product unpredictable, or how to split a large idea into the first slice that proves the direction.

His background includes airline systems at Sabre and earlier 5G RAN engineering at Samsung. That experience matters because it shaped how he thinks about reliability, rollback paths, data flow, and the cost of unclear ownership. CloudFloo still keeps public claims tied to work the company owns, but that enterprise context is visible in how he designs delivery.

On IndepAI, HSK WebKD, and CloudFloo platform work, Michał pushes for a technical core that stays explicit: deterministic business logic, observable services, careful release sequencing, and AI features bounded by product rules. He is rarely interested in impressive architecture for its own sake. The useful architecture is the one the team can operate, explain, and change.

He also protects the client conversation from drifting into vague engineering language. If a decision affects cost, timeline, maintainability, or production risk, he names the trade-off early. That gives founders and operators a clearer view of what they are buying, what can wait, and what would be expensive to ignore.

Inside CloudFloo, Michał sets the delivery standard for a small senior team: fewer handoffs, direct accountability, and technical decisions connected to business outcomes. When a project needs a pragmatic architect who can stay close to implementation, he is usually the first person in the room.