Skip to content
SYS.DOCS // DOCS

Kubernetes App Templates

Deploy application templates to your Kubernetes cluster in minutes. Edka stores each app template in the backend catalog with its metadata, configuration form, required add-ons, endpoints, and Kubernetes manifests.

Edka also includes dedicated workspaces for Databases and Agents. Use Apps for packaged services and app-like stacks. Use Databases when you need database-specific lifecycle, logs, insights, restore, or engine-aware settings. Use Agents for AI runtime health, profiles, webhooks, backups, and device approval.

  • Buzz: self-hosted Nostr workspace for people and AI agents, backed by PostgreSQL, Valkey, S3-compatible object storage, and a stable Envoy Gateway hostname. See the Buzz operations guide.
  • Multica: open-source workspace for coordinating AI agents and their work, with Slack and GitHub integrations, backed by PostgreSQL with pgvector and an Envoy Gateway hostname. See the Multica setup guide.
  • n8n: workflow automation platform with queue workers, task runners, Prometheus metrics, and native AI capabilities. See the n8n setup guide.

The backend catalog still contains deprecated PostgreSQL, Postgres Restore, and Redis Stack app templates for compatibility with older app workflows. New database deployments should use the Databases workspace instead:

  • PostgreSQL and Postgres Restore map to the dedicated PostgreSQL engine.
  • Redis Stack is deprecated in favor of Valkey in Databases.

Internal and organization-scoped templates

Section titled “Internal and organization-scoped templates”

Some app templates can be scoped to a specific organization. For example, Jenny is an internal enterprise template and is only visible to the target organization. Organization-scoped templates may not appear in every Edka account even when they exist in the backend repository.

For catalog apps, Edka handles:

  • rendering the app-specific configuration form
  • installing required add-ons before the app when needed
  • applying the rendered Kubernetes manifests
  • showing configured endpoints after deployment
  • tracking runtime status, logs, metrics, and app-specific update options where the template supports them

Some apps have no add-on dependencies. Others queue supporting add-ons during installation. Current examples include:

  • metrics-server for metrics-enabled apps such as n8n, Meilisearch, and Plausible
  • existing PostgreSQL, ClickHouse, Valkey, and S3-compatible object storage for Langfuse
  • metrics-server, existing PostgreSQL and Valkey services, a dedicated AWS S3 or S3-compatible object storage integration, and an Envoy Gateway hostname for Buzz
  • an existing PostgreSQL 17 or 18 database with the vector extension and an Envoy Gateway hostname for Multica
  • cert-manager, letsencrypt-issuer, and node-exporter for kube-prometheus-stack
  • cert-manager and eck-operator for Elasticsearch
  • cert-manager and opensearch-operator for OpenSearch