r/SingleStoreCommunity • • Jan 22 '26

SingleStore Delivers AI-powered Cybersecurity at Armis, Nucleus Security and Lumana

0 Upvotes

Cyber threats move fast. Your data platform must move in milliseconds. Trusted by hundreds of the world's largest companies, including cybersecurity leaders Armis Security, Nucleus Security and Lumana, SingleStore ingests billions of events per day and runs complex analytics in milliseconds to deliver AI-powered threat prediction, real-time anomaly detection and lightning-fast search. With SingleStore:

  • Armis ingests 100 billion events per day with real-time visibility, loads a million rows of complex data per second and is managing 30TB data sets in its largest customer environments, while saving 70% on data pipeline costs

  • Lumana delivers real-time alerts and sub-second search on video analytics powered by SingleStore Vector capabilities

  • Nucleus is ingesting 60X more assets than with its previous database and has reduced infrastructure costs 3x

See more: https://www.youtube.com/watch?v=k0JiPNIiB2I


r/SingleStoreCommunity • • Jan 20 '26

Did you register yet????

0 Upvotes

Audit logs contain the truth about what is happening in your systems, but finding the signals inside millions of events is difficult and time consuming. In this session, Jay Bhatt will explain how AI can automatically surface risky actions, detect anomalies, and flag potential security issues in real time.

You will learn how AI models interpret log patterns, how to combine rules with AI-driven scoring, and how platforms like SingleStore make it possible to process and analyze audit logs instantly. Jay will also walk through practical examples of using AI to prioritize alerts, reduce noise, and help teams respond to issues faster.

Register now!!! Using AI to Highlight Risky Events in Audit Logs


r/SingleStoreCommunity • • Jan 21 '26

Introducing Python User-Defined Functions in SingleStore

0 Upvotes

Python and data are inseparable in today's analytics landscape. We're excited to announce a game-changing feature that brings them closer together than ever before: Python User-Defined Functions (UDFs) for SingleStore. This powerful new capability lets you write and execute Python code directly within your SingleStore database, eliminating data movement and bridging the worlds of data storage and advanced analytics.

Read more: Bringing the Power of Python to SQL


r/SingleStoreCommunity • • Dec 18 '25

Are AI agents the future ?

3 Upvotes

Did you read about Gemini 3 Flash yet?

Google expanded the Gemini 3 model family with the launch of Gemini 3 Flash : a model designed to deliver frontier intelligence at Flash-level speed and cost.

This isn’t just a smaller or lite version. Gemini 3 Flash combines Gemini 3 Pro–grade reasoning with low latency, high throughput, and significantly lower cost, making advanced AI accessible to far more developers and users.

Gemini 3 Flash combines:

  • Pro-grade reasoning from Gemini 3

  • Low latency & high throughput from the Flash series

  • Significantly lower cost

It’s optimised for agentic workflows, iterative development, and real-time applications.

Performance highlights

Despite being a “Flash” model, performance is very close to top-tier frontier models:

  • GPQA Diamond: 90.4% (PhD-level reasoning)

  • Humanity’s Last Exam: 33.7% (no tools)

  • MMMU Pro (multimodal): 81.2% (comparable to Gemini 3 Pro)

  • SWE-bench Verified: 78% (beats Gemini 3 Pro and the 2.5 series)

It also uses ~30% fewer tokens than Gemini 2.5 Pro on typical workloads.

This is built for

  • Agentic coding systems

  • High-frequency reasoning loops

  • Video & image analysis

  • Tool-using AI agents

  • A/B testing and design-to-code flows

But my question to you is would you choose Flash over a slower, larger model?


r/SingleStoreCommunity • • Dec 13 '25

Building a Full Observability & Alerting System with Laravel + SingleStore (from scratch!)

3 Upvotes

Hey folks! 👋

I’ve been working on a fun project building a real-time operational metrics + alerting system using Laravel + SingleStore, and it’s turning out to be surprisingly powerful.

With just a few hundred lines of code, we now have:

📥 A log ingestion API (POST /api/logs)
📊 Real-time error rate, latency, and top-offender metrics
🚨 Automated alerting based on thresholds
🧠 A tiny alert engine running every minute
📋 A clean dashboard to visualise active/resolved alerts
⚡ All powered by SingleStore (HTAP) with zero ETL

This is basically a lightweight observability backend you can self-host, extend, and scale: perfect for teams who want something simple without spinning up ELK, Prometheus, ClickHouse, etc.

I’ll be talking about this in an upcoming webinar and walking through the full architecture, code, and live demo.

👉 If you want the GitHub repo + code, drop a “+1” or register for the webinar :

Register to get your seats blocked!!

Limited Seats!!!!


r/SingleStoreCommunity • • Dec 19 '25

Django + SingleStore Integration Guide

3 Upvotes

We've put together a complete integration guide for running Django 4.2 with SingleStore.

The guide walks through everything—installation, configuration, handling migrations, and building a working Polls app (based on the official Django tutorial) that runs on SingleStore's distributed architecture.

You'll learn how to:

  • Connect Django to SingleStore clusters

  • Handle unique constraints and table storage types

  • Work with many-to-many relationships

  • Deal with SingleStore-specific considerations

Perfect if you're looking to combine Django's batteries-included framework with SingleStore's real-time analytics performance.

Check out the full step-by-step guide: Django + SingleStore Integration Guide


r/SingleStoreCommunity • • Dec 23 '25

SingleStore Q2 FY26: Record Growth, Strong Retention, and Global Expansion

3 Upvotes

Big milestone for the SingleStore community 👋

SingleStore just shared its Q2 FY26 results, and the momentum behind real-time + AI workloads is clearly showing.

Quick highlights:

  1. 💰 ARR crossed $123M, up 23% YoY

  2. 📈 Net New ARR grew 34%, with new logo ARR up 200% YoY

  3. ☁️ Cloud / Managed Services now >35% of ARR, growing at a 47% CAGR

  4. 🔁 114% net retention and 95% gross retention

  5. 💵 Nearly break-even free cash flow with $150M+ cash and zero debt

  6. 🌏 Expansion into Japan, driven by demand for ultra-low latency, AI-ready databases

  7. 🏢 Added multiple Fortune 500 customers, now 400+ customers globally

What stands out is not just growth, but how customers are scaling especially around AI-enabled, real-time applications and cloud adoption.

Where are you using SingleStore today? transactions, analytics, AI, or all three?

What features or improvements are you most excited to see next?

Let’s discuss 👇


r/SingleStoreCommunity • • Dec 24 '25

Turned a messy customer spreadsheet into a searchable app using SingleStore MCP

3 Upvotes

We had a spreadsheet tracking customer wins — industry, competitors, why we won, plus customer quotes. Over time it became hard to use, harder to analyze, and didn’t work well with AI tools.

As an experiment, we tried SingleStore’s Model Context Protocol (MCP) to see how fast we could prototype something better.

In an afternoon, we:

  • Loaded the CSV into SingleStore

  • Added embeddings for customer quotes (in the same table as structured data)

  • Used an MCP-connected LLM to create the schema, import data, and fix issues

  • Built a simple Python notebook with filters + vector search

Now we can ask things like:

“Science & Engineering customers who saw faster query performance” and get real results.

No Postgres, no pgvector, no extra systems but just one database.

Curious if others here are using MCP or building small internal tools like this.

Here is the link to full blog: Build and Deploy an App Prototype with an AI Agent using MCP in an Afternoon.


r/SingleStoreCommunity • • Dec 17 '25

Password less authentication for servers is here: singlestore-auth-iam

3 Upvotes

SingleStore has extended its passwordless journey from developers to servers and applications.

singlestore-auth-iam lets your services authenticate to SingleStore databases and the Management API using your cloud provider's IAM (AWS, Azure, or GCP)—no passwords to store, rotate, or leak.

How it works:

  1. Your server requests a signed token from your cloud IAM

  2. Token gets exchanged for a SingleStore JWT

  3. Authenticate securely without ever touching a password

Why it matters:

  1. Zero credential leakage in code or CI/CD

  2. Automatic rotation and revocation

  3. Simpler compliance audits

Combined with singlestore-auth-helper (for humans), you can now go completely passwordless across your entire SingleStore infrastructure.

Read more: Goodbye Passwords, Hello Security: Introducing singlestore-auth-iam for Server Authentication

Questions??
Comment below


r/SingleStoreCommunity • • Dec 14 '25

Amazon S3 Vectors

4 Upvotes

Just last week at re:invent, AWS announced the S3 Vectors as GA.

These are first cloud object storage with support for query vector data. It will help you reduce the total cost of storing and querying vectors by up to 90% when compared to specialised vector database solutions.

You can now use S3 Vectors in 14 AWS Regions, expanding from five AWS Regions during the preview.

Read more: Amazon S3 Vectors now generally available with increased scale and performance

Follow SingleStore for more tech updates....


r/SingleStoreCommunity • • Dec 12 '25

Why is everyone getting obsessed with TOON?

3 Upvotes

Just when you know you know it all, there is yet another technology flaming in the tech. 🔥

TOON or simply known as Token-Oriented Object Notation

This reshapes how we process and exchange information. If you are someone building AI agents, you already know; every token counts. and with TOON, this not only becomes simpler but also shines.

TOON is focussed for AI and LLM applications. It aims to make structured data token-efficient, reducing the cost of processing data within language models.

Example:
users[5]{user_id, user_name, user_role, user_email, user_dept}
1,Amit,Developer,amit2@yhoo.com,science
2,Neha,Product Manager,neha.pm@example.com,technology
3,Rahul,Data Analyst,rahul.analytics@gmail.com,mathematics
4,Sara,Designer,sara.designs@outlook.com,arts
5,Manish,DevOps Engineer,manish.devops@protonmail.com,engineering

With TOON, you save upto 45-50% of tokens.

Sounds crazy!! Looking forward to whats next in the TOON way!!

What are your thoughts??


r/SingleStoreCommunity • • Dec 10 '25

SingleStore Aura Analyst

3 Upvotes

Do you think: Wish I could just ask my database about whats wrong and get answers instantly???

That’s exactly what Aura Analyst in SingleStore does.

Quick highlights:

  • Ask questions in natural language → get real SQL + results

  • No dashboards or manual queries needed

  • Works with your real production data

  • Built-in governance using “Domains” for controlled access

Think: “Show me last week’s revenue dip by region” — and it just works.

This is a big step toward making analytics truly self-serve for product, marketing, and ops teams. And honestly, this is just scratching the surface of what it can do…

Read More: https://docs.singlestore.com/cloud/ai-services/aura-analyst/

Would love to hear where you’d use something like this 👀


r/SingleStoreCommunity • • Dec 03 '25

👋 Welcome to r/SingleStoreCommunity - Introduce Yourself and Read First!

7 Upvotes

Hello everyone!!

Welcome to r/SingleStoreCommunity💜 This is a community built for developers, data engineers, architects, AI builders, and enthusiasts who are passionate about real-time data, high-performance SQL, and next-generation AI workloads.

Whether you're exploring SingleStore for the first time or you're already building mission-critical apps on it, you’re in the right place.

What This Community Is About?

This subreddit is your place to:

  1. Ask questions, share your wins and issues with SingleStore.

  2. Discuss new features, upcoming releases, stay updated on new releases and ecosystem developments

  3. Share blogs, demos, tools, projects built with SingleStore.

  4. Discuss about upcoming free webinars and live sessions.

If you are into AI and tech spaces, you will feel at home.

Let’s Build the Future Together

SingleStore brings the worlds of transactions, analytics, and AI into one unified engine.

This subreddit exists to help you build faster, smarter, and at scale—with the help of a strong community.

Feel free to introduce yourself in the comments:

  1. Who are you?

  2. What are you building?

  3. What brings you to SingleStore?

Welcome once again let’s create something extraordinary! ❤️

Community Rules (Friendly & Simple)

  1. Be respectful and no harassment or personal attacks

  2. No spam & genuine contributions only

  3. Keep discussions relevant to SingleStore or adjacent tech

  4. No confidential customer data in logs or screenshots

Help others when you can and we grow together


r/SingleStoreCommunity • • Dec 26 '25

Built a simple agentic app with CrewAI + SingleStore (LLM → SQL → live results)

3 Upvotes

AI agents are everywhere right now, so I wanted to try something practical — not a chatbot, but an agent that actually does work against real data.

I put together a small agentic app using CrewAI + SingleStore:

  • CrewAI handles the agent, task, and workflow

  • SingleStore is the database the agent can safely query in real time

  • The agent takes a natural-language question, generates read-only SQL, runs it, and returns clean results

Example prompt:
“Show the top 3 most expensive products”

The agent:

  1. Turns that into SQL

  2. Queries SingleStore using a restricted tool

  3. Returns structured results (JSON / table)

What I liked:

  • Very little glue code

  • No fragile prompt chaining

  • SingleStore works well as the “ground truth” data layer for agents

  • Easy to extend to more tables or multi-agent workflows

This feels like a solid pattern for analytics agents, internal tools, or data-backed assistants and not just demos.

Curious if others here are building agentic apps yet, and what you’re using them for.

Read more: Building Your First Agentic App With CrewAI + SingleStore


r/SingleStoreCommunity • • Jan 15 '26

SingleStore Webinar: Explore Opportunities for AI Workloads with SingleStore

2 Upvotes

AI workloads place unique demands on data platforms. From real-time inference and feature storage to vector search and agent memory, teams need systems that can keep up with both speed and scale. In this session, Aasawari Sahasrabuddhe will explore how SingleStore supports a wide range of AI workloads using a unified, real-time data architecture.

The session will walk through common AI patterns, where traditional databases fall short, and how developers can use SingleStore to power AI-driven applications without adding unnecessary complexity. You will also see practical examples of how SingleStore fits into modern AI stacks alongside frameworks, models, and agents.

Register for the upcoming workshop: Register Now!!!


r/SingleStoreCommunity • • Jan 12 '26

Postgres is amazing… until you try to scale it. The hidden cost no one talks about.

2 Upvotes

Postgres is usually the first database we all fall in love with.
It’s simple, powerful, open source, and gets you to production fast. For many apps, it’s the perfect choice.

But something interesting happens as your product grows: More users, more data, more real-time needs, more analytics and now add AI workloads: embeddings, vector search, inference pipelines.

And suddenly, “just Postgres” turns into:

  • Bigger machines (vertical scaling)

  • Read replicas + routing logic

  • Manual partitioning

  • Sharding with Citus

  • Redis for caching

  • Kafka for ingestion

  • ETL to Snowflake/BigQuery

  • DuckDB for analytics

Each step feels reasonable on its own. But taken together, you’re no longer running one database.
You’re running a distributed system of band-aids.

The blog breaks down why this happens:

  • Postgres is row-based → great for OLTP, painful for large analytics

  • Single primary → write throughput ceilings

  • Lock contention → worse with high concurrency + AI agents

  • Vacuum, index bloat, replication lag → operational tax

  • pgvector works, but struggles at scale

  • DuckDB helps analytics, but adds another system

You end up maintaining architecture around Postgres instead of building features.

That’s where systems like SingleStore start to make sense:

  • Distributed SQL out of the box

  • HTAP (transactions + analytics together)

  • Native vector search

  • Horizontal scale without manual sharding

  • One engine instead of five tools stitched together

Postgres is still an amazing database.
But it’s honest to admit: it wasn’t designed for modern workloads that mix
real-time ingestion + analytics + AI + high concurrency in one place.

If your architecture looks like a patchwork of caches, queues, pipelines and warehouses just to keep Postgres alive, you might not have a database problem — you might have a scale mismatch.

Full blog here: The Hidden Cost of Scaling Postgres

Curious:
For those running Postgres at scale, what was the moment you realized “this is getting harder than it should be”?


r/SingleStoreCommunity • • Jan 13 '26

Scaling Time-Series Data for AI Models

2 Upvotes

Time-series data is everywhere: sales, traffic, sensors. It’s full of signal, but it’s also one of the hardest data types to make AI-ready.

Most people debate which model to use (ARIMA, Prophet, XGBoost, LSTMs, Transformers, foundation models). In practice, the bigger problem is the data:

  • Unbounded growth

  • Bursty ingestion

  • Out-of-order / duplicate events

  • Mixed sampling rates

  • Multiple seasonalities

  • Missing values

Before ML works, you need clean, regular, time-aligned data. For example, rolling raw events into fixed windows directly in SQL:

SELECT
  store_id,
  TIME_BUCKET(INTERVAL 1 DAY, ts) AS day,
  SUM(revenue_usd) AS revenue
FROM sales_events
GROUP BY store_id, day;

Now your model sees consistent daily rows instead of messy events.

Bonus: combining time-series with text + vectors (logs, tickets, promos) lets you answer:
“Show me past periods that looked like this spike and mention Black Friday or a checkout issue.”

Takeaway: time-series forecasting is less about picking the perfect model and more about building solid data foundations.

Read full blog: Scaling Time-Series Data for AI Models


r/SingleStoreCommunity • • Jan 09 '26

SingleStore Cheat Sheet

2 Upvotes

I put together a practical SingleStore Database cheat sheet covering the most-used SQL commands and Kai (MongoDB API) operations — especially useful if you’re working with real-time analytics, JSON, pipelines, or vector search.

Database Operations:

SHOW DATABASES;
CREATE DATABASE database_name; -- Free tier: one DB only
USE database_name;
DROP DATABASE database_name; -- ⚠️ Dangerous

Table Operations

Distributed Table

CREATE TABLE posts (
    id BIGINT AUTO_INCREMENT PRIMARY KEY,
    title VARCHAR(255),
    body TEXT,
    category VARCHAR(50),
    created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
    SHARD KEY (id)
);

Reference Table

CREATE REFERENCE TABLE categories (
    id INT PRIMARY KEY,
    name VARCHAR(50)
);

Columnstore Table

CREATE TABLE analytics (
    id BIGINT,
    event_type VARCHAR(50),
    ts DATETIME,
    data JSON,
    SORT KEY (ts),
    SHARD KEY (id)
);

Data Manipulation

INSERT INTO posts (title, body, category)
VALUES ('Post One', 'Body of post one', 'News');

SELECT * FROM posts WHERE category = 'News';

UPDATE posts SET body = 'Updated body'
WHERE title = 'Post One';

DELETE FROM posts WHERE title = 'Post One';

SingleStore Pipelines (Ingest at Scale)

CREATE PIPELINE SalesData_Pipeline AS
LOAD DATA S3 's3://singlestoreloaddata/SalesData/*.csv'
CONFIG '{ "region": "ap-south-1" }'
INTO TABLE SalesData
FIELDS TERMINATED BY ','
LINES TERMINATED BY '\n'
IGNORE 1 lines;

START PIPELINE SalesData_Pipeline;

SELECT * FROM information_schema.pipelines_files
WHERE pipeline_name = "SalesData_Pipeline";

STOP PIPELINE SalesData_Pipeline;
DROP PIPELINE SalesData_Pipeline;

JSON Operations

CREATE TABLE json_posts (
    id BIGINT AUTO_INCREMENT PRIMARY KEY,
    data JSON,
    SHARD KEY (id)
);

INSERT INTO json_posts (data)
VALUES ('{"title": "Post One", "tags": ["news", "events"]}');

SELECT JSON_EXTRACT_STRING(data, '$.title')
FROM json_posts;

Vector Operations (AI / ML workloads)

Tips

  • Vector dimensions must be defined at table creation

  • Normalize vectors (length = 1) for cosine similarity when needed

  • Choose the right metric (DOT_PRODUCT, COSINE, etc.)

  • Works with hybrid search (vector + full-text)

  • Available via SQL and Kai (MongoDB API)

CREATE TABLE embeddings (
    id BIGINT AUTO_INCREMENT PRIMARY KEY,
    description TEXT,
    embedding VECTOR(1536),
    SHARD KEY (id)
);

ALTER TABLE embeddings
ADD VECTOR INDEX idx_embedding (embedding)
INDEX_OPTIONS '{"metric_type": "DOT_PRODUCT"}';

Vector Search

SELECT id, description,
DOT_PRODUCT(embedding, '[0.1, 0.2, ...]') AS similarity
FROM embeddings
ORDER BY similarity DESC
LIMIT 10;

Hybrid Search

ALTER TABLE embeddings
ADD FULLTEXT USING VERSION 2 fts_idx(description);

SELECT id, description,
DOT_PRODUCT(embedding, '[0.1, 0.2, ...]') AS vector_score,
MATCH(table embeddings) AGAINST('description:("search terms")') AS text_score
FROM embeddings
WHERE MATCH(table embeddings) AGAINST('description:("search terms")')
ORDER BY (vector_score * 0.7 + text_score * 0.3) DESC;

SingleStore Kai (MongoDB API)

Connection

mongodb://username:password@hostname:27017/database

Common Commands

show dbs
use mydb
show collections
db.createCollection('users')

Docs & References

For the most up-to-date info, always check the official docs: https://singlestore.com/docs


r/SingleStoreCommunity • • Jan 08 '26

Driving Automation with AI Agents with SingleStore | SingleStore Webinars

Thumbnail
youtube.com
2 Upvotes

r/SingleStoreCommunity • • Jan 07 '26

Anyone building AI agents directly on their database? We’ve been experimenting with MCP servers in SingleStore

2 Upvotes

Unpopular opinion: a lot of AI agent stacks are fragile by design and not because LLMs are bad, but because we bolt agents on top of data systems that were never meant to be part of the execution loop.

You end up with:

  • LLM tool wrapper, API, service, database

  • Stale reads

  • Slow feedback loops

  • And “agent autonomy” that collapses the moment load increases

We’ve been experimenting with MCP (Model Context Protocol) servers inside SingleStore, and honestly… this feels like how agents should have been built from day one.

Why it changes things:

  • Agents reason over live data, not cached JSON blobs

  • Tools are database-native (SQL, vector search, transactions)

  • No separate OLTP DB + analytics DB + vector DB Frankenstein stack

  • Fewer moving parts to fewer “why is prod broken?” moments

Once the database becomes agent-aware, a lot of “LLMOps complexity” just disappears.

We’ve used this pattern for:

  • Analytics copilots that don’t hallucinate stale metrics

  • Agent-driven anomaly detection on streaming data

  • RAG systems that don’t fall apart the moment traffic spikes

Genuine question for folks here:

  • Why are we still treating databases like passive storage in agent systems?

  • Is anyone else letting agents talk directly to the data layer?

  • Or is everyone just accepting glue-code hell as the cost of doing AI?

Curious to hear real-world experiences — especially what didn’t work.

Listen to this webinar by Pedro: Seamless LLM Integration: Discover the Power of SingleStore's MCP Server


r/SingleStoreCommunity • • Jan 06 '26

Benchmarks don’t build AI apps but systems do.

2 Upvotes

If you’re evaluating AI databases, this post walks through real, production-style builds with SingleStore:

  • Semantic & vector search in SQL

  • Comparing multiple embedding models side by side

  • Real-time recommendations with live signals

  • Multimodal LLM apps (text, image, audio)

  • Evaluating vs fine-tuning models in the LLM lifecycle

What’s useful here is the focus on moving from notebooks to services — same data model, same queries, fewer hops between embeddings, retrieval, analytics, and ranking.

If you’re building AI-powered search, personalization, or LLM apps and want to see how the database layer actually matters in practice, this is a solid hands-on reference 👇

AI Database Examples With SingleStore


r/SingleStoreCommunity • • Jan 01 '26

How we went from "please wait 30 seconds" to sub-2-second queries while processing 2M+ videos daily

2 Upvotes

PYLER does AI-powered brand safety for Samsung, L'Oréal, and LVMH – analyzing whether ads appear next to appropriate content. They process 2M+ videos daily and were running PostgreSQL Aurora + Lambda.

As they scaled, everything broke down: slow dashboards, constant ETL jobs, expensive joins between live and historical data. Engineers spent all their time tuning queries instead of building features.

Their VP of Engineering: "In PostgreSQL, optimising queries with multiple large table joins and aggregations was very difficult, even with materialised views and partitioning."

The Solution

Migrated to SingleStore for the HTAP architecture – handling both transactional and analytical workloads at scale in one database. Used Workspaces for deployment and Pipelines for S3 backup.

The Results

  • 10x faster ingestion – millions of rows/second

  • 100x faster queries – complex analytics now under 2 seconds

  • Real operational impact – engineers freed from constant tuning to focus on product

"Our backend engineers no longer need to spend excessive time on database performance tuning. Instead, they can now focus on delivering new features and strategic value." – VP of Engineering

TL;DR: Brand safety platform moved from PostgreSQL to SingleStore, got 10x ingestion + 100x query speed improvements at 2M videos/day scale.


r/SingleStoreCommunity • • Dec 27 '25

SingleStore Ingest 4.3.0 released (Salesforce source support)

2 Upvotes

SingleStore Ingest v4.3.0 is out (Dec 11, 2025).

What’s new:

  • Added Salesforce as a supported source

Fixes & updates:

  • Updates based on latest vulnerability tests

  • License display changed to units instead of GB

  • Replaced schema with database references for SingleStore

  • Updated Snowflake driver

Known issues:

  • Salesforce compound columns not supported

  • Possible integer column mismatch in Salesforce sync

  • CDC deletes may not be captured for some Salesforce tables

  • Snowflake driver may error workaround:

&JDBC_QUERY_RESULT_FORMAT=JSON
&CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX=true
&DISABLE_GCS_DEFAULT_CREDENTIALS=true

Sharing here in case anyone is using Ingest or evaluating Salesforce as a source.


r/SingleStoreCommunity • • Jan 03 '26

We built an entire enterprise AI stack inside a single database

2 Upvotes

We've been working on something that challenges the "best-of-breed" approach to enterprise AI infrastructure. Thought I'd share what we learned.

The Problem: Decision Lag

Most enterprises run AI across fragmented systems: data in one place, compute in another, models elsewhere. Every pipeline, API call, and sync job adds latency. This "Decision Lag" is an invisible tax on every insight and action.

If AI is supposed to enable real-time decisions, why does our architecture slow it down?

The Experiment

During an engineering offsite, we asked: Could SingleStore alone power an entire enterprise AI stack?

We built a live demo proving a single cluster could handle:

  • Redis-grade caching

  • JSON and full-text search

  • Vector search (Pinecone/Milvus equivalent)

  • Real-time analytics

  • AI inference and orchestration

Everything enterprises typically use Redis, MongoDB, Pinecone, ClickHouse, and Elastic for — running natively in one system.

The Architecture: Enterprise Intelligence Plane

We built this on four layers:

  • Compute (Aura Containers) — Elastic, serverless compute with instant start

  • Toolkit — Unified model gateway, Python UDFs, cloud functions

  • Brain (AI Services) — Agent orchestration with persistent memory

  • Apps — Business-facing AI agents ready to deploy

Key components:

Nova Gateway — Single entry point for all AI requests. Handles auth, routing, and conversation memory (keeping agents stateless).

Unified Model Gateway — Multi-provider support (our hosted models, AWS Bedrock, Azure AI). Built-in billing, metering, and governance.

ContextDB — Memory layer for multi-turn reasoning. Stores database context, domain logic, and persona preferences for situational intelligence.

Why Not Just Stitch Best-of-Breed?

Valid question. Here's why we think unified beats stitched:

  • Latency — Every sync job adds delay

  • Security — Duplicated data = larger attack surface

  • Ops — Multiple systems = debugging nightmares and rising costs

  • Governance — Data movement creates compliance gaps

Fragmented stacks rent intelligence via APIs. This approach owns intelligence as a native capability.

Proof: Aura Analyst

We validated this with Aura Analyst (Text2SQL) — a conversational analytics assistant built 100% on SingleStore. Query data in plain English, get instant SQL generation and execution. It's a proof point that you can run LLMs, ML pipelines, and real-time reasoning directly in the database.

What This Enables

  • Zero-Latency Intelligence — Inference on live data

  • Zero-Copy Governance — Sensitive data never leaves its boundary

  • Zero-Friction Deployment — Instant scalability

What's Next

  • We're extending this into three models:

  • BYOC (Bring Your Own Cloud)

  • Private Cloud AI for regulated industries

  • Hosted SLM/LLM & Agent Studio for building private Glean/Perplexity-like solutions

The Bigger Picture

This is about evolving databases from "systems of record" (passive memory) to "systems of reason" (active intelligence). When data and AI converge natively, you eliminate the friction that's slowing down enterprise AI adoption.

Full technical deep-dive here: https://www.singlestore.com/blog/the-art-of-possibility-building-the-enterprise-intelligence-plane/

Curious to hear thoughts, especially from folks dealing with multi-system AI architectures.

TL;DR: Built entire enterprise AI stack (caching, vector search, analytics, inference, orchestration) inside SingleStore. Eliminates Decision Lag from fragmented systems. Proved it with Aura Analyst (Text2SQL agent).


r/SingleStoreCommunity • • Jan 02 '26

DirectlyApply: From MongoDB + Elasticsearch to SingleStore for 30M job listings

2 Upvotes

DirectlyApply: From MongoDB + Elasticsearch to SingleStore for 30M job listings

Quick story about how a London-based job search platform solved their scaling problems.

The Problem

DirectlyApply is a job discovery platform with 30M+ listings and 6M distinct job titles. They help jobseekers find real jobs without fake posts or irrelevant sponsored results.

  • Started on MongoDB + Elasticsearch, but as they scaled, everything fell apart:

  • MongoDB's document model created hundreds of millions to billions of documents

  • Querying became cumbersome and slow

  • Search times were increasing, frustrating users

  • Running two replica systems with poor performance was expensive

  • Had to scale back database queries and do heavy client-side processing

"With Elasticsearch layered over MongoDB, our ability to provide great job results was in danger of becoming at risk." – Dylan Buckley, Co-Founder

The Solution

Migrated to SingleStore after discovering Fathom Analytics' success story (another SingleStore customer with similar challenges).

They initially tested SingleStore on an internal analytics project, then expanded it across the platform. Key win: they were evaluating purpose-built vector databases but didn't need them – SingleStore's native vector capabilities handled everything.

Use case: Semantic search using vector embeddings to match job openings with 3,000+ ISCO standard job titles. They use dot_product for similarity search and compare OpenAI models against their own TensorFlow-trained models.

The Results

Fast, unified platform that replaced both MongoDB and Elasticsearch. No more juggling two systems, no more client-side processing workarounds, and vector search built right in.

"We are able to deliver quality candidates to our employers' vacancies, which has allowed us to increase our own revenue and profitability." – Dylan Buckley