Apache Tomcat Experts in Germany
in minutes from 15,000 CVs with vetted, available specialistsHire experts who set up Tomcat servers, tune Java web applications, and manage servlet-based deployments with WAR files, TLS, and integration to your existing stack. Get fast, precise matching with vetted, available freelancers.
Meet FRATCH Experts in Germany, who have recently used Apache Tomcat
Khalid El Mansouri
Last position:
Lead Architect & Developer at kem-consulting
Development of an agent-based governance platform for the automated assurance of EU AI Act compliance and ODA-compliant orchestration of AI services in complex enterprise environments.
Design and implementation of an agent-based "Mission Control" framework (Aletheia Conductor) for autonomous state monitoring and process control.
Development of "Compliance-as-Code" (CaC) solutions based on OPA/Rego for system-wide enforcement of regulatory guardrails.
Integration of TM Forum ODA standards (TMF630, TMF622, TMF642) to ensure interoperability and standardization.
Building a highly available event-driven architecture using Redpanda and CloudEvents v1.0 for near-real-time event processing.
Implementation of an audit-proof "Evidence Chain" through cryptographic linking of trace logs in preparation for automated audits.
Tech Stack: Java 21 (Quarkus Native), TypeScript (Next.js), Redpanda (Kafka API), CloudEvents v1.0, OPA (Open Policy Agent) & Rego, TimescaleDB, ZincSearch, Redis, TM Forum ODA, Git, GitHub, Clean Code Development, Like-C4.
Ornel Franck Wora Yeno
Last position:
Purchasing Manager, Logistics & IT Manager at Onlinehandler
Proactive support of management in business field development & innovation management
New development of a suite of business applications for analyzing valuation, P&L, and market price risk data
Automation of all internal and external business and work processes
Development of AI-based and AI-supported ETL processes as well as data analysis
Business use-case development
Business and work process optimization
Enterprise architecture management
Sales data analysis and forecasting as well as capture
Inventory management & reordering
Supplier management and communication
Customs processing & clearance
Shipping handling & warehouse coordination
Interface management
Technologies used: Microsoft Office 365, Microsoft Teams, JTL-Wawi, JTL-WMS, OTTO Partner Connect (OPC), Amazon Seller Central, DHL Global Forwarding, Jira, Draw.IO, Java (8,17,21,25), Jenkins, SonarQube, Git, Gitea, Spring Boot, Spring Batch, Vaadin, H2, PostgreSQL, Docker, Local LLMs, Postman, JasperSoft Studio, JasperReports
Peter Fleischer
Last position:
Subproject Manager and Solution Architect - Microsoft 365 Transformation at Automotive Industry
Integration of highly regulated countries such as China and South Korea into a company-wide M365 tenant.
Technical contact for integrating special requirements for the executive board and German subsidiaries that are subject to BaFin compliance requirements.
Subproject management.
Coordination of requirements within the overall architecture.
Design of the use of DLP features from Microsoft Purview.
Design of special access restrictions via Entra ID Conditional Access.
Support in designing the provisioning of Teams teams and SharePoint sites with higher compliance requirements.
Technical support for implementing information classification with sensitivity labels for SharePoint Online and Teams.
Technical support for the subproject introducing CoPilot for M365.
Skills: M365, Purview, DLP, Entra ID, Sensitivity Labels, CoPilot, Teams, SharePoint Online.
Niko Schmuck
Last position:
Developing Architect, Technical Lead "gridlytics" at HH Energienetze
- Building a data integration platform for high, medium, and low voltage assets for contextual analysis of time series with master data from the SCADA control system (IEC 60870 104), INIS, and SAP.
- Responsibility for the architecture and implementation of the solution, as well as sparring partner for the Product Owner.
- Use of Kotlin, Spring Boot, Maven, TimescaleDB, PostgreSQL, liquibase, Elements IoT, Docker, Kubernetes, Grafana, Python, jupyter, and various API gateways.
Martin Hermann
Last position:
Lead Product Owner at Energy
- Team leadership: Prioritization and coordination of four cross-functional teams.
- Platform strategy: Development and implementation of strategies to optimize existing IT platforms.
- Stakeholder management: Active management of expectations and communication with internal and external stakeholders.
- Program and innovation management: Prioritization and coordination of cross-department projects as well as innovation initiatives.
- Product Owner consulting: Advising Product Owners with a focus on product development and continuous product improvement.
- Organizational development: Improving communication and decision-making structures across all organizational levels.
- Change management: Implementing best-practice change management methods to ensure continuous optimization and innovation.
- Quality assurance: Ensuring high quality standards in processes, services, and deliverables.
Sabahattin Kunas
Last position:
Sole responsibility (concept, development, infrastructure, operations) at Own project busik.ch
- Ride-sharing and bus platform, live and working. Backend Spring Boot 4.1 on Java 21, PostgreSQL with Flyway, Testcontainers integration tests. Running in my own AWS account (ECS Fargate, ALB, ECR, IAM least privilege) with CI/CD via GitHub Actions and OIDC federation without static credentials. Development throughout AI-assisted with Claude Code, including my own skills and project-specific memory. Spring Boot · Java 21 · PostgreSQL · Flyway · Docker · AWS ECS/ALB/ECR · CI/CD · GitHub Actions · Claude Code
Frédéric Klein
Last position:
Project Manager (Enterprise Cloud Governance) at CompuGroup Medical SE & Co. KGaA
Short description: Leading a group-wide project to establish standardized cloud governance for Microsoft Azure, including policies, security and compliance controls, automation, and cost and operations management while preserving the autonomy of decentralized business units within regulatory frameworks.
Tasks and activities:
Overall responsibility for designing, building, and implementing a company-wide cloud governance structure (Azure), including target picture, roadmap, and operating model.
Managing internal and external stakeholders (C-level, IT, Security, Compliance, Cloud Architecture, DevOps), including decision and escalation management.
Planning and facilitating workshops on cloud strategy, governance principles, and the design of areas such as identity, connectivity, and platform management.
Defining, implementing, and rolling out cloud policies (Azure Policy / custom policies), security standards, and compliance requirements (including GDPR, ISO 27001, BSI C5).
Building a cloud governance framework based on the Azure Cloud Adoption Framework (CAF), including landing zone and guardrail concepts.
Introducing automation solutions for governance, security, and cost control (policy/control automation, IaC, CI/CD-based control mechanisms).
Implementing cloud security and compliance monitoring mechanisms as well as continuous improvement processes.
Establishing and operationalizing FinOps in an enterprise environment (central and decentralized FinOps teams), including cost management strategies, reporting, and guardrails.
Integrating governance policies into DevOps processes (e.g. CI/CD principles for security and compliance checks, GitLab Runner concept in spokes, GitLab CI/CD for CAF landing zones).
Implementing access concepts including RBAC design and breaking-glass mechanisms (emergency access) as well as certificate automation (ACME / step-ca).
Achievements:
Created a unified, auditable governance and control set for Azure (policies, standards, compliance mapping) and thus laid the foundation for scalable cloud use in a regulated environment.
Established repeatable automation for governance, security, and cost control (IaC + CI/CD), reducing manual effort and implementation risk.
Improved operational and decision-making capability across central and decentralized units (clearer roles, responsibilities, escalation paths, balance between autonomy and group requirements).
Significantly increased workload compliance during lift-and-shift migrations.
Technologies used:
Microsoft Azure Policy, custom policies.
Terraform, OpenTofu, Terragrunt.
step-ca (ACME).
Entra ID.
Azure Firewall.
Azure Networking, hub-and-spoke architecture.
Azure vWAN (evaluation).
Azure Front Door, Azure Application Gateway.
Azure ExpressRoute.
Azure Key Vault.
NetBox.
GitLab (on-premises).
Infrastructure, concepts used:
Cloud shared responsibility model.
Hub-and-spoke connectivity / central shared services (from hub-spoke context).
Central governance with decentralized delivery (business unit autonomy with guardrails).
Methods used:
Scrum.
Stakeholder management (C-level to engineering).
Cloud governance, Azure Cloud Adoption Framework (CAF).
DevOps, CI/CD.
Cost and FinOps approaches: tagging/chargeback models, budget/alert concepts, reserved instances/savings plans vs. on-demand scenarios, sensitivity analyses.
RBAC, breaking-glass concepts.
ACME / certificate automation.
GitLab Runner concept in spokes, GitLab CI/CD pipelines for CAF landing zones.
Vicenco Kenk
Last position:
ITSM Project Manager (self-employed)
Unified ITSM framework
- Definition of a company-wide ITSM target picture
- Introduction of a uniform service structure across all business units
SLA and OLA management
- Building a standardized SLA framework
- Definition of service classes (Business Critical, Standard, Low Priority)
- Introduction of OLAs between internal teams
- Building meaningful SLA reporting
- Definition of KPI and service dashboards for business units
Service portfolio management
- Definition of service descriptions
- If needed, preparing possible cost and service billing
Ticketing & processes
- Incident management
- Uniform ticket categories
- Standardized prioritization
- Escalation matrix
- Automations
- Self-service optimization
Request fulfillment
- Service catalog across all business units
- Approval workflows
Problem management
- Introduction of root cause analysis
- Known error database
- Problem review process
Complete asset management concept
- Hardware lifecycle management
- Software lifecycle management
- Leasing lifecycle
- Mobile device lifecycle
- Monitor lifecycle
- Phone lifecycle
Processes
- Procurement
- Goods receipt
- Inventory
- Assignment
- Return
- Disposal
- Leasing return Goal: single source of truth for all assets
CMDB design
- Definition of all configuration items:
- Workplace
- Notebooks
- Monitors
- Mobile phones
- Printers
Infrastructure
- Servers
- Firewalls
- Switches
- WLAN
- Storage
- Backup systems
Cloud
- Azure resources
- Microsoft 365
- SaaS services
Relationships
- User ↔ Asset
- Asset ↔ Service
- Service ↔ Infrastructure
- Location ↔ Asset
- Goal: make all service dependencies visible
Software asset & license management
- License management concept
- License balancing
- Compliance reporting
- Microsoft license management
- Adobe license management
- SaaS management
- Contract management
- Renewal management
Interfaces & automation Existing systems
- Workday
- Joiner
- Mover
- Leaver
TESMA
- Leasing data
- Contract data
Matrix42
- Asset synchronization
- User synchronization
Active Directory / Entra ID
- User management
Microsoft 365
- License assignment
- Group management
Dormakaba
Access processes
Lifecycle services
Monitoring platforms
- PRTG
- Palo Alto
- Cisco
Reporting & KPI framework
- Definition of a management dashboard
- KPIs
- Ticket volume
- SLA fulfillment
- MTTR
- First resolution rate
- Asset accuracy
- License compliance
- Change success rate
- Service availability
- Degree of automation
Network redesign support
- Governance
- Support of the network redesign from an ITSM point of view
- Definition of affected services
- Change management structure
- Communication concept
CMDB integration
- Recording of all network components
- Service mapping
- Dependency analysis
Validation of documentation and knowledge base articles
- Network documentation
- Operations documentation
- Standard changes
Monitoring & event management
- Target picture
- Central monitoring concept
- Event management process
- Alerting strategy
- Escalation model
Systems
Cisco
Palo Alto
Fortinet
Rubrik
Veeam
Matrix42
Azure
Microsoft 365 Automation
Ticket creation from monitoring
Escalations
Standard actions
Audit, compliance & information security
- ISO 27001 consulting
- TISAX consulting
- NIS2 preparation - consulting
- Audit-ready processes
- Documentation structure
- Evidence tracking in Matrix42
Roadmap
- 12-month roadmap
- Prioritization of all measures
- Quick wins
- Medium-term projects
- Long-term target picture
- Documentation
Kiriakos Krastillis
Last position:
Tech Lead / Architect : OTTO API Platform at OTTO
maturing their API Practices on both, a Business and Technology level. My role encompasses strategy, architecture, developer advocacy as well as hands on software engineering, enabling both technical teams and business leadership to adopt and act on API- centric principles effectively. Coincidentally, we also establish GitOps, DX and Platform Best practices with this project.
Highlights:
- Aligning executives with the initiative by clarifying strategy, replacing misconceptions and myths with facts, clarifying the value of existing assets and enabling informed decision-making
- Formulating a way forward for API Lifecycle Management at OTTO
- Driving platform progress and fostering developer engagement by hands-on engineering work towards strategic goals
API Lifecycle Management, Team Topologies, Organizational Evolution, Regulatory, Platform Advocate, Developer Platform, Communities of Practice, Terraform, Kotlin, Kafka, Kong, WSO2, Apigee, Gravitee, Backstage, AsyncAPI, OpenAPI, API Design, AWS, react, nodejs, typescript, redocly, reactive programming, CDC, golang, gingonic, GitOps, DX (developer experience), stakeholder management, roadmaps, workshops, discovery.
Thorsten Matzner
Last position:
Odoo Implementer at N.N.
As project manager for the Odoo implementation at a small company, I was responsible for designing, implementing, and training a fully integrated CRM and accounting system. Through structured requirements analysis, precise data migration, and targeted change management, I was able to complete the rollout in just eight weeks. The project led to a significant reduction in manual tasks, faster business processes, and increased real-time transparency.
Main Responsibilities
Requirements analysis and process mapping Configuration of Odoo modules: CRM, Sales, and Accounting Data migration (Excel/CSV → Odoo) and quality control Creation of workflows, automated email rules, and dashboards Conducting training sessions and providing support after go-live Project coordination (budget, schedule, stakeholder communication)
Key Achievements
Full implementation of the Odoo suite within the set timeframe (8 weeks) 30% reduction in accounting time and 25% acceleration of the lead-to-sale flow 100% customer satisfaction after go-live, based on survey results Successful migration of 100% of existing master data without data loss Establishment of a sustainable support infrastructure (3-month post go-live support)
Impact
Improved decision-making through real-time dashboards and automated reports Increased efficiency and cost savings (≈ €8,000/month) Scalability for future growth (additional modules can be integrated seamlessly) Strengthened sales and finance departments through seamless process integration
This summary highlights how I created concrete and measurable value for the company through structured project work, technical expertise, and targeted training.
Rüdiger Schulz
Last position:
Full-Stack Software Engineer / Consultant for Digitalization at ARTEVENT
Designed, built, and launched an internal event planning web application used by over 100 department leads for a large event, despite having no dedicated testing phase.
Ensured smooth, failure-free operation during first production use, leading to the tool being adopted for future events.
Automated catering calculations and related workflows, significantly reducing email communication and manual computation effort for meal planning.
Managed deployment and hosting on a Linux server using Coolify, including application setup and runtime operations.
Hired and guided a communication designer on UX while independently owning all technical decisions and implementation.
Tymofii Sukhachov
Last position:
Senior Backend Developer at Medavis
- Developed backend features for Modern RIS, a web-based Radiology Information System integrated with the existing Classic RIS via WebView.
- Worked on a modular Spring Boot backend covering clinical workflows such as appointments, examinations, patients, orders, reporting, billing, and inventory.
- Contributed to event-driven architecture using domain events to decouple workflows across backend modules.
- Implemented REST/OpenAPI endpoints, service-layer business logic, DTO mapping, validation, and integration points for the React frontend.
- Worked with PostgreSQL-backed domain models, Liquibase database changes, read/write model separation, and legacy RIS database structures.
- Integrated authentication and authorization flows using Keycloak and OAuth2.
- Added and maintained unit/integration tests using JUnit, Rest Assured, Testcontainers, and project-specific test utilities.
- Supported CI/CD and local development workflows using Maven, Docker Compose, Jenkins, and generated OpenAPI clients.
Tech stack: Java 21, Spring Boot 3.5, Maven, PostgreSQL, Liquibase, Keycloak, OAuth2, REST, OpenAPI/Springdoc, MapStruct, Lombok, Docker, Testcontainers, Jenkins.
Markus Steffen
Last position:
Fullstack-Developer at VRM Digital / RYZE
- Development and maintenance of a news portal CMS with interfaces.
- PHP development with HTML, CSS, SCSS, JavaScript, MySQL, Laravel, documentation of the interfaces and the system.
- Further development of the SSO system based on Laravel with a large API and connections to AWS, SAP, ERPS.
- Reorganisation and development of the news portals on the basis of a publish platform, services and interfaces to Google, Facebook, Twitter, SSO, SAP technical based on NodeJS with TypeScript and AWS.
- Technologies: PHP, Laravel, MySQL, JavaScript, Vue.js, NodeJS, TypeScript, jQuery, CSS, SCSS, SASS, Unix, Jira, Confluence, Git, Apache, Nginx, AWS.
Kyu-Wang Lee
Last position:
Software Architect & Lead Software Engineer at Landesamt für Steuern Niedersachsen
The goal of BIENE is to provide a uniform program for tax collection for all states.
In tax collection, the aim is to collect the assessed taxes. This includes handling due dates, documenting incoming and outgoing payments, triggering reminders or refunds. Statute of limitations and payment reminders also play an important role. All payment transactions with banks and accounting are mapped in BIENE.
Setting up the architecture and coordinating the provisioning of development and test environments at the Hanover location
Installing and configuring environments on Linux servers (Apache Kafka, PostgreSQL)
Interface tasks: coordinating and aligning the integration of software products from other departments and their test data
Upgrading application server, JDK, Maven project structure
Environment coordination and build management
Implementing external interfaces
Implementing business requirements
Designing and implementing RESTful APIs and OpenAPI specifications
Designing and implementing microservice architecture
Setting up and maintaining CI/CD pipelines
Deploying applications on OpenShift
Creating technical documentation and diagrams
Working with SQL databases (Oracle and PostgreSQL)
Setting up authentication and authorization for the application and users
Containerizing the application (automated deployment via CI/CD pipeline)
Santhosh Kannan
Last position:
Freelance Software Engineer at Zalando SE
- Support Authorization as a Service initiative for enterprise-scale authorization platform
- Incorporate comprehensive observability solutions into authorization infrastructure
- Provision and manage AWS infrastructure for authorization services
- Mentor development team on AWS and Kubernetes best practices
- Tech Stack: Java/Kotlin, Golang, Python, OPA, Spring Boot, AWS, Kubernetes, Terraform, ELK Stack, Prometheus, Grafana
Discover over 15,000 top freelancers
Statistics of experts using Apache Tomcat
Aggregated from the professional profiles of matched freelancers.
Experience
24 years
Position duration
3 years
Positions per freelancer
17
Top business areas
Information Technology, Product Development, Quality Assurance
Top industries
Information Technology, Banking and Finance, Government and Administration
Certification focus areas
Information Technology, Product Development, Project Management
Bachelor's degree or higher
84%
Master's degree or higher
53%
Doctorate
8%
Certifications per freelancer
3
Most common languages
German, English, French
Speak two or more languages
97%
Based on our profile pool as of 30 Aug 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Germany are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Germany using Apache Tomcat
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 30 Aug 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
About the technology
What Tomcat does
Apache Tomcat is a Java web server and servlet container used to run web applications, APIs, and internal tools. It is common in enterprise systems that need a lightweight runtime for Java code without a full application server.
Where it fits
Tomcat is often used for:
- Deploying WAR-based web applications
- Running servlet and JSP applications
- Hosting internal business portals and admin tools
- Serving Java APIs behind a reverse proxy
- Supporting legacy Java stacks that still need stable runtime support
Core ecosystem
Strong professionals working with Tomcat know the Java ecosystem around it: Servlet API, JSP, JSTL, Maven or Gradle builds, and logging with Log4j or SLF4J. They also understand how Tomcat sits next to Spring Boot, reverse proxies, and container platforms when teams package or migrate applications.
When to bring in help
Companies usually seek freelance expertise when a Tomcat setup needs tuning, migration, or troubleshooting. That can include slow startup, memory pressure, TLS issues, session handling, connector configuration, or moving from older Jakarta Tomcat releases to current Apache Tomcat versions.
What good specialists do
Good Apache Tomcat experts read logs quickly, spot deployment errors, and separate application bugs from server issues. They know security headers, certificate chains, JVM flags, thread pools, and classpath problems. In Germany, they often work with mixed teams in English and German, on-site or remote.
Deliverables to expect
Typical deliverables are a hardened server setup, a clean deployment pipeline, performance checks, and clear handover notes. For long-running systems, specialists also document rollback steps, health checks, and the configuration needed to keep Tomcat stable in production.
Frequently asked questions
The facts hiring teams ask for most often when it comes to Apache Tomcat.
Apache Tomcat is used to run Java web applications that rely on servlets, JSP, or WAR deployments. Teams use it for customer portals, internal business tools, and APIs that need a stable Java runtime. It is a common fit when you want a focused servlet container rather than a full application server.
Tomcat focuses on the web layer: servlets, JSP, and HTTP serving. A full application server adds more enterprise services, but many teams do not need that extra scope. If your application mainly serves web requests and business logic, Tomcat is often the simpler choice.
A Apache Tomcat specialist helps when deployments fail, performance drops, or server settings need careful tuning. Teams also bring in help for migrations, security hardening, and production incidents. If your in-house team knows the application but not the runtime, outside expertise is valuable.
A strong Tomcat expert usually knows Java, Maven or Gradle, the Servlet API, and common logging tools. Skills with Linux, TLS certificates, reverse proxies, and JVM tuning also matter. For modern stacks, Spring and deployment automation are often part of the job as well.
Apache Tomcat is the current name most teams use, while Jakarta Tomcat appears in older discussions and legacy systems. The product line has long been tied to the Apache project and the Java web stack. When you search for support, using both names can help surface the right specialist for older environments.
A simple deployment or configuration task may need only a practical Tomcat specialist. Production issues, classloading problems, or migration work usually call for deeper experience with Java runtime behavior and server internals. The more critical the application, the more important hands-on production work becomes.
Yes. Apache Tomcat work is often done remotely because most tasks involve configuration, logs, and deployment access rather than physical hardware. In Germany, many teams still expect clear written communication and may ask for on-site support during major releases or incidents.
Look for clear answers about deployment flow, JVM settings, logging, and troubleshooting steps. A strong Tomcat expert can explain why an app fails to start, how a connector is tuned, and how they would secure the server. Good specialists also give practical handover notes that your team can use later.
The average hourly rate of freelancers in Germany who have used Apache Tomcat in their recent projects is 98 €, which corresponds to a daily rate of about 786 € based on an 8-hour working day.
Of the freelancers in Germany who have used Apache Tomcat in their recent projects, 84% hold at least a Bachelor's degree, 53% hold at least a Master's degree, and 8% hold a doctorate.
On average, freelancers in Germany who have used Apache Tomcat in their recent projects have 24 years of professional experience, with a single engagement typically lasting around 3 years.
The most common languages among freelancers in Germany who have used Apache Tomcat in their recent projects are German (99%), English (96%), and French (22%).
The most common industries among freelancers in Germany who have used Apache Tomcat in their recent projects are Information Technology (97%), Banking and Finance (64%), and Government and Administration (44%).
The most common business areas among freelancers in Germany who have used Apache Tomcat in their recent projects are Information Technology (100%), Product Development (85%), and Quality Assurance (66%).
Main locations of FRATCH Experts, who have recently used Apache Tomcat
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin
Hamburg
Munich
Cologne
Frankfurt