A BI system requires skills
An executive has to know SQL or wait for a report from an analyst. A simple question about data turns into a task that takes hours or days.
SUB–04 / DATA · Data Analyst · PostgreSQL · Voice and text
A data analyst for a PostgreSQL database. It queries the database in natural language by text or voice: it takes a question, translates it into an SQL query to the permitted views and returns an answer with an explanation of the calculation and a link to the source table. It does not change the data — it only reads. It can run locally within an approved environment or use cloud models; data-handling terms depend on the selected configuration.
Four reasons to use a specialized agent instead of a BI system or cloud AI.
An executive has to know SQL or wait for a report from an analyst. A simple question about data turns into a task that takes hours or days.
Every question about data goes through the analyst. The queue of requests grows, and teams have to wait for even simple metrics.
In cloud mode, queries and results are processed in the selected provider's infrastructure. Review the agreement, storage, access, and data-use terms before connecting it.
In a meeting, on the road or on the production floor, typing a query is inconvenient. Voice input solves this problem.
The Data Analyst accepts a question by voice or text, builds the SQL query, and links the answer to the source table. In a local configuration with no external integrations, processing remains within the approved environment.
Four steps — from speech recognition to an SQL query to PostgreSQL.
An executive asks a question by voice or in text. The agent recognizes the speech and extracts the business meaning of the request.
The agent identifies the user, their role and the data area they have access to.
The agent builds an SQL query to the permitted views of the database. Writing and modifying data is prohibited.
The agent returns the result, explains how it was calculated and points to the source table for verification.
The design decisions built into the foundation determine the nature of the result and the scope of application.
01
An executive asks a question by voice — the agent recognizes the speech, builds an SQL query and returns an answer. No access to a BI system is needed.
02
In a local configuration with no external integrations, data, queries, and results are processed within the approved company environment.
03
The agent builds SQL queries only to the permitted PostgreSQL views. Writing and modifying data is prohibited at the architecture level.
04
The engine supports local and cloud models. The user selects the configuration, and data flows and access terms are defined before launch.
Each role gets a concrete result that fits into its own workflow.


Operational metrics in response to a voice request, without going to analysts or BI systems.

Fast verification of data and metrics without writing SQL queries.

Revenue, margin and receivables metrics — by voice or in text.

Real-time operational data on the warehouse, production and deliveries.
Typical situations: from a voice query in a meeting to financial monitoring.
An executive asks: "What was the revenue for the last quarter by region?"
What is generated
What it gives
An analyst needs to quickly verify a metric without writing SQL.
What is generated
What it gives
A CFO checks the receivables.
What is generated
What it gives
Boundaries
The answer depends on the quality of the data model and the dictionary of metrics. The agent has no write access and does not bypass corporate access policies. Access to sensitive data is restricted through a role-based access model.
What the agent does not do
Direct answers for quick reading. Expand the question you need or open all at once.
No. The agent has read-only access to the permitted PostgreSQL views only. Writing and modifying data is prohibited at the architecture level.
In local mode — no. Data, queries and results stay inside the company perimeter. Cloud mode — only by the user's explicit choice.
Yes. The agent recognizes speech (locally via Whisper or a cloud STT) and builds an SQL query from the meaning of the question.
PostgreSQL. The agent works with permitted views, not with tables directly.
No. The question is asked in natural language — in text or by voice. The agent builds the SQL query itself.
Separate views with access rights for different roles are supported. Access to sensitive data is restricted through a role-based access model.
First step
Pick one of the twelve agents and subagents, or fill in the questionnaire for custom development.
