OpenMercato · The foundation of our implementations

OpenMercato —a system that belongs to you.

OpenMercato is an open-source (MIT), AI-native foundation platform for ERP, CRM and commerce. Omdyo co-creates its core and implements it as a certified partner — and this page explains its architecture and philosophy: why an implementation starts at 80% and ends with a system tailored to 100%.

Scroll
In short

What is OpenMercato?

OpenMercato (also written „Open Mercato") is an open, MIT-licensed foundation platform for building ERP, CRM and commerce systems. Instead of configuring an off-the-shelf SaaS, you get roughly 80% of the repeatable machinery — modules, permissions, multi-tenancy, events — and build the remaining 20% that sets your company apart as your own code: no fork, no per-seat fees, and full data ownership.

More: openmercato.com · GitHub (open source, MIT) · our partner profile

Philosophy

Three principles that shift the balance of power.

01

Open code, not a subscription.

OpenMercato is MIT-licensed open source. The code, the data and the infrastructure sit on your side — no module fees, no per-seat fees, no black boxes. You pay for work that builds your edge, not for permission to use your own system.

02

The system fits the process, not the other way around.

Closed platforms sell a template — it is your company that has to change to fit it. OpenMercato reverses the direction: from day one the architecture assumes every process has exceptions, and gives them a home inside the system, not in a spreadsheet next to it.

03

80% ready. The 20% makes the difference.

Over 50 modules cover what looks alike in every company: catalog, sales, CRM, documents, permissions. So all the implementation energy goes into the 20% that sets you apart from the competition.

Architecture

Everything is a module.

Every capability of the platform is a self-contained block: it has its own API, its own pages, its own data, events and permissions. Modules never reach into each other’s internals — they talk only through events and explicit contracts.

That is why each of them can be enabled, disabled, replaced or taken over — with no risk to the rest of the system. And that is why your module, the tailor-made one, is a first-class citizen in the system, not a bolted-on plugin.

  • own API
  • own data
  • own events
  • own permissions
  • own interface

Under the hood: TypeScript, Next.js and PostgreSQL, communication over an event bus, Redis for caching and full-text search. Modules are auto-discovered, and each ships its own AGENTS.md — machine-readable guardrails that keep AI-generated code aligned with the architecture.

OpenMercato ready modules: Catalog, Sales, CRM, Customer portal, Workflows, Payments, Shipping, Currencies, Staff, Communications, AI assistant, Data import, Webhooks, Permissions, Audit, Custom fields, Search, Dashboards, Notifications — plus your own module.

Layers

Five layers. One organism.

Modules arrange themselves in layers — from the foundation every company gets, to enterprise-grade extensions. All of them work on the same data and by the same rules.

The five OpenMercato platform layers: Foundation (permissions, company structure, custom fields, audit and undo, search); Commerce (catalog, sales and documents, payments, shipping, currencies); CRM and operations (relations and pipelines, customer portal, staff and rosters, workflows, communications); Integrations and AI (import / export, API and webhooks, PIM, supervised AI assistant); Enterprise (SSO and SCIM, MFA, record locking).

Tailoring

Three levels of change. Zero forking.

Fitting your process must not mean copying the platform — that way you lose updates and end up alone. So changes are made on three levels, from the lightest touch to full ownership.

01

Overrideoverride

With a single declaration in your app you replace any platform contract: an API route, a view, an event, a permission. Updates keep coming — your change stays.

02

Extendinject

You add a tab, a column, a field or your own logic to another module — without touching its code. The platform has named, stable extension points for exactly this.

03

Take overeject

You pull a module into your own application, and from that moment it is yours — down to the last line of code. An owner’s deliberate decision, not a desperate fork.

A closed SaaS ends the conversation before level one. Levels two and three don’t even have a price list.

Flow

Events instead of duct tape.

Every change in the system announces an event: a deal won, an invoice paid, a new customer. Other modules — and your integrations — listen and react. No point-to-point glue, no brittle connectors.

event Sales: deal won
workflowCustomer onboarding kicks off — with tasks assigned to specific people.
webhookYour ERP and accounting get the signal in the same second.
communicationsAn email goes out to the customer, and the conversation stays with the deal record.
Trust

Security by construction, not by price list.

Data isolation

Multi-tenant architecture: every query runs within the boundaries of the organisation it belongs to. The platform refuses to run a query without that context — by principle, not by convention.

Field-level encryption

Sensitive data is encrypted at the level of individual fields, with a separate key per organisation. What gets protected is configured from the admin panel — no code changes.

Per-feature permissions

Access is granted per individual feature, not per broad role. Without the permission, you won’t see the page, the button, or the API behind them.

AI under supervision

The AI assistant sees exactly what its user sees — and not a record more. Every write it proposes waits for a human “yes”.

0+ready modules as standard
0per module and per seat
0%of code and data on your side
0levels of tailoring without a fork
The difference

Open versus closed.

Closed SaaSOpenMercato
The cost grows with every login.
Zero per-seat fees — the team can grow without a bill.
Your process adapts to the template.
The template adapts to the process — exceptions live inside the system.
Data and configuration stay with the vendor.
Data, code and infrastructure stay with you.
A new need? “Contact our sales team”.
A new need? A module you switch on — or one we build together.
Leaving means migrating from scratch.
Leaving means… staying home. The system is already yours.
FAQ

Frequently asked questions about OpenMercato.

Is OpenMercato open source and free?

Yes. OpenMercato is open source under the MIT license — the code, data and infrastructure stay on your side, with no module or per-seat fees. You pay for implementation work, not for the right to use your own system.

Will I avoid vendor lock-in?

Yes. Extensions and changes live in your own layer (override, inject, eject), not in the platform core — updates keep coming and the system stays yours, down to the last line of code.

What can you build on OpenMercato?

CRM and ERP-like systems, WMS, B2B portals and commerce, production workflows, and mobile apps for operational teams — usually as one coherent system integrated with your ERP, PIM or payments.

What is the OpenMercato tech stack?

OpenMercato is built in TypeScript on Next.js and PostgreSQL, with an event bus, Redis caching and full-text search. Omdyo adds .NET services and mobile apps (React Native, .NET MAUI) where a project needs them.

Who is OpenMercato for?

For operational companies — manufacturing, distribution, B2B commerce and services — whose processes have outgrown off-the-shelf tools, and for teams that want to grow without per-seat fees or vendor lock-in.

Why implement with a certified OpenMercato partner agency?

Because it shortens the path to a working system. Omdyo is a certified OpenMercato partner agency and a core contributor, so we know the implementation happy path from the inside — from architecture and security to code review and quality.

Omdyo × OpenMercato

An accelerator, not a limitation.

We are not just users of this platform — we co-create its core and are a certified OpenMercato partner agency. So we implement it the way it was conceived: openly, modularly, and around your process. If that sounds like the system you are looking for — let’s talk.