triox informatika

Partners

The vendor side is our job. You have one contract

In a working environment, products from nine vendors work together: servers, networking, storage, backup and licensing. We hold this chain together—from procurement through monthly license reporting to lifecycle planning.

Where each vendor fits

A managed environment consists of six layers. Each layer has its own vendor, contract, update cycle and path for reporting issues—and all six are the responsibility of the same team.

The six layers of a managed environment and their vendors. From top to bottom: licensing and platform—Microsoft, under SPLA and CSP contracts; virtualization—Microsoft Hyper-V, VMware, Proxmox; server and compute—Dell, HP/HPE, Lenovo, IBM, with iDRAC and iLO out-of-band management; network—Cisco and MikroTik, with a dedicated gateway per client; storage—Synology NAS, plus SAN, iSCSI and RAID; backup and replication—Veeam and Synology, on multiple independent targets. All six layers are operated by the same team. LAYERS OF A MANAGED ENVIRONMENTLICENSE & PLATFORMMicrosoftWindows Server · SQL Server · Microsoft 365—on SPLA & CSP contractsHYPERVISORMicrosoft Hyper-V · VMware · Proxmoxall three platforms in operation—you don't have to switchSERVER AND COMPUTEDell · HP / HPE · Lenovo · IBMPowerEdge and ProLiant—with iDRAC, iLO out-of-band managementNETWORKCisco · MikroTikrouting, firewall, VLAN, VPN—dedicated gateway per clientSTORAGESynology · SAN / iSCSI / RAIDNAS and block-level storage, sized to the workloadBACKUP & REPLICATIONVeeam · SynologyBackup & Replication and Agent—on multiple independent targetsALL SIX LAYERS ARE THE SAME TEAM'S RESPONSIBILITY

Who we work with

Products from the vendors below run every day in the environments Triox operates. This list is not a catalog: for each one, it states exactly what we use it for.

Server and compute

The hardware your virtual machines run on—in our data center and at your site alike. With every vendor, we work with out-of-band management: the server can be managed even if the operating system won't start.

  • Dell

    Dell Technologies

    PowerEdge server platform with iDRAC out-of-band management.

    • Enterprise server fleet underneath our data center virtualization
    • Taking over an existing PowerEdge fleet for operations, without replacing it
  • HP / HPE

    Hewlett Packard Enterprise

    ProLiant server platform with iLO out-of-band management.

    • Operating on-site and data center servers
    • Firmware and lifecycle tracking across the hardware's entire life
  • Lenovo

    x86 server platform—the continuation of the server line acquired from IBM.

    • Operating and expanding servers in an existing fleet
    • Procurement support: configurations sized to the actual workload
  • IBM

    Operating legacy IBM servers and platforms.

    • Taking over and monitoring older IBM System x machines
    • The x86 line moved to Lenovo in 2014—we maintain the continuity

Network

The network is what keeps clients separate from one another. A dedicated gateway sits in front of each client's environment, with its own firewall rules, its own VPN endpoint and its own public IP.

  • Cisco

    Enterprise networking equipment in the core and access layers.

    • Switching and routing in the redundant 2×10 Gbps backbone
    • Operating and documenting on-site networks
  • MikroTik

    RouterOS—routing, firewall, VPN and VLAN on one device.

    • A dedicated gateway per client: firewall, NAT and VPN endpoint
    • VLAN-based segmentation between the public and the internal layer

Storage, backup and replication

For us, backup is not a by-product of the production system but separate infrastructure: on multiple, physically independent targets at multiple sites. Critical workloads also get an off-site VM replica.

  • Veeam

    Backup & Replication and Veeam Agent—the backbone of the backup chain.

    • Backup of virtualized and physical machines, VM replication to an off-site target
    • Restore tests: does the system actually start from the backup
  • Synology

    NAS storage and a standalone backup target.

    • An independent backup target—not the same storage the production system runs on
    • File services and local backup at smaller sites

Platform and licensing

Software licensing becomes a risk where nobody keeps track of it. Licenses for Microsoft products running in the leased environment are held in our name and reported based on actual monthly usage.

  • Microsoft

    CSP reseller · SPLA contract partner.

    • SPLA: Windows Server, RDS and SQL Server based on monthly usage
    • CSP: Microsoft 365 and cloud add-ons on one invoice, with support in Hungarian
    • Operating Hyper-V, Windows Server, Entra ID and Exchange

Why this matters to you

Nobody cares about a vendor list on its own. What matters is how many contracts you have to keep track of, and who you call when the system is down.

A comparison of two arrangements. On the left: your company deals directly and separately with six suppliers—server, network, storage, backup, virtualization and licensing—so there are six contracts and six contacts, and none of them sees the whole picture. On the right: your company connects to Triox through a single contract, and all six vendor lines run through Triox—one contact, one party responsible for the entire chain. VENDOR BY VENDORYour firmServer vendorNetwork vendorStorage vendorBackup vendorHypervisor licenseLicense resellerSIX CONTRACTS · SIX CONTACTSAND NONE SEES THE FULL PICTUREWITH TRIOXYour firmTrioxONE CONTRACTServerNetworkStorageBackupHypervisorLicenseONE CONTRACT · ONE CONTACTONE OWNER FOR THE FULL CHAIN
01

One contract for everything

When something doesn't work, it isn't up to you to coordinate between the server vendor, the network vendor and the license reseller. You have one contractual partner, and it handles the vendor side.

02

The license audit risk is ours

Microsoft licenses running in the leased environment are held under an SPLA agreement, in the service provider's name. Reporting the correct license quantities is our job and our responsibility—every month.

How SPLA and CSP work →

03

We don't tie you to one vendor

We are not committed to any single vendor. If your existing fleet is HPE, it stays HPE; if MikroTik is the right answer for the job, it won't become something else just because that would be more convenient for us.

04

Manageable even when it's down

iDRAC and iLO out-of-band management means we can reach the server even if the operating system won't start. Nobody has to go on site just to see what's wrong.

The vendor should be a choice, not a constraint. We look at what solves the problem—not at which logo looks better on a proposal.

What this means in practice

If a server component fails today, you don't need to know which vendor's support to contact, with what contract number and in what language. If a network device's firmware gets a security update, you don't need to watch the vendor's notices. If Microsoft's licensing terms change, you are not the one who has to keep up with it.

That's the difference between a supplier list and an operations contract. The list is still there—just not on your desk.

You can read about completed projects on the Case studies page, and about the infrastructure behind them on theTechnology page. We do not publish our clients' names.

The brand and product names listed are trademarks of their respective owners. They are shown to identify the technologies we use.

Let's look at what's behind your system today

In a review, we map which vendor contracts, support periods and licenses you currently have in place—and where the gaps between them are.

Request an infrastructure review