- Home
- Projects
What we have done
and what came of it.
We only show projects here that we can back up. Two of them are published as Netgate case studies. Where we may not name customers, we describe the starting point anonymously. You won't find invented references or estimated percentages here.
Six projects at a glance
Click a project to open the details.
With customer names
Case study · PublishingGräfe und Unzer: firewall migration at a publishing house
Netgate case study
The Munich publisher Gräfe und Unzer, founded in 1722 and known for travel guides and lifestyle titles, ran two pfSense CE machines virtualised on vSphere. In high-availability mode the pair was unstable and caused fluctuations in the network.
ESBYTE migrated to two dedicated Netgate 8200 MAX with pfSense Plus. Result: stable HA operation, independence from server virtualisation, configured IPsec and OpenVPN connections and traffic shaping, implemented in one working day with minimal interruption.
Also published by Netgate: case study on netgate.com
- 2×
- Netgate 8200 MAX, HA pair
- 1 day
- Implementation
- 1722
- founded
Case study · Event technologyNeumann & Müller: one standard for around 20 sites
Netgate case study
Neumann & Müller Veranstaltungstechnik (event technology) runs around 20 sites with more than 900 employees. The network gateways ran on consumer hardware from various manufacturers, without a uniform setup and with increasing outages.
Netgate 6100 MAX were deployed at the larger sites and 2100 MAX at the smaller ones, based on a standard configuration developed once. Many devices were shipped preconfigured and only had to be plugged in on site.
ESBYTE handled product selection, technical consulting and rollout support; the customer's internal team carried out the implementation. Result: one uniform standard across all sites, greater stability and significantly less recurring configuration work.
- ~20
- sites
- 900+
- employees
- 1
- standard configuration for all
Published as a Netgate case study: case study on netgate.com
Reference · Public administrationMunicipality of Pullach: ongoing operations across many systems
ongoing operations
The case studies above each describe a project with a beginning and an end. Everyday life as an external IT department looks different. One example:
For the Municipality of Pullach we look after a landscape of many individual systems: firewalls, email security, network, telephony, access, workplaces and monitoring. Part of it runs on the municipality's own infrastructure. We work there partly under our own responsibility and partly together with the colleagues on site. What applies in each case is stated below.
Firewall and network
- Ongoing support of the firewall infrastructure on pfSense and OPNsense, including adjusting configurations as requested by the municipality
- Maintenance of these firewalls, i.e. installing software updates
- Support of the Omada SDN infrastructure, operated on the municipality's infrastructure
- Operation and maintenance of NetBox as the single source of truth for the network infrastructure
Email security
- Support of Hornetsecurity as the upstream email security system, including all communication with the manufacturer's support
- Operation and support of NoSpamProxy as the email security system in the municipality's infrastructure, including maintenance and communication with the manufacturer
Access, telephony, workplaces
- Operation and maintenance of LoginTC for two-factor authentication when employees dial in via VPN from their home office
- Co-support of the phone systems, implemented with 3CX on the municipality's infrastructure
- Co-support of the virtual workplaces, implemented with Omnissa Horizon on the municipality's infrastructure
- Occasional help with user support, by phone or email
Monitoring and security
- Monitoring of various resources, such as the operating status of firewalls and servers, via a monitoring system operated by ESBYTE
- Security audits of the systems mentioned: review and hardening of the configurations
- Client
- Municipality of Pullach im Isartal
- Role
- Ongoing support and operations, partly in co-support with the internal team
- Firewall
- pfSense and OPNsense
- Email security
- Hornetsecurity, NoSpamProxy
- Network
- Omada SDN, NetBox as SSOT
- Access
- LoginTC (2FA for VPN)
- Telephony
- 3CX
- Workplaces
- Omnissa Horizon (VDI)
- Ongoing
- Monitoring, maintenance, security audits
Anonymised
For these customers we do not have permission to name them. We therefore describe the starting point and approach without names.
Compliance · manufacturingSupply chain law: an audit request designed for corporations
In progress, result pending
Starting point
The customer received a request from one of its own customers as part of a Third Party Cyber Risk Management (TPCRM) review. The background is the German Supply Chain Act: it obliges certain companies to ensure security measures in their own supply chain too. In practice, this means that review processes designed for large companies are applied unchanged to smaller suppliers.
Challenge
The request confronted the customer with a fundamental choice: sign a formal agreement or complete a self-assessment. And in both cases the question of which obligations would actually be entered into.
Approach
We compared both options and assessed which obligations each would create. Since the obligations of a signed agreement seemed too extensive for the customer's size and structure, we recommended the self-assessment.
Implementation
We broke the self-assessment down into manageable parts, a structured Excel table. We gave the customer clear feedback on which parts could only be partly fulfilled, or not at all, in our own structure as a rather small mid-sized IT service provider. We proactively completed and explained the sections on which reliable statements were possible, and advised on the remaining points.
Result
The process is ongoing, so there is no result yet.
- Industry
- Manufacturing company
- Size
- up to 50 employees
- Trigger
- TPCRM review by a customer, background: German Supply Chain Act
- Recommendation
- Self-assessment instead of a signed agreement
- Status
- In progress, result pending
IT operations · manufacturingMaintenance that goes unnoticed during operations
in production use
The assignment was: automate updates. The first question was a different one: when do people in this company actually work?
Starting point
Updates and software installations came up regularly and had so far been done by hand, in the middle of working hours. Every update was a noticeable interruption: restarts at inconvenient times, blocked workstations during installation, questions about when the computer would be free again. Because different operating systems are in use, a single solution could not cover it.
Challenge
Maintenance was to run reliably and automatically in the background, without disrupting operations, across Windows, macOS and partly Linux. In addition, critical processes must not be interrupted, restarts may only happen at non-critical times, and employees should notice as little as possible.
Approach
First we got an overview: which systems are in use, in which cycles they receive updates and when people actually work. This led to the decision to develop a dedicated script for each operating system, rather than force a cross-platform solution that would not have done justice to the particularities of the individual systems.
Implementation
On Windows, a script triggers updates and installations on a schedule outside core working hours, detects running applications and active sessions, and only restarts once nobody is working on the device any more. For macOS, a comparable script was created that fits into the system logic there and also works in the background, without pop-ups and without forced restarts. Where Linux runs, a script was added that automates and logs package updates. All three report back whether maintenance succeeded. If something goes wrong, it is corrected rather than going unnoticed.
Result
The scripts are in production use. Since then, updates and installations happen in the background without noticeably affecting operations. An evaluation over a longer period is still pending.
- Industry
- Manufacturing
- Task
- Automate updates and software installations
- Systems
- Windows, macOS, partly Linux
- Solution
- A dedicated script per operating system
- Status
- in production use
Start-up · financial sectorHow we clarify needs with new customers
Quote submitted
Starting point
A newly founded company in the financial sector was facing the fundamental build-up of its IT infrastructure, in the office as well as for mobile working. Strong security measures on different levels are indispensable for its business.
Challenge
First, the needs had to be clarified, a particularly open question for a start-up without any existing IT structure.
Approach
We held two briefing sessions: the first captured the basic needs, the second clarified the specific technical points resulting from them. Using GDPR-compliant transcription and AI-assisted evaluation, we documented the requirements quickly, comprehensively and transparently, and agreed them with the customer.
Implementation
Based on the agreed requirements, we prepared a quote, also with AI assistance, and sent it to the customer.
- Industry
- Financial sector, start-up
- Size
- up to 10 employees
- Task
- Build IT infrastructure for the office and mobile working
- Setting
- High security requirements on several levels
- Status
- Quote submitted
How a project comes about
This is the path of an IT project. If, on the other hand, it is about a workflow that gets stuck in everyday work, the starting point is not a needs analysis but a Process Diagnosis. There we first check whether a project is needed at all.
Contact
No obligation and free of charge.
Needs analysis
We understand the requirements and the status quo.
Implementation
Cut to fit, built properly.
Operations
Reliable continued operation instead of project completion and goodbye.
A similar starting point?
Describe in two sentences where things are stuck for you. We will tell you whether we have solved something like it before.
Oder direkt anrufen: +49 89 2000 6500 · Mo bis Fr, 9 bis 17 Uhr