IT Infrastructure for Software Development Teams in Bosnia: A Practical Buyer’s Guide

Every software company that opens a development office in Bosnia and Herzegovina goes through the same discovery process. The hiring is usually the easy part with Sarajevo, Banja Luka, Tuzla, and Mostar all having strong engineering talent pools, and the cost-to-quality ratio is a big part of why nearshore software teams choose BiH in the first place. What catches most foreign-owned companies off guard is everything around the engineers: the servers, the network, the build pipelines, and more than anything else the procurement process required to get any of it into the country legally and on time.

This guide is written for engineering leads, IT directors, and operations managers who are setting up or scaling a dev team in Bosnia and need to understand what real IT infrastructure for software companies in Bosnia involves.

Beyond Laptops: What are Dev Team Needs

A typical non-technical office setup checklist stops at desks, monitors, and a fast internet connection. A software development team needs a fair amount more, and the gap between “office IT” and “engineering IT” is where most new BiH offices lose their first few months.

At minimum, a functioning dev team in Bosnia needs:

  • Local or cloud build infrastructure capable of running CI/CD pipelines without becoming a bottleneck for daily commits
  • A network architecture that treats the local office as one node in a distributed, often global, engineering organization
  • Environment parity between local dev machines, staging, and production, which usually means dedicated hardware or well-managed cloud accounts, not shared consumer-grade routers and ad hoc VPNs
  • Endpoint and access management that satisfies the parent company’s security policy, not just local IT preferences
  • A procurement pathway that can get servers, networking equipment, and specialized hardware into BiH without three-week customs delays

Skipping any of these doesn’t create only technical debt, it creates the kind of daily friction that makes a nearshore team feel like a second-class part of the organization instead of a genuine extension of it.

CI/CD Infrastructure: Local vs. Cloud, and How to Size It

This is usually the first real infrastructure decision a growing BiH-based dev team has to make, and it’s worth thinking through deliberately rather than defaulting to whatever the parent company already uses elsewhere.

When Local Build Infrastructure Makes Sense

Running self-hosted CI/CD infrastructure on local hardware in Bosnia makes sense when:

  • Build workloads are heavy and continuous (large monorepos, native mobile builds, ML training jobs) and cloud compute costs are climbing into five figures monthly
  • Data residency or client contractual requirements restrict where source code and build artifacts can live
  • The team already has, or is building, an in-house DevOps function that can own the infrastructure long-term
  • Latency to a specific cloud region is consistently a problem for build agents

For CI/CD infrastructure, sizing typically depends more on build concurrency than on team headcount. A 15-person engineering team running frequent small PR builds needs a different runner topology than the same team running infrequent but resource-intensive integration test suites. As a starting reference point, most mid-sized dev teams in the region run comfortably on a small cluster of dedicated build servers (rack-mounted, redundant power, local NVMe storage for build caches) sized around 32–64 cores and 128–256GB RAM total across the runner pool, scaling horizontally as parallel job counts grow. This is exactly the kind of server sizing conversation worth having with a local IT infrastructure partner before hardware is ordered.

When Cloud Build Infrastructure Makes Sense

Cloud-hosted CI/CD (GitHub Actions cloud runners, GitLab.com CI, CircleCI, cloud-hosted Jenkins on AWS/Azure) tends to be the better default when:

  • Build volume is variable or bursty and elastic scaling matters more than raw throughput
  • The team is small (under ~10 engineers) and doesn’t want to carry infrastructure ownership overhead
  • The parent company already standardizes on a specific cloud provider globally and wants BiH to plug into the same account structure
  • Compliance requirements are already satisfied by the cloud vendor’s certifications

In practice, most software companies with a BiH office end up in a hybrid model: cloud-hosted orchestration (GitHub Actions, GitLab CI) with self-hosted runners physically located in Sarajevo for cost control, data locality, or performance-sensitive build steps while lighter jobs run on standard cloud runners. This hybrid approach is increasingly common specifically because it lets a company keep global tooling standardization while still getting local performance and cost benefits, and it’s a pattern worth discussing directly with whoever is managing your local infrastructure.

Network Setup for Distributed Teams

A BiH engineering office is rarely a standalone network. The most common mistakes we see in newly opened offices:

  1. Treating the office network like a small business LAN. A flat network with a consumer router and shared Wi-Fi password might work for a marketing office; it will not hold up for a team pushing code, running local containers, and connecting to client VPNs simultaneously.
  2. No site-to-site connectivity plan. If the BiH office needs persistent, low-latency access to infrastructure hosted elsewhere (US, Western Europe), a proper site-to-site VPN or SD-WAN setup should be part of the initial network design.
  3. Underestimating redundancy needs. A single ISP connection with no failover is a common gap. For a team whose daily output depends on connectivity, a secondary WAN link with automatic failover is a modest cost relative to the productivity risk of an outage.
  4. Ignoring segmentation. Build servers, engineer workstations, guest Wi-Fi, and any client-specific access (common when the office serves multiple end clients) should sit on separate, properly firewalled network segments.

A properly designed office network for a software team typically includes managed switching, a business-grade firewall with site-to-site VPN capability, redundant internet links, and network segmentation aligned to security zones, all sized to the team’s actual growth trajectory.

IT Procurement in Bosnia: What Foreign-Owned Companies Don’t Expect

This is the part of the puzzle that surprises almost every international company setting up a dev office in BiH, regardless of how experienced their global IT procurement team is.

Import and Customs Realities

Bosnia and Herzegovina is not in the EU customs union, which means server hardware, networking equipment, and specialized peripherals ordered from EU or US vendors are subject to customs clearance, import duties, and VAT on entry, even for a company that already has accounts and volume pricing with a global vendor elsewhere. A few realities that catch people off guard:

  • Lead times are longer than they look. A server that ships from a European warehouse in two days can sit in customs clearance for one to three weeks depending on documentation completeness, HS code classification, and current customs workload. Ordering “just in time” for a new hire’s start date routinely fails.
  • Import duties and VAT apply on top of hardware cost. Budgets built purely on vendor list price without a local import cost estimate are usually 15–20% under actual landed cost.
  • Documentation requirements are specific. Commercial invoices, certificates of origin, and correct customs declarations matter, incomplete paperwork is the single most common cause of customs delays, not the hardware itself.
  • Direct-to-BiH shipping from some vendors isn’t straightforward. Certain manufacturers and distributors don’t ship directly to BiH at all, or only do so through regional distribution partners, which means procurement often has to go through an authorized local reseller rather than a vendor’s global portal.

Why This Changes the Procurement Model

For a foreign-owned company, the practical implication is that IT procurement in Bosnia works best through a local partner who already holds vendor relationships and understands the customs process, rather than trying to route every purchase order through a US or EU headquarters procurement system built for a different regulatory environment. This is one of the most common reasons companies opening a BiH office end up working with a local IT infrastructure partner even when they already have global vendor agreements in place elsewhere, someone has to own the local reality of getting hardware from an order to a rack.

A capable local partner should be able to:

  • Match server, storage, and networking specifications to your existing global standards (so a BiH-deployed server is a like-for-like match to what’s running elsewhere in the organization)
  • Handle vendor relationships with major manufacturers directly, with authorized partner or reseller status that ensures genuine hardware and valid warranty coverage
  • Manage customs documentation and import logistics as part of the procurement process, not as a separate problem for your team to solve
  • Provide realistic lead-time estimates that account for customs
  • Advise on public procurement law (ZJN) requirements in cases where the BiH office serves public-sector or internationally-funded clients, where formal tender rules apply

Why “Vendor-Agnostic” Matters More Than It Sounds

Global engineering organizations tend to standardize on specific vendors using a particular server manufacturer, a specific networking stack, a preferred backup solution etc.. A local IT partner that’s tied to a single vendor’s product line will either push you toward hardware that doesn’t match your existing standards, or simply can’t fulfill the order at all.

A vendor-agnostic IT partner, one with authorized status across multiple manufacturers rather than an exclusive reseller relationship with one, can match your existing infrastructure standards instead of dictating new ones. That matters most in exactly the CI/CD and network infrastructure decisions described above: sizing a build server cluster, choosing networking equipment, or selecting backup and disaster recovery tooling should be based on your team’s actual workload and your organization’s existing standards, not on which vendor happens to pay the local reseller the best margin.

A Practical Checklist Before You Sign a Lease

For any company scoping a new engineering office in Sarajevo or elsewhere in Bosnia, it’s worth working through these questions before hardware gets ordered:

  • Will CI/CD run locally, in the cloud, or in a hybrid model and who owns that infrastructure day-to-day?
  • What’s the realistic build server sizing based on team size and workload, not a generic office IT template?
  • How will the local network connect to existing infrastructure elsewhere be it site-to-site VPN, SD-WAN, or something else?
  • What’s the actual landed cost of hardware once import duties, VAT, and customs handling are included?
  • Who locally can manage vendor relationships, warranty claims, and hardware replacement without routing every issue through a headquarters procurement team unfamiliar with BiH regulations?
  • If the office will serve public-sector, EU/US government, or internationally-funded clients, is there a plan for procurement that satisfies BiH public procurement law (ZJN) or donor compliance requirements?

Getting IT Infrastructure Right From Day One

Software companies that treat their Bosnia office as a full engineering site with the infrastructure, network design, and procurement pathway to match consistently avoid the six-month scramble that offices built on a generic “office IT” template run into. The technical talent in BiH is not the bottleneck. The infrastructure decisions made in the first few months usually are.

Zerick works as a vendor-agnostic IT infrastructure and procurement partner for software companies, consulting firms, and BPO/shared-service centers building engineering teams in Bosnia and Herzegovina. With authorized partner status across HPE, Dell EMC, Supermicro, Microsoft, Cisco, Fortinet, Veeam, and Acronis, and nine years of experience navigating BiH import and procurement realities for international clients, Zerick handles the infrastructure side including server and network sizing, CI/CD build environments, procurement and customs logistics, so engineering leadership can focus on the team, not the supply chain.

If you’re scoping IT infrastructure for a new or growing software development team in Sarajevo or elsewhere in BiH, get in touch with Zzerick to talk through your specific setup.