What is Mikro Fly?
Mikro Fly is the broadest product in Mikro's family. On top of Mikro Jump it adds MRP2, advanced accounting, human resources, CRM, and business intelligence. The advanced accounting covers IFRS, inflation accounting, and consolidation with elimination parameters. E-documents are managed from inside the program.
On the production side, MRP2 works with a Gantt view, routings, and work orders, alongside machine maintenance, a subcontracting module, and a work order board. When the MRP2 result turns into work orders, it appears on the workshop screens, so planning and production meet in the same program. Fly also includes the functions of Jump.
Companies that use Fly
Mikro recommends Fly for businesses with 50 or more employees. Typical users at this scale are holding companies, manufacturers, and companies that report under IFRS. What these companies share is that several companies and production units work in the same program.
For companies moving from Jump to Fly, MRP2 and the multi-company structure bring a new load to the memory and disk of the database server. Because the size of that load differs from company to company, it is determined by measurement.
Take a group with several subsidiaries. Each company keeps its own books and the group consolidates them at month end. The group's factory takes its work orders from the program, so the accounting close and the production records meet on the same server. The more companies a group has, the more work lands on the server at once during the close.
Database load, client, and API
Fly's database is Microsoft SQL Server. Mikro's version 17 hardware article supports SQL Server 2016 SP1 or later for Fly; we confirm this for the Fly version you use before setup.
How long an MRP2 run takes depends largely on the server's memory and disk speed. In a group structure each company's data grows at its own pace, while month-end close and consolidation create a heavy load that concentrates in a short window. The database grows as bills of materials, stock movements, and work order records accumulate, so room for growth is left on the disk.
Mikro does not publish client requirements by number of users; it gives minimum values only. When a factory, warehouse, or branches have many users, the application runs centrally on terminal servers (RDS), and the number of terminal servers grows with the number of users. Running the application on terminal servers also reduces the work of installing and updating a client on every computer.
The API is used to connect external systems. The source address of each connected system is defined and logged. E-document submission also needs an outbound path from the server to the provider. Logging the connections makes it easier to find which system connected when a problem comes up.
Mikro Fly setup on ARGE Cloud
Fly's SQL Server database and terminal servers run in your dedicated VPC on ARGE Cloud. A highly available (HA) firewall is placed in front of the VPC, and ARGE Cloud is our own infrastructure in a data center in Istanbul. In sizing, we ask about the number of companies, each company's database size, MRP2 run frequency, concurrent factory users, and the month-end close calendar. The number of terminal servers and the memory and disk of the database server follow from those answers.
For MRP2 runs, we keep the database on Dell and Supermicro servers with Xeon Platinum processors, enterprise NVMe drives, and a 25–200G NVIDIA Mellanox network between hosts.
The factory connects to the VPC over IPsec, MPLS, or SD-WAN. Workshop users open work orders on the terminal server. If the link drops, production records cannot be entered, so the link is monitored and we recommend a second link for the factory. Managers away from the workshop and users outside the office connect over SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA.
If the API is exposed to the internet, its traffic passes through a web application firewall (WAF). The e-document path is defined on the firewall for the provider's addresses only. Monitoring covers servers, disks, memory, the SQL Server service, links, and backup results, and the contract defines monitoring hours and the scope of response. Antivirus and XDR/EDR, together with security information and event management (SIEM) and security orchestration, automation, and response (SOAR), are located in the service zone next to the VPC.
Company databases go to the isolated backup zone one by one, so a restore can be done company by company. We set the restore order with you and put it in writing; restore tests are run, and their frequency is stated in the contract. The backup design is covered in detail under backup and disaster recovery. A SQL HA cluster and a disaster recovery (DR) site in a second data center are optional; we confirm the application's cluster and second data center behavior with Mikro.
MRP2 parameters, bills of materials, and consolidation definitions stay with your Mikro partner. Licensing, application setup, and version upgrades also remain with your partner. Functional support and data migration from an older product stay with your Mikro partner as well; we build and operate the infrastructure.
Mikro Fly server requirements and sizing
Mikro's installation and hardware article for version 17, which we read in November 2026, covers Fly together with Run, Jump, and Müşavir and gives minimum values only. There is no table by number of users, so the table below shows the minimum per role. SQL Server 2016 SP1 or later is supported for the database. A domain is a Windows environment where users and computers are managed in a central directory; a workgroup has no such directory.
| 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 |
MRP2 runs and month-end consolidation are heavy on memory and disk. We treat the 16 GB minimum as a floor and set memory by measurement, taking into account Mikro's 32 GB recommendation and, in a group structure, the combined size of the company databases. According to the article, SQL Server Express licenses can be used free of charge. We choose the SQL Server edition (Express or a licensed edition) in the sizing call, based on the size of the company databases and the MRP2 load, and we confirm the limits of the chosen edition in Microsoft's documentation.
Mikro's rule for the terminal server works like this: 8 GB of base memory, plus 1 GB of memory and 1 GB of free disk for every user. For 40 factory users on the terminal server, that comes to at least 48 GB of memory and 40 GB of free disk; as the user count grows, more terminal servers are planned. On the user's computer the minimum is Windows 10, 2 cores, 8 GB of memory, and 2 GB of free disk. The article notes that Windows 10 support ended on October 14, 2025, and recommends Windows 11 or later.
These values do not cover backup or disaster recovery. Backing up each company database separately into the isolated backup zone, restore tests, and the optional SQL HA cluster and DR site described above stay with us as the party that runs the infrastructure.
What we confirm with Mikro before setup
- SQL Server versions supported for Mikro Fly
- Whether the minimum values in Mikro's version 17 article also apply to the Fly version you use
- The server size Mikro or your partner recommends for your number of users (the article gives minimums only)
- Server-side requirements of the API and integrations
- Conditions for running on a SQL HA cluster and at a second data center
Technologies: Microsoft SQL Server · Windows Server · Remote Desktop Services (RDS) · IPsec · SSL VPN · ARGE ZTNA · ARGE Cloud
Frequently asked questions
What changes in the infrastructure when moving from Mikro Jump to Fly?
MRP2, consolidation, and a growing number of users enlarge the memory and disk of the database server and the number of terminal servers. Data migration and module settings stay with your Mikro partner. We work out how much each module adds to the load from usage measurements.
How does the factory connect to Mikro Fly on ARGE Cloud?
Through the factory's firewall, over IPsec, MPLS, or SD-WAN. Users work on a terminal server, and we recommend a second link against outages. The number of concurrent users at the factory sets the number of terminal servers.
How is a restore planned in a multi-company structure?
Each company's database is backed up separately. We set the restore order with you and put it in writing, and the frequency of restore tests is stated in the contract.
Does Mikro Fly run on a SQL HA cluster?
On the infrastructure side, a SQL HA cluster can be built as an option. Before setup we confirm with Mikro how the application behaves on a cluster. The scope of the cluster is stated in the contract.
What are the minimum server requirements for Mikro Fly?
According to Mikro, the database server needs a Xeon-based dual processor, 16 GB of memory (32 GB recommended), and 250 GB of free disk. The terminal server needs 8 GB of memory plus 1 GB of memory and 1 GB of free disk for each user. These are minimums; we size for your number of users by measurement.
Mikro Yazılımevi Yazılım Hizmetleri Bilgisayar Sanayi ve Ticaret A.Ş. (Mikro Yazılım) owns the Mikro Fly name and trademark. ARGE ICT is not an official partner or reseller of this vendor; we provide and operate the infrastructure the software runs on. Licensing, implementation, and functional support come from the vendor or your partner.