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

Logo

Server and cloud infrastructure for Logo Tiger 3 Enterprise

Take the last working day of the month: accounting starts cost allocation while sales issues the final invoices and the warehouse lead at the factory enters the stock count variance. In Tiger 3 Enterprise, all of this writes to the same database. Server capacity, branch links, and the backup routine are planned around that day.

Product architecture

Logo Tiger 3 Enterprise architecture on ARGE Cloud

In the diagram, the Tiger 3 Enterprise application server, the SQL Server database, and the terminal server run in your dedicated VPC. The factory and branches connect over encrypted links, and e-Invoice traffic goes out only to the provider's addresses.

ARGE ICT infrastructure diagram (Logo Tiger 3 Enterprise). 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 (Logo Tiger 3 Enterprise), 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-Archive, and e-Ledger the firewall allows outbound traffic only to the provider's addresses.ARCHITECTURE · LOGO TIGER 3 ENTERPRISELogo Tiger 3 Enterprise 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 serverLogo Tiger 3 Enterprise · Windows ServerHA cluster: optionalApplication serverLogo Tiger 3 Enterpriseredundant 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 floorFactoryproduction on the same systemFactory firewallIPsec · second link advisedFactory firewallfactory over an encrypted linkE-invoicing providere-Invoice, e-Archive, e-LedgerE-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 (Logo Tiger 3 Enterprise), 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 Logo Tiger 3 Enterprise?

Tiger 3 Enterprise is Logo Yazılım's enterprise resource planning (ERP) product, installed on a company server; Logo labels it an on-premises product. By Logo's description, its scope runs from production to finance and from procurement to fixed asset management. One strength Logo highlights is managing the finances of every organization in a corporate group from a single center.

The foreign trade module covers export credits, tracking of inward processing permits, e-Export, and cost accounting for free zones. Production comes in two levels: Quick Production, and Advanced Production, which handles bills of materials, engineering changes, subcontract production, and production orders. Planning uses MPS, MRP, and CTP, and cost accounting and TFRS adjustments are part of the scope. The standard version ships in Turkish and English, and other languages are added separately.

Logo has gathered its on-premises products under the Logo Edge name. The Tiger group is offered as Logo Edge T-Series, while Tiger 3 Enterprise still has its own product page. Its web-based version is Logo Tiger Wings Enterprise. For an existing installation, we recommend settling with your Logo partner which path to follow.

Companies that use Tiger 3 Enterprise

Manufacturers and companies with foreign trade use Tiger 3 Enterprise, as do holding companies and corporate groups. An exporting industrial company, or a group that keeps several separate company records, fits this profile.

The work that stresses the infrastructure is the month-end and year-end close, cost accounting, and consolidation. Every new company and every new period makes the database larger and the backup longer.

For the infrastructure, what these companies share is the work that piles up at month end and the users who connect from factories and branches. The server is sized for those two loads.

Client-server architecture and database

Tiger 3 Enterprise uses a client-server design: the Tiger application on the user's computer talks directly to the database server and sends a large number of small queries. Each query adds only a small delay, but there are so many of them that the total wait grows as the link gets longer. On a local network in the same building this goes unnoticed, but for a user connecting from a branch or from home, screens open slowly. For remote users, the application is therefore run on a terminal server (RDS) next to the database.

According to Logo's product page, the supported databases are Oracle and Microsoft SQL Server. We build on Windows Server with Microsoft SQL Server; for an Oracle installation, version and license terms are discussed separately.

The database server grows mostly with the number of companies and periods, while cost allocation and consolidation runs put it under the heaviest load. Memory and disk speed are chosen for closing days, not for an average day.

According to Logo, the product works together with Logo e-Solutions, and e-Invoice, e-Archive Invoice, e-Dispatch, and e-Ledger run through it. This needs an outbound connection from the server to the integration service.

Tiger 3 Enterprise setup on ARGE Cloud

Two roles run in the VPC: the Microsoft SQL Server database server, and the terminal servers where users open Tiger. Both run in your dedicated VPC on ARGE Cloud, our own infrastructure in a data center in Istanbul; a highly available (HA) firewall is placed in front of the VPC. The terminal servers and the services that need it connect to the database. For cost allocation and consolidation runs, we use Dell and Supermicro servers, Xeon Platinum processors, enterprise NVMe disks, and a 25G to 200G NVIDIA Mellanox network between hosts.

Head office, branch, and factory links connect to the VPC over IPsec, MPLS, or SD-WAN, and we recommend a second link for each site. Users outside the office authenticate with SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. They can access only the terminal server. The e-document outbound path is defined on the firewall for the required addresses only, and the state of that connection is within the monitoring scope.

If an internet-facing component is added (an API or a portal, for example), its traffic passes through a web application firewall (WAF). Servers, disks, memory, the database service, links, and backup results are monitored, and the service zone next to the VPC runs SIEM and SOAR, antivirus, and XDR/EDR. Monitoring hours and the scope of response are written into the contract. The terminal servers, where many users are signed in at once, carry the most sessions in the environment, and their session and access logs are collected in SIEM.

Full, differential, and transaction log backups are stored in the isolated backup zone, and restore tests are performed; their frequency is written into the contract. The backup arrangement is described separately under our backup and disaster recovery service. Sizing takes the number of companies and periods, concurrent users, and expected growth as inputs. Data, log, and backup areas are kept separate.

Optionally, a SQL HA cluster and a disaster recovery (DR) site in a second data center can be added. We confirm with Logo how the product behaves in a cluster and at a DR site.

The cost allocation parameters, the period close steps, and the e-document definitions are the work of your Logo partner. The license, the application setup, version upgrades, and functional support also rest with the vendor or your partner; we build and operate the infrastructure.

Tiger 3 Enterprise server requirements and sizing

Logo's technical documents, which we read in November 2026, size Tiger 3 Enterprise servers by the number of users. The two tables below give Logo's values for the database server and for the application and terminal server; vCore in the processor column means a core assigned to a virtual server. Logo calculates these values from the average module use of a company; if you process 100,000 or more transactions a month or add integrations, you need a custom configuration from Logo.

Tiger 3 Enterprise database server
UsersProcessorMemoryFree disk
1–10 users8 vCore16 GB100 GB
11–20 users12 vCore32 GB200 GB
21–50 users16 vCore64 GB300 GB
51–100 users16 vCore128 GB400 GB
101+ usersSized with LogoSized with LogoSized with Logo
Tiger 3 Enterprise application and terminal server
UsersProcessorMemoryFree disk
1–10 users8 vCore16 GB250 GB
11–20 users12 vCore32 GB300 GB
21–50 users12 vCore64 GB350 GB
51–100 users16 vCore128 GB400 GB
101+ usersSized with LogoSized with LogoSized with Logo

Database files must sit on disks separate from the system disk; Logo advises against keeping database files or backups on it. In our setup the data, log, and backup areas are already kept apart, and the database runs on enterprise NVMe drives. SQL Server Standard uses at most 128 GB of memory, and the 51–100 user row reaches that ceiling, so for anything above it we pick the edition together with Logo. SQL Server Express is tightly limited (1 GB of memory, 10 GB of data), and Logo does not recommend it for production. If you prefer Oracle, Logo recommends Oracle Database 19c, 64-bit.

For desktop use, Logo recommends one terminal server for every 25–30 users, so a company with 60 users ends up with two or three. Logo asks for at least 8 Mbps of bandwidth per user; we plan the branch link on that figure and on terminal server use. No other server application, such as Exchange or IIS, should run on the servers that run Logo. Logo recommends a 64-bit operating system, Windows Server 2019 as the minimum, SQL Server 2016 or later, and .NET Framework 4.6.2 or later on the application server. On the user's PC it asks for an i5 or better processor, 16 GB of memory, 100 GB of disk, and Windows 10 Professional or later.

Logo does not count backup planning, or database disaster recovery and failover, as its own responsibility; that falls to whoever runs the infrastructure. The isolated backup zone, restore tests, and the optional SQL HA cluster and DR site described above exist to cover it.

What we confirm with Logo before setup

  • Supported Microsoft SQL Server and Oracle versions for your Tiger version
  • Whether the Windows Server 2019 and .NET Framework 4.6.2 values in Logo's document apply to the Tiger version you use
  • Whether Logo's recommendations for running on a terminal server apply to the version you use
  • Effect on the infrastructure if you plan to move to Logo Edge T-Series
  • Whether the 25–30 users per terminal server recommendation and the application and terminal server row in the table are read per server or as a total

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

Frequently asked questions

Are Tiger 3 Enterprise and Logo Edge T-Series the same product?

No. Edge T-Series is the new name for the Tiger group under Logo Edge. The version and license side of the move rests with your Logo partner, and on the infrastructure side Logo Base, the Agent, and outbound rules are added.

Which database does Tiger 3 Enterprise run on?

According to Logo, Oracle and Microsoft SQL Server are supported. We build with Microsoft SQL Server. The supported version is confirmed with Logo before setup.

Does e-Invoice delivery depend on the server's outbound connection?

Yes. Documents go to Logo e-Solutions over a connection that goes out from the server, so that path has to be open on the firewall. It is defined for the required addresses only, and the state of the connection is monitored.

Does every user need the terminal server?

For users who connect remotely, yes. With the server on ARGE Cloud, the query traffic of a desktop client slows down on the link. When the client runs on the terminal server, only the screen image crosses the link. We confirm Logo's terminal server recommendations for your version before setup.

How many cores and how much memory does Tiger 3 Enterprise need?

According to Logo, for 1–10 users the database server and the application and terminal server each need 8 vCores and 16 GB of memory. At 51–100 users both grow to 16 vCores and 128 GB. For 101 users and above, we size the servers together with Logo's teams.

Logo Tiger 3 Enterprise is a product of Logo Yazılım, and its name and trademark belong to the vendor. ARGE ICT is not an official partner or reseller of that vendor. What we provide and operate is the infrastructure the software runs on; for licensing, implementation, and functional support, you turn to the vendor or your partner.

Sizing call for Logo infrastructure

Share your Logo product and your user and branch counts; we respond to your request within one business day.

Request a sizing call