# Clidey: open-source decision infrastructure for live operational data

Canonical: https://mudpie.ai/companies/clidey/
Breadcrumb: [Home](https://mudpie.ai/) / [Companies](https://mudpie.ai/companies/) / [Clidey: open-source decision infrastructure for live operational data](https://mudpie.ai/companies/clidey/)
Author: Ali Abouelatta (https://mudpie.ai/authors/ali-abouelatta/)
Published: 2026-09-19
Updated: 2026-09-19
Research type: Company profile
Method: Company and accelerator sources checked 2026-09-19. Product claims are attributed to their sources; this is research, not a hands-on product trial.

Clidey is the company behind WhoDB, an open-source data platform for modeling an organization's entities, relationships, rules, and decision logic. The buyer decision is whether declarative, inspectable decision infrastructure is more useful than dashboards, ad-hoc queries, and scattered business logic.

## What it does

The YC profile describes WhoDB as continuously ingesting operational data into a live model of customers, accounts, assets, and workflows. Teams express what should happen under which conditions and constraints; WhoDB evaluates the rules as data changes and produces actions, recommendations, or state updates. Clidey's current homepage positions the company around open-source data infrastructure and WhoDB ([YC profile](https://www.ycombinator.com/companies/clidey); [Clidey homepage](https://clidey.com/)).

| Fact | What the public sources say |
| --- | --- |
| Buyer | Engineering, data, and operations teams with fragmented business logic |
| Core model | Entities, relationships, rules, objectives, and live operational data |
| Outputs | Actions, recommendations, state updates, and auditable decision logic |
| Positioning | Open-source, self-hosted data infrastructure with no vendor lock-in emphasis |
| Founders | Hemang Kandwal and Anguel Hristozov |

## Why it fits

The useful distinction is making decisions a first-class system rather than a report. A team can model the objects and relationships it actually operates, declare a rule, and inspect the data and logic that produced an action. That is relevant when the same customer or asset logic currently appears in a dashboard, a cron job, a spreadsheet, and a manual process.

The public product record has evolved from Docucod, an earlier documentation product described in the YC launch, to WhoDB and open-source data infrastructure in the current company positioning. A buyer should evaluate the current repository, ingestion path, rule engine, permissions, deployment, and migration from existing business logic rather than rely on the older product story ([YC launch](https://www.ycombinator.com/launches/NZc-docucod-automatically-generate-and-maintain-your-project-documentation)). Pricing was not published.

The founders bring systems and finance context: YC describes Kandwal as a former Palantir and financial-services builder, and Hristozov as a developer who worked on financial software and community technology projects ([YC company profile](https://www.ycombinator.com/companies/clidey)).

Short version: Clidey is worth exploring when the problem is fragmented operational logic, not a lack of charts. Start with one decision that currently crosses three systems and make its inputs and outputs inspectable.

## Sources checked — 2026-09-19

- [YC company profile](https://www.ycombinator.com/companies/clidey)
- [Clidey homepage](https://clidey.com/)
- [Clidey YC launch](https://www.ycombinator.com/launches/NZc-docucod-automatically-generate-and-maintain-your-project-documentation)

## Cohort context

Clidey is listed in Spring 2025. In our 2026-09-18 directory snapshot, 97 of 143 listed companies in that cohort have YC’s primary industry label B2B (67.8%). This is a current-directory comparison, not an original intake count or a performance ranking. [Nine-cohort dataset](https://mudpie.ai/research/yc-cohorts-2026-09-19.json).

## Public website snapshot

Observed 2026-09-19T16:15:35.931Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.

| Signal | Homepage observation |
| --- | --- |
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |

[Public observations](https://mudpie.ai/research/yc-homepage-links-2026-09-19.json) · [Collection method](https://mudpie.ai/research/yc-homepage-methods/README.md). Missing links here do not establish that a capability or file is absent elsewhere.


## Author disclosure

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.