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

Logo

Server and cloud infrastructure for Logo Edge T-Series

Edge T-Series is installed on a company server, yet it talks to Logo's cloud services for licensing and its product list. Which external addresses the server may connect to is therefore part of the setup. Access from outside the company is set up separately for users on a browser or the mobile app.

Product architecture

Logo Edge T-Series architecture on ARGE Cloud

In the diagram, the Edge T-Series server, Logo Base, and the Agent run in your dedicated VPC. The Agent's outbound path to Logo's cloud services is defined on the firewall for the required addresses only.

ARGE ICT infrastructure diagram (Logo Edge T-Series). 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 Edge T-Series), the database, and the Logo Base and Agent 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). Logo Base and the Agent connect to Logo's cloud services through the firewall, to the required addresses only.ARCHITECTURE · LOGO EDGE T-SERIESLogo Edge T-Series architecture on ARGE CloudLogo bulutMPLS · 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 requestsLogo Base and Agentinstallation and license managementLogo Base and Agentlicensing and setup run hereApplication serverLogo Edge T-Series · Windows ServerHA cluster: optionalApplication serverLogo Edge T-Seriesredundant cluster on requestDatabase serverengine and version to be confirmed with vendorDatabase 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 upLogo cloud servicesAgent outbound · required addresses onlyLogo cloud servicescontrolled 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 Edge T-Series), 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 Edge T-Series?

Logo divides its products into two families: Logo Cloud, which runs in the cloud, and Logo Edge, which combines products installed on company premises with cloud services. The Tiger, Netsis, and j-Platform groups take the names T-Series, N-Series, and J-Series in Edge. Edge T-Series is the counterpart of the Tiger group; Logo defines it as a hybrid structure enriched with cloud services and labels it on-premises.

The product is offered in Basic, Standard, and Enterprise packages. Production is an add-on module in Basic and included in the other two. E-document items and the database usage license are listed as separate modules.

The cloud services Logo calls PaaS are added on top of this. They include personal report dashboards, online quote collection from suppliers, and Online Account Statement, which brings bank transactions into the ERP.

Logo AI Assistant turns questions asked in natural language into queries and returns the result as a report. According to Logo, Logo Edge Mobil lets users handle account, stock, cash, bank, invoice, and order work from a phone.

Companies moving to Edge T-Series

The Edge T-Series product page does not state a company size or sector. Two groups look at the product: companies planning a new installation on the Tiger line, and Tiger users planning to move to Edge. Teams that want to work from a browser and from mobile devices also belong to this audience.

The infrastructure side of Edge covers the two components added to an existing Tiger installation, Logo Base and the Agent, and the outbound rules. The user base is the same as the Tiger group's; for that group's business profile and the work that stresses its infrastructure, see the Logo Tiger 3 Enterprise page.

Tiger 3 Enterprise still has its own product page, and the timing of a move to Edge and the license terms are settled with your Logo partner. Whichever path is chosen, the server and network are prepared for it.

Logo Base, Agent, and browser access

The server side is the ERP application and its database on Windows Server, and two components are added. According to Logo, Logo Base is where installation is started: installation steps complete automatically, components are loaded after specific checks, and the whole process is followed from one screen. Installed products appear there in one place, and single sign-on (SSO) moves users between applications without signing in again.

The Agent service talks to Logo's cloud infrastructure. According to Logo, the license is synchronized once on first use, later changes arrive through the Agent, and no product key is entered. For the infrastructure, the result is that the server must be able to connect outbound to Logo's cloud services.

For browser access, in Logo's words, the desktop ERP application is virtualized in the web environment and used from the browser. Every browser session consumes resources on the server, so sizing is based on the number of concurrent sessions. According to Logo, this access is made from the internal company network, and connecting from outside the company requires a secure access configuration.

The product page does not state the database engine or version, and Logo lists the database usage license as a separate module. We settle this with Logo or your partner before setup.

Edge T-Series setup on ARGE Cloud

The Edge server and the 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. Sizing follows the number of users and the resources their browser sessions will consume.

We obtain from Logo the list of addresses and ports that the Agent and Logo Base need to access, and the firewall allows outbound traffic only to those. The state of the Agent's outbound connection can be included in monitoring, and the scope is written into the contract. The Agent's connection to Logo does not mean the server is opened inbound.

Browser and mobile users connect with SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. If publishing to the internet is required, the traffic passes through a web application firewall (WAF). Offices and branches connect over IPsec, MPLS, or SD-WAN, and we recommend a second link for each site. Before setup we settle with Logo whether the mobile application connects to the server directly or through Logo's cloud services, and we design access accordingly.

The Logo Base and Agent configuration is backed up with the database to the isolated backup zone; restore tests are run, and their frequency is set in the contract. Backup arrangements are described under our backup and disaster recovery service. Monitoring covers the server and disks, memory, 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; monitoring hours and the scope of response are set in the contract.

If you move from Tiger to Edge, we recommend testing the move first on a copy of the production database; the test environment is optional.

An HA cluster and a disaster recovery (DR) site in a second data center are optional; how the Edge components behave in a cluster is confirmed with Logo.

Package selection, license synchronization, and the steps of moving from Tiger rest with your Logo partner; we build and operate the infrastructure.

Edge T-Series Enterprise server requirements and sizing

Logo publishes a separate system requirements document for Edge T-Series Enterprise, which we read in November 2026; its tables and notes match those of Tiger 3 Enterprise. This section covers the Enterprise edition only, and the Basic and Standard editions have their own documents. In the tables, vCore means a core assigned to a virtual server.

Edge T-Series 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
Edge T-Series 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

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. What is specific to Edge is that the load from browser users and the extra load of Logo Base and the Agent are added on top of the table. We start from the row in the table, confirm it by measurement, and confirm the extra load with Logo.

Logo's document leaves backup, database disaster recovery, and failover out of its scope. That is why the setup section describes the backup of the Logo Base and Agent configuration, restore tests, the optional HA cluster, and the DR site.

What we confirm with Logo before setup

  • Supported database engines and versions
  • Addresses and ports the Agent needs to reach
  • Whether Logo's Enterprise tables are enough once browser sessions and the load of Logo Base and the Agent are added
  • The values in the separate Basic and Standard documents
  • Infrastructure steps when moving from an existing Tiger installation
  • How Logo Edge Mobil connects to the server

Technologies: Windows Server · Logo Base and Agent · SSL VPN · ARGE ZTNA · WAF · ARGE Cloud

Frequently asked questions

Is Logo Edge T-Series a cloud product?

Logo separates its products that run in the cloud under Logo Cloud and those installed on company premises under Logo Edge. Edge T-Series runs on your server or in your dedicated VPC on ARGE Cloud, and it uses Logo's cloud services in addition.

Does the Edge server have to be open to the internet?

It does not need to be open inbound. The Agent has to be able to connect to Logo's cloud services, and that outbound path is defined on the firewall for the required addresses only.

What is done on the infrastructure side when moving from an existing Tiger installation?

The steps of the move rest with your Logo partner. Before the move, we take a backup, define the outbound rules for Logo Base and the Agent, and plan resources for browser sessions.

How does Logo Edge Mobil connect to the server?

We confirm the connection path with Logo before setup. Access from outside the company is planned to pass through a layer that authenticates users (SSL VPN, ZTNA, or ARGE ZTNA).

What server size does Logo Edge T-Series Enterprise need?

Logo gives the same tables for Edge T-Series Enterprise as for Tiger 3 Enterprise. At 21–50 users the database server needs 16 vCores, 64 GB of memory, and 300 GB of free disk; the application and terminal server needs 12 vCores, 64 GB, and 350 GB. For 101 users and above, sizing is agreed with Logo's teams.

Logo Edge T-Series, the product named on this page, is made by Logo Yazılım; the name and trademark belong to the vendor. ARGE ICT is not an official partner or reseller of this vendor; its job is to provide and operate the infrastructure the software runs on. Licensing, implementation, and functional support, in turn, come from 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