Red Hat Premier Partner for automation, platforms, and hybrid cloud.

Level Up Labs · AAP rider

Video series

Becoming Cloud Native with Red Hat

Level Up’s YouTube channel hosts the Becoming Cloud Native series: public-sector pro tips, network automation with Ansible, and the integrations that make AAP visible to change management and developers.

• Executive overview
• Public sector pro tips 1–5
• Public sector pro tips 6–10
• Public sector pro tips 11–12
• Network automation with Ansible
• Full series index

AWS Marketplace

Fixed-scope Red Hat engagements, transactable on AWS

Buy against AWS committed spend. Custom scopes and private offers are available after the standard package. Support: support@levelupla.io.

Lightwell services

Make open-source remediation a controlled operating capability.

Red Hat Lightwell can help organizations address open-source vulnerabilities across the software they depend on. Turning that capability into safe, repeatable remediation takes more than identifying an issue: teams need to prioritize business risk, work within engineering and change-control processes, validate fixes, and show what changed.

Level Up brings an outcomes-led delivery method shaped by years of Red Hat automation and platform engineering. We help customers assess readiness, establish a measurable baseline, integrate remediation into their workflows, and scale the operating model, with Lightwell as part of the solution where appropriate.

Define. Measure. Analyze. Improve. Control.

Every engagement establishes the scope and baseline first, tests changes against agreed acceptance criteria, and leaves the customer with evidence and a practical control plan.

These packages are a progression, not a commitment to buy every stage. Each one is independently scoped and paid. A customer may stop after any stage with a usable deliverable and a clear decision.

1. 01

   Lightwell Risk & Readiness Assessment

   Establish whether the customer is ready to pursue a Lightwell-supported remediation program and identify the highest-value initial scope.

   Typical activities

   • Align business, security, application, and platform stakeholders on desired outcomes and constraints.
   • Review customer-provided inventories and evidence, such as repositories, SBOMs, findings, application criticality, release processes, and change controls.
   • Map the current vulnerability-to-release workflow and identify bottlenecks, ownership gaps, and operational risks.
   • Establish a baseline for agreed measures where the customer's data supports it.
   • Prioritize candidate applications and remediation work by business impact, exposure, exploit context, and feasibility.

   Deliverables

   • Current-state workflow and stakeholder map.
   • Risk-weighted opportunity and readiness assessment.
   • Baseline and measurement definitions, with data gaps identified.
   • Prioritized candidate backlog and recommended first scope.
   • Decision brief: proceed, remediate prerequisites, or defer.
   • Fixed-scope proposal for the next stage when appropriate.

   Exit decision. Whether to proceed to a paid, bounded remediation pilot, address readiness gaps, or stop.

2. 02

   Controlled Remediation Pilot

   Validate a bounded remediation workflow in the customer's real operating environment before broader rollout.

   Typical activities

   • Select an agreed application, repository set, or workload cohort.
   • Confirm baseline, target measures, acceptance criteria, roles, approvals, and rollback expectations.
   • Configure the agreed Lightwell-related workflow and required customer-system touchpoints, subject to product capability and access.
   • Run a controlled set of remediation cases through review, testing, approval, release, and evidence capture.
   • Analyze outcomes, exceptions, handoffs, and failure modes with the customer team.

   Deliverables

   • Working, documented workflow for the agreed scope.
   • Case-level evidence of actions, decisions, validation, and exceptions.
   • Before-and-after measures for the agreed pilot cohort where data permits.
   • Risks, operational findings, and unresolved dependencies.
   • Scale, revise, or stop recommendation with a production roadmap.

   Exit decision. Whether the measured outcome and operating controls justify production implementation and expansion.

   This is paid implementation work, not a software demonstration. The pilot does not promise that every finding will be remediated or that changes will be released without customer review.

3. 03

   Remediation Value Stream Implementation

   Put the approved workflow into production use across the agreed initial portfolio.

   Typical activities

   • Integrate the validated workflow with agreed source control, build, test, ticketing, security, and change processes, as supported by the customer environment and Lightwell capabilities.
   • Define ownership, decision rights, exception handling, evidence retention, and escalation paths.
   • Establish validation gates, human review, release controls, and rollback procedures.
   • Develop operating documentation, runbooks, dashboards, and team enablement.
   • Conduct a readiness review and transition to the customer's operating teams.

   Deliverables

   • Production-ready remediation workflow for the contracted scope.
   • Operating model, RACI, control points, and exception paths.
   • Validation and release criteria.
   • Runbooks, training, and operational handoff.
   • Baseline-to-production measurement report and backlog for the next increment.

4. 04

   Remediation Factory Scale-Up

   Extend a proven remediation value stream across additional applications, repositories, business units, or environments.

   Typical activities

   • Segment and sequence the expansion portfolio.
   • Reuse and adapt approved workflow patterns.
   • Establish repeatable intake, prioritization, remediation, validation, and reporting.
   • Identify common blockers and cross-portfolio improvement opportunities.
   • Transfer delivery capability to customer teams or designated delivery partners.

   Deliverables

   • Portfolio rollout plan and prioritized waves.
   • Reusable workflow patterns and onboarding materials.
   • Adoption and performance reporting by cohort.
   • Updated capacity, dependency, and risk plans.

5. 05

   Continuous Improvement & Assurance

   Sustain the operating capability and improve performance as the portfolio, threats, and organizational needs change.

   Typical activities

   • Review agreed performance measures and control exceptions at a recurring cadence.
   • Analyze root causes of aged findings, failed remediation attempts, rework, and release delays.
   • Recommend process, automation, governance, and enablement improvements.
   • Support periodic operating-model reviews and new-scope onboarding.

   Deliverables

   • Recurring performance and control review.
   • Improvement backlog with accountable owners.
   • Updated operating procedures and measures.
   • Periodic scale, risk, and investment recommendations.

Open source · Apache 2.0

Ansible POC Generator

A Configuration-as-Code bootstrap for Red Hat Ansible Automation Platform 2.5 or later. After AAP is installed, it creates organizations, credentials, inventories, and job templates for a primary use case so the first live jobs run in minutes, not hours.

• linux_config_mgmt
• network_automation
• rhel_patching
• windows_automation
• windows_patching