Stallora is a working multi-vendor marketplace, and a production-shaped Spring Boot microservices reference implementation. Several independent shops sell through one storefront; a basket can hold items from all of them; at checkout the order splits into one delivery per shop; each shop fulfills its own slice and is settled separately with commission taken. You get the whole thing — six services, a server-rendered storefront, two web consoles and a Flutter app for iOS and Android — as source.
Before you buy: this is six JVMs, Kafka and PostgreSQL. It requires a VPS with at least 6 GB of RAM (8 GB recommended) and Docker. Measured peak on a cold start is 3.35 GB across all thirteen containers. It will not run on shared hosting or cPanel, which cannot run Docker or a JVM at all. Payments are deliberately mocked — one interface to implement, documented step by step.

This is the signature interaction. A basket can hold items from any number of shops. At checkout the order splits into one sub-order per shop — each with its own subtotal, its own fulfillment status and its own settlement. Paying moves all of them at once. Stock is reserved synchronously, so overselling is impossible, and refunds are per shop inside that shop’s return window.

deploy/verify-m4.sh builds the jars, cold starts all thirteen containers and walks the entire product path with 32 assertions.Every client — the Flutter app, the storefront and both consoles — goes through one Spring Cloud Gateway that validates the JWT, rate limits and denies internal routes at the edge. Behind it, six services each own their own PostgreSQL database; no service reaches into another’s tables. Consistency is events plus compensation over a transactional outbox on Kafka, not a distributed transaction coordinator. One Jaeger trace crosses the gateway, the services and the queue.

A delivered sub-order becomes billable when its return window closes — never when it was paid. Commission is resolved most-specific-first and frozen onto the bill, so changing a rule later never rewrites history you already settled. The seller requests a payout, which locks those bills so nothing is paid twice, and an admin approves before money leaves. Refunded sub-orders are excluded before billing rather than clawed back afterwards, which is why the return window and the settlement window are the same number.

Source for all of it — nothing is a compiled black box:

The storefront is Next.js 15 with product and shop pages rendered on the server, plus a sitemap and robots.txt out of the box, search, category filters and paging. Buyers can sign up on the storefront or in the app — it is the same account either way.

One codebase, both platforms, no web view. Riverpod state, persisted session and cart, infinite scroll, and a demo mode that needs no server. Sign in, storefront, product detail, shop page and account are all finished screens, not placeholders — and every one of them calls the same gateway the web surfaces call.

A seller manages their own products, their own stock and their own orders to ship, decides refund requests themselves, sees earnings as gross, commission taken and net owed, and requests payouts for the platform to approve. Every request takes its shop from the token, so a seller cannot ask for another shop’s rows — and the answer is 404, not 403, because a 403 would confirm the row exists.

The admin console approves or rejects seller applications, sets commission rules per shop, per category or as a default, reviews bills per shop and approves payouts, and shows parked failures so nothing is lost silently. Approving an application creates the shop and binds it to that account in one step.

Use the Live Preview button on this page to open the buyer app in your browser and click through the real screens. It is the Flutter app in demo mode — the same code that ships in the package, running the whole buyer journey with no backend behind it. Signing in, browsing across shops, a basket that spans two shops, and a split order are all live.
1. Unzip the package 2. docker compose -f deploy/docker-compose.yml up -d 3. Wait for the health checks, then run deploy/verify-m4.sh 4. Open documentation/index.html for the 16-section handbook
Step 3 is the same gate used before release: it builds the jars, cold starts all thirteen containers and walks the entire product path with 32 assertions, so you know the whole system is healthy before you touch a single file. The database is seeded with demo shops, products and accounts, so the storefront and both consoles have real rows in them on the first boot rather than empty tables. The handbook covers VPS setup, TLS, secrets, backups, doing database work without the command line, and replacing the mock payment gateway.
PaymentGateway is the seam; the handbook covers implementing it, including webhook idempotency. No processor keys ship with the item.deploy/verify-m4.sh will tell you exactly which container is unhealthy.Version 1.0.0 — initial release.
$133 |
Download |
0 average based on 0 ratings.
| Last Update | 2026-08-18 |
| Created | 2026-08-18 |
| Sales | 1 |
| Discussion | Comments |
| Software Version | Flutter 3.x |
| Files Included | Dart YAML JavaScript JSON .java CSS HTML |
| Video Preview Resolution |