Open Mercato in one sentence
Open Mercato is an open-source AI-Engineering framework for building business apps — CRM, ERP, e-commerce, customer portals, ops dashboards. Instead of starting every project from an empty folder, you get „80% done” out of the box: auth, roles, multi-tenancy, audit, catalog, orders, search, an AI assistant — and you only add the 20% that actually differentiates your company.
It is not a finished SaaS where you pay per user. It is not low-code where you're locked inside a visual editor either. It is a framework for developers (and for AI), distributed as a versioned npm package, MIT-licensed and fully code-accessible.
Who is Open Mercato built for?
The Open Mercato team explicitly calls out three target audiences. Each solves a different problem, but they share one thing: ready-made SaaS turned out to be too narrow, and building from scratch — too slow.
- 1
Teams in mid-sized and large companies
They want to launch a new product — a shop, a partner portal, an ops tool — without six months of setting up auth, an event queue and CI/CD. Open Mercato gives them a foundation in week one.
- 2
Software houses and agencies
They deliver fixed-scope projects for clients. Every project is 70% identical to the previous one and 30% different. Open Mercato lets them prepare their own overlay, reuse it across deployments, and improve margin.
- 3
Companies running away from low-code
They started on Bubble, AppSheet or Retool and hit a ceiling — performance, cost, or features. They want to keep the speed they had but this time control the code, the database, and licensing costs.
What's in the box?
Open Mercato is built from modules that you'd normally spend the first 3–6 months of every new project building. Here they're available immediately — ready to use, wired into a coherent architecture, and covered by tests.
Security and foundations
- Authentication and RBAC (roles)
- Multi-tenancy — many customers, one database
- Change audit and undo
- Vault with AES-256 encryption
Business logic
- CRM (customers, contacts, deals)
- Orders, shipments, warehouse
- Product catalog + CPQ (quote configurator)
- Workflow / automations
- Customer self-service
Performance and AI
- Event-driven architecture, Redis cache, Meilisearch
- Custom entities (your own objects)
- Built-in AI Assistant + MCP support (Model Context Protocol)
- Specs written with coding agents in mind
The core idea: „modify nothing, extend everything”
That sentence sets Open Mercato apart from most frameworks you know. The classic approach is to fork — you grab the repo, copy it to your own org and start editing files. Six months later your code has nothing in common with the original, upgrades become impossible, and every new framework release is a migration project.
Open Mercato does it differently. The framework core is a versioned npm package — exactly the same as any other library. Separately, you create what's called an overlay: an extension layer that plugs into the core at build time, adds new fields, entities, views and logic — but does not modify the core files.
AI is not bolted on at the end — it's built in from day one
Most ERPs on the market were designed 10–15 years ago. The AI assistant was added recently as a layer „next to” the engine. The result: AI only sees fragments, doesn't know the full data model, and can't write meaningful extension code.
Open Mercato approached this differently. The framework ships with written specifications from the very beginning — an AI assistant (e.g. Claude inside Cursor) sees the entity schema, module contracts and architectural conventions. As a result, the code it writes is consistent, safe and fits the rest of the system.
- 1
AI Assistant inside the app
Your users talk to the system. „Show orders stuck for more than 5 days” generates a report. „Send an offer to customer X based on the last deal” creates a document.
- 2
MCP (Model Context Protocol)
A standard that lets external AI agents (Claude Desktop, ChatGPT) ask your system for data and trigger actions. Open Mercato supports MCP in the core.
- 3
Agent-friendly architecture
Conventions, file structure, naming and comments are designed so a coding agent doesn't get lost. That's the difference between „AI writes 30% of correct code” and „AI writes 90%”.
Open Mercato vs ready-made SaaS vs custom code from scratch
| Aspect | Ready-made SaaS | Open Mercato | From scratch |
|---|---|---|---|
| Time to start | Weeks of configuration | Days (foundation ready) | Months |
| Process fit | Low | High — overlay | Full, expensive |
| License cost | High, grows with users | None (MIT) | None |
| Vendor lock-in | Very strong | None | None |
| Updates | Done for you by SaaS | Bump the npm version | You do them yourself |
| Reuse with the next client | No | Yes (overlay) | Every project from scratch |
| Cooperation with AI | Very limited | Built in (MCP) | Depends on discipline |
The Open Mercato team cites an example: a logistics ERP built in 6 weeks, with no license fees and no vendor lock-in. Those numbers sound unbelievable next to a classic Comarch or SAP B1 deployment — and that is exactly what an AI-ready framework changes.
When Open Mercato is NOT for you
No tool is universal. Open Mercato shines when your process is a bit non-standard and you care about control — but there are a few cases where you should pick something else:
- Very standard process — a typical B2C shop → just take Shopify. Open Mercato shines where standard isn't enough.
- No access to a developer — this is a framework, not no-code. You need a developer (or an agency) to stand up the first version.
- An industry that requires certifications — medical, aviation. Here a ready-made certified system is often mandatory.
- A company below 10 people with no growth plans — the cost of standing up your own system (even in 6 weeks) can be higher than a year of a simple SaaS subscription.
A practical scenario: an orthotics manufacturer
Picture a company manufacturing orthopedic orthotics. 35 people in production, 3 sales reps, 1 accountant. Processes: individual quoting based on patient measurements, batched production planning, settling with the public health fund and private clients.
Comarch or SAP B1 — a deployment that costs hundreds of thousands, a rigid quote configurator, months of waiting for customizations. Excel + 3 emails a day — works, but quoting errors cost the company a few percent of margin per year.
Summary — is it worth a look?
Open Mercato is the answer to a question mid-sized company owners have been asking themselves for years: „How do I get a system written for us without spending a million and waiting two years?” The framework solves it by combining three things:
- A ready core with modules every business project would have to build anyway.
- Overlay architecture, which protects you from vendor lock-in and lets you upgrade the core painlessly.
- Built-in AI, which shortens delivery time and lowers maintenance cost.
If you run a mid-sized business with a process that doesn't fit in the box and you have access to a developer or technology partner — Open Mercato is worth considering instead of yet another „big” ERP license.
Related article
Low-code vs ready-made CRM/ERP — what to choose?
Manufacturing implementations
Open Mercato for mid-sized manufacturers

Mateusz Kozłowski
Założyciel flowbiz · Ekspert automatyzacji procesów
Wdrażam automatyzacje, integracje i AI w średnich firmach na Pomorzu i w Kujawsko-Pomorskiem.
