Infrastructure Services
Network, security, voice, video and data infrastructure, designed, deployed and managed.
Cloud & Platform Engineering
We design, build and run Kubernetes platforms on upstream, unforked cloud native open source, on AWS, Azure, Google Cloud or your own data centre. Each platform is delivered through GitOps and hardened to your security and policy requirements. Through k8s.ng, our sub-brand, we offer two things: an internal developer platform (IDP) that gives your engineers golden paths, self-service environments and platform APIs, and enterprise support for the cloud native projects that run underneath it.
Scope
What we deliver
- Platform architecture and design for Kubernetes on AWS, Azure, Google Cloud, on-premises or a hybrid of them.
- Cluster builds on Talos Linux, an immutable operating system managed through an API rather than by logging in to servers.
- GitOps delivery with Flux, so every change to the platform and its workloads is versioned, reviewed and reversible.
- Policy as code with Kyverno and central identity with FreeIPA, aligned to your security and audit requirements.
- Stateful services on the platform: Rook-Ceph storage, Kafka streaming and PostgreSQL offered as a database service.
- An internal developer platform through k8s.ng, with golden paths for building and shipping services, self-service environments and platform APIs your engineers can use without raising a ticket.
- Migration of existing workloads onto the platform, followed by lifecycle management, upgrades and security patching.
- Enterprise support through k8s.ng for the cloud native projects you run, covering security hardening, integration and lifecycle management.
Outcomes
What changes for you
A Kubernetes platform built entirely on upstream projects, with nothing proprietary to migrate off later.
Engineers who can create environments and ship services themselves, on paths your platform team has already secured.
Infrastructure changes that are versioned, reviewed and auditable through Git, with security and policy controls enforced by the platform itself.
One accountable partner for the platform and its support, from the operating system to the database.
Supported stack
Upstream open source, integrated as one platform
These eight projects are a subset of what we support, shown to illustrate the range rather than to list everything. Each one is upstream and unforked, with no proprietary abstractions, so you get enterprise accountability without vendor lock-in. If you run something that is not listed, ask us whether we can support it.
| Layer | Project | Role |
|---|---|---|
| Orchestration | Kubernetes | Runs your containerized applications and keeps them in the state you have asked for, restarting and rescheduling them when something fails. |
| Operating system | Talos Linux | A minimal, immutable operating system for the servers underneath Kubernetes, managed through an API rather than by logging in to each machine. |
| GitOps and delivery | Flux | Keeps every cluster in step with configuration stored in Git, so each change is versioned, reviewed and easy to roll back. |
| Policy enforcement | Kyverno | Applies your security and configuration rules as code, checking workloads before they are allowed to run on the platform. |
| Identity | FreeIPA | Provides central identity, sign-in and access control for the people and services that use the platform. |
| Storage | Rook-Ceph | Delivers replicated block, file and object storage inside the cluster, with a hardened configuration. |
| Streaming | Kafka | Moves events and data between systems as they happen, in durable, ordered streams that other applications can read. |
| Database | PostgreSQL | Offered as a database service on the platform, so teams can provision reliable relational databases without building them by hand. |
Questions
Frequently asked
Do you build on public cloud or in our own data centre?
Both. We build on AWS, Azure and Google Cloud, on your own hardware in your data centre, or as a hybrid. Because the platform is built on upstream Kubernetes, it behaves the same way wherever it runs.
Why upstream open source rather than a commercial Kubernetes distribution?
The projects we build platforms on are upstream and unforked, with no proprietary resource types and no mandatory vendor operating system. Your workloads stay portable, and you can change support arrangements without rebuilding the platform.
Can you take over a cluster we already run?
Yes. We start by reviewing the existing cluster, its delivery pipeline and its security posture, then agree with you what moves onto the platform, what we take under support and in what order.
What is the internal developer platform?
It is Cloud Remark’s IDP, offered through k8s.ng. It sits on top of Kubernetes and gives your engineers golden paths for building and shipping services, self-service environments and platform APIs. Your platform team sets the guardrails once, and developers work within them without waiting on tickets.
How is the platform supported after it goes live?
Through k8s.ng, our sub-brand for cloud native enterprise support. It covers security hardening, integration and lifecycle management for the cloud native projects we support, which include the eight listed on this page and others from the CNCF landscape. Wider operational support is available through our Support & Aftercare service. The scope of cover is agreed with you as part of the engagement.
How does an engagement start?
With a conversation with one of our engineers about your current estate and what the platform needs to do. From there we propose an architecture and a delivery plan you can review before any build work begins.
01 / Cloud & Infrastructure
Related services
Support & Aftercare
Managed support, lifecycle management and outsourcing that keep systems healthy after go-live.