KeevaathTech/Products
Two live. A third in build.
Platforms we funded, designed and still operate. We point at these before we point at a case study, because the consequences are still ours.
Two live. A third in build.
Different markets, same team and same discipline. Both live platforms are multi-sided, with real users, live infrastructure and a roadmap we own. Each page describes what the product does and what went wrong building it, including what that cost.
Why we point at these before case studies
A case study describes work that finished. A platform we still operate describes work that continues, with the consequences still landing on us. When a deploy breaks something at two in the morning, it is our phone, and that changes how we write migrations and what we are willing to ship on a Friday.
It is also why both product pages carry an account of what went wrong. One took six and a half weeks of defect cycles before we read the deployed files directly. The other produced a hundred and fifty three failures from a test harness that was itself broken. Those accounts are the most useful thing we can show a client, because they describe the discipline that came out of them.
Questions we are asked
Are these available to license or white label?
Both live platforms are conversations worth having, and the contract analyzer inside Gulf Careers Academy is the component most often asked about. Pilots are the usual starting point.
Who operates them?
KeevaathTech, meaning the team that built them. Uptime, support and the roadmap all sit here.
Can we see Meridian before it launches?
Yes, as a design partner or a pilot organization. That is the most useful conversation to have about it right now.
Pilots, partnerships, licensing or distribution.
Tell us which platform and which of those fits. You will usually hear back within five working days, from the person who would run it.