ModernERP technologies

The engineering behind ERP, APS and integrations

From business logic and transactions to queues and software delivery. See the role of each tool and how it relates to our products and development work.

The stack depends on the task, workload and client infrastructure. Not every project needs every component listed here.

Applications and APIs

Business logic, access control and contracts between systems.

PHP

Business logic for enterprise web applications and services.

Application

Processing orders, manufacturing documents and API requests.

Symfony AI

Symfony components for integrating AI models, building agents with tools and working with enterprise data context.

Application

Building AI assistants with a unified model interface, authorized tool calls and retrieval from connected sources. We contribute to symfony/ai.

Go

Dedicated services for concurrent processing and network communication.

Application

Integration adapters and data processing where a separate service is justified.

Gin (Gin Gonic)

An HTTP framework for Go with routing, middleware, JSON handling and input validation.

Application

REST APIs for integration services and adapters: request handling, data validation, error handling and logging integration.

Where we apply this approach

Interfaces and interaction

Server-rendered HTML pages and interactive elements for enterprise workspaces.

Twig

A PHP template engine with shared layouts, page components and automatic output escaping.

Application

ERP and APS workspaces, forms, tables and product pages with a consistent visual style.

Stimulus

JavaScript controllers that add behavior to existing HTML elements.

Application

Interactive forms and workspace elements: user actions, component state and event handling.

Symfony UX

Symfony components for interactive interfaces built with Twig, Stimulus and Turbo.

Application

ModernERP Pro uses Live Components in the stock transfer form: a server-side component handles form state and actions.

Where we apply this approach

Data and transactions

Consistent storage, relationships between objects and controlled schema changes.

PostgreSQL

Relational data, transactions, integrity constraints and SQL queries.

Application

Orders, resources, routes and production plan versions.

ClickHouse

A column-oriented database for analytical queries and aggregation of large datasets.

Application

Analytical datasets for manufacturing, orders and integration events. Data comes from operational systems, while heavy reporting queries run in a separate analytics environment.

Redis

An in-memory data store for caching and fast access to temporary application state.

Application

Caching reference data and query results, storing sessions and rate-limit counters. Key expiration and cache invalidation rules follow the business workflow.

Where we apply this approach

Messaging between systems

Deferred processing, controlled retries and recovery from failures.

RabbitMQ

A message broker that separates task producers from consumers.

Application

Queues for integration events. Delivery acknowledgements and retries must be configured alongside application logic.

Symfony Messenger

Messages and handlers, with synchronous or background execution through a chosen transport.

Application

Background tasks, retry policies and a failure queue for investigation.

Where we apply this approach

Application serving and deployment

Application runtime and repeatable delivery of components.

Docker

Containers and images for applications and their dependencies.

Application

Consistent development, testing and deployment environments, with configuration and data managed separately.

Ubuntu

A Linux server platform for hosting applications, databases and integration services.

Application

Deployment in the cloud or on client servers: dependency installation, service management and environment updates.

Astra Linux

A Russian operating system for enterprise infrastructure and deployment on company servers.

Application

Hosting ERP, APS and integration services in Astra Linux infrastructure. OS versions, packages and access settings are agreed for the target environment.

Where we apply this approach

Monitoring and observability

Service metrics, dashboards and alerts for the operations team.

Prometheus

Time-series metrics collection and storage, PromQL queries and alerting rules.

Application

API response times, error rates, worker health and queue age. Notification delivery is configured through Alertmanager.

VictoriaMetrics

Time-series metrics storage and querying with support for the Prometheus ecosystem.

Application

Metrics storage for monitoring services and integrations, with charts and analysis in Grafana. The choice depends on data volume and project requirements.

Grafana

Dashboards and visualization of monitoring data from Prometheus and other sources.

Application

An overview of applications and integrations: latency, errors and load. Dashboards help trace a broad warning to the affected service.

Where we apply this approach

Development and quality

Change history, dependencies, reviews, tests and releases.

PHPUnit

Automated tests for business logic, persistence and HTTP workflows.

Application

Checking schedule calculation, role permissions and preservation of APS plan history.

Git

Code history, branches and preparing changes for review.

Application

Separating tasks and tracking which changes went into an application version.

GitHub

Repositories, pull requests and workflow automation with GitHub Actions.

Application

ModernERP open-source PRs and collaborative development. CI/CD is configured per project repository.

GitLab

Repositories, merge requests and GitLab CI/CD pipelines.

Application

Development in client infrastructure, including self-managed GitLab. Platform choice follows project requirements.

GitVerse

A Russian platform for Git repositories, collaborative development and CI/CD.

Application

Source hosting, code review and automated builds and tests for projects that require a Russian development platform.

Where we apply this approach

How we choose a project stack

Tasks and constraints

Define system boundaries, data ownership, access requirements and acceptable processing delays.

Justified complexity

Add a service, broker or platform for a specific task. First assess what the existing systems can already handle.

Support after launch

Agree dependency updates, backups, monitoring and the release process with the client team.

Open Source

We contribute to the tools we use

Card links point to merged changes in Symfony, Doctrine, FrankenPHP, Composer and other projects. The full history is available on our Open Source page.

All accepted contributions →
merged pull requests
358
public repositories
215

GitHub snapshot:

Let’s discuss your system architecture

Tell us about your current stack, integrations and infrastructure constraints. We will identify what can stay and what needs to change for the next stage.

Discuss your architecture