What we build
Two engines, one layer.
Platforms are where most of our building goes: estate, the data layer and the Expard engine. Business services start with Tap and are meant to pay for themselves. Every product below carries its real status; none has customers yet.
- Status
- In development
- Engine
- Platforms
- For
- Renters, landlords and verified partner realtors in Almaty.
01
Estate (working name)
Every listing checked. Every week.
Estate is our flagship platform: a long-term rental marketplace for Almaty, built so that what you see is current. A listing that is not reconfirmed within seven days is hidden, and every listing shows when it was last confirmed. A “checked by us” mark appears only after a check passes, and it never affects ranking. Estate is designed and in development; it has no listings yet.
We launch it data first, one district at a time. First, a study: we plan to hand-check a random sample of Almaty rental listings and publish how many are real, with the method and sample next to the result. Then a monthly Almaty Rent Index. Listings open district by district, from realtors, agencies and owners who choose to list with us, and our own team in Almaty will do the checking.
What it does05
Reconfirmed every week
A rental listing that is not reconfirmed within seven days is hidden. Every listing shows when it was last confirmed available.
Checked by us, only when the check passes
Our team will visit, take photos and confirm the lister may let the flat. The mark appears only if the check passes; paying for a visit never guarantees it, and realtors pass the same checks as owners.
No paid ranking
Money buys tools, never position. The rule is part of the design: ranking does not look at what anyone pays.
One flat, one record
Listings are tied to a building record and a confirmed map pin; suspected duplicates go to a person, not an algorithm.
The full monthly cost
Rent and the other monthly costs, shown as labelled estimates. Any AI price estimate is shown only as a range.
- Status
- In development
- Engine
- Platforms
- For
- Business owners and renters first; later, developers, real-estate firms and chains that need aggregated, anonymised data.
02
exPardus data layer
Small apps. One data layer.
Every product we build is also a place where verified data is recorded. A business owner sees their own data first and, later, benchmarks against similar businesses; every estate check adds verified property data. One vocabulary — organisation, place, tag or sensor, event, metric — lets listings, buildings, venues and scans be joined.
It is designed and in development, and today it holds no dataset: the first will come from our listing study. The layer takes only anonymised aggregates, never personal data, explained in plain language at sign-up, with a private option that keeps a business's data out of the aggregates. We are a platform, not a bank and not an ad seller.
What it does04
One vocabulary
Organisation, place, tag or sensor, event, metric: the same terms in every product, so the data joins.
Non-standard sources
Hand-checked listings, call outcomes, in-person visits, owner-entered records and scans.
The model proposes, the engine proves
Language models help find patterns; a deterministic engine checks every claim before anyone sees it.
Consent, explained
Anonymised aggregates by default, said plainly at sign-up; a private option for businesses that want out; aggregates only above a minimum number of businesses.
- Status
- In talks with a design partner
- Engine
- Platforms
- For
- Institutions that schedule people and rooms, and our own platforms.
03
Expard (working name)
Messy data in. Verified data out.
Expard keeps three layers: raw snapshots that are never changed, a cleaned copy that quarantines anything it cannot prove, and claims that carry their evidence and confidence. Rules are proposed by an AI model but checked against the whole dataset before they are accepted. The first version was built in five days, and its own checks caught a silent data-corruption bug along the way.
Its first product is scheduling on verified data for institutions, and we are in discussions with one as a design partner; nothing is signed. Inside exPardus, the engine is meant to turn messy listing records and call notes into verified data for estate and the data layer. Today it runs on its own and is not yet connected to our other products.
What it does04
Ingest what you already have
Databases, spreadsheets and screenshots become one cleaned, structured dataset.
Raw, cleaned, claimed
Raw snapshots stay untouched; the cleaned copy quarantines what it cannot prove; every claim carries its evidence.
Rules, not one-off fixes
The AI proposes rules; each one is validated against all the data before it is accepted.
Plans on proven data
The scheduler is designed to use only verified data, so every assignment traces back to its source.
- Status
- First pilot venue lined up
- Engine
- Business services
- For
- Cafés, restaurants, salons and other venues in Almaty that live on reviews and maps.
04
Tap by exPardus
One tag, one permanent link, pointed anywhere.
A tag on the table or by the till carries one link that never changes; where it leads is set from a panel, so a chain can re-point every tag without touching one. Every scan will be recorded and shown to the owner. We count taps, not reviews, because a review site does not tell anyone whether a review was posted. The public review button is always shown, and we never offer rewards for reviews.
A first version of the tags service is built and tested locally, and a first pilot venue in Almaty is lined up; we will say here when it starts. Next in business services: a reviews and reputation dashboard and a maps profile makeover, both at the idea stage, and table ordering for restaurants, which is designed but not built.
What it does04
One permanent link per tag
Tags are made in batches and linked for good; the owner decides where each one points and can change it at any time.
Every scan counted
Scans per tag, by day and by NFC or QR, so an owner sees which table or door works.
An honest review flow
The public review button is always shown, unhappy guests can also leave private feedback, and there are no rewards for reviews.
Designed next: table ordering
Secured tags that prove a guest is at the table, one shared cart per table, and orders sent to the venue's POS. Designed, not built.
Not sure which one fits?
Tell us what you run or what you are looking for. We will say plainly what exists today and what does not.
Get in touch