Skip to content
Kakoriya Cloud
Menu

Our work, labelled for what it is.

Kakoriya Cloud opened in October 2026. This page keeps three kinds of work apart and labels every item: work the firm has delivered for clients, demonstration projects, and the experience our founder brings from previous roles.

Client work

Work Kakoriya Cloud delivered for a client, shown with their written permission.

Nothing to show here yet: Kakoriya Cloud opened in October 2026. Client work appears here only when the firm delivered it and the client has agreed in writing to it being shown.

Demonstration projects

This website, built by Kakoriya Cloud, and an independent build by our founder from before the firm. Each is labelled; none was made for a client.

  • Demo project

    This website

    Website · Kakoriya Cloud

    Astro and Tailwind on Azure Static Web Apps; a brief form that works without JavaScript and posts to an Azure Function; a content security policy checked at every build; light and dark themes.

    Designed and built by Kakoriya Cloud for itself, October 2026.

    Related: Business websites

  • Independent demonstration

    Retrieval that cannot leak, and an upgrade refused (on our founder’s portfolio)

    Retrieval-augmented generation

    A document assistant that can never show one source’s material in another’s answers, because the separation is built into the system, not asked of the model. Tested on 87 real questions, which ruled out a model upgrade.

    Built by our founder, alone, May to August 2026, before Kakoriya Cloud existed. No client, no employer.

    Related: AI solutions

Founder experience

Before Kakoriya Cloud existed, our founder, Akshay Kakoriya, spent 7 years designing and building on Azure as an employee of Accenture, Cognizant and Capgemini. The write-ups below come from those roles. The work was done for those employers and their clients, usually as one member of a larger team, and it is not Kakoriya Cloud’s client work. None names a client, and each says which decisions were our founder’s and which were the team’s.

  • Founder experience

    200 integrations, counted before designed (on our founder’s portfolio)

    Migration architecture · Ferry and cruise

    A legacy integration estate with a data-centre exit date and no inventory: the count that had to come first, the 4 patterns it produced, and the design that was approved as the baseline for the build.

    Done by our founder in a previous employed role, before Kakoriya Cloud. The design was approved; the build began after our founder left.

    Related: Azure solutions

  • Founder experience

    30 interfaces, one go-live date (on our founder’s portfolio)

    Integration platform · Construction and ERP

    Bespoke on-premises applications wired into a new ERP against a fixed date, with requirements still moving: the contract-first discipline that absorbed the churn, and what a batch of messages is worth.

    Done by our founder in a previous employed role, as part of a team, before Kakoriya Cloud.

    Related: Azure solutions

  • Founder experience

    An estate nobody had documented (on our founder’s portfolio)

    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.

    Related: Maintenance & support

Write-ups open on our founder’s portfolio, akshay.kakoriyacloud.com, where they are written in the first person.

Founder experience

Figures from our founder’s previous employed roles, before Kakoriya Cloud. They are not the firm’s results.

  • 60+ interfaces built or materially changed two employer engagements, 2022 to 2025
  • 50+ integrations assigned a target pattern one estate of 200+, 2025 to 2026; design approved as the build baseline Read the write-up on our founder’s portfolio