ProMatrix

R2O approach · Requirements-to-Operation

From spec to operation — in one model.

You set the requirements and make the decisions. Calculations, documentation and inter-discipline assignments come out of the model and update themselves with every change.

Change it once — everything follows.

More about the approach ProMatrix Engineering

CAD Persondraws lines Systemstores lines

BIM Personmodels objects Systemderives views and schedules from the objects

R2O Personsets requirements and makes decisions Systemderives objects, calculations, documents, assignments and manufacturing data from them — and rebuilds it all with every change

The idea

Not a set of apps, but one environment

A typical company runs not one system but nine: accounting, HR, file storage, email, a messenger, CAD, a task tracker, reporting and a spreadsheet where it all gets reconciled by hand. ProMatrix removes the seams between them.

Client-server with an offline-capable client

A full desktop application, not a browser tab. The client keeps a working copy of the data locally, runs without a network and syncs with the server once the connection is back.

Collaboration

Several people edit the same document or project at once: you see who is changing what, edits are merged, and conflicts are resolved by rules — not by “last save wins”.

Communication inside processes

Project channels, mail and the correspondence log are built into the system. Discussions are tied to a project and a department and stay in the history instead of getting lost in a third-party messenger. Calls and conferencing are planned.

Desktop, browser, mobile

One server, three clients. The desktop application works today; the browser client, for those who can't install software, and the mobile client, for work on site, come next.

AI where there are no clear rules

We are designing AI agent integration: preliminary document review, comparing revisions, finding analogues and contractors. The agent prepares and suggests — the decision stays with a person.

Unified core

All modules share common reference data and one permission model — a single permission core on the client and the server. A project created by a manager is immediately visible to document management, tasks, cost estimates and procurement.

Modularity

Start with one module and add the rest as you need them. Each module line is built and connected separately.

Your infrastructure

The server is hosted by you, by us or in a hybrid setup. There is also an edition with no server at all — a local installation for a single seat.

Client-server

Works offline. And together — when you're online

ProMatrix is a desktop application with a local copy of your data. The server connection is for sharing with colleagues, not for opening a document.

01

Offline

A laptop on a business trip, a shop floor with no network, a site with no internet. The user works with a local copy: creating documents, editing the project, keeping records. Everything goes into the operation queue.

Full functionality without a server
Local change log
Deferred operation queue
Offline work with files and drawings

02

With synchronization

As soon as a connection appears, the client pushes its changes to the server and pulls everyone else's. Conflicts are shown to a person with a line-by-line diff, not resolved silently.

Changes replayed in both directions
Manual and rule-based conflict resolution
Resume after a dropped connection
Works over low-bandwidth links

03

Together and online

Several people in the same document or project at once: you see colleagues' cursors and selections, changes appear instantly, and a chat and a call about that same item are right alongside.

Concurrent editing
Participant presence and cursors
Node locking when needed
Edit history by author

Where to work

Three clients, one system

The desktop app, browser and phone connect to the same server side: same data, same permissions, same history. No need to pay for each device separately.

Desktop application

Windows 10 / 11

The main client, built on the DockStudio platform. All modules, a dense interface with docks and panels, offline sign-in and work with an operation queue.

All modules, no limitations
Offline sign-in and operation queue
Engineering tools
Personal workspace layouts

Web client

Chrome · Firefox · Safari · Edge

Web access to the same system with nothing to install. A fit for managers, external participants and workstations where software can't be installed.

Documents, approvals, tasks, chats
Dashboards and reports
Project viewing and review comments
Sign-in via corporate SSO

Planned after the desktop client. Requires the server.

Mobile application

iOS · Android

For work outside the office: approve a document on the road, mark work as done on site, attach a photo, reply in a chat. Data accumulates offline and goes to the server once a connection appears.

Approvals and notifications
Tasks and on-site check-offs
Photos, attachments, signatures
Chats and calls
Offline operation queue

Planned after the desktop client. Requires the server.

What's inside

A report and dashboard builder over data from all modules: sales, manufacturing, finance, HR, warehouse, and projects in a single set of metrics.

Dashboards, reports, metrics Open

Flagship development

Engineering — a next-generation design environment

An object-based design system for every construction discipline. Engineers work with objects rather than lines — ducts, dampers, sensors, cables — each with parameters, connectors and a system it belongs to. The drawing, the bill of materials, the isometric view and the brief for another discipline are all views of one model.

The goal is to replace the patchwork of a drafting tool, calculation packages, network folders and email threads with a single environment, where changing a parameter automatically rebuilds the model, reruns the calculations and reissues the documentation.

More about the module Become a pilot customer

What it replaces

AutoCADline drafting and sheet layout

Revitcollaboration on a model

Spreadsheet bills of materialscounting and reconciling equipment

Emails to other disciplinesopenings and load briefs

Manual controls coordinationsignals, diagrams and controller programs

Network foldersversions, issues and file exchange

The module is in active development. DWG, IFC and STEP import and export remain — so you can work with contractors still using legacy tools.

Artificial intelligence

AI where a process can't be reduced to rules

Accounting and routing are automated with rules. But reading a contract and spotting what changed, finding a similar project, picking an assignee or a substitute item — rules can't describe that. This is where AI agents come in.

The module connects any model to the system — ours, a third-party cloud model or a local one in your own infrastructure — and grants it access strictly by permissions. The agent prepares, suggests and highlights; a human approves.

More about the module Discuss a use case

What the agent takes on

01

Connect any model

Cloud APIs, local models in your own infrastructure, several providers at once. Switch without reworking your processes.

02

Agent and role registry

An agent is set up as a participant in the system: its own role, access rights, spending limits and permitted actions.

03

Document pre-analysis

Data extraction, classification, a summary, and highlighting of risks and non-standard terms before the document reaches legal counsel.

04

Comparison and version control

What changed between revisions, how the document differs from the template, and which clauses dropped out of the approved version.

05

Matching and semantic search

Similar projects and solutions, equivalent items, suitable assignees by workload and skills, and archive search by meaning rather than keywords.

The module is in development and is purchased separately. With a local model, data never leaves the company perimeter.

Architecture

How it works inside

A client built on the DockStudio platform, local storage, a sync layer, an application server and a collaboration server. All of it is deployed in your own infrastructure or in ours — your choice.

About the DockStudio platform

01

Client (DockStudio)

Desktop application: a single window, module panels, tabs, themes and personal workspace layouts. Works offline.

02

Local storage

A working copy of data and files on the user's machine. Every change is written to a local operation log.

03

Synchronization layer

Two-way exchange with the server: replaying pending changes, conflict resolution, resumable file transfers, and operation over a weak link with resume.

04

Application server

Business logic, approval routes, access rights, calculations, a background job queue and integration connectors.

05

Collaboration server

Concurrent editing sessions, user presence, and a signaling server and media server for calls and conferences.

06

Storage

PostgreSQL as the primary DBMS, S3-compatible file storage, full-text search and a versioned archive.

07

Integration layer

An open REST/gRPC API, webhooks, and connectors to 1C, Active Directory, EDI operators, email, telephony and CAD systems.

End-to-end scenario

How the modules work together

A single object travels through the whole system with no manual data transfer between departments.

CRM: deal→ Documents: contract→ Engineering: design→ Projects: tasks & deadlines→ ERP: production→ Warehouse: shipment→ Accounting: closing→ Analytics: margin

One directory

Counterparties, employees, items and sites are created once and are available to every module with the same history.

One set of permissions

The role from the HR module defines what a person sees in documents, finances, projects and production.

One history

Every action, message and call about an object stays in its record: a year later it is still clear why the decision was made.

Users

Who ProMatrix is for

Manufacturing companies

An end-to-end chain: order — design documentation — production plan — warehouse — shipment — payment. No manual data transfer between departments.

Design and engineering firms

Project collaboration, documentation versions, approvals, and exchange with the client and subcontractors. The Engineering module is the core of this work.

Design-and-install contractors

The full cycle: design — estimate — procurement — installation — handover. As-built documentation, concealed-work certificates, site remarks and client exchange in one system. The crew on site works offline, and data reaches your infrastructure once a connection appears.

Companies with heavy document workflows

Holdings, property developers, service organizations: hundreds of contracts and approvals a month, deadlines, owners, an archive and legal validity.

Distributed teams

Office, sites, remote employees. Offline work in the field and sync when back on the network, with messaging and calls inside the system.

Integrations

Works alongside what you already have

You don't have to roll the system out “instead of everything”: it works alongside 1C, Active Directory and industry-specific software.

Questions

Frequently asked questions

Can it run without a server?

Yes. The local edition is installed on a workstation and runs standalone with its own database. The server component can be added later — your data carries over.

What happens if the network goes down?

The client keeps working with a local copy and queues the changes. Once the connection is restored, your changes are pushed to the server and other people's edits come down to you. Conflicts are shown with a line-by-line comparison.

Where can the server be hosted?

On your own infrastructure (on-premise), in our data center, or in a hybrid setup: the primary server with you, the backup with us. Pricing differs in each case.

Can I buy just one module?

Yes, the system is licensed per module. Start with document management or projects and tasks; other modules are added as you need them.

How is this different from a set of separate applications?

A single core: shared directories, one permission model, end-to-end processes, and a common history. Data is not moved between systems — it is shared from the start.

Is Engineering available to buy yet?

Not yet: the module is in development. The model core and geometry are done; the first milestone — architecture and HVAC as objects, standalone — is under way; the pilot runs on one project side by side with AutoCAD. If you would like to join the pilot and shape the feature set, get in touch — terms are discussed individually.

Is there integration with 1C?

Not yet — 1C integration is planned. Today ProMatrix works with mail (IMAP and SMTP) and a PostgreSQL database.

Are there calls and conferencing?

Not yet: project channels, mail and the correspondence log work today. Calls and conferencing are planned; their server will be deployed inside your own infrastructure.

How long does implementation take?

We estimate the timeline after an assessment: it depends on the set of modules and the data to be migrated. We roll out in stages, putting each part into use as it is ready.

What about import independence?

Built on open components: a Linux server and a PostgreSQL database. Workstations run Windows.