Research Coverage Map 2026 06 26

Assistance service documentation coverage map — 2026-06-26

Purpose: audit Assistance's current public service documentation and map it against buyer questions, portfolio gaps, and authoritative market/service references. This is a research artifact only; it does not change navigation, routes, pricing, or service content.

Repository evidence reviewed#

Public docs service catalogue: apps/docs/content/guides/services/index.mdx.
Docs-backed service pages under apps/docs/content/guides/services/.
Managed infrastructure pages under apps/docs/content/guides/infrastructure/managed-*/index.mdx.
Public guide hubs under apps/docs/content/guides/*/index.mdx.
Prior internal research artifacts: docs/services/proposition-inventory-2026-06-26.md, docs/services/opsfleet-portfolio-extension.md, and docs/services/xebia-ai-content-research.md.

Executive summary#

Assistance already has a broad service inventory and a useful docs-backed route model. The strongest coverage is in DevOps/SRE, Kubernetes, cloud infrastructure, CI/CD, managed data stores, and emerging AI-agent infrastructure. The biggest documentation gaps are not missing capability names; they are buyer-journey gaps: clearer umbrella pages for platform engineering, security/compliance, AI/data operations, migrations, documentation/developer experience, training, SaaS/admin tooling, and self-hosting. Several pages exist but need consolidation or cross-linking because commercial entry points, docs guide URLs, and marketing service routes describe the same offers differently.

Coverage map by offering area#

Offering area	Current Assistance evidence	Target reader questions to answer	Coverage assessment	Recommended new or revised pages
Cloud and platform engineering	`cloud-infrastructure`, `cloud-management`, `cloud-account-management`, `managed-kubernetes`, `kubernetes`, `kubernetes-support`, `gitops`, `paas-solution`, `solution-for-paas`, infrastructure managed add-ons	Which platform should we build or modernize? What is the landing-zone, IaC, network, Kubernetes, GitOps, and operating model? Who owns day-2 operations?	Strong inventory, fragmented story. Platform engineering is implied across cloud, Kubernetes, GitOps, and PaaS pages but lacks one buyer-friendly umbrella.	Add `platform-engineering` or revise `cloud-infrastructure` as the umbrella. Add comparison sections: cloud foundation vs managed Kubernetes vs PaaS vs GitOps project.
DevOps and delivery engineering	`devops-as-a-service`, `cicd-audit`, `managed-runners`, runner guide hub, `gitops`, pricing feature pages	How do we ship faster without increasing change failure? Which pipeline, runner, environment, and release controls are included?	Strong. Current docs answer retained support, audit, runners, and GitOps. Gap is tying DORA/developer experience outcomes to service selection.	Add a `developer-productivity-and-delivery` page or expand `devops-as-a-service` with DORA, platform-team interfaces, internal developer portal/backstage-style needs, and DX measurement.
SRE, observability, incident, and resilience	`sre-as-a-service`, `emergency`, `disaster-recovery-planning`, `managed-prometheus`, monitoring guide pages, `agent-observability`	How do we reduce incidents? What is response scope? What proof do we get? How do RTO/RPO, SLOs, alerts, runbooks, and DR tests fit together?	Good but split across response, ongoing SRE, DR, and Prometheus. Disaster recovery is present but not always routed consistently from marketing.	Add an `operational-resilience` hub linking SRE, emergency, DR, managed Prometheus, backup/restore evidence, and incident review artifacts.
Security, DevSecOps, and compliance	`devsecops-as-a-service`, `security-audit`, `security-compliance`, `managed-bitwarden`, security guide pages, `managed-certificates`, `managed-dns`	Are you auditing or implementing fixes? Which controls are covered? How do IAM, secrets, supply chain, Kubernetes, compliance evidence, and incident response fit?	Moderate. Service names exist, but security-compliance is broad and overlaps with DevSecOps/security audit. Compliance evidence is mentioned but not organized by framework/control family.	Add a `security-and-compliance-services` hub. Clarify audit vs retained implementation vs managed tooling. Add control-mapping sections for SOC 2/ISO 27001-style evidence without over-claiming certification services.
AI engineering and agent platforms	`ai-as-a-service`, `generative-ai-engineering`, `ai-agent-infrastructure`, `agent-orchestration`, `agent-observability`, `managed-mcp-servers`	How do we move from prototype to production? What is covered: RAG, assistants, agents, gateways, evals, LLMOps, MCP, governance, observability, cost?	Strong and growing. Assistance has agent infrastructure depth; gaps are LLMOps/MLOps and AI governance as explicit buyer journeys.	Add `llmops-platform`, `mlops-platform`, and `ai-governance` pages as recommended in `xebia-ai-content-research.md`. Keep vertical AI use cases examples, not broad guarantees.
Data platforms, analytics, and streaming	`data-as-a-service`, `managed-postgresql`, `managed-mysql`, `managed-mongodb`, `managed-redis`, `managed-kafka`, `managed-opensearch`, database and queues guide hubs	What data foundation do we need for analytics or AI? Who owns pipelines, freshness, governance, streaming, search, and handoff?	Moderate. Managed data components are clear; end-to-end data-platform engineering and analytics governance are less explicit.	Add `data-platform-engineering` page or revise `data-as-a-service` with lakehouse/warehouse, pipeline, lineage, freshness, semantic/metrics ownership, and AI-readiness sections.
Training and academy	`devops-trainings`, academy app, blog/training content, events	Can you train our team? What curriculum, format, prerequisites, hands-on labs, and post-training support are available?	Thin as a commercial docs journey. `devops-trainings` exists, but training/academy is not connected to implementation services or role-based enablement.	Add `training-and-enablement` hub linking DevOps, Kubernetes, CI/CD, cloud, security, AI/data, and academy cohorts. Include team-readiness and enablement-after-project sections.
Documentation and developer experience	docs app, `community` guide pages, `runners`, `reference/cli-install`, local development guides, service pages' proof/handoff language	How will our developers learn the platform? Do you produce runbooks, diagrams, onboarding docs, API docs, internal portal content, and support handoff?	Gap. The repository demonstrates docs capability but no explicit docs/DX service line.	Add `documentation-and-developer-experience` page focused on runbooks, onboarding, platform docs, internal developer portals, docs-as-code, service catalogues, and release/change documentation.
SaaS, PaaS, admin, and productivity tooling	`solution-for-saas`, `solution-for-paas`, `paas-solution`, `managed-saleor`, `managed-git-server`, `google-apps-management`, `office365-management`, `sovereign-productivity-suite`, manager/studio apps	Can you operate our admin platform, SaaS foundation, commerce stack, productivity suite, or delivery tooling? What is product work vs operations?	Broad but uneven. Several pages exist; some feel like stand-alone product/service ideas rather than an integrated SaaS/admin tooling offer.	Add `saas-and-admin-platform-operations` hub. Clarify SaaS platform strategy, Managed Git Server options, Saleor/productivity suites, Supabase/admin tooling, tenancy, billing, auth, compliance, and support boundaries.
Self-hosting, sovereignty, and migrations	`self-hosting`, `sovereign-cloud`, `sovereign-productivity-suite`, `managed-bitwarden`, `managed-git-server`, `vmware-migration`, `cloud-migration`, `kubernetes-migration`, managed infrastructure pages	Should we self-host, migrate from SaaS/VMware/on-prem, or use sovereign/private infrastructure? What risks, operating costs, and compliance tradeoffs apply?	Good raw material, but no single decision framework. Migration pages exist separately and sovereignty/self-hosting pages are not tied to TCO/operating responsibility.	Add `self-hosting-and-migration-strategy` hub. Include decision matrix for SaaS vs managed tenant vs self-hosted vs customer cloud, plus migration readiness checklist.
Cost, FinOps, and commercial planning	`cost-optimization`, `finops`, `cloud-account-management`, pricing pages, `aws-graviton-migration`	Where can we save money without reliability/security risk? How are savings measured and governed? Which plan fits?	Good but overlapping: cost optimization and FinOps both exist, while cloud account management includes cost hygiene.	Consolidate with a `finops-and-cost-optimization` landing page or cross-link the two pages. Add savings validation and ownership model guidance.

Current offering inventory by route family#

Family	Public docs/routes observed	Notes
Retained operations	`devops-as-a-service`, `sre-as-a-service`, `devsecops-as-a-service`, `ai-as-a-service`, `data-as-a-service`, `cloud-account-management`	Strongest commercial shape: retained capacity with onboarding, proof, and package language.
Audits and advisory	`infrastructure-audit`, `security-audit`, `cicd-audit`, `cost-optimization`, `technology-consulting`	Good entry point for unclear buyers. Needs explicit paths into implementation services.
Cloud/platform projects	`cloud-infrastructure`, `cloud-management`, `cloud-migration`, `managed-kubernetes`, `kubernetes`, `kubernetes-migration`, `kubernetes-support`, `gitops`, `paas-solution`, `solution-for-paas`	Inventory is broad; add selection guidance to reduce internal competition between similar pages.
Resilience and emergency	`emergency`, `disaster-recovery-planning`, `sre-as-a-service`, `managed-prometheus`	Present but should be grouped as resilience/readiness.
AI and agent systems	`generative-ai-engineering`, `ai-agent-infrastructure`, `agent-orchestration`, `agent-observability`, `managed-mcp-servers`, `ai-as-a-service`	Strong differentiated area. Add LLMOps/MLOps/governance if pursuing enterprise AI buyers.
Data and managed components	`managed-postgresql`, `managed-mysql`, `managed-mongodb`, `managed-redis`, `managed-kafka`, `managed-opensearch`, `managed-prometheus`, `data-as-a-service`	Managed components are well represented; data-platform architecture page would connect them.
Delivery and code platforms	`managed-runners`, `managed-git-server`, `managed-git-servers`, `managed-artifact-repos`, `managed-docker-registry`, runner docs	Good component coverage; DX/developer productivity narrative is the gap.
Security and productivity tooling	`managed-bitwarden`, `security-compliance`, `managed-certificates`, `managed-dns`, `google-apps-management`, `office365-management`, `sovereign-productivity-suite`	Needs clearer boundary between security service, compliance support, and managed business tooling.
SaaS/commercial platform services	`solution-for-saas`, `managed-saleor`, `aws-marketplace-onboarding`, `aws-graviton-migration`	Useful specialist offers; should remain scoped/on-request unless productized.
Self-hosting and sovereignty	`self-hosting`, `sovereign-cloud`, `sovereign-productivity-suite`, `vmware-migration`, managed infrastructure pages	Strong topic fit for Assistance; needs decision framework and TCO/ops responsibility language.
Training	`devops-trainings`, academy app/content	Commercial service path is present but underdeveloped.

Recommended page backlog#

Priority	Page	Purpose	Evidence basis
1	`platform-engineering`	Umbrella for cloud foundations, Kubernetes, GitOps, IaC, internal platforms, operating model, and day-2 ownership.	CNCF platform engineering maturity model; internal pages `cloud-infrastructure`, `managed-kubernetes`, `gitops`, `paas-solution`.
2	`operational-resilience`	Tie SRE, observability, incident response, DR, backup/restore tests, and emergency response into one buyer journey.	Google SRE practices, DORA reliability/change metrics, NIST contingency planning; internal `sre-as-a-service`, `emergency`, `disaster-recovery-planning`.
3	`security-and-compliance-services`	Clarify audit vs DevSecOps implementation vs compliance evidence vs managed security tooling.	NIST CSF 2.0, OWASP ASVS/SAMM, SLSA, CIS Benchmarks; internal `security-audit`, `devsecops-as-a-service`, `security-compliance`.
4	`llmops-platform`	Production operations for LLM apps: routing, evals, monitoring, deployment controls, cost, and access control.	Xebia AI research, NIST AI RMF, OWASP Top 10 for LLM Applications; internal AI agent pages.
5	`data-platform-engineering`	Connect managed databases/Kafka/OpenSearch to governed data products, analytics, lakehouse/warehouse, freshness, and AI readiness.	Xebia cloud/data research, DAMA/data governance concepts, Databricks/lakehouse and dbt analytics-engineering patterns; internal `data-as-a-service`.
6	`documentation-and-developer-experience`	Productize Assistance's docs/runbook/platform-handoff capability.	Google technical writing guidance, Diataxis documentation framework, Backstage/internal developer platform patterns; internal docs and service proof language.
7	`training-and-enablement`	Role-based enablement for DevOps, Kubernetes, cloud, security, AI/data, and post-project adoption.	CNCF training/certification ecosystem, Xebia AI upskilling research; internal `devops-trainings` and academy app.
8	`self-hosting-and-migration-strategy`	Decision framework for SaaS vs sovereign/self-hosted, VMware/cloud/Kubernetes migrations, and operating responsibility.	CNCF cloud-native guidance, NIST SP 800-34 contingency planning, VMware-to-Proxmox content already in repo; internal sovereignty/migration pages.
9	`saas-and-admin-platform-operations`	Group SaaS/PaaS foundations, admin tooling, commerce, productivity suites, marketplace onboarding, and Studio/manager capabilities.	Internal `solution-for-saas`, `solution-for-paas`, `managed-saleor`, productivity/admin pages.
10	`finops-and-cost-optimization`	Consolidate cost optimization, FinOps, cloud account management, Graviton migration, savings validation, and showback/ownership.	FinOps Foundation framework; internal `cost-optimization`, `finops`, `cloud-account-management`, `aws-graviton-migration`.

Umbrella overlap: cloud-infrastructure, cloud-management, platform, paas-solution, and solution-for-paas compete for platform-engineering intent.
Security overlap: security-audit, security-compliance, and devsecops-as-a-service need clearer buying boundaries.
AI taxonomy: Agent-specific pages are strong, but enterprise AI buyers expect LLMOps, MLOps, responsible AI/governance, and data foundations.
Data taxonomy: Managed databases are component pages; data-platform buyers need pipelines, freshness, lineage, governance, and analytics/AI readiness.
Docs/DX absence: Handoff/runbooks appear as deliverables in many pages, but there is no explicit documentation/developer-experience service.
Training under-positioned: Training exists but is not connected to academy, post-project adoption, or role-based enablement.
Self-hosting decision support: Sovereign cloud and managed self-hosted tools exist, but there is no decision matrix for when self-hosting is worth the operational burden.
Commercial clarity: Specialist pages such as AWS Marketplace onboarding, Graviton migration, managed productivity suites, and managed commerce should remain on-request unless pricing/operations are productized.

Source references#

Internal sources#

apps/docs/content/guides/services/index.mdx — current service catalogue and buyer scenarios.
apps/docs/content/guides/services/devops-as-a-service/index.mdx — retained DevOps scope and proof artifacts.
apps/docs/content/guides/services/sre-as-a-service/index.mdx — reliability/SRE retained scope.
apps/docs/content/guides/services/devsecops-as-a-service/index.mdx and apps/docs/content/guides/services/security-audit/index.mdx — security implementation and audit scope.
apps/docs/content/guides/services/ai-as-a-service/index.mdx, generative-ai-engineering, ai-agent-infrastructure, agent-orchestration, agent-observability, managed-mcp-servers — AI/agent offer inventory.
apps/docs/content/guides/services/data-as-a-service/index.mdx and apps/docs/content/guides/infrastructure/managed-*/index.mdx — data and managed infrastructure offer inventory.
docs/services/proposition-inventory-2026-06-26.md — route, CTA, navigation, and inventory drift map.
docs/services/opsfleet-portfolio-extension.md — competitive service taxonomy compared with Opsfleet.
docs/services/xebia-ai-content-research.md — AI/data competitive taxonomy and recommended AI/data pages.

External authoritative and competitive references#

CNCF Platform Engineering Maturity Model: https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/
CNCF Cloud Native Trail Map: https://www.cncf.io/cloud-native-trail-map/
Google SRE books and practices: https://sre.google/books/
DORA / Google Cloud DevOps research: https://dora.dev/
NIST Cybersecurity Framework 2.0: https://www.nist.gov/cyberframework
NIST AI Risk Management Framework: https://www.nist.gov/itl/ai-risk-management-framework
NIST SP 800-34 contingency planning: https://csrc.nist.gov/publications/detail/sp/800-34/rev-1/final
OWASP Application Security Verification Standard: https://owasp.org/www-project-application-security-verification-standard/
OWASP Top 10 for LLM Applications: https://owasp.org/www-project-top-10-for-large-language-model-applications/
SLSA supply-chain security framework: https://slsa.dev/
CIS Benchmarks: https://www.cisecurity.org/cis-benchmarks
FinOps Foundation Framework: https://www.finops.org/framework/
Diataxis documentation framework: https://diataxis.fr/
Backstage internal developer portal project: https://backstage.io/
Opsfleet public services referenced in docs/services/opsfleet-portfolio-extension.md: DevOps as a Service, AI as a Service, Data as a Service, cloud migration, Kubernetes implementation, Graviton migration, DevSecOps, AWS Marketplace provisioning, and disaster recovery planning.
Xebia public AI/data pages referenced in docs/services/xebia-ai-content-research.md: AI strategy, agentic AI, AI governance, responsible AI, AI managed services, LLMOps, MLOps, data engineering, data platforms, analytics engineering, data governance, streaming, and lakehouse services.