Stop selling hours. Start shipping products.

Clients want fast, working software they own. Open Mercato enables fixed-price projects on a reusable foundation with sensible margins.

Clone the Repo
See Live Demo
the math

Same client project. Completely different economics.

A typical CRM/portal project for a mid-market client. Here’s what changes when you stop building from scratch.

Without Mercato
With Mercato
Auth, RBAC, multi-tenancy3 weeksIncluded
CRM core + entities4 weeksIncluded
Design system + UI2 weeksIncluded
Search, events, caching2 weeksIncluded
Client-specific features4 weeks3 weeks
Testing & security audit2 weeks1 week
Total delivery17 weeks4 weeks

3× the margin.

See Live Demo
Same scope. Same price to the client. 4 weeks instead of 17.
Your workflow

Clone → Overlay → Ship → Repeat.

  1. 01

    Clone the base

    Fork Open Mercato for the new client. Auth, CRM, design system — running in 5 minutes.

    Day 1
  2. 02

    Overlay their workflow

    Your team (or AI agents) drops files in src/apps/. Core never modified. Clean separation.

    Week 1–3
  3. 03

    Ship & handoff

    Client gets a fully-owned codebase on their infra. No vendor lock-in. No recurring platform fees.

    Week 4
  4. 04

    Maintain & upsell

    Sell ongoing feature development. Each overlay is scoped — easy to estimate, profitable to deliver.

    Ongoing
What your team gets

Mid-level devs ship senior-quality output.

The architecture and AI guardrails do the heavy lifting. Your team learns real skills — not workarounds.

Architecture that enforces quality

OCP overlays mean your devs can’t accidentally break core modules. The structure prevents the mistakes before code review catches them.

AI agents that follow the rules

AGENTS.md and .ai/specs/ ship with the repo. Claude, Cursor, Copilot — they all generate code that fits the architecture, not fights it.

Real AI engineering skills

Your team learns spec-driven development and context-first workflows. Skills compound across projects.

Enterprise security out of the box

Field-level encryption, RBAC, audit trails, GDPR. Stop spending 3 weeks on auth for every client. Pass security reviews on day one.

Reusable across clients

Build a logistics overlay once. Use it for 5 clients with minor customization. Your IP compounds. Your margins grow.

No vendor lock-in (for you or them)

MIT licensed. Client gets full source. You’re not reselling someone else’s SaaS — you’re delivering owned software on open infrastructure.

Before vs. After

What changes on your next project.

Dimension

T&M / From Scratch
With Mercato
Pricing model3 weeksFixed-price packages
Time to first demo4 weeksDay 1 (clone + run)
Auth & security2 weeksPre-built, pre-audited
Junior dev effectiveness2 weeksArchitecture enforces quality
Client ownershipThey own the codeThey own the code
Maintenance revenueAd-hoc, hard to scopeOverlay-scoped, predictable
IP reuse across clientsStart over each timeOverlays reusable across projects
Typical gross margin15–25%50–65%
What teams ship

Case Studies

  • Senior Care Operations on Open Mercato — manager dashboard demo
    ERPMulti-tenancy

    Senior Care Operations on Open Mercato

    A demo for German non-medical senior care providers — dashboards, scheduling, and signed service-confirmation workflows, built on Open Mercato.

    Read case study
  • Open Service ticket intake screen
    CRM

    Open Service

    A centralized field service platform replacing scattered tickets, spreadsheets, and tribal knowledge with one system for intake, machine history, and technician scheduling.

    Read case study
  • TraceCore customer orders module with kanban board
    ERPEnterprise

    MRP System

    An on-premise MRP system giving food and pharma manufacturers integrated production, warehouse, and sales operations with native LOT traceability and GMP-ready audit trails.

    Read case study

Software is about to be built completely differently.

Start with 80% done.
$ git clone https://github.com/open-mercato/open-mercato.git
Clone the Repo