Building Muchiround: Business and community on one stack

People still call Muchiround “the logistics app.” Wrong. Open the monorepo.

Muchiround is where Southern African sellers, pros, buyers, and neighbors trade, talk, and move goods. Sell a product. Hire a plumber. Chat a customer. Follow someone who knows the neighborhood. Pay a courier. Check in at a place. One account, one map, one wallet trail — not five apps duct-taped with hope.

This is how we built it, and why the seams look the way they do.

Start from constraints, not analogies

Clone marketplace X and you inherit their country: tidy street numbers, always-on networks, one currency, English-only support, homogeneous fleets. Those defaults die in Harare on a Thursday, Bulawayo on market day, or when a cousin in the diaspora needs a plumber on the ground.

We named the constraints first:

• Addresses are often landmarks, not street numbers
• Fleets mix bikes, cars, and whatever is running today
• Money moves across rails and currencies that change under you
• Users live on phones and bounce between chat and commerce without ceremony
• Trust is local — social graph and transaction history belong next to each other

Then we chose a stack that can hold all of that without five SaaS accounts and a prayer.

One application, many domains

The live surface is a Rails monolith with domain engines — namespaced models, controllers, services, jobs — sharing auth and database. From the domain index in the repo, the public-facing picture includes:

• Identity — users, business profiles, KYC, OIDC
• Feed & communities — posts, reactions, follows, groups
• Commerce — products, carts, checkout, disputes, reviews
• Payments — wallets, ledger, withdrawals, gateway rails
• Logistics — couriers, jobs, capacitated routing, live tracking
• Messaging — DM and business threads with product and order cards
• Leads — pay-per-lead for service pros
• Places / Geo — POIs, PostGIS + H3, map page
• Search — full-text plus semantic
• Muchi AI — tools, memory, help inside the same login
• Sites — custom domains and path multiplex for branded surfaces

That list is not a roadmap slide. It is how the code is organized today.

Logistics still matters — it is not the whole product

RouteFlow is the capacitated vehicle routing path: scenarios, multi-vehicle capacity (weight, volume, piece count), mixed fleets, resumable bulk ops. Geocoding leans on self-hosted Pelias for descriptive addresses. Routing stacks are pluggable. Live tracking prefers simple GPS POSTs and ETag polling over WebSocket cosplay on a single VM.

If you only need fleet software, those pieces stand alone. Most of our users do not only need fleet software. They need the order, the chat, the wallet debit, and “where is my guy” to stop living in four apps.

Commerce next to community

Storefront and social feed share the platform on purpose. Discovery is not only ads. Reputation is not only stars. A seller who shows up in a community and completes escrow cleanly is a different product than a cold listing page.

Leads are the profitability spine for service pros: prepaid budgets, paid delivery, refund discipline. Internally we treat leads net revenue as the north star — not GMV theater. That focus shows up in what we refuse to scale until the metric prints.

Money has physics

Wallets, ledger entries, Paystack rails, custom currencies (including Roundbuck and ZiG) go through the money gem as source of truth with admin-controlled rates. Auto-fund can cover a charge across wallets in one tap and still leave an honest ledger trail. Marketing dashboards do not invent revenue the ledger cannot defend.

Frontend that matches the street

The UI is Inertia + React + Vite, mobile-first, progressive disclosure. Single-item flows. Large tap targets. Clear primary and destructive actions. Custom domains can host branded surfaces while auth and checkout stay on trusted hosts — path multiplex instead of a new OIDC app per vanity domain.

What we will not pretend

We will not call a pilot “scale.” We will not stack fee products before pros see lead ROI. We will not publish classified side projects as if they were the public roadmap. Muchiround earns the homepage because the codebase and the users are there.

If you are evaluating us

Read the product page. Ask how a single user journey crosses commerce, chat, wallet, and logistics. If the answer requires four vendors and a spreadsheet, that is not this system.

Next: Muchiround product · Self-hosting Pelias · Rails engine architecture · Talk about access