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

Mikro

Server and cloud infrastructure for Mikro Fly

An MRP2 run in Mikro Fly reads bills of materials, stock, open orders, and machine capacity together and writes the result to the same database. In a group structure, each company's month-end close comes on top. According to Mikro, Fly has no user limit, so the size of the company, not the license, decides how many people connect at once.

Product architecture

Mikro Fly architecture on ARGE Cloud

In the diagram, the Mikro Fly application, the SQL Server database, and the terminal servers run in your dedicated VPC. The factory connects from its own firewall over an encrypted link, and the SQL HA cluster is added with the button above.

ARGE ICT infrastructure diagram (Mikro Fly). 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 Fly), 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). The factory connects to the data center over an encrypted link from its own firewall. For e-Invoice, e-Ledger, and e-Payroll the firewall allows outbound traffic only to the provider's addresses.ARCHITECTURE · MIKRO FLYMikro Fly 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 Fly · Windows ServerHA cluster: optionalApplication serverMikro Flyredundant cluster on requestDatabase serverMicrosoft SQL Server · version to be confirmedDatabase 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 upFactoryproduction · MRP2 and work ordersFactoryproduction on the same systemFactory firewallIPsec · second link advisedFactory firewallfactory over an encrypted linkE-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 Fly), 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 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.

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

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.

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