Skip to content
+90 850 885 27 43 info@argeict.com

Mikro

Server and cloud infrastructure for Mikro Jump

For most companies, moving to Mikro Jump starts as a database server project. According to Mikro, Jump does not run on SQL Server 2014 and needs SQL Server 2016 or later. On older installations, the Windows Server version comes up along with SQL Server. Branch and external accountant access is rebuilt in the same move.

Product architecture

Mikro Jump architecture on ARGE Cloud

In the diagram, the Mikro Jump application, the SQL Server database, and the terminal server run in your dedicated VPC. Branches connect over encrypted links, and e-document traffic goes out only to the provider's addresses.

ARGE ICT infrastructure diagram (Mikro Jump). Head office and branches connect from their own firewall to the Istanbul data center over an IPsec tunnel or MPLS/SD-WAN; remote staff use SSL VPN, ZTNA, or ARGE ZTNA. Traffic passes from the data center router through the ARGE ICT Backbone HA Cluster to an HA firewall. Inside the dedicated VPC it passes the VPC firewall and the WAF and is spread across the application servers by a load balancer; the application server (Mikro Jump), the database, and the terminal server run in this VPC; application and database tiers can be built as HA clusters on request. A service zone beside the VPC runs monitoring, SIEM and SOAR, antivirus/XDR/EDR, and DLP. It runs on Dell and Supermicro servers with Xeon Platinum and enterprise NVMe, hosts linked by a 25–200G NVIDIA Mellanox network. Backups are kept in an isolated backup zone and can optionally be replicated to a second data center (DR site). For e-Invoice, e-Ledger, and e-Payroll the firewall allows outbound traffic only to the provider's addresses.ARCHITECTURE · MIKRO JUMPMikro Jump architecture on ARGE Cloude-DönüşümMPLS · SD-WANInternetCustomer: head office and branchesyour own firewallData center · Istanbuldata stays in TürkiyeARGE physical environmentARGE ICT network and racksYour dedicated VPCfirewall · WAF · serversVPC monitoring and security serviceMonitoring · SIEM and SOAR · AV/XDR/EDR · DLPBackup infrastructureisolated backup zoneDR site · second data centeridentical to the primary environmentHead officeBranchesCustomer firewallIPsec tunnel endpointCustomer firewallyour company's gatewayIPsec tunnelfrom head office and branches, encryptedIPsec tunnelencrypted private linkRemote staffSSL VPN · ZTNA · ARGE ZTNARemote staffsecure access from home or fieldDC routersdata center network · HA pairDC routersterminates external linksARGE ICT Backbone HA ClusterHA link from DC network to ARGE networkARGE ICT Backbone HA Clusterredundant core backboneFirewall (HA)ARGE perimeter · HA pairFirewall (HA)only allowed traffic passesVPC firewallrules for you onlyVPC firewallentry to the VPCWAFweb application firewallWAFinspects web requestsTerminal serverRDS · desktop clientsTerminal serverremote access to the programApplication serverMikro Jump · Windows ServerHA cluster: optionalApplication serverMikro Jumpredundant cluster on requestDatabase serverMicrosoft SQL Server 2016 or laterDatabase HA cluster: optionalDatabase serveryour data lives hereredundant cluster on requestInfrastructure monitoringserver, disk, network, backupInfrastructure monitoringon one dashboardSIEM and SOARlog collection and correlationSIEM and SOARalerts handled in defined stepsAntivirus · XDR · EDRendpoint protection on serversAntivirus · XDR · EDRmalware and suspicious behavior stoppedDLPdata loss preventionDLPdata egress monitoredVirtualization hostsDell and Supermicro serversXeon Platinum · enterprise NVMeVirtualization hostsenterprise-class serversfast processors and storage25G / 50G / 100G / 200G host networkNVIDIA Mellanox Ethernet cards25G / 50G / 100G / 200G host network25–200G links between serversBackup copiesseparate logical zoneseparate from productionBackup copiesyour copies are kept hereDR firewallsame rulesDR application serveractive · serving usersDR application serverstandby · takes over in a disasterDR databasesynchronized both waysDR databaseup-to-date copy, read-onlyGlobal Load Balancerhealth-checked routingGlobal Load Balancersends users to the site that is upE-invoicing providere-Invoice, e-Ledger, e-PayrollE-invoicing providercontrolled outbound linkSSL VPN · ZTNAARGE ZTNAlogs and metricsBackup lineAlso to DR (active-active)traffic shared across both sitesFailover pathused only in a disasterTwo-way replicationContinuous replicationone way, primary to DR123456IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replication1Step (below the diagram)Listed outboundIllustrative · HA and DR are added with the buttons on the page
IPsec tunnelMPLS / SD-WANSSL VPN · ZTNAInternet to WAFDC and ARGE networkHA pairingApplication ↔ data25–200G host networkLogs and metricsBackup lineGlobal Load BalancerFailover pathDR replicationListed outboundIllustrative · HA and DR are added with the buttons on the page
Hover over or tap a component to see its name and role; choose “Show all” to see every label at once. Zoom with Ctrl/⌘ + scroll, a two-finger pinch or a double click. Use the buttons above to add HA and DR options; click a step to bring its layer forward.
The diagram shows the path we build (Mikro Jump), from your sites to the data center and from the dedicated VPC to the isolated backup zone. Application and database HA clusters and the DR site (passive, or active with a Global Load Balancer) are added with the buttons above the diagram. It is illustrative; ports, database, and integration details are confirmed with the vendor before installation.

How to read the diagram

  1. 1
    Your sites and staff connect over encrypted links

    Head office and branches come in from their own firewall over an IPsec tunnel, or over an MPLS or SD-WAN circuit. Staff outside the office use SSL VPN, ZTNA, or ARGE ZTNA. Where an application is internet-facing, its traffic passes through the WAF.

  2. 2
    Traffic is filtered at the data center edge

    The connection goes from the data center router to the ARGE ICT Backbone HA Cluster and then to the firewall. All three are HA pairs side by side; if one fails, the other takes over.

  3. 3
    Your dedicated VPC: firewall and WAF

    Traffic entering the VPC passes your own firewall and then the WAF, and a load balancer spreads it across the application servers. The application, terminal, and database servers run in this VPC. On request we build the application and database tiers as HA clusters.

  4. 4
    Monitoring and security service beside the VPC

    Server, disk, network, and backup status show on the monitoring dashboard. Logs are collected in SIEM and SOAR, and alerts are handled in defined steps. Antivirus and XDR/EDR run on the servers, and DLP monitors unauthorized transfers of sensitive data. The scope is set in the contract.

  5. 5
    Enterprise hardware, fast internal network

    The environment runs on Dell and Supermicro servers with Xeon Platinum processors and enterprise NVMe drives. Hosts are interconnected at 25G, 50G, 100G, or 200G with NVIDIA Mellanox cards.

  6. 6
    Backup in an isolated zone, DR site optional

    Backups are kept in an isolated backup zone, separate from the production environment. On request we build an identical environment in a second data center: in passive mode it takes over in a disaster, in active mode a Global Load Balancer spreads traffic across both sites.

What is Mikro Jump?

Mikro Jump is a modular ERP product from Mikro Yazılım for mid-sized businesses. In Mikro's product family it is positioned above Mikro Run and Jump Basic and below Mikro Fly. Add-on modules are bought or rented on top of the main package. Which modules are needed depends on the number of users, the number of branches, and the e-document needs.

The retail module works with the POS terminal and the new-generation fiscal cash register (YN ÖKC). Serial, color-size, and lot tracking are part of the product. On the e-document side, e-Invoice, e-Archive, e-Ledger, and e-Payroll are joined by the e-Z Report and e-Export. Retail and e-document work needs outbound connections from the server to outside services; these are defined separately on the firewall.

There are two separate offerings under the same name. Jump Basic is the sibling product that Mikro describes as a desktop application installed on a computer, while Mikro Jump Bulut is the service Mikro provides on its own cloud. Which one you use changes the infrastructure decision: in a setup on ARGE Cloud, the Jump you have licensed runs in your dedicated VPC.

Companies that use Jump

According to Mikro's recommendation, Jump suits businesses with 5–50 employees. Companies moving over from Mikro's older products, Hesapçı and Ekoticari, and wholesale and retail businesses with branches are also among its users.

Take a wholesaler with three branches. Each branch enters records from the POS terminal and the warehouse, while accounting at head office collects e-Ledger and e-Invoice work at month end. The connection of the branches and the external accountant is therefore as much an infrastructure item as the server.

SQL Server, desktop client, and API

Jump's database is Microsoft SQL Server. According to Mikro's frequently asked questions page, the product does not run on SQL Server 2014 and needs SQL Server 2016 or later. Upgrading SQL Server can also affect the Windows Server version.

That relationship sets the order of a migration: the supported SQL Server version is chosen first, and the Windows Server and application versions are planned around it. On installations left on an old server, the two upgrades can be handled in the same migration.

Mikro does not publish a table by number of users for the application side and gives minimum values only. When there are branches and remote workers, the application is run centrally on a terminal server (RDS), and the conditions are confirmed with Mikro or your partner. Each user session on a terminal server uses its own memory, so the number of servers grows with the number of sessions.

E-documents are sent over a connection from the server to the e-invoicing service provider. The signing method is part of the infrastructure. If a financial seal is used, how the seal will work in the server environment is settled in advance. If Mikro's cloud signing option that needs no financial seal is used, the addresses the server must connect to are settled instead.

According to Mikro, its sector-specific solutions (warehouse and shelf tracking, quick sales, restaurant management, and B2B dealer management) are built on the application programming interface (API). If an e-commerce site or another system is to connect to Jump, the connection is opened on the server side only to the resources it needs. For each system that connects to the API, the source address is defined on the firewall.

Mikro Jump setup on ARGE Cloud

Jump's SQL Server database and terminal server run in your dedicated VPC on ARGE Cloud. ARGE Cloud is our own infrastructure in a data center in Istanbul, and a highly available (HA) firewall is placed in front of the VPC. Users at branches work with the application in an RDS session. In the sizing discussion we ask about the number of branches, concurrent users, the current size of the database, and the days when e-Ledger and e-Invoice submission peaks.

Branches connect to the VPC over IPsec, MPLS, or SD-WAN. The external accountant and users outside the office connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. Which user connects by which route is written down during setup. If a branch's link drops, that branch's users cannot open their RDS session, so we recommend a second link for critical branches.

On the firewall, the e-document path is opened only to the addresses it needs. If the API is to be exposed to the internet, its traffic passes through a web application firewall (WAF). The outbound addresses come from the provider and are updated on the firewall if the provider changes.

We set up a SQL Server maintenance plan that does not overlap with the backup schedule. Backups go to the isolated backup zone, and a restore test is carried out at a frequency stated in the contract. The details of the backup and recovery plan are described under our backup and disaster recovery service. A SQL HA cluster and a disaster recovery (DR) site in a second data center are optional.

Servers, disks, memory, the SQL Server service, links, and backup results are monitored. Security logs feed the security information and event management (SIEM) and security orchestration, automation, and response (SOAR) systems in the service zone next to the VPC. Antivirus and XDR/EDR also run there. Monitoring hours and response scope are also stated in the contract.

Module selection, e-document definitions, and data migration from an older product stay with your Mikro partner. Licensing and functional support also rest with your Mikro partner. Your Mikro partner works on the application side; we build and operate the server, access, and backup.

Mikro Jump system requirements

Jump shares one installation and hardware article with Run, Fly, and Müşavir: Mikro's version 17 requirements, which we read in November 2026. The article gives minimum values only, with no table by number of users. SQL Server 2016 SP1 or later is supported for the database, so the SQL Server 2016 floor described above is, more precisely, SP1. A domain is a Windows network where user accounts and computers are managed from one place; in a workgroup each computer keeps its own accounts.

Minimum values for Mikro version 17
RoleOperating systemProcessorMemoryFree disk space
Database serverWindows Server 2016 or later in a domain environment; Windows 10 or later in a workgroupXeon-based dual processor16 GB (32 GB recommended)250 GB
Terminal serverWindows Server 2016 or laterXeon-based dual processor8 GB + 1 GB per user1 GB per user
User computerWindows 10 or laterAt least 2 cores8 GB2 GB

For a company with branches the application runs on a terminal server, so the row that matters in the table is the terminal server. Mikro adds 1 GB of memory per user to a base of 8 GB and asks for 1 GB of free disk per user: a setup with 20 users means at least 28 GB of memory and 20 GB of free disk. That figure covers the server only; because a branch whose link drops cannot reach its RDS session, we plan the second link we recommend for critical branches separately.

According to the article, SQL Server Express licenses can be used free of charge. On ARGE Cloud we settle in the sizing call whether Express or a licensed SQL Server edition goes in, based on the current database size and the e-Ledger and e-Invoice peaks, and we confirm the limits of the chosen edition in Microsoft's documentation. A note for branch PCs: the table lists Windows 10 as the minimum, but the article points out that its support ended on October 14, 2025, and recommends Windows 11 or later.

These values do not cover backups. Because we operate the infrastructure, scheduling SQL Server maintenance so it does not overlap with backups, keeping backups in the isolated backup zone, and running restore tests stay with us.

What we confirm with Mikro before setup

  • SQL Server versions supported for the Mikro release you use
  • Whether the minimum values in Mikro's version 17 article also apply to the Jump version you use
  • Conditions for running on a terminal server
  • Server-side requirements of the API and integrations
  • The number of concurrent users in your license and the signing method to be used for e-documents

Technologies: Microsoft SQL Server · Windows Server · Remote Desktop Services (RDS) · IPsec · SSL VPN · ARGE ZTNA · ARGE Cloud

Frequently asked questions

Which SQL Server version does Mikro Jump need?

According to Mikro, SQL Server 2016 or later is required; Jump does not run on SQL Server 2014. We confirm the supported versions for the Mikro release you use before setup. The decision to upgrade SQL Server can also bring up the Windows Server version.

How is Mikro Jump Bulut different from a setup on ARGE Cloud?

Mikro Jump Bulut is the service Mikro provides on its own cloud. On ARGE Cloud, the Jump you have licensed runs in your dedicated VPC with your own SQL Server. The server, access, and backup are with us, and application support stays with your Mikro partner.

What does the server need to send e-Ledger and e-Invoice documents?

The server needs an outbound path to the e-invoicing service provider and a signing method settled in advance. The outbound addresses are defined on the firewall. If a financial seal is used, how the seal works in the server environment is also settled at this stage.

How does the number of concurrent users in the license affect the infrastructure?

On the server side, the deciding factor is the number of sessions open at once; the memory and count of terminal servers are set to match it. Your Mikro partner can tell you the number of concurrent users in your license.

How much memory and disk does a Mikro Jump terminal server need?

According to Mikro, a terminal server needs 8 GB of memory plus 1 GB of memory and 1 GB of free disk for each user. With 20 users, for example, that is 28 GB of memory and 20 GB of disk. The operating system should be Windows Server 2016 or later, on a Xeon-based dual processor.

Mikro Jump, the product named on this page, is made by Mikro Yazılımevi Yazılım Hizmetleri Bilgisayar Sanayi ve Ticaret A.Ş. (Mikro Yazılım); the name and trademark belong to the vendor. ARGE ICT is not an official partner or reseller of this vendor; its job is to provide and operate the infrastructure the software runs on. Licensing, implementation, and functional support, in turn, come from the vendor or your partner.

Sizing call for Mikro infrastructure

Share your Mikro product, your user count, and where users connect from; we respond to your request within one business day.

Request a sizing call