Bring Red Hat Experts Into Your Team
Temporary expert support, embedded in your team, with platform depth through SPAS knowledge.
There are four ways to get Red Hat expertise on short notice. Three have a catch.
EaaS is the fourth way: named experts who know your platform, work in clearly defined task areas, and leave behind documented results.
Four paths. Three catches.
Every model has its logic. Only one has no hidden costs, no quality gap, and no dependency on luck.
Fast to find.
Opaque day rates, no coverage if they drop out, no knowledge of your platform standards. You pay for time, not outcomes.
Full control.
3 to 6 months to hire. Tight salary bands. Fixed costs even with no active work. Certified Red Hat talent is scarce on the open market.
Structured.
Slow and expensive. Generalists filling gaps instead of specialists delivering results. No platform depth, high day rates.
Availability like a freelancer. Depth like an internal team. Reliability like a system integrator.
The experts know your platform because they built SPAS. No ramp-up. No loss of control. Documented results from day one.
Named experts. No black box.
You always know who is working with you, what they are capable of, and how much capacity is available.
Marcel König
Lead Engineer and Architect
Available 1 to 2 days per week
- Ansible architecture and rollout
- JBoss EAP hardening and migration
- Compliance frameworks (CIS Benchmarks, NIST, BSI)
- Policy design and target architectures
Matthias Siegl
Senior DevOps Engineer
Available full-time
- Golden Images (Packer, RHEL, OpenShift)
- Jenkins CI/CD pipelines
- RHEL platform work
- Compliance scanner implementation
Benjamin Strebel
DevOps Engineer, Windows Specialist
Available full-time
- Ansible for Windows
- PowerShell DSC
- Windows Server hardening (CIS Benchmarks)
- Active Directory automation
When EaaS fits
Not ongoing operations. Not outsourcing. Targeted expertise for specific tasks within a clearly scoped timeframe.
Introducing a platform module
Rolling out a new SPAS module (e.g. GIaaS or the JBoss Collection) in live operation. You need the expertise for 2 to 3 months, not permanently.
Migration and modernization
WebSphere to JBoss EAP. VMs to containers. These are one-time projects with high risk. External expertise precisely for the critical phase.
Audit preparation
8 weeks until the audit. Baselines need to be defined, scanners configured, reports generated. Time-boxed engagement, concrete deliverables.
Temporary reinforcement
Your own platform expert is on leave or sick. Bridge a key position without a permanent hire, without losing control.
Incidents and troubleshooting
Production incident on JBoss. Compliance scanner returns 200 findings. Complex configuration problem. For situations like these, you need someone immediately.
Policy design and target architectures
Which CIS level for which environment? What belongs in a custom policy? Which hardening measures are relevant for your regulatory requirements?
The advantage of product proximity
EaaS experts are not generic Red Hat consultants. They built SPAS and know every layer of it.
They know the Ansible Collections, the GIaaS policy model, the Compliance Scanner. When they work in your team, they bring platform-specific knowledge, not just general expertise.
That means no long ramp-up, better architecture decisions from day one, and direct access to the team that can extend the platform if needed.
No ramp-up
The experts know your toolchain because they built it themselves. No reading in, no testing the waters.
Better decisions
Knowing the platform means making architecture decisions with real context, not from a textbook.
Direct extensibility
If the platform needs to be adapted or extended, the team behind it is directly reachable.
What EaaS includes
No "let us have a look." Clear structures from day one. Results that stay with you.
Clear responsibilities
Defined scope, clear expectations, no vague engagements. You always know who is doing what and why.
Full documentation
Every change documented. Handover documentation at the end of the engagement. No knowledge drain. Your internal teams can take over everything themselves.
Continuous communication
Regular status updates, direct integration into your team processes (Jira, Confluence, Slack), no black holes.
01 Who holds technical responsibility in an EaaS engagement?
Technical responsibility rests clearly with the named EaaS experts from lennlay. All architecture decisions and security-relevant measures are owned and documented by experienced specialists.
02 What is the difference between EaaS and a freelancer?
A freelancer arrives without platform knowledge, without backup in case of absence, and without structured documentation obligations. EaaS experts know SPAS, work to defined standards, and leave behind results your team can take over independently.
03 How quickly can an EaaS engagement start?
Typically within a few days of the initial scoping call. Because the experts already know the platform, there is no lengthy onboarding process.
04 How do you ensure that knowledge stays with us permanently?
Knowledge transfer is a core component of every EaaS engagement. Documentation, Architecture Decision Records, and structured handover sessions ensure knowledge remains internal.
05 How flexible is the scope of an EaaS engagement?
EaaS is modular and scalable. Scope, duration, and focus areas are defined together at the start and can be adjusted as needed. Short-term engagements are just as possible as multi-month accompaniments.
06 Does EaaS work if we are not using lennlay products?
Yes. The EaaS experts bring general Red Hat and DevSecOps expertise that applies independently of SPAS. The advantage of product proximity is an added benefit, not a prerequisite.
07 How is EaaS billed?
EaaS is billed based on a clearly defined service scope. Regular reporting cycles ensure you always have full transparency on services and costs.
Discuss EaaS with no commitment
15 minutes. No pitch. We figure out together whether and how EaaS fits your situation.
Discuss EaaS (15 min.)Non-binding · No sales pitch · Confidential
