Governed catalog
Publish approved Crossplane-backed templates with versioning, dependency metadata, source review, and access control.
Crossplane self-service, governed by platform teams
cOTTER gives application teams a controlled portal for requesting infrastructure while platform teams retain ownership of templates, credentials, quotas, approvals, audit trails, and recovery.
What cOTTER does
Publish approved Crossplane-backed templates with versioning, dependency metadata, source review, and access control.
Separate teams by project, membership, lifecycle tier, provider, credentials, quotas, and audit scope.
Turn template schemas and dependencies into guided workflows that hide raw manifests from application teams.
Queue identifier-only jobs to agents that apply resources, observe Crossplane status, and report back through the platform.
Trace who changed what, when work was queued, and how recovery actions were handled for a deployment.
Manage blocked deployments, dead-lettered work, reapply flows, support bundles, and health signals from one portal.
Security model
Frontend code never talks directly to Kubernetes, Crossplane, Redis, RabbitMQ, databases, or cloud provider APIs.
Provider credentials are encrypted at rest and exposed only through backend and agent-secured paths.
Every user action is role-checked, project-scoped, and auditable before it reaches infrastructure.
Built for platform teams
Expose approved infrastructure options without teaching every team Crossplane or Kubernetes internals.
Give teams controlled deployment rights while centralizing credential handling and template policy.
Prepare for remote agents, operational visibility, customer-cluster diagnostics, and enterprise support workflows.
Early product
cOTTER is being shaped around platform-team operations, not a generic cloud dashboard.