Orqest ERP
Overview
Production multi-tenant ERP system serving Metropolia Technologies and Midville on a single React + TypeScript + Node.js codebase, with isolated databases and isolated backend processes per tenant.
- Year
- 2026
- Status
- Shipped
- Role
- Lead Engineer
- Kind
- Multi-tenant ERP Platform
- Domain
- Web
- Terminal command
/orqest-erp
What it does
- HR, finance, sales, IT business development, attendance, tasks/kanban, civil ops, inventory, and employee portal modules
- GPS-verified attendance with face verification (Vladmandic Human) and interactive Leaflet maps
- Two live tenants (Metropolia, Midville) on the same codebase via release-symlink deploys
- Application-owned observability: /api/health, /api/metrics, dependency probes, request and Socket.IO metrics
One codebase, isolated tenant operations
Orqest ERP serves Metropolia Technologies and Midville from one React, TypeScript and Node.js codebase. Each tenant has an isolated backend process and PostgreSQL database. My role is Lead Engineer.
Tenant runtimes share application code while keeping their processes and databases separate. Prisma, Socket.IO, PM2, nginx and Docker are part of the documented stack.
Read more: Infrastructure overview · Engineering experience
Shared release, separate runtimes
Each tenant receives the application code through its release deployment and runs its own backend and database.
Shared application
React + TypeScript frontend and Node.js backend in one codebase.
Release deployment
Versioned releases become active through a release-symlink switch.
Isolated tenant runtimes
Separate backend processes and databases for each tenant.
Metropolia Technologies
Isolated Node.js process → tenant PostgreSQL database
Midville
Isolated Node.js process → tenant PostgreSQL database
Business modules and verified attendance
The ERP covers day-to-day operations across the documented modules below.
Attendance combines GPS verification with face verification using Vladmandic Human. Interactive Leaflet maps support the location component of attendance.
- HR and employee portal
- Finance and sales
- IT business development
- Attendance
- Tasks and kanban
- Civil operations and inventory
Release deployment and observability
Release-symlink deployment delivers the shared codebase to the two tenant runtimes. The infrastructure record describes timestamp-and-commit releases with an atomic switch of the active release.
The application owns /api/health, /api/metrics, dependency probes, request metrics and Socket.IO metrics. The related observability stack uses Grafana, Prometheus and Loki for application and host metrics, log aggregation and synthetic uptime checks.
The public orqest.id link is the corporate website. The ERP tenant applications are separate systems.
Read more: Infrastructure overview · Self-hosted observability stack · Orqest corporate website
References
- Infrastructure overview →
Tenant isolation, hosting and the release deployment model.
- Engineering experience →
Lead engineering role and ERP delivery.
- Self-hosted observability stack →
Application instrumentation, monitoring and logging.
- Orqest corporate website ↗
The public company site associated with the platform.
Stack
- Languages
- TypeScript
- Frontend & mobile
- React
- Backend & APIs
- Node.jsPrismaSocket.IO
- Data
- PostgreSQL
- Infrastructure & ops
- PM2nginxDocker