Architecture
AWS, Azure, and Google Cloud architecture
Landing zones with accounts, networking, identity, and guardrails, designed for your security requirements and built as code.
Solutions · Cloud
Cloud and Modernization
Silex designs hybrid and public cloud environments and moves applications onto containers when that lowers cost or improves delivery. We assess each workload, build the landing zones as code, migrate in planned waves, and stay to operate the result with your team.
What we deliver
- AWS, Azure, and Google Cloud architecture
- Migration and disaster recovery
- Containers on Red Hat OpenShift
- Cost optimization
Workload placement
Each workload goes where it runs best.
Silex does not move everything to the cloud. We assess each workload on cost, performance, dependencies, and how your team will operate it, and then recommend where it should run.
Your data center
ApplicationsCustom and packaged
DatabasesTransactional and analytic
File sharesUser and application data
Virtual machinesHypervisor clusters
Silex assesses each workload
RetainKeep it in your data center when that costs less or performs better.
RehostMove it as it is to cloud virtual machines.
ReplatformMove it to containers on Red Hat OpenShift.
RefactorRebuild it on cloud services when the gain justifies the work.
RetireDecommission it when nothing depends on it.
Where it runs
Amazon Web ServicesLanding zones, accounts, and guardrails built as code
Microsoft AzureSubscriptions, networking, and identity built as code
Google CloudProjects, networking, and identity built as code
Red Hat OpenShiftContainers and virtual machines on one platform, on premises or in the cloud
Cost optimization loop
TagMeasureRightsizeReserve
The loop repeats after migration, so spend follows actual use.
Primary site
Your data center or cloud region
Disaster recovery
A second cloud region
What we deliver
Architecture, migration, platforms, and cost.
Migration
Migration and disaster recovery
Workloads moved in planned waves, with replication and tested failover to a second region or from your data center.
Platforms
Containers and application platforms
Applications moved to Red Hat OpenShift and Kubernetes when containers lower cost or improve delivery.
Cost
Cost optimization
Tagging, rightsizing, and reserved capacity, with cost reviews that continue after migration.
Every environment is defined as code. Silex builds landing zones with Terraform and deploys applications with GitOps through Argo CD, so each change is reviewed, tested, and repeatable.
Automation and Platform EngineeringHow we migrate
From assessment to an optimized environment.
- 01
Assess
Silex inventories applications, dependencies, and costs, and recommends a destination for each workload.
- 02
Plan
Landing zones, networking, identity, and security controls are built as code before any workload moves, and each cutover has a rollback plan.
- 03
Migrate
Workloads move in waves ordered by dependency and risk, starting with the least critical.
- 04
Validate
Each wave is tested for function, performance, and failover before the source systems are retired.
- 05
Operate
Forward Deployed Engineers run the environment, hold monthly service reviews that cover cost and security, and transfer ownership on your schedule.
Disaster recovery in the cloud
Disaster recovery and cyber recovery solve different problems.
Disaster recovery
Disaster recovery restores service after an outage, such as a failed data center or cloud region. It assumes the replicated data is clean, so the goal is to fail over quickly to a second location.
Cyber recovery
Cyber recovery assumes an attacker reached your data. Recovered systems are scanned, cleaned, and validated in an isolated recovery environment before they return to service.
Platforms
What we build with.
Select Tier Services Partner
Microsoft Azure
Premier Partner
HashiCorp Terraform
Amazon Web Services · Microsoft Azure · Google Cloud · Red Hat OpenShift · OpenShift Virtualization · Kubernetes · Terraform · Ansible Automation Platform · Argo CD · Zerto for replication
Questions buyers ask
Questions
Should everything move to the cloud?
No. Silex assesses each workload and recommends where it runs best. Some workloads stay in your data center, some move to AWS, Azure, or Google Cloud as they are, some move to containers, and some are retired.
How do you control cloud cost?
Silex tags every resource by owner and application, measures spend against those tags, rightsizes resources that run below their allocation, and buys reserved capacity for steady workloads. The review continues after migration.
Should we use containers or virtual machines?
Containers fit applications that release often or scale with demand, and Red Hat OpenShift runs them the same way on premises and in the cloud. Applications that change rarely can stay on virtual machines. Silex recommends one or the other for each application.
How does disaster recovery work in the cloud?
Silex replicates critical workloads to a second cloud region, or from your data center to the cloud, with Zerto or native cloud services, and tests failover on a schedule. For recovery after ransomware, Silex designs isolated recovery environments.
Do you operate the environment after migration?
Yes. Forward Deployed Engineers can run the environment with your team, hold monthly service reviews that cover cost and security, and move operational ownership to your team on your schedule.
Next step
Talk to a cloud engineer.
Tell us which workloads you are considering, and we will recommend where each one should run and how to move it.