Skip to Content
MTD Cloud Docs — Kubernetes-native platform services (Clusters, Serverless, Data Stores, Observability, Confidential Computing).
DocsIntroduction

Introduction

Welcome to the documentation for MTD Cloud — a cloud platform foundation delivered as a service.

MTD Cloud is built for teams that want the speed of modern cloud-native engineering without the overhead of assembling every building block from scratch. It combines platform capabilities (infrastructure patterns, automation, and operations) into a coherent experience, so you can go from idea → environment → production with confidence.

What you get with MTD Cloud

MTD Cloud focuses on the essentials required to run serious workloads:

  • A platform-first approach: standardized building blocks that reduce complexity and keep delivery predictable.
  • Operational readiness: patterns designed for reliability, security, and day-2 operations, not only “hello world” deployments.
  • Developer enablement: self-service workflows and automation that help teams ship faster and safer.
  • Consultancy-backed delivery: MTD Technology experts can support architecture, migration, implementation, and ongoing optimization.

Who this documentation is for

This documentation is intended for:

  • Developers deploying applications and using platform services
  • Platform / DevOps engineers operating environments, automation, and observability
  • Architects and tech leads designing target architectures and delivery standards
  • Security & compliance stakeholders validating controls and operational processes

How to use the docs

Use this documentation to:

  1. Understand the platform concepts and the “golden path”
  2. Set up environments and integrate your workflows
  3. Deploy services using recommended patterns
  4. Operate and troubleshoot production workloads

If you’re new here, start with Getting Started, then follow the guides by capability (compute, serverless, data stores, observability, security, and automation).

Documentation principles

  • Clarity over complexity — opinionated defaults, explained decisions
  • Repeatability — everything should be automatable and consistent across environments
  • Outcome-based operations — measure what matters (reliability, cost, performance, delivery speed)
  • Security by design — least privilege, auditability, and secure-by-default patterns
Get Started