Aura Analyst

Note

This is a Preview feature.

Overview

Aura Analyst is an AI-powered data analyst that makes it easy to converse with the data in plain English. It is a fully managed agentic AI service built natively for SingleStore that translates natural language questions into precise SQL queries and instantly delivers insights from the databases. By removing the requirement of manually writing SQL or building complex dashboards, Aura Analyst accelerates analytics and empowers users to uncover insights faster. Leveraging SingleStore’s Agentic AI platform, it ensures that queries are accurate, context-aware, and governed, helping teams make smarter, data-driven decisions with ease.

How Aura Analyst Works

Aura Analyst is a fully managed agentic, multi-component AI system designed to transform natural language into reliable, actionable insights. Instead of relying on a single, monolithic model, it orchestrates a series of specialized stages, including intent interpretation, query planning, SQL generation, validation, execution, and result summarization. This modular architecture enhances accuracy, ensures control, and adapts flexibly across diverse datasets and query types.

By clarifying ambiguous inputs, exposing query plans, and automatically retrying on failures, Aura Analyst provides a more dependable experience while building user trust. Beyond running SQL, the system makes results easy to interpret through natural-language summaries and visualizations, enabling business and technical users alike to act on data with confidence.

What is a Domain

A Domain is the context service for Aura Analyst. It acts as a knowledge base, supplying the semantic and structural framework required to interpret questions accurately, generate the right SQL, and deliver governed insights.

Users with the “Agent Domain Owner” permission can configure Domains by selecting relevant workspaces, databases, and tables. They can enhance Domains with custom instructions, business-specific formulas, or logic that Aura Analyst applies when answering questions.Once configured, a Domain abstracts the complexity of raw schemas. Users interact with a curated, context-rich view of the data, making analytics more accurate, consistent, and accessible.

Domains are dynamic. As data changes and new business requirement emerges, users can continuously refine them. Each update enhances the context service, ensuring that insights remain reliable, governed, and immediately actionable.

Create a Domain

Once the Aura Analyst is enabled, select Create domain. In the Create Domain dialog:

Domain Details

Name

Enter the name of the domain.

Description

Enter the domain description.

Connect Data

Connection

Select the SingleStore deployment (workspace) the domain connects to.

Specifying a workspace allows connecting the SingleStore databases referenced in the domain.

SingleStore recommends creating a new workspace with a read-only database attachment for Aura Analyst to maintain clarity and separation of workloads.

Select tables

Select the tables from the SingleStore databases.

Select Create to create the domain for Aura Analyst.

Note

Aura Analyst keeps the workspace active as hourly metadata collection prevents the cluster from remaining idle for more than one hour.

Configure an Existing Domain

To configure an existing domain, enable Creator Mode, and enter or select the following:

Build

Context

Contexts are reference materials that the Analyst can draw on to answer questions more accurately. Use them to provide custom instructions, background knowledge, assumptions, or business logic that may not be immediately obvious from the raw data.

  • Instructions: Add general instructions to set response style, constraints, and domain-specific guidance. To add an instruction, enter your context in Instructions, and then select Save. The following are the context states for the instructions:

    • Draft: A working copy of domain instructions that can be edited and tested without affecting the live published version. It is created when a domain owner begins editing instructions in Creator Mode and changes remain isolated until explicitly published. This allows domain owners to test and refine instructions, make multiple edits without disrupting active users, and discard changes if needed.

    • Published: The current live version of domain instructions that the Analyst actively uses to answer questions. All users querying the domain see and use the published version, and the Analyst applies these instructions when generating SQL and interpreting questions. This is the production state visible to all domain users.

  • Learned Context: The system automatically learns contexts from user questions and interactions. The following are the context states for the learned contexts:

    • Pending: Learned contexts that have been automatically generated by the system but have not yet been reviewed by a domain owner. These insights are awaiting approval or rejection.

    • Approved: Learned contexts that have been reviewed and approved by a domain owner. Only approved contexts are actively used by the Analyst to answer questions and generate SQL queries.

    • Rejected: Learned contexts that have been reviewed and rejected by a domain owner.

    You can update and delete existing learned contexts.

Data

The Data section allows you to review and enhance schema metadata and includes relationship management capabilities.

  • Database: Navigate to the Database tab. Auto-generated descriptions for tables and columns help the Analyst understand the data model. Domain owners can edit and refine these descriptions to improve accuracy.

    Add more tables to the domain by selecting Add. Tables can be added from the deployment connected to the domain.

    To edit the table description, select the ellipsis (three dots), and then select Edit.

    To delete the table, select the ellipsis (three dots), and then select Delete.

    In the Table column, select the table and you can view and edit the description of each column of the table.

  • Entity-Relationship: Navigate to the Relationship tab. A relationship crawler automatically discovers foreign key relationships using schema analysis and LLM inference, assigning each relationship a confidence score between 0.0 and 1.0. Discovered relationships include source and target database, table, column, cardinality, and description.

    You can also manually create relationships by selecting source and target tables and columns, specifying cardinality (> for many-to-one, < for one-to-many, - for one-to-one, <> for many-to-many), and saving entries individually or in bulk. Manually created relationships are labeled accordingly.

    To add a relationship, select Add. In Add table relationship, enter of select the following:

    • Left Table: Select the table from the list.

    • Right Table: Select the table from the list.

    • Join Condition: Select the columns from each table to create a join condition.

    • Type: Select the cardinality type.

    • Description (Optional): Enter the description.

    Select Save Relationship to save the table relationship.

    To edit the relationship, select the ellipsis (three dots), and then select Edit.

    To delete the relationship, select the ellipsis (three dots), and then select Delete.

Governance

Chat Review

Review recorded analyst conversations and user feedback to monitor quality and identify areas for improvement.

View the question, rating, reason, and comment of the response. Select the question to view the Analyst’s response. Monitor response quality, review user feedback, and identify areas for improvement.

Access Controls

Access Control provides the ability to assign roles, set permissions, and control who can access the domain.

View all the users or teams and their roles in this tab. To share access to the domain with a user or a team, select Add. In the Share <your_domain> dialog, select User or Team, select the access role, and then select Save.

To remove access for any User or Team, select Remove Access in the access role of the selected user or team.

Note

Inherited roles cannot be modified.

Settings

Update the domain name and description in the Name and Description fields, respectively. Enable Record conversations for review. When enabled, the system saves all conversations for the selected domain to the Chat Review. If this setting is disabled, only questions with user feedback are captured in Chat Review.

Aura Analyst Access Controls

SingleStore Aura defines three RBAC (role-based access control) roles for Aura Analyst:

  • Organization Level Controls:

    • Aura Creator: Provides the ability to install and uninstall Aura Analyst.

    • Agent Domain Owner: Provides the ability to create and manage domains.

      Note

      Domain creation is limited to the tables accessible by the "Agent Domain Owner".

  • Domain Level Controls:

    • Owner: Provides the ability to manage a given domain.

      Note

      Domain creation is limited to the tables accessible by the "Owner".

    • User: Provides the ability to use the domain and ask questions in natural language and receive responses.

When an Agent Domain Owner creates a domain, the system performs the following actions:

  • Aura Analyst fetches the data accessible to the Agent Domain Owner.

  • Aura Analyst uses AI to infer tables and column definitions.

    • SingleStore recommends owners to review the description and modify as required.

  • When creating a new domain, a database user <domain_id>_auraanalyst is created with select permissions to the tables selected in the domain.

  • All queries run by Aura Analyst within a Domain are run as <domain_id>_auraanalyst user.

A user can be granted Domain-level access even without having privileges on the underlying databases or tables referenced by the Domain. Aura Analyst runs queries inside the Domain as the <domain_id>_auraanalyst database user. This allows any user with access to the Domain to query the underlying databases.

A user may be an Aura Domain User or Domain Owner regardless of other organization roles. A user can be a member without any additional roles (a "roleless" org member) and still receive Domain-level permissions. However, these permissions do not grant or imply elevated privileges on the underlying databases.

Note

Domain owners must manage Domain roles and access settings to align with their organization’s governance policies.

Interacting with Aura Analyst

Once a domain is created and configured, you can ask any data related questions to Aura Analyst using natural language. To start a conversation, select the desired domain in the chatbox. Domains can be switched at any time during a conversation.

Note

All queries and interactions require an active Domain context.

Within a conversation, following features can be accessed:

  • Thoughts block: View how Aura Analyst approached to provide the insights as a response including the SQL queries executed.

  • Left panel controls:

    • View the chat history.

    • Start a new session.

    • Delete an existing session.

  • Feedback: Your feedback enables a human-in-the-loop system that continuously improves results.

    • Improve accuracy over time: Feedback helps refine how queries are interpreted and answered to deliver more reliable and complete responses for future queries.

    • Domain expert review: Domain owners can review query interactions to identify gaps and improve overall system performance.

    For a query response, use the “Is this correct?” option under the query result to provide feedback.

    • Select Yes (thumbs-up) if the response is correct.

    • Select Needs Improvement (thumb-down) if the response is incorrect or incomplete.

    When Needs Improvement is selected, submit feedback by selecting one of the following options:

    • Values look off

    • Missing data

    • Misunderstood question

    • Analyst made something up

    • Other

    Optionally, enter additional details in the field to describe what went wrong.

Note

Observers can use Monitoring and Query History to track queries run by Aura Analyst, including slow-performing queries.

Share a Chat

You can share an Aura Analyst chat with other users in your organization, enabling them to review the conversation and its associated insights.

To share a chat:

  1. Open a chat that includes at least one assistant response.

  2. Select Share from the right top of the chat.

  3. Copy the generated link and share it with the users who need access.

Note

  • The shared chat is a snapshot of the conversation up to the most recent assistant response at the time of sharing. It does not update if the chat continues.

  • Shared chats are not public. A user can access a shared link only if the following conditions are met:

    • The user is signed in as a member of the same organization that owns the chat.

    • The user has permission to use the Aura Analyst domain associated with the chat.

  • Users who do not meet these conditions see an access denied message.

  • Sharing a chat link is separate from other sharing features in Aura Analyst. It does not affect the following:

    • Saving or sharing charts to dashboards

    • Domain access or domain sharing settings in Domain settings

Continue a Shared Chat

When a user opens a shared link, the conversation appears in read-only mode.

To continue working from that conversation:

  1. Select Continue conversation at the bottom of the page.

  2. Aura Analyst creates a new chat session that copies the shared conversation.

New messages in this session do not affect the original chat or the shared snapshot.

Examples

Example 1: SaaS Product Usage Analytics

This example analyzes product adoption by creating a domain focused on it, using the relevant tables from the saas_usage database.

Create Domain dialog showing 'SaaS Usage Domain' name, connection deployment set to workspace-1, and four tables selected from saas_usage database: subscriptions, support_tickets, usage_logs, and users. Cancel and Create buttons appear at the bottom.

Once the domain is created, questions can be asked about the data.

Example 2: E-commerce Marketing and Campaign Analytics

This example analyzes marketing product adoption by creating a domain focused on it, using the relevant tables from the marketing_analytics database.

Create Domain dialog showing 'Marketing Analytics Domain' name, connection deployment set to workspace-1, and five tables selected from marketing_analytics database. Options to cancel or create are at the bottom.

Once the domain is created, questions can be asked about the data.

Last modified:

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.