exPardus · Almaty, Kazakhstan · a verified data layer
exPardus builds a verified data layer for businesses and property in Central Asia, starting in Almaty. Two engines feed it: small, useful apps for businesses, and platforms led by a rental marketplace where every listing is reconfirmed each week and nobody can pay to rank higher. We are early: no customers and no revenue yet.
In Almaty it is hard to tell which rental listings are real, and a small business rarely sees or owns the data about its own customers. We treat both as the same problem: data nobody has checked. Checking it is an operations job as much as a software one, and every check, every app screen and every scan should add to one layer of data people can rely on.
01
Thin, useful apps for small businesses, starting with Tap. Owners see their own data first. This engine is meant to pay its own way.
02
Estate, a rental marketplace that launches data first, and Expard, the engine that turns messy records into verified data. Most of our building goes here.
03
What accumulates across every product: checked listings, visits, calls and scans on one shared vocabulary. The layer takes only anonymised aggregates, never personal data, and this is explained in plain language to everyone who contributes.
01 · Platforms
In developmentEvery listing checked. Every week.
A rental marketplace for Almaty where listings are reconfirmed every week, checked by our own team, and nobody can pay to rank higher. It launches data first.
02 · Platforms
In developmentSmall apps. One data layer.
What accumulates across every product: checked listings, visits, calls and scans on one shared vocabulary, so data from one product joins with another. The first public output we plan is a monthly Almaty Rent Index.
03 · Platforms
In talks with a design partnerMessy data in. Verified data out.
The verification engine behind our platforms: it takes the spreadsheets, databases and screenshots an organisation already has, cleans them and records every claim it makes, so nothing downstream rests on a guess.
04 · Business services
First pilot venue lined upOne tag, one permanent link, pointed anywhere.
NFC and QR tags for venues. Each tag carries one permanent link; the owner points it at a review page, a menu or anything else, and every scan is counted. The first of our business services.
Our engineering runs on Claude Code: one manager session dispatching a fleet of coding agents, each told to consult a read-only oracle rather than guess, with Codex workers on the side when a second model's hands help. That tooling did not exist, so we built it, run it on our own repositories, and publish it — with a footnote on every claim the benchmark does not prove.
Run a whole team of Claude Code sessions from one seat.
A multi-session manager for Claude Code: one manager session spawns, steers and hands off many workers across every project on your machine. Durable sessions, mailbox steering, token caps — no daemon, no dependencies.
A Claude Code plugin that stops your session from flailing.
The moment a session is unsure or stuck, it consults a read-only, best-model oracle and implements the plan it gets back. Two commands to install; nothing to configure.
One shell. Independent workers.
Lightweight background Codex workers from Codex or Claude Code: one Bash executable, five commands, plain files, no daemon. Released 10 September 2026.
Money buys tools, never position. On our platforms, nobody can pay to rank higher.
We grew up around family businesses. Each of us focuses on one track: the company and estate, business services, the platform and data layer, and the Expard engine. Everyone builds.
Altai
Team
Mukhamedali
Team
Arnur
Team
Magellan
Team
Run a business in Almaty, let flats there, or want to help build this? Tell us. We will say plainly what exists today and what does not.
