{
  "schema_version": 2,
  "id": "develop/ai/featureform/overview",
  "title": "Redis Feature Form overview",
  "url": "https://redis.io/docs/latest/develop/ai/featureform/overview/",
  "summary": "Learn what Redis Feature Form is, who it is for, and how it fits into Redis-based ML workflows.",
  "tags": [],
  "last_updated": "2026-09-11T15:54:40+01:00",
  "page_type": "content",
  "content_hash": "9c082e234195e7e3a8ef873886785e4c467d5374eba6ebe895abe061883c78bd",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "This page describes the standard Feature Form onboarding path: workspace creation, access handoff, secrets, providers, definitions, apply, and serving. Use it as the high-level sequence before you dive into task-specific guides."
    },
    {
      "id": "audience",
      "title": "Audience",
      "role": "content",
      "text": "- Global admins creating and handing off workspaces\n- Workspace admins wiring secrets and providers\n- Feature engineers authoring definitions files\n- Application or model teams serving ready feature views"
    },
    {
      "id": "recommended-path",
      "title": "Recommended path",
      "role": "content",
      "text": "1. Create the workspace and grant initial access.\n2. Confirm the intended principal can see the workspace.\n3. Reuse the built-in `env` secret provider or register another backend.\n4. Register the providers the workspace will reference.\n5. Author a definitions file and run `ff apply`.\n6. Inspect the graph and catalog, then serve from a feature view."
    },
    {
      "id": "what-to-verify-before-the-first-apply",
      "title": "What to verify before the first apply",
      "role": "content",
      "text": "- The workspace exists and the right principal can access it.\n- Secret references such as `env:PG_PASSWORD` resolve from the runtime environment.\n- Providers are already registered by the names the definitions file expects.\n- The team understands whether the definitions file represents complete desired state or a partial subset."
    },
    {
      "id": "latest-updates",
      "title": "Latest updates",
      "role": "content",
      "text": "The latest release adds enterprise-oriented capabilities:\n\n- **Unified batch and streaming pipelines**: Support for tiling, backfills, and incremental updates reduces custom pipeline work.\n- **Workspaces for multi-tenancy**: Isolate providers, data, authentication, and observability at the workspace level.\n- **Fine-grained job control**: Planning, impact analysis, split materializations, and queue-based job management provide visibility into changes before they affect production systems.\n- **Atomic DAG updates**: Manage graph-level changes atomically instead of versioning individual resources, which simplifies rollback and change history.\n- **Enhanced RBAC and security**: Workspace-scoped access controls, API key pairs, a granular role model, audit logs, secret-provider improvements, mTLS, and encrypted internal transport.\n- **Two-service deployment model**: A simplified deployment architecture that reduces operational complexity.\n- **Redesigned dashboard**: Configure workspaces and providers directly from the UI."
    },
    {
      "id": "what-to-read-next",
      "title": "What to read next",
      "role": "content",
      "text": "- [Quickstart](https://redis.io/docs/latest/develop/ai/featureform/quickstart)\n- [Register providers](https://redis.io/docs/latest/develop/ai/featureform/register-providers)"
    }
  ],
  "examples": []
}