Manuqube
Technology & Infrastructure

A serious foundation for the factory you are building.

Manufacturing software needs more than a clear interface. ManuQube brings established database technology, container orchestration, layered access controls and disciplined release practices together to support trustworthy records and controlled operations.

ManuQube / MOM
MESOMSQMSEMSRMSPLMSAMSAPSWMS
ISA-95 · LEVEL 3

Technology with a business purpose

Every production transaction has a consequence: material is consumed, an order advances, a quality decision is recorded or a user receives authority to act. The platform beneath those transactions needs to preserve data, enforce rules and give technical teams visibility into service health.

ManuQube's infrastructure foundation addresses those needs across the application, database, network and delivery layers. Business leaders gain a clearer basis for assessing operational risk. IT teams gain recognizable building blocks they can examine and manage.

01 / Data integrity

Keep the rules close to the records

The self-hosted MES backend uses PostgreSQL with Supabase services for authentication, APIs, real-time updates and file storage. Relational records give production steps, material movements and operational evidence a structured foundation.

Critical MES controls operate in the database, including permission checks on controlled transactions and checks on material consumption. Row-level access policies constrain which records authenticated users can access. These controls help maintain consistent rules when requests arrive through different screens or supported service interfaces.

Business valueGreater confidence that operational records follow the same rules wherever a transaction starts.
02 / Access governance

Connect business authority to technical controls

AMS provides the platform's central place to manage users, roles and module permissions. Connected applications query that authority and enforce access within their own workflows. Server-side authorization and database access policies provide additional controls behind the interface.

Infrastructure access has its own boundaries. Private VPN access, restricted management routes, HTTPS and backend credential management help protect the services supporting daily operations. Sensitive server credentials remain behind the application boundary.

Business valueA clearer connection between who is authorized to act and how that authority is enforced.
03 / Service resilience

Manage the platform across nodes

The infrastructure configuration uses Kubernetes through K3s across a three-node cluster. Containerized services give technical teams a repeatable packaging and deployment model, while Kubernetes manages placement and restart behavior.

Longhorn replicates persistent volume data. HAProxy and Keepalived provide a shared traffic entry point with failover configuration, and Traefik routes requests to the relevant application services. These mechanisms support resilience at different infrastructure layers.

Recovery depends on the service, available capacity and failure conditions. The current self-hosted MES database has one active instance per environment; its recovery can require a restart and volume reattachment.

Business valueLess dependence on individual components and a practical foundation for service recovery and managed maintenance.
04 / Release discipline

Check changes before they reach production

Development, staging and production use separate Kubernetes namespaces within the shared cluster. The self-hosted MES backend has independent database deployments, persistent volumes and credentials for each environment. Network policies, resource quotas and access permissions add boundaries around workloads.

Defined build and release paths support repeatable application delivery. Staging provides a place to validate changes before production release. Database migrations follow a separate review process, keeping application delivery and database change authorization explicit.

Business valueMore control over changes that affect live manufacturing operations, with clearer responsibilities at each release stage.
05 / Monitoring

Give technical teams a shared view

Prometheus and Grafana monitoring configuration supports the collection and review of infrastructure health and resource usage. Rancher provides a Kubernetes management layer for technical operations.

Manufacturing dashboards explain what is happening in production. Infrastructure monitoring helps technical teams investigate the systems behind those workflows, assess resource constraints and plan maintenance.

Business valueBetter evidence for troubleshooting, capacity planning and maintenance decisions.
06 / Recovery planning

Protect the ability to resume work

Replicated storage, recovery copies and configuration recovery serve different purposes. Longhorn provides a storage replication layer. The self-hosted MES backend also defines daily local database and file recovery copies with seven-day retention.

The deployment recovery plan should establish acceptable downtime, acceptable data loss, off-site protection and restoration testing. Those decisions need to reflect the business impact of an interruption and the responsibilities agreed for the deployment.

Business valueA concrete basis for setting recovery priorities before an incident occurs.
07 / Growth

Expand with an assessable foundation

Container packaging, Kubernetes workload management and namespace resource budgets give technical teams explicit tools for managing application demand. As modules and usage expand, teams can review service load, storage consumption and cluster capacity to plan the next stage.

Established technologies and documented service interfaces support technical due diligence. Expansion requirements and performance targets can be assessed against the manufacturing workloads the business expects.

Business valueA clearer basis for planning platform growth alongside operational adoption.

The foundation at a glance

Technology or practicePlatform roleBusiness relevance
PostgreSQL and Supabase services in the MES backendStructured data, authentication, APIs, real-time updates and filesA coherent foundation for operational records and application services
Database rules and row-level policiesData-layer validation and access enforcementConsistent controls across supported transaction paths
AMS and application authorizationCentral access governance with application enforcementClearer ownership of user authority across modules
Kubernetes / K3s and containersManaged placement, restarts and deploymentRepeatable operations and service recovery
Longhorn replicated storagePersistent volume replicationAn additional resilience layer for stateful workloads
HAProxy, Keepalived and TraefikTraffic routing and entry-point failover configurationManaged access to services across cluster nodes
Separate environments and reviewed migrationsValidation and change boundariesGreater control over production releases
VPN, HTTPS and backend secretsRestricted management access and protected credentialsReduced exposure of privileged services
Prometheus, Grafana and RancherMonitoring and cluster managementEvidence for troubleshooting and capacity decisions
Recovery copies and restoration planningPreparation for service restorationRecovery priorities aligned with business needs

Bring your IT team. Bring your operational requirements.

Explore application boundaries, AMS permissions, environment separation, integrations, monitoring and recovery requirements in a platform walkthrough. Establish what your rollout needs and how those requirements will be verified.

Arrange a technical discovery session