RadinAI · Software Studio & WordPress Flagship
Software-engineering studio home for three service lines — WordPress products, custom SaaS platforms, AI automation — with the Daftaryar WooCommerce plugin as flagship proof.
01 — The Operational Problem & Stakes
Radinai (رادین هوش, radinai.ir) is the studio identity behind the systems in this portfolio: one studio, three service lines — WordPress products led by the Daftaryar WooCommerce plugin, custom software and SaaS platforms, and AI automation — with no single home that presented them together with verifiable proof.
The studio site had to do three jobs at once: sell the flagship plugin with its real test numbers, show the six production showcases (Hamesu, Cvly, Exvorta, Firoza, Daftaryar, Automation Engines) plus the six Exvorta Web export brands, and convert enterprise inquiries into a WhatsApp conversation — without a backend to operate or a CMS to patch.
02 — System Architecture & Execution
The studio site (radinai-site v1.0.0, HEAD 80439b6, launched 2026-11-18) is a 21-route static SSG build on Cloudflare Pages: 22 HTML files, self-hosted Yekan Bakh + IRANYekanX variable fonts with zero external font calls, GSAP + ScrollTrigger + Lenis motion, a 3-lens interactive workbench, a 5-tab Daftaryar simulator, a project estimator, and a Ctrl+K command palette.
Two Cloudflare Pages Functions carry the only dynamic behaviour: GET /api/health returns {ok:true, service:'radinai-edge'} and POST /api/inquiry validates the form behind a spam guard, issues a tracking code (RDN-...), and hands off to WhatsApp (hamid@exvorta.com, 989150033963). There is no notification backend — Telegram/Resend inquiry alerts are not configured, and this case does not claim them. The "Yaar family" follow-up plugins are roadmap only, not built.
The flagship proof is borrowed, not re-asserted: Daftaryar’s 2,645 tests / 15,501 assertions and 397/397 LDD gate belong to the Daftaryar case (Case 07). The studio’s own macro claims — 8 years, 14 systems, +16,600 assertions, 21 countries — are the studio’s marketing copy in src/data/portfolio.mjs with no independent evidence (the assertion arithmetic closes: 15,501 + 1,152 = 16,653 ≥ 16,600), so this case repeats them only as the studio’s own claims, never as verified fact. The same honesty applies to the plugin itself: the vault-verified bundle is Daftaryar v1.7.0 at 850,000 Toman (verified 2026-11-15), while the studio site still lists v1.0.0 at 890,000 Toman; the Sepidar piece is an adapter + mock built from public docs — the 70M Toman live ERP integration was cancelled — and the public demo (daftaryar-demo.radinai.ir) was re-verified HTTP 200 on 2026-11-19 after timing out earlier the same day. Note the naming boundary: "Radinai" here is the studio and its site, not the older OmniRoute gateway identity (router.radinai.ir / omni.radinai.ir).
03 — Interactive Subsystem Topology (Click Any Node)
WordPress Products · Daftaryar Flagship
Flagship plugin proof with a 5-tab simulator on the site (official invoice, anti-fraud card rotation, Torob profit guard, postal labels, SMS ping test).
04 — Key Engineering Decisions & Trade-Offs
Static SSG + Edge Functions Instead of a CMS
A studio brochure site does not need a database, an admin login, or a patch treadmill: 22 pre-rendered HTML files serve instantly from the edge, and the only dynamic surface is two tiny Functions. Design rationale as implemented — no decision log survives for this build.
One Studio Home, Three Lenses
Instead of three separate sites, the hero workbench switches between WordPress products, custom platforms, and AI automation lenses on one page, so a visitor sees the full range before choosing a path. Framed as design rationale, not a documented decision — no decision log exists for the Radinai site.
Flagship Proof Borrowed, Studio Claims Labelled
Daftaryar’s test numbers are cited only as flagship-product proof and point back to Case 07; the studio’s macro claims (8 years / 14 systems / +16,600 assertions / 21 countries) are presented as the studio’s own marketing, because no independent evidence supports the 14-systems / 21-countries counts; the assertion arithmetic now closes (15,501 + 1,152 = 16,653).
Inquiry to WhatsApp, No Notification Backend
The inquiry form ends in a WhatsApp handoff with a tracking code instead of a mailbox, a CRM, or a Telegram bot — a deliberate scope cut for a brochure site. Telegram/Resend alerts are not configured and are not claimed; the "Yaar family" follow-up plugins are roadmap only.
05 — Verified Build, Test & Runtime Proof
$ npm run build (radinai-site @ 80439b6)
✓ 22 HTML files emitted to dist/ (21 routes + /404)
$ curl -s https://radinai.ir/api/health
{"ok":true,"status":"healthy","service":"radinai-edge"}
✓ radinai.ir/ 200 · www 200 · /products/daftaryar/ 200 · /sitemap.xml 200 (verified 2026-11-19)
✓ Playwright QA at launch: 42/42 PASS · Lighthouse desktop 98–100 (mobile 75–82 open)