Updates, monitoring, bug fixes, small enhancements and cloud cost reviews, for what we build or what someone else built, on terms agreed in writing.
A call, a WhatsApp chat, or a written brief if you prefer. We ask about the outcome you need, the constraints you are under, and what has already been tried.
Within 2 business days: a one-page scope with options and the assumptions behind them, and a fixed quote for each, or a short paid discovery first if too much is still unknown.
Short milestones against acceptance criteria agreed in the scope. Decisions are written down as they are made, so nothing important lives only in a meeting.
Documentation, runbooks and decision records, with access and ownership in your name. Defects found after launch are fixed within a window agreed in your scope; ongoing support is a separate, optional agreement.
Support is agreed in writing before it starts, so both sides know what happens when something goes wrong.
Every project includes a limited window after launch for fixing defects: things that do not work as the acceptance criteria said. Its length is in your scope. Support is the separate, optional agreement for everything after that.
Timelines are planning estimates for a typical scope. Yours goes in the written scope, with a fixed quote for each option, within 2 business days of our first conversation.
Monthly: hosting kept healthy, updates, small changes, uptime checks, and a named person to message.
Monitoring, bug fixes, dependency updates, and a set number of hours each month for enhancements.
One-off or regular: where the Azure bill goes, with each saving ranked by effort and impact.
From our founder’s previous employed roles, before Kakoriya Cloud, and labelled so. It is not the firm’s client work.
Founder experience
Estate turnaround · Automotive
An integration estate that arrived undocumented, deployed by hand and failing in ways nobody could explain: the order the team took it in, and the 5 decisions inside it that were our founder’s.
Done by our founder in a previous employed role, as part of a team, before Kakoriya Cloud.
Yes. We start by auditing and documenting what exists and making it deployable from a pipeline, before changing any of it.
Response targets are set in your support agreement, by severity, so they fit what your site or app needs. There is no out-of-hours cover unless the agreement includes it.
The defect-fix window comes with every project: things that do not work as agreed are fixed for a limited time after launch. Support is a separate, optional agreement for updates, monitoring and changes after that.
No. Without one you get a clean handover with everything documented, and it all stays in your name.
You do, ideally. We work in a subscription you own, with access you grant and can remove, so nothing about leaving us is hard.
Hosting kept healthy, platform updates, uptime checks, small content changes and a named person to message. The details and hours are written into the plan.