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.
| Users | Processor | Memory | Free disk |
|---|---|---|---|
| 1–10 users | 8 vCore | 16 GB | 100 GB |
| 11–20 users | 12 vCore | 32 GB | 200 GB |
| 21–50 users | 16 vCore | 64 GB | 300 GB |
| 51–100 users | 16 vCore | 128 GB | 400 GB |
| 101+ users | Sized with Logo | Sized with Logo | Sized with Logo |
| Users | Processor | Memory | Free disk |
|---|---|---|---|
| 1–10 users | 8 vCore | 16 GB | 250 GB |
| 11–20 users | 12 vCore | 32 GB | 300 GB |
| 21–50 users | 12 vCore | 64 GB | 350 GB |
| 51–100 users | 16 vCore | 128 GB | 400 GB |
| 101+ users | Sized with Logo | Sized with Logo | Sized 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.