Frequently asked questions

Most engagements start with a short scoping call, followed by a proposal within about a week. Retainers can usually move faster since there's no discovery phase.

No — most projects start with what already exists. We audit first and only replace what's actually holding you back, not everything by default.

English and Polish, fully remote, with comfortable overlap across CET/CEST business hours. Retainer clients get an agreed on-call window on top of that.

That's exactly what the retainer and fractional models are for — we become that team, on a schedule and budget that fits you.

Everything is delivered as code and documented, so there's no lock-in — your team or another provider can pick it up at any time.

Projects are scoped and quoted per engagement. Retainers and fractional work are billed monthly against agreed hours or an SLO-backed retainer — we'll walk through the right shape on the first call.

Yes — a scoped audit or a single migration is a common, low-risk way to start before moving to a retainer.

AWS, Google Cloud, Azure, Cloudflare, Scaleway and OVHcloud today — we pick the platform based on your workload, not a single vendor relationship.

We work with what's there whenever it's sound — we extend and refactor existing infrastructure-as-code rather than rewriting it from scratch by default.

Kubernetes is common in our work but not required — we design around the workload, including plain VMs, managed PaaS or serverless where that's the better fit.

Yes — NDAs are standard practice, and we work within whatever compliance framework your industry requires.

Secrets live in a dedicated secrets manager — never in source control — with access scoped per engineer and rotated on offboarding.

You do. Repositories, infrastructure-as-code and documentation are handed over in full, under your own accounts and cloud billing.