About Caellix

Small by design. Senior by default.

Caellix is a Microsoft practice built around one idea: cloud projects go right when the people who design them also build them — and then hand them over. No juniors learning on your invoice, no slide-deck consulting, no dependence sold as a service.

Founded
2026
Based in
Poland — delivering across the EU
Stack
Azure & Microsoft 365 only
Languages
English & Polish

The rules we run on

Decided once. Not renegotiated per project.

01

Microsoft-only, on purpose

Azure and Microsoft 365 are the whole practice, not two lines in a longer list. We'd rather have seen your exact problem before than hold a partner badge for everything.

02

Senior-only, founder-led

The founder leads every engagement and stays hands-on. When a project needs more hands, they're senior engineers employed by Caellix — not a delivery pyramid.

03

Ready for pressure

The real test of an environment comes during growth, incidents, audits, releases, and people changes. Caellix designs for those moments, so the platform behaves predictably when the business cannot afford confusion.

04

Documented, or it didn't happen

Decisions, configuration, and runbooks land in your repository as we go. Handover isn't the last milestone — it's a constraint on every milestone before it.

Kamil Pyrkosz, founder of Caellix
Kamil Pyrkosz Founder, Caellix

Who you'll work with

Founder-led — literally.

I founded Caellix after seven years of building and running Azure and Microsoft 365 environments — architecture, administration, security operations, and FinOps — and 10 active Microsoft certifications along the way. Long enough to see the same pattern everywhere: the expensive problems were never about missing technology. They were about environments nobody fully understood anymore.

So Caellix works the way I always wished suppliers did. I'm on every project personally, I bring in senior engineers employed by Caellix when the work needs more hands, and everything we build is explained and handed over. And if your problem isn't one we're right for, I'll tell you on the first call.

How we work

From first call to handover. No theatre.

The same four steps whether you buy a scoped assessment or an end-to-end build — only the depth changes.

  1. Scope

    One call, then a written proposal.

    A working session with an engineer, then scope, price, and deliverables in writing — whether it's a focused audit or a full build. You decide with a document in hand.

  2. Assess

    Evidence before promises.

    Every engagement starts from what's actually there: estate, configuration, spend, or security posture. You get a written read and a prioritised backlog — for audit engagements, this is the deliverable.

  3. Deliver

    End to end, in visible increments.

    From architecture decisions to a working, documented platform. Progress demos, decisions recorded as they're made, and everything landing in your repository as we go.

  4. Hand over

    Your team runs it.

    Runbooks, documented decisions, and a clean exit. Every engagement is designed to end — and to end well.

Next step

Bring us a problem, not a brief.

Tell us what's broken, what it's costing you, and what has to change. You'll get a straight answer about whether Caellix is the right fit — and what we'd do first.