FAQ
Straight answers, including when we're not the right fit.
Working together
How does an engagement start?
With a short intro call about what you run and what you want changed. Afterwards we send a written proposal: scope, deliverables and a fixed price. Nothing starts until you accept it.
Do you work alongside our engineers?
Yes, through your review process, and we pair with your engineers where it helps. Not a fit if you want work done with no one on your side reviewing it.
Who do you work with?
Startups, established companies, technical founders and engineering teams that run software in the cloud. The size of the system matters less than having someone who will own it after handover.
Is this a fit for us?
Yes if you run software in the cloud and want it automated, secured and documented, with your engineers involved. Not a fit if you want a team to run your systems indefinitely with no one on your side. Ongoing support is available, but always alongside your team.
Where are you based, and which time zones do you cover?
We're based in Pakistan and work remotely. We agree overlapping working hours with your team at the start of each engagement, whatever your time zone.
Pricing and timing
How do you price work?
A fixed price per agreed scope, so you know the cost before we start. Extra work gets its own quote. Not a fit if you want an open-ended hourly arrangement. Pricing is agreed in a written proposal.
How long does a typical engagement take?
The first month is fixed: findings in week 1, first changes handed over by week 4. After that it depends on scope, and the proposal sets out the timeline.
Security and access
What access do you need, and how do you handle credentials?
The least the work needs: read-only while assessing, scoped access while building. Access goes to named people through your identity provider where possible. Credentials stay in your systems. Access is removed when the engagement ends.
Will you sign an NDA?
Yes. We're happy to sign your NDA, or a mutual one, before you share details about your systems.
Can you help with compliance frameworks such as SOC 2 or ISO 27001?
We implement and document the technical controls those frameworks ask for: access control, logging, change management, vulnerability management. We're not an auditor and can't certify you.
Tools and technical approach
Which cloud providers do you work with?
AWS, Azure and Google Cloud. We work in the one you already use rather than moving you to ours. Not a fit if you need on-premises hardware work.
Do you have preferred tools?
Widely used, well-documented ones. We start from what you already have and only suggest a change when there's a clear reason, along with what switching costs.
Can you work with our existing CI system?
Usually. Most CI systems can run a well-structured pipeline, so we only suggest moving if yours blocks what you need. Common examples are GitHub Actions, GitLab CI, Jenkins, Azure Pipelines and Bitbucket Pipelines.
Do we actually need Kubernetes?
Not always. For a handful of services, a managed container platform or serverless is often simpler and cheaper. We'll say so if Kubernetes isn't worth its operating cost for you.
Will security scanning slow down our pipeline?
A little, so we place checks deliberately. Fast ones run on every change. Slower scans run in parallel or on a schedule. The pipeline only blocks on findings you've agreed matter.
Can a migration happen without downtime?
Often, depending on the workload. Every move gets its own cutover and rollback plan. Where a maintenance window is the safer choice, we tell you before we start.
What happens to our data when an agent uses an LLM?
You decide before we build: which data an agent may see, which model providers and regions are acceptable, what gets logged, and what is never sent. Those limits live in code and in the docs.
How do you know an agent is working well?
By testing it. We build an evaluation set from real examples, run it before every change, and monitor quality and cost in production. Not a fit if you need guaranteed answers from a language model; no one can promise that.
What do we get from an assessment?
A written report with findings, risks and options, a prioritized roadmap, and a session to walk your team through it. Act on it with us, with your own team, or with someone else.
After handover
Who owns the code and the accounts?
You do, from day one. Everything lives in your repositories and cloud accounts, under your access control. If we stopped tomorrow, nothing would stop running.
What happens after handover?
Your team runs it, with the runbooks we wrote together. If you want us to stay on, ongoing support is optional and month to month, with 30 days' notice to cancel. Normal requests get a reply by the next business day, and on-call cover for critical incidents is available on the Premium support plan only. Each month we do a short review of changes and open issues. Pricing is agreed in a written proposal.
Tell us what you're running.
A few lines about your stack is enough. We'll reply to set up a short intro call, then send a written proposal with a fixed price.
