In production · Odesa, Ukraine

Equipment maintenance for restaurant chains, in one place.

EquipmentManager keeps every fridge, oven, POS terminal and venue PC on record, schedules maintenance, tracks repairs and payments, and lets one service team reach the computers in every venue.

Why we built it

Restaurant equipment breaks at the worst possible time.

A chain runs dozens of fridges, ovens, coffee machines, printers, POS terminals and PCs across many venues. When their history lives in chats and spreadsheets, maintenance is missed and every breakdown starts from zero.

The problem

  • No single record of what equipment each venue has, its specs, condition and documents.
  • Scheduled maintenance is forgotten until something fails during service.
  • Repair requests and payments get lost between managers, technicians and accounting.
  • Fixing a venue PC or a receipt printer often means a trip across the city.

Our solution

  • Equipment cards with typed specs, condition, photos and documents for every venue.
  • Maintenance schedules that show what is due and what is overdue.
  • Repair requests and payments tracked end to end, with roles for each participant.
  • A hub with lightweight Windows agents for remote access, printing, logs and inventory on venue PCs.

Features

Everything a restaurant service team needs.

From the equipment register to the computers on the floor, EquipmentManager covers the full maintenance loop.

Equipment records

Cards for every unit with typed specs, condition, photos and documents, organised by venue.

Maintenance schedules

Planned maintenance for each unit, so service happens on time instead of after a breakdown.

Repairs & payments

Repair requests from report to resolution, with the related payments kept alongside.

Roles & access

Role-based access for managers, technicians and administrators.

Remote access to venue PCs

AnyDesk, browser-based Guacamole sessions and on-demand reverse SSH tunnels through the agent hub.

Printing tools & failover

Printer tooling on venue PCs, with failover so receipts and kitchen tickets keep coming out.

Log collection & analysis

Agents collect logs from venue PCs, including POS logs, and the hub analyses them.

PC inventory & accounts

Hardware and software inventory of venue PCs and management of local Windows accounts.

Subscriptions & limits

Keep track of subscriptions and their limits, so nothing runs out unnoticed.

API for automations

A REST API that plugs into workflow tools such as n8n for notifications and integrations.

Multi-client hub in progress

Designed so one service team can maintain several restaurant businesses from a single hub.

AI assistant in development

Ask about equipment or request an action in plain language, on the web or in Telegram.

AI assistant · in development

An assistant that knows your equipment and can act on it.

We are building an in-app assistant for managers and technicians. It answers questions about equipment and performs actions through the EquipmentManager API, using tool calls that are always scoped to the signed-in user's permissions.

  • 1
    Web and TelegramAvailable inside the app and in a Telegram chat, where restaurant staff already work.
  • 2
    Text and voiceType or dictate a request, for example from the kitchen while looking at the broken unit.
  • 3
    Actions via the APITool calls go through the same API and role checks as the user, so the assistant can never do more than the person asking.
  • 4
    Claude at the coreWe plan to use Claude as the reasoning and tool-use engine of the assistant.
Assistant · illustrative example
When is maintenance due for the combi oven at our second venue?
→ equipment.search(venue, "combi oven")
→ maintenance.schedule(equipment_id)
The next scheduled maintenance is in 5 days. The last service note mentions a worn door seal. Shall I create a repair request for it?
Yes, please.
→ repairs.create(equipment_id, "Replace door seal") ✓ allowed for your role
Done. The repair request is created and linked to the oven's card.

Illustrative example of the planned interaction, not a product screenshot.

How it works

A central hub, lightweight agents in every venue.

The web app and API run as a hosted service. Each venue PC runs a small Windows agent that connects back to the hub, so the service team can see and fix things without being on site.

Web appmanagers · technicians Telegramtext · voice n8n / automationsREST API EquipmentManager hub API · records · schedules · repairs agent registry · remote access · log analysis each agent connects to the hub Venue A PC agent POS · printer Venue B PC agent POS · printer Venue C PC agent POS · printer
  1. Register equipmentAdd venues and equipment cards with specs, photos and documents.
  2. Install the agentA Windows agent on each venue PC connects to the hub and reports inventory and logs.
  3. Plan and reactMaintenance schedules and repair requests drive the team's daily work.
  4. Fix remotelyOpen a remote session or tunnel to the venue PC on demand, straight from the app.

Stack

TypeScript monorepoNode 22ExpressReactViteSQLiteDocker

Status

In production since 2026.

Development started in April 2026 and the product has been running in production since mid-2026. We are independent and bootstrapped.

Stage
In production
Started
April 2026
Funding
Bootstrapped
Based in
Odesa, Ukraine

Contact

Let's talk about your equipment.

Questions, partnerships or a demo for your restaurant chain: write to the founder directly.