AI transformation · Automation
Automation and Platform Engineering
Automation is how AI acts safely. Silex designs and operates Ansible Automation Platform, Terraform, and OpenShift GitOps, so every change runs through tested, approved code, whether a person, a pipeline, or an AI agent requests it.
Kept in Git
- aap/job_templates
- eda/rulebooks
- aap/execution_environments
- terraform/modules
- argocd/applications
- opa/policies
How change works
One governed path for every change.
People, pipelines, events, and AI agents all request changes. In a Silex design, every request takes the same route: a policy check, an approved job template, and a verified, recorded result.
Who requests the change
The path every request takes
The agent lane
Agents never log in to hosts and never hold secrets. An agent can request only a job template that already exists, and its request passes the same policy check and change approval as a person's.
The automation is code too
Job templates, rulebooks, Terraform modules, OPA policies, and Argo CD applications live in Git and deploy through CI/CD. Every change to the automation itself is reviewed and tested before it runs.
What we deliver
The platform, the code, and the controls.
Automation platform
- Ansible Automation Platform architecture and operationsSilex designs, deploys, and operates Ansible Automation Platform, including execution environments and Event-Driven Ansible.
- ITSM self-serviceTeams request approved automation from ServiceNow or Jira, and the ticket records the result.
- Network automationConfiguration backup, templating, compliance checks, and change workflows run as code across your network platforms.
Infrastructure as code and GitOps
- TerraformSilex writes Terraform modules for cloud and on-premises resources that your teams can reuse.
- OpenShift and GitOpsArgo CD keeps Red Hat OpenShift clusters and applications in the state defined in Git.
- CI/CD for automation contentPlaybooks, roles, and collections are linted, tested, and released through pipelines before they reach production.
Governance and compliance
- Policy as codeOpen Policy Agent enforces change, access, and compliance rules automatically.
- Dynamic credentialsCyberArk Conjur supplies credentials when a job runs, so automation content never stores passwords.
- Hardening and compliance scanningCIS benchmarks are applied as code, and OpenSCAP scans confirm that systems stay compliant.
Experience
The job templates, collections, and pipelines that agents use in a Silex design are ones our engineers build and maintain. Agentic operations starts from an automation program that already runs every day.
Workshops
Hands-on labs for your team.
Silex engineers lead every workshop. Each session runs one track, chosen by your team.
Ansible Automation Platform
- Linux AutomationThis track covers provisioning, patching with validation, CIS hardening, and OpenSCAP scanning on Red Hat Enterprise Linux.
- Network AutomationThis track covers configuration backup and templating, compliance checks, and change workflows with certified Ansible collections.
- Windows AutomationThis track covers Windows Server patching, configuration, Active Directory tasks, and application deployment.
Red Hat OpenShift
- OpenShift for DevelopersThis track covers building and deploying applications, CI/CD pipelines, and GitOps with Argo CD.
- OpenShift for AdministratorsThis track covers cluster architecture, access control, networking, storage, upgrades, and policy as code.
To request a workshop, email sales@silexdata.com.
How we engage
From assessment to a platform your team runs.
- 01
Assess
An Automation Maturity Assessment reviews your automation practices, credentials, CI/CD, and governance.
- 02
Design
A blueprint covers platform topology, execution environments, credentials, Git structure, and policy, reviewed with your platform and security teams.
- 03
Build
Silex deploys the platform as code, builds the first job templates and pipelines, tests them, and writes the runbooks.
- 04
Operate
Forward Deployed Engineers run the platform, add new automation, and hold monthly service reviews and quarterly governance reviews.
- 05
Transfer
Structured knowledge transfer and hands-on workshops move ownership of the platform and its content to your team.
Platforms
What we build with.
Premier Partner
HashiCorp Terraform
Red Hat Ansible Automation Platform · Event-Driven Ansible · Red Hat OpenShift · Argo CD · Terraform · Open Policy Agent · CyberArk Conjur · OpenSCAP · ServiceNow · Jira
Questions buyers ask
Questions
Why does automation come before AI agents?
An agent that changes production needs a safe way to act. In a Silex design, agents request approved Ansible job templates instead of running commands on hosts, so the automation library sets the limits of what an agent can do.
We already have Ansible playbooks and scripts. Is that enough?
Playbooks are a start. A platform adds role-based access, credentials from a secrets manager, content in Git with testing through CI/CD, execution environments, and a record of every run. The Automation Maturity Assessment shows which of these you have and what to add first.
Can Silex operate Ansible Automation Platform for us?
Yes. Forward Deployed Engineers can run the platform, maintain the content, and onboard new workflows, then move operational ownership to your team on your schedule.
How are credentials handled?
Automation content never contains passwords. Credentials come from a secrets manager such as CyberArk Conjur when a job runs, and AI agents never hold secrets at all.
Do you automate network devices?
Yes. Silex automates configuration backup, templating, compliance checks, and change workflows across network platforms with certified Ansible collections. The Network Automation workshop track covers the same work.
Next step
Request an Automation Maturity Assessment.
We review your automation practices, credentials, CI/CD, and governance, and recommend what to change first.