Skip to main content

Agents

Feldera supports agents in two ways. It gives agents instantly fresh context: SQL views that instantly reflect changes to live and historical data. For agent security, it keeps the permissions of every user and agent current, so each access check uses the latest rules.

Instantly fresh context​

An agent is only as good as its context. With Feldera, that context is a set of SQL views over all of your data, in any combination of historical and live sources. Feldera updates each view on every input change and pushes the changes to the agent as they occur, so the agent always acts on current data and never re-queries from scratch all the time.

All your datahistorical + liveFeldera pipelineincremental SQL viewsAgentLLM + toolsevery changeview changesqueries and/or defines SQL views
The agent defines the logic. Feldera evaluates it on every change.
  • Agents write SQL. An agent can define the context it needs as a SQL view and deploy it. The views, no matter how complex, instantly reflect changes to inputs (live and historical data).
  • Current context for every action. When input data changes, agents instantly know what changed in the views they listen to or query.

Agent security​

Agents act for users, so each action needs a permission check. Fine-grained authorization models express permissions as a graph of users, agents, groups and resources. Feldera evaluates these graphs with recursive SQL, and updates the results incrementally when a permission or a resource changes. Auth0 FGA, part of Okta, uses Feldera to precompute billions of permission checks for AI agents and search.

  • Permission checks for every user and agent. Feldera computes the access rights across deeply nested access graphs, so a check reads a precomputed answer.
  • Current after each change. When a permission changes, Feldera updates only the access rights that the change affects.