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.
| Role | Operating system | Processor | Memory | Free disk space |
|---|---|---|---|---|
| Database server | Windows Server 2016 or later in a domain environment; Windows 10 or later in a workgroup | Xeon-based dual processor | 16 GB (32 GB recommended) | 250 GB |
| Terminal server | Windows Server 2016 or later | Xeon-based dual processor | 8 GB + 1 GB per user | 1 GB per user |
| User computer | Windows 10 or later | At least 2 cores | 8 GB | 2 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.