Building Muchiround: Business and community on one stack

People still introduce Muchiround as “the logistics app.” That was never the whole story. The monorepo says otherwise.

Muchiround is a place to do business and socialize. Sell a product. Hire a plumber. Chat a customer. Follow a creator. Pay a courier. Check in at a place. The domains share one identity layer, one ledger philosophy, and one map.

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

Start from constraints, not analogies

If you start from “clone marketplace X,” you inherit their assumptions: tidy addresses, always-on networks, single currency, English-only support, homogeneous fleets. Those assumptions fail in Harare on a Thursday afternoon.

We named the constraints first:

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

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

One monolith, 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 — social posts, reactions, follows, groups
• Commerce — products, carts, checkout, disputes, reviews
• Payments — wallets, ledger, withdrawals, gateway rails
• Logistics — couriers, jobs, RouteFlow CVRP, live tracking
• Messaging — DM and business threads with product/order cards
• Leads — pay-per-lead marketplace for service pros
• Places / Geo — POIs, PostGIS + H3, map page
• Search — Typesense full-text + semantic
• Muchi AI — tools, memory, in-product agent
• 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 just isn’t the whole product

RouteFlow is the generalized capacitated vehicle routing path: scenarios, multi-vehicle capacity vectors (weight, volume, piece count), mixed fleets, resumable bulk ops. Geocoding leans on self-hosted Pelias for descriptive addresses. Routing stacks are pluggable (open-source OSRM/VROOM, or commercial when a tenant pays for them). 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 don’t only need fleet software. They need the order, the chat, the wallet debit, and the “where is my guy” view to stop living in four apps.

Commerce next to community

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

Leads are the profitability spine for service pros: prepaid budgets, paid delivery, refund discipline. Strategy docs call Leads Net Revenue 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 get to 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 won’t 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’re evaluating us

Read the product page, poke the domain list, and 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