Infrastructure

User docs for platform choices, operated infrastructure boundaries, onboarding, changes, and support.

Infrastructure

Use this section to choose an infrastructure operating model with clear boundaries: what Assistance operates, what the customer owns, how onboarding works, and how support or change requests are handled.

Platform choices#

Assistance infrastructure documentation now uses three primary platform choices:

Choice	Use it when	Ownership focus
Managed Kubernetes	Containerized services need GitOps, ingress, observability, policy, and day-2 platform operations.	Assistance operates the cluster/platform boundary; the customer owns workloads, releases, and business data.
Managed Proxmox	VM/LXC workloads need Assistance-operated virtualization on physical servers / dedicated physical hardware, including evaluation, prerequisites, architecture, migration, backups, monitoring, security, and day-2 support docs.	Assistance operates Proxmox and the agreed host boundary; the customer owns applications, access approvals, and business policy.
Local Private Cloud	A private platform must run on physical servers / dedicated physical hardware in a customer-approved site, colocation, or private environment.	Assistance operates the scoped platform layer; the customer owns facility/provider decisions, data policy, and application behavior.

Guides#

Managed Kubernetes

Managed Proxmox

Local Private Cloud

Supporting Infrastructure Add-ons

Local Development

Landing Zones and Infrastructure as Code

Kubernetes operating model

Docker

Next steps#

Pick the platform choice that best matches workload shape, hosting constraints, and ownership needs.
Use the related guide to confirm what Assistance operates and what your team owns.
Open an assessment with current architecture, desired outcome, data boundaries, support expectations, and deadline.