A multi-tenant operating system for independent local businesses.
A production system operating in Kazakhstan across 7 tenants, 15 locations, and 818 recorded orders as of September 1, 2026.
Independent local businesses often split customer journeys, orders, staffing, stock, and daily controls across disconnected tools. That fragmentation makes each handoff harder to operate and verify.
Prodmake built Perko as one multi-tenant operating record connecting the customer marketplace, venue experience, staff workflows, owner controls, and production infrastructure.
One release and schema serve multiple tenants and locations. Modules, business blueprints, and country packs change the operating composition without creating tenant-specific codebases.
PostgreSQL owns orders, stock, money, workforce, and permissions. Client state and provider systems remain projections or adapters; they cannot silently replace authoritative records.
Consequential mutations retain tenant, location, actor, device, timestamps, idempotency, and retry lineage. Corrections append compensating facts instead of editing protected history.
Authentication identity, customer membership, and staff assignment remain distinct. Orders and reward liabilities keep their source business and location instead of being merged across the network.
Module access requires separate entitlement, activation, readiness, rollout, and permission checks. Unsupported offline payments and unresolved financial or sync states stay blocked and visible.
Share the market, constraint, current state, and budget reality in writing. If it looks like a fit, you will get a human response with the next step.
Start a product brief