Cloud advisory and assessment
Understand the estate before choosing a platform.
Onyx evaluates the environment you already run - applications, infrastructure, dependencies, cost and risk - before recommending a platform or a migration strategy. The assessment is the deliverable: a documented picture of what exists, what it costs, what it depends on, and what should move first.
The output is a migration roadmap with wave planning, workload placement recommendations, and the commercial case that supports the decision.
- Cloud readiness assessments
- Application and infrastructure discovery
- Dependency mapping
- Migration business cases
- Total cost of ownership analysis
- Workload placement recommendations
- Security and compliance gap assessments
- Migration roadmaps and wave planning
Cloud foundation and engineering
A platform that can be governed, not just provisioned.
Before workloads move, the destination needs structure: account and subscription boundaries, identity, network connectivity, logging, and a recovery position. Onyx designs and implements that foundation on AWS and Azure so later migration waves land somewhere governed rather than somewhere improvised.
Foundations are delivered as infrastructure as code with the pipelines to change them safely.
- AWS and Azure cloud architecture
- Landing-zone design and implementation
- Account and subscription structures
- Identity and access foundations
- Network and hybrid connectivity
- Security, logging and audit foundations
- Backup and disaster-recovery planning
- Infrastructure as code
- CI/CD and platform automation
On-premises-to-cloud migration
Move the workloads, keep the operation running.
Migration is the core of this division. Workloads are assessed individually and assigned an appropriate strategy - rehost, replatform, refactor, retain or retire - so effort goes where it changes the outcome and nothing moves without a reason.
Delivery runs in waves, beginning with a pilot migration that proves the pattern before scale. Cutover and rollback plans are designed around each workload's operational requirements, and every wave closes with post-migration validation against agreed criteria.
- Server and virtual-machine migration
- Application migration
- Database migration
- File and storage migration
- Identity and directory migration
- VMware and data-centre migration
- Hybrid-cloud implementation
- Pilot migrations
- Migration waves
- Cutover planning and execution
- Post-migration validation
Onyx does not promise zero downtime. Each cutover plan states the expected impact, the validation steps, and the rollback position before the wave begins.
Application modernization
Modernize where it earns its cost.
Not every application should be rewritten. Onyx separates the work that reduces operating cost and risk from the work that simply changes technology, and modernizes selectively against that line.
Migration and modernization can be delivered as separate phases when that reduces project risk - move first, modernize once the workload is stable and measurable in its new environment.
- Application replatforming
- Containerization
- Kubernetes adoption
- Database modernization
- API modernization
- CI/CD implementation
- Infrastructure automation
- Serverless adoption
- Selective application refactoring
Observability and reliability
Vendor-neutral visibility into how services actually behave.
Onyx approaches observability without a fixed platform answer. We assess the tooling already in place, identify the gaps between what is collected and what is needed to answer operational questions, and recommend an architecture that fits. When the current environment is the better base, we extend it.
Implementations favour open standards, with OpenTelemetry instrumentation for logs, metrics and distributed tracing, so telemetry stays portable across platforms.
- Observability assessments
- OpenTelemetry implementation
- Logs, metrics and distributed tracing
- Application and infrastructure monitoring
- Dashboards and alerting
- Service-level objectives
- Incident-management design
- Performance baselining
- Telemetry cost optimization
- Managed observability
Platform selection is a recommendation, not a precondition. An observability assessment does not require an immediate platform replacement.
Managed cloud services
Ongoing operation after the project ends.
Managed cloud services and managed observability are the division's recurring engagements. Onyx takes on the day-to-day administration of the platform and the telemetry estate - maintenance coordination, backup oversight, capacity and cost management, and support during incident investigation.
Each engagement is written down: what Onyx operates, what the customer retains, and how work is reported back.
- Cloud platform administration
- Observability platform administration
- Backup and recovery oversight
- Patch and maintenance coordination
- Capacity and performance management
- Cost and usage optimization
- Incident investigation support
- Operational reporting
- Architecture reviews
- Configuration and automation improvement
Support coverage, response targets and service responsibilities are defined for each managed-service engagement.
AI operations
AI applied to operational work, under human control.
AI is a capability inside the service portfolio, not the identity of the division. Onyx applies it where operational work is repetitive or where a human needs a faster route through evidence - correlating telemetry during an investigation, summarising change and cost signals, automating a documented runbook step.
Automation runs within defined controls, and an operator can see what was proposed, what acted, and why.
- AI-assisted incident investigation
- Operational workflow automation
- Cloud and telemetry analysis
- Responsible automation controls
- AI workload observability
- AI cost and performance monitoring
