Every unit,
on the record.
Inventory, sales, reservations, service charges, and the moment a unit becomes the owner's. One instance per developer, built around how your development is run.
Everything you're juggling,
in one place.
The unit list, the payment chase, the certificates. Today they live in a spreadsheet, a chat, and a Word file. keys.krd makes them one record.
Every part of the handover,
on one system.
Reservations to sales, service charges to certificates, and the people and numbers around them. Each one a part of the same record, in your colours.
Custom documents
Receipts, statements and certificates on your letterhead, generated from the record itself. Nothing retyped, no version 7.
receipt
Statistics
Units, sales and collections across the whole development, moving as the record moves.
Handovers
Reserved to sold to handed over, with the date and signature on the unit.
WhatsApp reminders
Service charge notices and payment links, sent where owners actually read them.
Users & roles
Sales sees sales, finance sees finance, and a resident sees only their own unit.
| Role | Units | Sales | Finance | Docs |
|---|---|---|---|---|
| Developer | ||||
| Sales | ||||
| Finance | ||||
| Resident |
Reservations
Holds with an expiry and a deposit on the record, so nothing is reserved twice.
Pay for what you run.
Nothing you don't.
keys.krd is one system, built in parts. Switch on the modules your development actually needs and your instance is exactly that shape. What you turn off is not in your way, and not on your invoice. You pay once on signing, then once a year. There is no monthly collection to chase.
We build it once.
It wears your identity.
Every developer runs their own instance with their own tokens. The same app, the same generated documents, in your colours and on your letterhead. Pick a tenant to preview.
certificate
Your data never meets
anyone else's.
Every developer runs a separate instance in its own container, with its own database, its own file storage, and its own backups. There is no shared table and no query that can reach across.
From a conversation
to a live instance.
No procurement process and no implementation project. We set the instance up around your development, put your units in it, and hand it to your team.
The conversation
Half an hour on what you are building, how many units, and how handover runs today.
Day oneYour instance
Stood up on your domain, in your colours, with your letterhead on every document it generates.
Week oneYour units in it
We import the register from whatever holds it now, spreadsheet included, and reconcile it against your records.
Week oneYour team on it
A session each for sales, finance, and the site. Then the record is yours to run.
Week twoConsidering keys.krd for your development?
Empire Business Complex, Erbil, Kurdistan Region, Iraq