What's shipped, dated
Real, dated changes to MergeMind Platform, Commerce and this site — not a curated highlight reel.
GreenLeaf Garden case study updated: a 46-product sample store and a second paid order
The store was re-seeded and the checkout rules corrected (live plants at 0% GST, prices include tax, a flat delivery charge). A second order, ₹278, was run to PAID on 27 October 2026 through a real browser on a mock payment gateway. It is a sample store on our own stack, not a live shop, and the page now says what is not yet true, including which of its sample orders predate the corrected rules.
The site now follows the platform’s shape: engines, solutions, products
Platform shows the shared core and its four engines; Solutions start from the business you want to run; Products shows Edwyn and FixerJi, the products we built on it. The developer pages moved to Developers. Old addresses redirect to the new ones.
Edwyn added, FixerJi walk-through published, Learning figures recounted
Edwyn, our learning product, has its own page saying what is live and what is not yet. FixerJi’s page now carries a captured walk-through of one booking (local stack, test payment, 23 October 2026). The Learning engine’s figures were recounted on the live server on 27 October 2026.
Repositioned around founder-operators: “Build what’s yours.”
MergeMind now presents one core with four domain platforms — Commerce, Marketplace, Learning and Finance — each with an honest status label, plus a picker that maps your business needs onto them.
Stories: FixerJi and White Owl
Two more ventures built on the platform, alongside GreenLeaf Garden — a home-services marketplace and a group savings product — each stating what is live and what is not yet.
One source of truth for SDK status
The Platform page, docs and pricing now describe SDKs from a single list — including a real, not illustrative, TypeScript SDK example — after earlier pages contradicted each other.
Public documentation expanded to seven sections
Authentication, tenancy, authorization, billing, events & workflows, deployment, and how to get API/SDK access — each as its own real page, not one long overview.
Security & Trust page published
What’s implemented today versus what’s planned, stated plainly — including that we don’t yet hold SOC 2 or ISO 27001.
Case Study #001 published
A sample store (GreenLeaf Garden) on our own stack, an 8-product catalog, and an order taken end to end to a confirmed, PAID state on a mock payment gateway — not a mockup.
Services separated from Pricing
Services now explains how an engagement actually runs — discovery through handover — instead of repeating the same six pricing cards.
Build-engagement ladder moved to fixed, INR-first pricing
Six engagement levels, each with a starting price, a written scope boundary, and a stated timeframe — from a two-week Foundation Start through a dedicated enterprise build.
Founder identity added
A named person now stands behind the platform and the Build Review — not an anonymous team.
Real checkout wired for platform plans
Paid platform plans connect to real Razorpay hosted checkout rather than a request-only form.
Live lead capture
The Build Review and Contact forms now submit directly into our CRM instead of only offering a mailto fallback.
Repositioned as MergeMind Platform + MergeMind Commerce
One platform (PaaS), one proof product built on it (commerce), under one brand — replacing an earlier, more fragmented positioning.
Production-grade site hardening
Security headers, per-page SEO metadata and an accessibility pass applied across the site.