Maintra overview

API-first EAM architecture

The Maintra API is the product. Build any client around it.

Maintra keeps asset, work, planning, authorization and audit rules in one backend. Use the Maintra web and mobile apps, or connect customer-built clients, sensors, agents and enterprise systems through the same governed APIs.

Review a deployment plan See the system design
Compact enterprise IT room with a standard server rack, network switch, database storage, industrial edge gateway and rugged field tablet
One compact rack can host the API, database, network controls and plant-edge connections.

Product boundary

Keep EAM rules in the backend and infrastructure choices open.

Maintra’s backend enforces asset relationships, work transitions, permissions, audit records and integration controls. Web, mobile and customer-built clients can change while those rules remain in one supported service layer.

Shared API contracts

Every client uses the same maintenance rules.

The web app, field mobile client, customer applications, equipment signals and delivery agents call the same domain services. The database records each accepted state change and its audit trail.

Client surface
Choose the brand, device, workflow and implementation technology.
API rules
Share permissions, lifecycle transitions, receipts and record ownership.
Database records
Commit operational state, audit and recoverable background work in the database.
Review the API contract model

Architecture decisions

Review the five decisions behind a Maintra deployment.

Each view states the supported pattern, the operating controls and the decisions that belong in a customer-specific proposal.

API as the product

One EAM API for every client.

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.

 Deploy anywhere

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

Maintra ships as a containerized API application backed by a database. Run it on a private VPS, on-premise infrastructure, AWS, Google Cloud or another container platform, then size each environment for its workload and service levels.

 Data & scale

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

Maintra stores EAM records, audit, idempotency receipts, background job claims and workflow state in the database. API, worker and database capacity can be scaled independently. Redis remains optional.

 Custom apps & connections

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

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.

 Agent-assisted delivery

Use delivery agents for bounded changes under human release control.

Product-aware delivery agents inspect Maintra’s contracts, update existing configuration or code paths, run the established checks and prepare release evidence. People define the scope, review risk and authorize production.

Deployment footprint

Start on a VPS. Add capacity where the workload requires it.

Development can run one API container with a database. Test and UAT add controlled data, identity, migrations and promotion. Production can add API replicas, external workers and database resilience. A million-request target becomes an engineering requirement only after the time window and workload profile are defined.

Compare deployment topologies

Development

One API container

Run the application and database with a small, inspectable footprint.

Test and UAT

Separated environments

Control configuration, migrations, identity, backups and acceptance data.

Production

Independent capacity

Size API containers, background workers and database for measured demand.

Database design

Store transactional state in the database. Add Redis only when needed.

Work status, audit, idempotency receipts and background job claims commit through the database. The smallest deployment needs no separate queue or cache. Add Redis for a defined cache, rate-limit or coordination workload after measurement.

Review database and capacity planning

First-party and custom clients

Use the Maintra apps or build for a specific operation.

Maintra web and mobile applications provide the standard operator experience. Customers can also build a role-specific console, contractor portal, inspection device or data-platform connection against the same APIs.

Each client shares the same permissions, work transitions and audit rules.

Explore the Maintra mobile starting point

Review custom clients and integrations

Agent-assisted customization

Use LLMs to shorten bounded changes. Keep production approval with your team.

Product-aware delivery agents inspect the current contract, update an existing configuration or code path, run the established checks and prepare release evidence. People define the requirement, review data and operational risk, and authorize UAT or production.

A delivery plan can target days for a well-defined configuration or integration. Scope, data impact and operational risk determine the schedule.

Review the governed delivery process
Define intent Extend existing product Run executable evidence Human production approval Deploy and verify

Production requirements

Define service levels before production.

Each deployment proposal specifies hosting topology, throughput, availability, backup, recovery, data residency, identity and external connections. Technical discovery turns those requirements into an implementation and acceptance plan.

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