API as the product

Keep EAM rules in one API across web, mobile and integrations.

Maintra enforces asset, work, planning, authorization and audit rules in the backend. Maintra web and mobile apps, customer-built clients and integrations use the same API contracts.

Plan a technical review

Reference topology

One contract across every client.

Web, mobile, custom apps, sensors and agents call the same domain services. The database records each accepted state change and its audit trail.

Domain services

Keep asset and work rules in the backend.

Asset relationships, work status transitions, material readiness, permissions and audit rules run in backend services. A new client can use those rules without reimplementing them.

  • Domain-specific services for assets, work, planning, materials, reliability and safety
  • Organization and site scope resolved at the API boundary
  • The same governed mutations used by first-party and customer-built clients

Supported contracts

Publish contracts that clients can implement and upgrade against.

Maintra exposes OpenAPI documentation and product-contract metadata. Each supported product family identifies its compatibility posture, pagination model and synchronization policy before a client depends on it.

  • Contract-family metadata and compatibility preview
  • Typed request and response models at the service boundary
  • Additive evolution before a second live contract version is justified

Retry-safe writes

Make retries safe when links are unreliable.

Retry-sensitive operations create idempotency records and receipts. Mobile batches, automation workers and browser actions can retry a request without creating a second maintenance action.

  • Replay readback through mutation receipts
  • Conflict-aware mobile execution mutations
  • Atomic database boundaries around business changes and their receipts

Server-side reads

Fetch the records each client needs.

Server-side search, filtering, keyset pagination and cursor-based synchronization keep large record sets out of the client. Mobile packets contain the work and reference data needed in the field.

  • Server-backed lookup and filter contracts
  • Delta reads and checkpoints for mobile consumers
  • Purpose-built projections for field and operational workflows

Implementation constraint

Publish only the contracts Maintra can support.

Each implementation classifies which contract families are supported for suite or customer use. Internal and preview routes stay outside the customer integration surface until Maintra can support their compatibility and upgrade path.

Related decisions

Continue the technical review.

Architecture overview
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.

 Custom apps & connections

Use Maintra apps or build a custom client against the same APIs.

 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