RepairCore Cloud generalises the process that has been running in real workshops and fleets since 1998 into a platform other organisations can use. This page shows what already runs in production, what does not yet exist, and how to start a conversation.
by Muto · Automotive Technology
Three things that separate this from another workshop system drawn from scratch: where the product comes from, the shape of its data, and how it earns.
The product is built by generalising a process that genuinely runs - in the eCarService workshops and in FleetPoint fleet coordination - rather than by designing a system away from the workshop floor and selling it into the industry afterwards.
The workshop, the fleet and the network work on the same work order and the same vehicle card, instead of three separate systems stitched together after the fact. That is an architectural decision a competitor cannot copy with a single feature.
Four subscription plans with public prices and a published work-order limit, with three deliberately separate layers above them: add-ons, usage and individual rollouts. We do not sell "everything, unlimited, in the top plan".
The platform is developed by Muto sp. z o.o. The operator’s registry data and the product’s origin are set out on the Company page.
Go to the Company pageThe maturity of each item is stated plainly. What is a pilot we call a pilot - and what runs in production is not talked down just to sound careful.
The current SaaS platform, actively developed towards RepairCore Cloud - with a working core of work orders, estimates, subscription billing and a full audit trail of decisions.
The damage-estimate decision inside an existing work order, with deadlines and a decision trail - running today in production with an insurance partner.
Data exchange with technical partners - controlled, auditable access granted individually after verification and consent; the broader partner platform remains a direction, not a state.
Service relationships built since 1998, today in a requalification programme - activated with further partners after verification, contact and consent.
We are not starting with an empty partner base. We are starting with a quarter-century of service relationships, which we turn into a network through a controlled requalification process.
500+
Historical service records for requalification
16
Regions in the historical relationship base
118
Records from the earlier eCar structure
Historical data. Current partner status requires renewed verification, contact, consent and confirmation of the scope of cooperation. Historical network relationships do not represent active RepairCore Cloud subscriptions.
We publish anonymised aggregates only. We publish no workshop names, addresses or contact details, and every entity may update its data or opt out at any stage.
See the full network registerFour separate monetisation layers. Separate on purpose - blending them is the most common way vertical SaaS loses its margin to rollouts.
Four plans with a published price and a published monthly work-order limit, billed per organisation.
Specialist technical data, advanced automation and additional communication channels - a separate product and a separate licence, never "included in the plan".
Messages sent and paid external lookups, billed on actual consumption.
Service networks, large fleets, CFM, insurers and enterprise integrations - priced per contract.
Subscription plans
There is no public signup or checkout today - every plan path leads to a conversation. That is a known gap in the funnel, not a product feature.
See the full pricingThe market for vehicle service in Europe is fragmented, increasingly regulated, and has no dominant vertical player covering the workshop, the fleet and the network with one product.
Independent workshops run on a mix of separate tools, spreadsheets and paper. What wins is not another feature, but joining the process into a single record.
The strong vertical products grew primarily in the US market. Europe has no equivalent covering workshops, fleets and networks at once.
Documentation and settlement obligations grow faster than a small organisation’s capacity to handle them by hand. That turns software from a convenience into a requirement.
The same work-order record serves an individual customer and a fleet, but a fleet contract carries higher value and a longer horizon. One product, two sales motions.
Mechanisms that are a constant of the architecture, not a parameter of one rollout. Described by what they do, not by vendor name.
One organisation’s data is separated at the architectural level, not merely by a filter in a query.
A multi-site network sees its locations separately and together, with no data mixing between entities.
Vehicle and work-order history can be reconstructed: who decided on a cost, when, and on what basis.
Sensitive operations require an additional confirmation - and when verification is unavailable, the operation is held rather than let through.
Traffic to programmatic interfaces is rate-limited and monitored, which contains the blast radius of a faulty or malicious integration.
A new capability can be enabled for one organisation ahead of the rest, so it can be piloted without risk to every customer.
Hosting, data location and the remaining infrastructure parameters are agreed individually with each partner during onboarding.
Six points that limit the product today - and what we are doing about each one.
There is no public signup or checkout today - a conversation carries the sale. Closing the path from website to subscription is the first direction for capital.
The entitlement engine runs in observe mode today: it measures and reports before it starts refusing. That is why we publish exactly one numeric limit and confirm the rest of the boundaries at onboarding.
Support for the national e-invoicing system is functionally complete but runs in a single-environment pilot. Extending it to further organisations is planned, not done.
The broad "any audited partner plugs itself in" programme is deliberately on hold in favour of case-by-case pilots. We do not sell it as available.
Today the product grows out of a single operating environment in Poland. That is the source of its credibility and, at the same time, a concentration risk - diversifying needs capital and partners.
Historical relationships are not active partners. Every record goes through verification, contact and consent before it becomes part of a working network.
Four different conversations, each with a different first step. Choosing a path in the form below lets us answer with specifics instead of a generic deck.
An introductory call, then the materials pack: financial model, operating indicators, company structure and pilot status.
A shared use case on one concrete process - a fleet, an insurer, a network - before we discuss the shape of an agreement.
A technical conversation about the scope of data exchange and a pilot on a limited scope, ahead of any public communication.
Verification of the scope and terms of cooperation, followed by entry into the network requalification programme.
The scope of materials investors and partners receive after an initial call.
Investor pack
We share materials individually, after a short introductory call. We sign a non-disclosure agreement at the other side’s request.
Contact
Arrange a meetingRepairCore Cloud is developed by Muto sp. z o.o., Poland.