Custom apps & connections

Build role-specific apps and integrations without duplicating EAM rules.

Maintra web and mobile applications use the same backend contracts available to customer-built clients. Build role-specific apps, partner portals, sensor adapters, agent workflows and enterprise handoffs while Maintra retains asset and work rules.

Plan a technical review

Reference topology

Client choice with one set of EAM rules.

First-party and customer-built clients call the Maintra API. Equipment signals, inspection agents, ERP handoffs and data platforms connect through governed integration contracts.

Custom clients

Build a focused interface against supported APIs.

A customer-specific screen can be role-based, branded or embedded in an existing portal. Backend services continue to enforce permissions, workflow transitions, validation and audit.

  • Web, native mobile, kiosk and supervisor experiences
  • Role-shaped payloads instead of raw database access
  • One authorization and lifecycle model across clients

Mobile contracts

Use explicit packets and synchronization rules for field work.

The mobile product family supports assigned queues, execution packets, batched mutations, receipts, replay and conflict handling. A customer-branded client can use those contracts for work-order execution on intermittent links.

  • Device and session-aware bootstrap
  • Cursor-based pull and packet versions
  • Replay-safe field actions and attachment intent flows

Equipment signals

Authenticate and deduplicate incoming operational events.

Maintra can attach sensor readings, inspections, external events and agent observations to asset context. Any resulting maintenance action still passes through the configured permissions and approval rules.

  • Meter and observation capture
  • Source identity and duplicate-event protection
  • Reviewable action proposals with bounded write payloads

Enterprise handoffs

Keep each system responsible for its own records.

Typed events and secret-backed webhooks carry maintenance context to ERP, identity, data and partner platforms. Maintra retains asset and work records; each connected system retains the records it owns.

  • Typed events, delivery attempts, retries and replay
  • Maintenance-specific material and capital handoffs
  • Connection scope validated with representative scenarios

Implementation constraint

Use typed extension points and external adapters.

Customer extensions use typed contracts, bounded expressions and external adapters. Maintra reviews inbound event mapping and customer-specific connectors as integration work, with explicit ownership, security and upgrade requirements.

Related decisions

Continue the technical review.

Architecture overview
API as the product

One EAM API for every client.

 Deploy anywhere

Run one container on a VPS, then add capacity without changing application code.

 Data & scale

Keep transactions in the database. Add caches for measured bottlenecks.

 Agent-assisted delivery

Use delivery agents for bounded changes under human release control.

Evaluate Maintra against a real maintenance process.

Use a representative asset, work order, access model and operational handoff to assess product fit.

Plan an evaluation session