Clidey: open-source decision infrastructure for live operational data

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; Clidey homepage).

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). 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).

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

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.

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 · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.