Product
Muchiround
A place to do business and socialize. Not a logistics bolt-on. Not a social app with a shop stuck on the side. One platform where trade, community, money, and movement share identity, ledger, and map.
Do business
Storefronts, carts, escrow, leads for pros, invoices that land in chat — commerce that fits how people already buy and sell.
Socialize
Feed, communities, follows, reactions, creator surfaces. Reputation and discovery live next to the transaction, not in a different app.
Move things
Couriers, fleet routing, descriptive addresses, live tracking. Logistics is a first-class domain, not a webhook to someone else's black box.
Why it exists
Western product assumptions break on this terrain.
Structured street numbers. Always-on networks. Homogeneous fleets. Single-currency wallets. English-only support threads. Those are design defaults in most SaaS — and wrong defaults for Harare, Bulawayo, the diaspora corridor, and every town that still finds itself with "behind the Shell, Dangamvura."
Muchiround is built from the constraints up. The codebase is a Rails monolith with domain engines — commerce, feed, communities, logistics, payments, messaging, places, leads, search, ads, news, events, AI — sharing auth, ledger, and geo instead of duct-taping five vendors and hoping the seams hold.
Surfaces
What lives in the product
Commerce
Products, carts, wishlist, checkout, disputes, reviews. Sellers run real catalogs; buyers get progressive, mobile-first flows.
Social feed & communities
Posts, reactions, comments, follows, groups. Business and people share the same social graph when it helps discovery.
Messaging
Direct and business threads with product and order cards in-line — support without bouncing to email hell.
Logistics / RouteFlow
Courier profiles, delivery jobs, scenario-based CVRP, multi-vehicle capacity vectors, mixed fleets, live pings.
Leads franchise
Pay-per-lead service marketplace. Pros keep prepaid budgets; delivery quality is the north star metric, not vanity GMV.
Wallets & ledger
Fiat wallets, withdrawals, Paystack rails, custom currencies (including Roundbuck / ZiG) with the money gem as source of truth.
Places & map
POIs, check-ins, PostGIS + H3 geo layer, map page that product surfaces actually share.
Muchi AI
In-product agent with tool calling and multi-tier memory — ops help inside the same identity session, not a chatbot island.
Search
Typesense full-text plus semantic rank across the catalog of people, places, and products.
Sites & surfaces
Custom domains and path multiplex so brands can own a hostname while still riding platform identity and checkout.
Architecture
One monolith. Many domains. Shared physics.
Stack truth from the repo: Ruby / Rails, PostgreSQL + PostGIS + pgvector, Inertia + React + Vite, Solid Queue, Typesense, Kamal deploys. Auth via cookie JWT and Visa OIDC. Domains talk through clear boundaries — not through five Slack channels and a spreadsheet of API keys.
Rails
Monolith + engines
Inertia/React
Mobile-first UI
PostgreSQL
PostGIS · pgvector
Typesense
Search + semantic
money gem
Currency SSOT
Paystack
Payment rails
Pelias / OSRM
Geo + routing stacks
Kamal
Production deploys
Terrain-shaped details
Descriptive address geocoding
Self-hosted Pelias with OSM data handles landmark addresses Google never sees. Manual pins accumulate; hit rates climb because we own the data loop.
Scenario-based bulk logistics
Upload hundreds of stops, optimize routes, assign riders, resume when geocoding fails mid-batch. Failure on stop 47 pauses the scenario — it does not trash the run.
Live tracking without WebSocket theater
GPS pings over simple POST. ETag polling keeps perceived latency tight without a zoo of persistent connections on a single VM.
Multi-dimensional capacity
Weight, volume, piece count — a bale of fabric and a crate of chickens are not the same problem just because the scale agrees.
Currency honesty
Custom currencies and admin-controlled rates live in the money gem. Ledger recognition is real; marketing dashboards do not invent revenue.
Progressive disclosure UX
Single-item flows, large tap targets, clear primary and destructive actions. Built for phones first, because that is where the day actually happens.
Who it's for
Built for
- Sellers and service pros who need leads, payments, and reputation in one place
- Buyers and neighbors who already mix WhatsApp, cash, and mobile money
- Logistics operators who run mixed fleets on messy maps
- Diaspora users who still need a foot in the local economy
Not a fit if
- You want a white-label clone of a US marketplace with a Zim skin
- You measure success only by GMV theater and vanity MAU
- You need us to pretend spreadsheet ops are a product strategy
Keep reading