Kurdify: platform architecture and what the raise builds
Kurdify

The platform is built.
The raise is for distribution.

Kurdify is a Sorani-first business directory and commerce platform for the Kurdistan Region of Iraq, with a second lane into the global Kurdish diaspora. 13,271 businesses and 261,294 reviews across 12 cities are live in the product today. It is pre-revenue, and this page explains exactly what exists, what it runs on, and what the money changes.

13,271businesses live
261,294reviews
12cities
4languages, Sorani default
$0revenue, pre-launch

What is already built

Not a prototype and not a deck mockup. The rails below are running in production and can be opened in a browser right now.

The dataset

13,271 businesses, 261,294 reviews, 12 cities, collected and cleaned by an in-house pipeline, with a server-rendered page per business carrying structured data for search engines and answer engines. This is the asset that takes the longest to build and it already exists.

The business product

A 25-tab owner dashboard: profile, hours, catalogue, promotions, coupons, jobs, events, reviews, billing and performance. Plus a claim-and-verify flow so an owner takes control of a listing that was already there.

The consumer product

Directory, magazine, jobs, marketplace, real estate, autos, a buyer-requests board and a creator marketplace, with a points and Credit loyalty economy tying usage to discounts at verified merchants.

The WhatsApp agent

A per-business AI agent on the WhatsApp Cloud API that answers customers, books appointments into a calendar and meters its own message cost. $200 a year plus usage. WhatsApp is where commerce in this market actually happens.

The AI layer

A Kurdish-language assistant with voice in and voice out, plus an advisor that answers a business owner's questions from its own data, industry data and market data as three separated sources rather than one blended guess.

The ranking engine

Placement is decided by an online learning model with exploration, over signals like category and city match, rating, review volume, recency and click history. It is a statistical ranker, deliberately not dressed up as anything larger.

How it fits together

Four public surfaces, one platform, one dataset. A visitor, a business owner, a WhatsApp customer and a search engine all reach the same source of truth.

High-level request path. Everything to the right of the edge is Kurdify's own code.

AudienceConsumersdirectory, magazine, marketplace
AudienceBusiness ownersclaim, dashboard, billing
AudienceWhatsApp customersthe per-business agent
AudienceSearch and AI enginesstructured data, sitemaps
EdgeCloudflareDNS, cache, tunnel, storage
ApplicationThe platformAPI, server-rendered pages, dashboards
ApplicationAgents and jobsWhatsApp, AI, scrapers, backups
Source of truthOne databasebusinesses, reviews, accounts
Source of truthThe media libraryevery listing photo

The backend stack

Built for a market where a fixed monthly cloud bill is a real constraint, so the engineering choices are deliberately unfashionable and deliberately cheap to run.

RuntimeNode.js, no framework, no bundler, and zero third-party packages in the core application. Nothing to patch on a supply-chain advisory, no lockfile drift, no framework upgrade treadmill. The whole server is code we own.
DatabaseSQLite in write-ahead mode, using the driver built into the runtime, with full-text search on businesses and reviews. One file, no database server, no per-hour hosting charge, and a snapshot is a single verified operation.
PagesServer-rendered business pages with per-language alternates and structured data, so a listing is indexable by Google and quotable by an AI answer engine without shipping a JavaScript app to a phone on a slow connection.
EdgeCloudflare for DNS, caching, the tunnel that publishes the application, static hosting for the marketing site, key-value storage for leads and object storage for offsite backups.
MessagingMeta WhatsApp Cloud API, with per-business agents, ad-click attribution on the first inbound message, and message-cost metering that prices packs from the live carrier and model rates rather than a hand-typed number.
AIModel-agnostic by design: an ordered fallback across providers for text, a separate provider for images, and a Kurdish speech vendor for voice. No single model is load-bearing, so pricing or availability changes are a configuration edit.
Data pipelineAround 60 collection and enrichment jobs covering directory, autos, property, jobs, news and reviews, with deduplication, transliteration and image harvesting, running nightly.
PaymentsBuilt for the market as it is: local bank transfer and mobile wallet with a receipt-proof queue, plus a card processor for diaspora and international customers. Prices come from one file that the site build refuses to contradict.
Quality81 test files, roughly 300 tests, two API suites totalling 593 assertions, and 16 browser harnesses that measure real rendered pixels, because a status code cannot see a broken image or an unreadable colour pair.
BackupsNightly snapshot with an integrity check, a restore actually performed and verified, and a checksum round trip against offsite object storage. A backup nobody has restored is not a backup.

Why this matters commercially

The whole platform runs at near-zero fixed infrastructure cost. That is not an aesthetic preference, it is the reason a business can be charged $450 a year in a market where a Western SaaS price is impossible, and still leave a margin. The engineering constraint and the pricing strategy are the same decision.

How a listing becomes revenue

The commercial mechanism, end to end. Every business in the directory starts at step one already, which is the point of building the dataset first.

The owner funnel. Gold marks a step where money or a commitment changes hands.

Step 1Listing existsalready collected, unclaimed
Step 2Owner is reachedWhatsApp outreach or organic search
Step 3Claims and verifiesdocument plus phone code
Step 4Free value firstverified badge, page, tools
Revenue 1Plan$450 or $650 a year
Revenue 2Placement$150 a month, ranked by the engine
Revenue 3WhatsApp agent$200 a year plus metered use
Revenue 4Services and ticketingbuilds, marketing, event fees

The loyalty economy sits underneath all four: consumers earn points for real activity, points convert to Credit, and Credit is redeemed by QR at a verified merchant. The merchant gets measurable footfall, which is the proof that renews the subscription.

Where it runs today, stated plainly

This is the honest part, and it is the clearest single argument for the raise.

The constraint

The application currently runs on one machine, published through a secure tunnel. It is supervised, it restarts itself, it is backed up offsite nightly with verified restores, and its public reachability is checked every five minutes. It is a genuinely careful setup, and it is still one machine.

There is no second origin, no failover, and no alerting that reaches a phone. That is an acceptable cost while the product is pre-launch with no customers depending on it. It stops being acceptable on the day the first hundred businesses are paying.

Why it was built this way

Every dollar not spent on infrastructure went into the dataset and the product. 13,271 businesses and 261,294 reviews were collected, cleaned and made searchable without a hosting bill, by one engineer, before raising anything.

The architecture was chosen so that moving to real infrastructure is a deployment change and not a rewrite. The application is already containerised, the database is a single portable file, and the media layer can be pointed at object storage with one setting.

What an investor should take from this

The risk here is operational, not architectural. There is no technical debt to unwind and no rebuild in the plan: the hard part, a clean data model and a working product, is done. What is missing is the boring, purchasable layer, which is hosting, redundancy, monitoring and a second pair of hands. That is precisely what the infrastructure and hiring lines of the raise pay for.

What the raise builds

$500,000 over 18 months on a YC post-money SAFE at a $6,500,000 cap, roughly 7.7% dilution. The allocation below is the one in the business plan, not a summary written for this page.

CategoryShareAmountWhat it actually does
Go to market35%$175kGround sales in Erbil and Sulaymaniyah, paid acquisition, influencers and events. The dataset exists; this converts it into claimed and paying businesses.
Product30%$150kNative mobile apps, the Credit economy, and the diaspora lane. Mobile is the single biggest product gap today.
First hires20%$100kA Kurdistan team: sales lead and two reps, a Sorani community and content manager, support and operations, and a contract mobile engineer.
Legal and entity8%$40kHolding company structure, securities counsel per jurisdiction, local operating company, and the compliance work the loyalty and prize mechanics require.
Infrastructure and reserve7%$35kOff the single machine and onto managed hosting with redundancy, monitoring and alerting, plus a reserve.

The engineering roadmap, in order

1. Production infrastructure

  • Managed hosting with a real deployment target, so the platform no longer depends on one machine staying awake.
  • Media moved to object storage and served from the edge.
  • Monitoring and alerting that reaches a phone, plus external uptime checks and error reporting from the browser.
  • The test suite on a schedule rather than on memory.

2. Mobile

  • Native applications for iOS and Android, which is the primary device in this market and the single largest product gap.
  • Push notification, which is what makes a loyalty economy and a coupon actually get used.
  • An installable web app first, as the fast path to a home-screen icon while native is in build.

3. Commerce depth

  • Automating the payment path, so a subscription does not need a person to confirm a receipt.
  • The Credit economy at scale, with redemption reporting a merchant can act on.
  • The diaspora lane: travel, property and gifting demand from abroad routed to verified businesses at home.
Month 2
Entity structure complete, first grant applications filed, Erbil ground team hired.
Month 4
Erbil public launch. 1,000 claimed or verified businesses, first 100 paying.
Month 8
Sulaymaniyah launch. Loyalty loop live at 200+ verified merchants. Mobile apps in beta.
Month 12
400+ paying businesses in the base case. Ticketing revenue live. Investor updates unbroken.
Month 18
Seed round opened on live revenue. Diaspora commerce lane in pilot.

On the projections

Every figure above is a target, not a commitment, and the platform is pre-revenue today with one business on a paid plan. The base case exits month 18 at roughly $380k to $450k annualised. The long-run reference point is the Kurdistan Region alone: 200,000+ businesses, and 2% of them at an average of $40 a month is about $2M in annual recurring revenue, before any transaction income and before the diaspora lane.

Next

The rest of the material

This page covers the technology. The market case, the model and the full data room sit alongside it.