What is Logo Tiger Wings Enterprise?
By Logo's definition, Tiger Wings Enterprise is the web-based version of Logo Tiger 3 Enterprise. According to Logo, a browser that supports HTML5 is enough and nothing is installed on the client computer. The product also runs as a desktop application, and the two ways of working can be used together. In the arrangement Logo describes, the accounting team can work on the desktop while field users work in the browser.
According to Logo's product page, Wings shares the Tiger family's functions: quick and advanced production, MPS and MRP planning, subcontract tracking, stock control, foreign trade, and fixed asset tracking. One detail Wings' product page highlights is that Ba-Bs reconciliation can be done with a single click. Logo labels the product on-premises, and it can be bought as a one-time payment or as a subscription. The standard version is in Turkish and English.
Companies that choose Tiger Wings
Wings suits companies that have branches and employees working outside the office, and that do not want to install and update a client on every computer. Companies that use Tiger 3 Enterprise and want to move to a browser are part of the same audience. A business with branches in different cities or a field sales team is one example.
Logo positions Wings for companies that want to manage large and complex operations on one platform.
The user profile affects the infrastructure directly. A desktop user inside the office and a browser user connecting from a hotel place different kinds of load on the same server and raise different security questions. Logo does not publish a current limit on the number of users, so sizing is based on the number of concurrent users.
Wings Server, browser sessions, and the database
The core component is a Windows service that Logo's setup documentation calls Tiger Wings Server. Logo describes it as an HTTP/WebSocket server that handles communication between the browser and the application. During setup a virtual directory name is chosen and users open the program at that address; there is also an administration panel. According to Logo, IIS does not need to be installed on the server.
According to Logo's setup documentation, the server needs a graphics card with at least 2 GB of memory and .NET Framework 4.5 in addition to the general requirements. Memory and processor needs also grow with the number of concurrent users.
Logo describes the Broker and Gateway services that come with the installation only for scaling and load balancing scenarios. When the number of users exceeds a single server, Wings spreads across several servers through these services.
The product page does not state the database engine separately. We build on Windows Server with Microsoft SQL Server and confirm the supported version with Logo. Browser access needs a valid TLS certificate.
Every session in the browser consumes resources on the server. The ratio of desktop users to browser users therefore enters the load calculation.
Tiger Wings setup on ARGE Cloud
We start the setup with browser publishing. The application server that runs Wings Server and the SQL Server database 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.
The Wings address is not opened directly to the internet; it is placed behind an access layer that authenticates users, and a signed-in user can access only the Wings address. Access is built with one of these: SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. Where the Wings address has to be published to the internet, a web application firewall (WAF) is placed in front of it. Sites such as offices and branches connect over IPsec, MPLS, or SD-WAN, and we recommend a second link for each site.
The TLS certificate is installed, and its expiry date can be included in monitoring; that scope is written into the contract. Monitoring covers the application server's memory and disk, the database service, the links, and the result of the backup. The service zone next to the VPC runs SIEM and SOAR as well as antivirus and XDR/EDR, and monitoring hours and response scope are also set out in the contract.
We start sizing with measurement: how many people connect at the same time, the busy hours, and the ratio of desktop users to browser users. We set the memory and processing power of the application server accordingly.
The backup captures the Wings configuration (service settings, virtual directory, certificate) along with the database and stores it in the isolated backup zone. Restore tests are performed; the contract states how often. The arrangement is described under our backup and disaster recovery service.
Sizing is not final until Logo confirms how the graphics card requirement is met on a virtual server. If users outgrow a single server, an optional second Wings server is prepared, and the load balancing setup Logo describes with Broker and Gateway is planned with your partner. How that setup works with Wings is confirmed with Logo. A SQL HA cluster and a disaster recovery (DR) site in a second data center are optional as well.
The Wings license, version upgrades, and screen customizations rest with your Logo partner; we build and operate the infrastructure.
Tiger Wings Enterprise server requirements
According to Logo's technical documents, which we read in November 2026, the server tables for Tiger Wings Enterprise match those of Tiger 3 Enterprise. Even though users reach Wings from a browser, Logo gives the sizes by user count; vCore in the processor column means a core assigned to a virtual server. The shared notes, such as separate disks, the 128 GB limit of SQL Server Standard, the terminal server ratio, per-user bandwidth, and the custom configuration conditions, are covered in Tiger 3 Enterprise server requirements.
| 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 |
These points are specific to Wings: Logo recommends a discrete 2 GB graphics card for the server, and the same on the computer that runs the Wings application. For the web application, users only need a browser with HTML5 support. Logo gives no separate terminal server ratio for browser sessions, so we measure user counts and peak hours first. The existing setup document mentions .NET Framework 4.5, while the system requirements document recommends 4.6.2 or later; we confirm which one applies before setup.
Logo does not take on backups, database disaster recovery, or failover. The isolated backup zone, restore tests, and the optional SQL HA cluster and DR site described in the setup section of this page cover that work.
What we confirm with Logo before setup
- Whether the values in Logo's document (read in November 2026) still apply to the Wings version you use
- How the Wings server components work
- Operating conditions behind a reverse proxy or access layer
- Supported database versions
- How the graphics card required for the server is provided on a virtual server
- .NET Framework version: the difference between 4.5 in the setup document and 4.6.2 or later in the system requirements document
Technologies: Windows Server · Microsoft SQL Server · Tiger Wings Server · TLS · SSL VPN · ARGE ZTNA · WAF · ARGE Cloud
Frequently asked questions
Does anything need to be installed on users' computers?
No. Logo considers a browser that supports HTML5 sufficient. The product can also be used as a desktop application.
What changes in the infrastructure when moving from Tiger 3 Enterprise to Wings?
The database stays where it is. What is added is the Wings Server service, the publishing address and TLS certificate, and the memory and processing power that sessions need. With fewer desktop clients, less terminal server capacity is needed, and the license and version steps rest with your Logo partner.
Does Tiger Wings need IIS on the server?
According to Logo it is not required, because Tiger Wings Server is its own HTTP/WebSocket server. We also confirm this for your version before setup.
How is the graphics card Logo asks for on the server provided on a virtual server?
Logo's setup documentation asks for a graphics card with at least 2 GB of memory on the server. We confirm with Logo before setup how that is met on a virtual server. The server plan is not final until that confirmation arrives.
What server size does Tiger Wings Enterprise need?
According to Logo, 1–10 users need 8 vCores and 16 GB of memory on both the database server and the application and terminal server; at 51–100 users both grow to 16 vCores and 128 GB. For 101 users and above, the size is agreed with Logo. Logo also recommends a discrete 2 GB graphics card for the server.
For Logo Tiger Wings Enterprise, licensing, implementation, and functional support are obtained from the vendor or your partner. Logo Yazılım makes the software and owns its name and trademark; ARGE ICT is not an official partner or reseller of the vendor, and it provides and operates the infrastructure underneath the software.