{
  "id": "featureform",
  "title": "Redis Feature Form",
  "url": "https://redis.io/docs/latest/operate/featureform/",
  "summary": "Deploy and operate Feature Form on Kubernetes.",
  "tags": [
    "docs",
    "operate",
    "featureform"
  ],
  "last_updated": "2026-04-20T15:33:16+02:00",
  "children": [
    {
      "id": "deploy",
      "summary": "Deploy and operate Feature Form on Kubernetes.",
      "title": "Deploy",
      "url": "https://redis.io/docs/latest/operate/featureform/deploy/"
    },
    {
      "id": "auth",
      "summary": "Manage Feature Form auth and RBAC",
      "title": "Authentication and RBAC",
      "url": "https://redis.io/docs/latest/operate/featureform/auth/"
    }
  ],
  "page_type": "content",
  "content_hash": "460b023e081fe58925cb2ec41e1f0d52fed6b6de157280a98029652273480497",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "Feature Form runs as a Kubernetes-based platform for feature engineering and online feature serving. Use this section to prepare your environment, choose a deployment method, install Feature Form, and verify that the platform is ready for application teams.\n\nThese docs are cloud-neutral in framing. Where Terraform examples are useful, request them from your Redis account team.\n\nUse this section to decide how you want to install Feature Form before you create workspaces or register providers."
    },
    {
      "id": "deployment-model",
      "title": "Deployment model",
      "role": "content",
      "text": "The Helm chart deploys:\n\n- one shared API server deployment that exposes both REST and gRPC\n- separate services for REST and gRPC\n- an optional dashboard\n- optional addons for Postgres state, provider infrastructure, and observability\n\nAuthentication is required. Standard installs need OIDC configuration."
    },
    {
      "id": "state-backend-choices",
      "title": "State-backend choices",
      "role": "content",
      "text": "- External PostgreSQL: the durable default for shared deployments\n- Bundled state PostgreSQL: useful for self-contained evaluation or test installs\n- Memory state: local or CI only, not durable\n\nWith memory state, gRPC and REST do not share one durable graph. Keep that in mind when troubleshooting “missing” workspaces or resources."
    },
    {
      "id": "exposure-choices",
      "title": "Exposure choices",
      "role": "content",
      "text": "- internal-only services\n- service-specific ingresses\n- unified ingress\n- direct `LoadBalancer` services\n\nDo not combine unified ingress with service-specific ingress settings."
    },
    {
      "id": "helm-profiles",
      "title": "Helm profiles",
      "role": "content",
      "text": "- base chart\n- `profiles/memory.yaml`\n- `profiles/provider-stack.yaml`\n- `profiles/observability-postgres.yaml`\n- `profiles/provider-observability.yaml`"
    }
  ],
  "examples": []
}