We build your AWS platform, or take on the one you have. Then we operate it.

Whether you already run AWS, need a new platform or are planning significant change, our Cloud Platform Engineers set up the platform and its operating model. Then we take ongoing responsibility for the scope we agree with you.

MRI Software
Entersekt
Kazang
Altron Health Tech
Velocity Trade
Habari Media
FluentyLisaProp
  • AWS Advanced Tier Services Partner badge

    AWS Advanced Tier Services Partner

  • AWS ECS Delivery Partner badge

    AWS ECS Delivery Partner

  • AWS Public Sector Partner badge

    AWS Public Sector Partner

  • AWS Well-Architected Partner badge

    AWS Well-Architected Partner

Different starting points. One managed AWS platform.

We can take on what already runs, build what does not yet exist, or change the platform before moving it into managed operations.

EXISTING AWS PLATFORM

Take on what already runs.

Understand the estate, agree the responsibility boundary, address priority gaps and move the agreed scope into managed operations.

NEW AWS PLATFORM

Build with operations designed in.

Design and build the AWS platform around the workload and its operating requirements, then take responsibility for the agreed scope.

MIGRATION OR MODERNISATION

Change what needs changing first.

Migrate, modernise or remediate what cannot support the required target state, then move the resulting platform into managed operations.

Platform work we've delivered on AWS.

Before a platform moves into managed operations, it has to be built, migrated or proven. This is that work, delivered for teams like yours.

Abstract fintech AWS ECS migration and deployment operations environment

Fintech workloads moved from Azure to Amazon ECS

A phased cross-cloud migration that simplified deployments and mapped compliance controls to their AWS equivalents.

Abstract property technology Amazon EKS modernisation and observability environment

A property platform rebuilt on Amazon EKS

Legacy hosting moved toward managed Kubernetes on Amazon EKS, with repeatable releases across environments.

Abstract AWS primary and secondary environments connected within a resilience architecture assessed for Habari

Habari's AWS resilience architecture, validated

A non-production proof of concept that tested the design and defined backup and recovery testing as the next step.

Managed Platform takes work like this into ongoing operations, with the responsibility boundary agreed first.

One AWS platform. Seven connected responsibilities.

Managed Platform brings the AWS responsibilities that need ongoing ownership into one operating model.

BUILD

Engineer the platform and the changes it needs.

OPERATE

Run the agreed AWS platform scope and recurring routines.

SECURE

Maintain agreed identity, access and platform security controls.

PROTECT

Manage backup, recovery and resilience responsibilities.

OBSERVE

Keep the platform visible through the telemetry that matters.

OPTIMISE

Improve cost, capacity, configuration and efficiency.

ASSURE

Validate that important controls and recovery behaviours still work.

You keep ownership of your business and applications. We take responsibility for the AWS platform scope we agree.

The responsibility boundary is defined before the platform moves into managed operations.

A platform that is easier to run, govern and improve.

CLEAR OWNERSHIP

Know where your team's responsibility ends and ours begins.

LESS OPERATIONAL LOAD

Keep application teams focused on applications, not recurring AWS platform work.

BETTER CONTROL

Make security, recovery, observability and cost part of normal operations.

CONTINUOUS IMPROVEMENT

Keep engineering the platform as workloads and requirements change.

Engineered in South Africa.

Here is what working with a South African team means in practice.

Where your data lives
We run your platform in the AWS Region that suits your workload and customers, including AWS Africa (Cape Town) when your data needs to stay in South Africa.
Data protection
We map platform controls to POPIA, and to GDPR or other data-protection laws in the countries where you operate, and give you the evidence your privacy and audit teams ask for.
Who you talk to
Our Cloud Platform Engineers are based in Cape Town and Johannesburg and work on South African time (SAST). Support hours and response times are agreed with you in your service agreement.

From where you are to managed AWS operations.

  1. Stage 01

    Understand the platform and the required outcome.

    Review the current state, workload requirements, dependencies, operating constraints and responsibilities.

  2. Stage 02

    Build, take on or change what is required.

    Stabilise, remediate, migrate, modernise or build what the target platform requires.

  3. Stage 03

    Agree responsibility and establish the operating model.

    Define the managed scope, controls, support boundaries, escalation paths and recurring platform routines.

  4. Stage 04

    Run the platform and keep improving it.

    Operate the agreed AWS platform scope and continue platform engineering as requirements change.

Platform work moves into an ongoing operating model.

Choose how much platform responsibility we take on.

Not every AWS environment needs the same level of operating responsibility. The service depth is shaped around the platform, workload criticality and the responsibilities you want KineticSkunk to own.

Basic

Essential visibility and platform operations.

AWS visibility, platform hygiene and defined support ownership.

Pro

A stronger operating rhythm.

Adds deeper release, reporting, cost and recurring platform-management responsibilities.

Business

Managed production operations.

Adds production governance, backup and recovery, access discipline and operational evidence.

Enterprise

Deeper control for critical environments.

Adds greater resilience, escalation, stakeholder reporting and continuous optimisation.

Compare service levels

What changes as operating depth increases?

The difference is not simply the number of activities included. It is the amount of recurring platform responsibility KineticSkunk takes on.

Operations

CapabilityBasicProBusinessEnterprise
Monitoring and alert awarenessIncludedIncludedIncludedIncluded
Operational hygieneIncludedIncludedIncludedIncluded
Release supportAdd-onIncludedIncludedIncluded
Operational reportingLightIncludedIncludedExecutive-ready

Security & Recovery

CapabilityBasicProBusinessEnterprise
Access review supportAdd-onLightIncludedAdvanced
Backup posture reviewIncludedIncludedIncludedIncluded
Backup policy managementAdd-onAdd-onIncludedIncluded
Restore testingAdd-onAdd-onScheduledScheduled + evidence
Recovery evidenceAdd-onAdd-onIncludedIncluded

Management & Assurance

CapabilityBasicProBusinessEnterprise
Incident escalationBasicStandardPriorityCritical workload
Cost optimisationLightIncludedIncludedContinuous
Stakeholder reportingNot includedLightIncludedIncluded
Resilience testingAdd-onAdd-onRecommended add-onIncluded or packaged

Support coverage and response targets

Coverage windows, incident classifications, escalation contacts and response targets are agreed during onboarding and documented in the managed service agreement.

Some needs start as a project.

Migration, recovery, cost, security or architecture work can start as focused engineering. Where ongoing ownership makes sense, the resulting AWS platform scope can move into Managed Platform.

Built for ongoing responsibility, not a hand-off.

We combine platform engineering with managed operations, so the AWS platform can move from engineering work into a defined operating relationship.

Questions before you get in touch.

We already have an engineering team. Is this for us?

Yes. You keep ownership of your business and applications. We take responsibility for the AWS platform scope we agree, so your team can focus on the applications.

Who owns our AWS account?

You keep ownership and administrative control of your AWS Organisation, accounts and data. How AWS usage is billed is agreed separately.

What if we decide to move on?

We hand over documentation, access and runbooks for the platform scope we operated, with 60 days' notice.

Can we start smaller than a managed service?

Yes. Migration, recovery, cost, security or architecture work can start as a focused engagement, such as an AWS Well-Architected Review.

Start with the AWS platform you have, or the one you need.

Show us the environment or the requirements. We'll help define what needs to change, where responsibility sits and what should move into managed operations.

After you get in touch

What happens when you get in touch.

  1. 01

    We reply

    A Cloud Platform Engineer replies within one business day.

  2. 02

    A short call

    A 30-minute call about your platform, what you need and where it runs. No obligation.

  3. 03

    Discovery

    We review your platform, or your plans for a new one, so the proposal fits what you actually run. Discovery is free if you go ahead with Managed Platform. If you don't, it is charged at a fee we agree with you in writing before it starts.

  4. 04

    A written proposal

    Scope, responsibility boundary, service level and fee, in writing.

Who you'll speak to.

Donovan Mulder, CEO of KineticSkunk

Donovan Mulder

CEO

Donovan reads every enquiry from this page and will make sure the right Cloud Platform Engineer joins your first call.