Datagate is built on a modern Microsoft stack: .NET Core on the backend, SQL Server as the database, HTML and JavaScript on the frontend. The interface is exclusively web — users access the application from the browser, without installing software on the workstations. Any modern browser is supported.
The choice of .NET Core allows the platform to run on both Windows and Linux, providing flexibility in the choice of infrastructure.
On-premise — the application is installed on the client's servers. The customer has full control over data, infrastructure, backup policies, and network access. The Mercator Analyst team provides technical support and delivers updates, but the day-to-day operation remains with the client.
SaaS — the application is hosted by Mercator Analist. Maintenance, backup, monitoring, and updates are included in the service. The client accesses the application from the browser, without managing the infrastructure. It is the recommended option for companies that do not have or do not want to maintain a dedicated IT team.
Both are officially supported and tested. The choice depends on the competencies of the management team and the client's IT policies.
Datagate implements data protection at the database level, not just at the interface level. These mechanisms work regardless of how the data is accessed — from the web interface, from the API, or directly from the database.
Document lifecycle — each document goes through well-defined states: draft → issued (validated) → canceled. An issued document can no longer be modified — the only option is to cancel it and create a new document. This rigor prevents situations in which a document already processed (invoiced, shipped, accounted for) is retroactively modified.
Document lock — In addition to the lifecycle, a document can be locked. This happens automatically in certain situations: generating the eInvoice, exporting to an external system or other processes where the document no longer needs to be touched. A blocked document cannot be undone either.
Period Close — The administrator can close a accounting month. After closing, no more transactions from that month can be changed — no sales, no inventories, no purchases. The mechanism prevents historical data from being altered, intentionally or accidentally.