Fluss: the multi-tenant commerce platform behind Kreboks and MEEPLE

Fluss is a marketplace and e-commerce platform I have written and operated since 2023. One codebase runs several independent shops and marketplaces, each with its own domain, admin, catalogue and payments. It is not open source and it is not rented from a menu: I configure and extend it per project, and the client keeps the code and the data.

What is Fluss?

A Laravel back office with a Vue storefront rendered on the server, split into tenants. A tenant is a shop, a marketplace or a plain website with its own domain, staff, roles, languages, catalogue, customers and orders. The software underneath is updated once for everyone. As of 2026 it ships in 5 languages, with 8 plug-ins (payments, accounting, delivery, registries, AI providers, chat, wishlist, comparison) and 51 payment gateways for different countries.

Who runs on Fluss?

• KreboksAn agricultural B2B marketplace delivered for RGP SIA in 2025: company buyers, invoice and pay-later terms, regulated products, integrations with state registers, 500 additional tenants with a target of 6,000. The project and its registry connections belong to RGP.
• MEEPLEA board-game rental shop in Riga. One day from tenant archive to a live store; shares a small server with this site.
• Jobsucher and ElontradeTwo products that use Fluss only as their payment system: a subscription is sold as a product, and Fluss handles the checkout, the gateway and the invoice.
• This sitecunskis.lv is a Fluss tenant with no catalogue: pages, forms, three languages, structured data and the security headers come from the platform.
• OtakuFestThe first client in 2023, a convention shop. It has since closed; the lessons from it are in every tenant that came after.

What did the Kreboks project actually require?

Company accounts with registration and VAT numbers, per-customer price lists, licence checks before restricted products can be bought, orders split per supplier, invoice PDFs at placement, lookups against state registers, and an admin that a non-technical team runs daily. Most of it was configuration of what Fluss already did. The registry integrations and the licence workflow were built for the project.

What did I decide not to build?

A product tagging system. The client asked for it; search already covered the need. I said no in writing and the request was closed the same day.

A product import before the supplier had agreed a file format. A parser written against a guess is written twice, so it waited for a sample file.

Why not Shopify, Magento or WooCommerce?

For a five-product consumer shop, use Shopify. Fluss earns its place when the customers are companies, the products are regulated, there is more than one brand, or the checkout has to follow rules a rented platform does not know. The full comparison is on the e-commerce page. E-commerce and Marketplaces.

How does a Fluss project start?

A call about your customers, your products and the rules you follow. If Fluss fits, you get a quote for consulting, configuration, training and whatever has to be built; there is no platform licence and no monthly fee per anything. A first version is typically live in two to six weeks, on a server that costs less than a lunch.