FaceOps · Invoke
Hand activating a digital automation panel with gears and connected icons

An Invoke product · Managed Service console

The intelligence layer for your automation.

Red Hat Ansible executes. FaceOps decides what to do, prioritizes, requests approval, runs with full traceability and measures the value of every action across your entire estate.

  • Runs in your infrastructure
  • Agentless inventory
  • Every action ticketed and approved
300+prebuilt automations
6health pillars
×21productivity in the patching exampleillustrative
0direct connections from FaceOps to your machines
  • RHEL
  • Windows Server
  • Red Hat Ansible
  • OpenShift
  • Vault
  • Satellite
  • Grafana
  • ServiceDesk Plus
  • Dynatrace
  • Qualys
  • SIEM
  • AD · LDAP · IGA
  • PostgreSQL
  • JBoss EAP
  • KVM
  • VMware
  • Google Cloud
  • AWS
  • Azure

The problem

Automating isn't enough if no one governs what gets automated.

Most IT teams already have scripts and playbooks. What's missing is the layer that decides when to use them, with whose approval and with what result.

Without a decision layer

  • Scripts and playbooks scattered across teams, different in each one.
  • No one knows for sure what ran, on which machines and with what approval.
  • Alerts arrive, but remediation depends on who's on call.
  • The value of automation can't be proven to management.

With FaceOps

  • A single catalog of actions, ready to use from day one.
  • Every run starts as a ticket, with approval and a complete record.
  • Estate health suggests what to fix before it fails.
  • Productivity, ROI and MTTR visible to whoever manages the contract.

How it works

FaceOps decides. Ansible executes. One ticket.

Every action follows the same cycle, whether it's restarting a service or patching the entire estate.

FaceOps architecture FaceOps, the intelligence layer, receives signals from management tools, decides and sends approved tickets to the Red Hat Ansible engine, which executes on servers, databases, networks, storage, edge sites, physical servers, hypervisors, OpenShift and clouds. ITSM Monitoring SIEM · CVE AD · LDAP · IGA FACEOPS Intelligence layer Detect Decide Approve Execute Measure approved ticket Red Hat Ansible the engine that executes Vault Servers Databases Network · Storage Edge Physical · BMC Hypervisors OpenShift Clouds
FaceOps decides. Ansible executes. Your estate stays governed.
  1. Detect

    Daily agentless inventory, health by pillar, alerts and integrations with monitoring and SIEM.

  2. Decide

    Cross-checks findings against your stack, your policies and the known-error database, and proposes the action.

  3. Approve

    The action becomes a ticket. The group that owns that area approves it.

  4. Execute

    The automation engine runs it with credentials from the vault, on one machine or across the whole estate.

  5. Measure

    Result, report attached to the ticket and hours saved added to the value dashboard.

Example
TCK-2611
CVE assessment · 148 RHEL servers · requested by Security · report cve-assessment.pdf attached
ApprovedExecuted

Capabilities

Your entire estate, in one console.

Daily operations, health, governance and development under the same rules: whatever goes through FaceOps is approved, recorded and measured.

Actions

300+ prebuilt automations, ready to use

Run them on one machine or across the entire estate in a single ticket. Assessments attach a standard PDF report to the ticket.

  • Patching
  • CVE assessment
  • Country time change
  • Certificates
  • Backups
  • OS updates
  • Service control
  • Daily inventory

IT governance

If it's not in the stack, it can't be enabled

  • Technology stack and obsolescence
  • Expiring licenses and policies
  • CVEs, scanning and incidents with a known-error database
  • SLAs and reports

Integrations: ServiceDesk Plus, Dynatrace, SIEM, Qualys, AD, LDAP and IGA.

Technician monitoring robotic arms on a production line from a tablet

Edge & field

Your remote sites, in plain view

Group stores, mine sites or branches as edge sites. Open each one to see its architecture diagram with the health of every component, including physical servers via BMC.

Full visibility

Physical, virtual and far away

  • Virtual and physical servers
  • Networks, storage and hypervisors
  • Containers on OpenShift
  • Clouds, databases and platforms
  • Business segments with their architecture

Development factory

From requirement to code, by the rules

An AI agent turns requirements into code under your organization's development policies for OpenShift, and hands it to the pipeline for review and deployment.

Health radar

Six pillars tell you how healthy your estate really is.

Inspired by the AWS Well-Architected framework. Every finding becomes a preventive remediation, launched as a ticket with approval.

Pillar · 1/6

Reliability

82%

Whether services stay up and recover from failures.

Sample policies

    Each item to remediate launches a preventive ticket that the owner group approves.

    Health at every level

    1. Machine
    2. Operating system
    3. Platform
    4. Business segment
    5. Entire estate
    Estate health after preventive remediationsIllustrative example
    68%91%

    Six weeks, 23 remediation tickets approved and run. Each one left its report attached.

    Value & performance

    Productivity is measured in ×N.

    Every action run adds up hours saved. The contract administrator sees the benefit by area in an executive view.

    ×N = manual hours ÷ automated hours
    ProductivityHow many times more your team gets done per action.
    ROIAutomation benefit versus its cost.
    MTTRMean time to resolve incidents.
    Hours saved per monthIllustrative example
    M1M6

    Monthly server patching

    Illustrative example
    200
    45
    Manual
    150 h
    With FaceOps
    7 h
    ×21productivity on this action, with the assumptions above.

    Assumption: with FaceOps, 3 h of preparation and approval plus 1.2 minutes of supervision per server. Actual values are calculated on your estate.

    Business segments

    Organized by what matters to the business, not by server.

    Each segment groups its components across every layer and environment, with its owner group, its health and its availability. Segments roll up into categories.

    • Applications
    • Networks
    • Solutions & identity
    • Platforms
    • Data
    Example segment with three environments, component health, replicas and a drift alert between QA and Production Payments Example Owner: Payments team Availability 99.95 % DEVELOPMENT QA PRODUCTION Apps · OpenShift Databases Servers Network · Storage app v2.4×1 PostgreSQL 15×1 RHEL 9×1 LB · SAN×1 app v2.3×1 PostgreSQL 15×1 RHEL 9×1 LB · SAN×1 app v2.4×2 PostgreSQL 15×2 RHEL 9×2 LB · SAN×2 QA is misaligned with Production app v2.3 in QA vs v2.4 in Production · remediation ticket proposed
    Health rules per environment

    In production, every component needs at least 2 replicas. QA and Development can run 1, with the same architecture and versions as production.

    Drift detection

    FaceOps flags any environment that drifts from production in architecture or versions.

    Governed by segment

    Actions and approvals belong to each segment's owner group, with its live architecture and availability.

    Value by business area

    The benefit of automation is reported by segment and business area, not by server.

    Operations data lake & AI

    Every action leaves a history. AI turns it into foresight.

    Inventory, runs, tickets, approvals, alerts and health are stored as structured history in an operations data lake. You keep control and governance of your data.

    1. Sources
      • Daily agentless inventory: packages, images, OS and platform files, configs
      • Runs, tickets and approvals
      • Alerts and health over time
      • Git repository per machine
    2. IngestionNormalized and structured, every day
    3. Operations data lakeThe full history of your estate, under your governance
    4. AI modelsTrends, prediction and anomaly detection
    5. Insights & actionsRecommendations and executive reports

    Insights come back as remediations: ticket, approval, execution and measurement.

    Trends

    How health, incidents and effort evolve by machine, segment and area.

    Failure & capacity prediction

    Disks, memory and certificates that will run out, before they do.

    Drift detection

    Changes that move a machine or environment away from its baseline.

    Automation recommendations

    Repetitive manual work that should become an action.

    Executive value reports

    Productivity, ROI and MTTR by business area, ready to share.

    Sample insightsIllustrative
    • Predictiondb-02: disk will reach 90 % in about 12 days. Suggested: expand the volume.
    • DriftPayments QA drifted from production after the last deployment.
    • RecommendationCertificates were renewed by hand 9 times this quarter. Suggested: automate.

    Security & architecture

    Designed not to touch what it shouldn't.

    Two layers: a platform that is secure by design, and an operation that keeps your estate secure every day.

    01Secure by design

    1. Usersigns in via IGA, AD or LDAP
    2. FaceOps DMZdecides and proposes the action
    3. Ticket & approvalthe owner group approves
    4. Automation engineRed Hat Ansible runs the action
    5. Vaultreleases the credential, strict mode
    6. MachineSSH · WinRM, change saved to Git
    Installed in your DMZAlways on your infrastructure. No estate data on third-party servers.
    Never touches machines directlyEvery action goes through the automation engine, with a ticket and an approval.
    Vault in strict modeCredentials live in the vault. A machine that isn't linked to it is unreachable.
    No mandatory agentsInventory and metrics over SSH and WinRM. The agent is optional.
    Full audit trail per userWho requested, who approved, what ran and with what result.
    Owner-group approvalEach area has an owner group. Any member can approve, and participation is measured.
    Least privilegeEach user sees and requests only what their area allows.
    Identity at the sourceUsers come from IGA, AD or LDAP, and access is managed there.
    Git history per machineEvery machine has its own repository with all of its changes.

    02Security for your operations

    • CVE managementPrioritized by severity and exposure, with automated patching.
    • Security scanningScheduled scans across the estate, with results attached to tickets.
    • Security policies per OSHardening per operating system, measured in the health radar.
    • Expiring certificatesTracked and renewed before they cause an outage.
    • Incidents & known errorsA known-error base whose fixes are verified on the machine before they are applied.
    • SIEM & QualysFindings from your security tools become actions.
    • Audit evidenceEvery ticket carries its standard PDF report.
    Security postureIllustrative
    Critical CVEs open6
    Patches up to date96%
    Certificates expiring within 30 days1
    Critical CVEs openPatches up to date

    Automations

    Some automations replace entire projects.

    Beyond the 300+ prebuilt automations, advanced automations do in days what used to be a project. They are always visible, and each one shows its productivity.

    300+prebuilt automations, ready from day one

    Middleware

    Migration to JBoss EAP 8

    Moves applications to the current release with prior assessment, execution and validation.

    Productivity×N

    Operating system

    CentOS → RHEL conversion

    Converts servers in place, without reinstalling, with a report per machine.

    Productivity×N

    Infrastructure

    Move machines between infrastructures

    Moves workloads between hypervisors, datacenters or clouds in an orderly way.

    Productivity×N

    Applications

    Modernization

    Takes legacy applications to current platforms along a defined path.

    Productivity×N

    The productivity of each advanced automation (manual hours versus hours with the automation) is calculated on each customer's estate.

    Robotic arm scanning a box in an automated warehouse, next to a digital operations map

    Advanced automations

    Visible from day one, activated when you need them

    Every advanced automation appears in FaceOps with its productivity, even before it's activated. You choose which ones to turn on, based on the estate they impact.

    Base

    Fixed value per node

    A simple model based on the size of the estate you want to govern.

    Included

    300+ automations included

    The prebuilt catalog is included so FaceOps works from day one.

    On demand

    Advanced automations by activation

    Activated separately, based on the estate they impact.

    Regional reach

    One console for an estate spread across the region.

    Invoke operates from 6 Latin American countries. FaceOps brings datacenters, cloud and edge sites together under the same rules, operated remotely.

    6Latin American countries
    10years specialized in Red Hat
    3environments: datacenter, cloud and edge
    Invoke base in ChileSites of a distributed estate (illustrative)

    Getting started

    Try it at your own pace.

    Start with a demo to get to know the console, or go straight to a proof of concept on your estate.

    Option 1

    Demo

    Use FaceOps today, nothing to install.

    Where
    Invoke environment on Google Cloud
    Activation
    Your account executive activates it and it's ready in minutes
    Installation
    None: you sign in from the browser
    Validity
    Limited
    Best for
    Getting to know the console and running actions on a test scenario
    Request a demo

    Option 2

    Proof of concept

    FaceOps on your real estate.

    Where
    In your infrastructure
    Activation
    Invoke specialists support you throughout
    Installation
    Guided, in your DMZ
    Validity
    Limited and agreed with you
    Best for
    Validating with your machines, integrations and policies
    Talk to a specialist

    Invoke business lines

    FaceOps connects everything Invoke does for you.

    Invoke works across three lines. FaceOps is where they meet: what we implement, license and operate is governed in the same console.

    Line 1

    Services

    Consulting, architecture and implementation, with in-house and partner specialists.

    Line 2

    Licenses & subscriptions

    Mainly the Red Hat portfolio. Every subscription includes an Invoke value component to help you integrate the technology.

    Line 3

    Products

    • Managed Serviceoperations
    • Rack VRvirtualization
    • FaceOpsintelligence

    Managed Service

    Invoke specialists run your estate from FaceOps.

    It's the same console our team uses. You keep approval of every action and see the value delivered.

    • You approve every action
    • Same console as our team
    • Value reported by area

    FAQ

    What people usually ask before starting.

    If your question isn't here, write to us and a specialist will answer.

    Another question?[email protected]
    Does FaceOps access my servers directly?

    No. FaceOps decides and records, but every run goes through the automation engine with an approved ticket. Credentials live in a vault and FaceOps never sees them.

    Where is it installed?

    Always in your infrastructure: the console in the DMZ and the automation engine in your internal network. No data about your estate sits on external servers.

    What do I need to get started?

    For the Demo, nothing: you sign in from the browser. For the PoC, space in your DMZ, SSH or WinRM connectivity to the machines in scope and the credentials registered in the vault. Invoke specialists define the details with you.

    Demo or proof of concept?

    The Demo lets you explore the console on a test scenario in Invoke's environment, with nothing to install and limited validity. The PoC validates FaceOps with your machines, integrations and policies, with hands-on support.

    Which systems does it support?

    Linux, with RHEL as the reference, over SSH; Windows Server over WinRM; and OpenShift through the cluster API. Plus networks, storage, hypervisors, clouds and databases, depending on the actions in the catalog.

    Do I need to install agents?

    No. Inventory and metrics are collected agentlessly. The agent is optional and FaceOps works the same without it.

    Does it replace Ansible?

    No, it complements it. Ansible remains the engine that executes. FaceOps adds the layer that decides, approves, records and measures.

    Next step

    Put an intelligence layer on top of your automation.

    Tell us the size of your estate and what you want to govern first. We'll propose a demo or a proof of concept.