Quill
by RavenDB
Production AI agents on the SQL database you already run — no migration, no assembled stack
Quill is RavenDB's context layer for putting production AI agents on top of existing PostgreSQL, SQL Server or MySQL systems without migrating them. It connects via change data capture, generates embeddings, vector indexes and full-text search automatically, and adds governed per-agent permissions, persistent memory and multi-channel delivery, so teams ship agents in weeks rather than assembling a RAG stack.
Quill is RavenDB's context layer for putting production AI agents on top of SQL databases a company already runs, without migrating the system of record. It connects to PostgreSQL, Microsoft SQL Server or MySQL through change data capture — passive log reads rather than table scans or heavy queries against the live system — and maintains a continuously synchronised, AI-ready copy alongside it. From that copy Quill automatically generates embeddings, vector indexes and full-text search, so there is no separate vector database to run, and layers persistent cross-session memory, retrieval-augmented generation and the agents themselves on top. Access is governed per agent: each agent is synced only the slice of data it is authorised to see, with permissions defined independently of the underlying database's access controls, which is the part most hand-built RAG deployments get wrong and only discover after an agent answers a question it should not have been able to answer. Quill is model-agnostic — bring your own LLM provider and switch later — and surfaces agents through web chat, WhatsApp, Telegram, Slack and Discord. It runs in RavenDB's cloud, self-hosted, or fully on premises including air-gapped environments, so data residency and compliance control stay with the customer. RavenDB launched Quill on 8 September 2026, pitching roughly six weeks to production against the 18 to 24 months a comparable in-house build typically takes across security review, infrastructure and re-indexing. The vendor is not a startup: RavenDB was founded in 2010 by CEO Oren Eini and CTO Paweł Pekról, ships a NoSQL document database it reports is used by more than 12,000 customers across 50 industries, and now sells Quill alongside its on-premise, cloud and edge database products. Pricing is published and metered on writes rather than seats, with a three-month full-feature free trial.
The CTO or VP of engineering at a company whose operational data sits in a legacy PostgreSQL, SQL Server or MySQL estate, who has an AI mandate from the board and no appetite for an 18-month data-modernisation project first.
A governed, continuously synced AI copy of the existing database — embeddings, vector search, memory and agents included — without touching the system of record or hiring a RAG platform team.
At a Glance
- Category
- Enterprise Search & Knowledge
- Pricing
- Subscription, Usage-based
- Target Market
- CTOs, VPs of Engineering, Enterprise Architects, Data Engineers, CIOs
- Deployment
- Cloud-first, Self-hosted, Hybrid
- Founded
- 2010
- Headquarters
- Hadera, Israel
- Customers
- RavenDB reports 12,000+ customers across 50 industries for its database products; Quill's own customer count is not public, with Albos Technologies and Holdings named as an early adopter
Key Features
- ✓CDC connection to existing SQL
Connects to PostgreSQL, SQL Server or MySQL via change data capture with passive log reads, so the production database sees minimal load.
- ✓Automatic AI pipeline
Generates embeddings, vector indexes and full-text search from the synced data, removing the need to run a separate vector database.
- ✓Governed per-agent exposure
Each agent is synced only its authorised slice of data, with permissions set independently of the source database's access controls.
- ✓Persistent memory
Context carries across sessions, with long-term memory, retention policies and conversation forking and rewinding on higher tiers.
- ✓Bring your own model
Works with any LLM provider and lets teams switch models later without rebuilding the retrieval and governance layer.
- ✓Multi-channel delivery
Agents are exposed through web chat, WhatsApp, Telegram, Slack, Discord and voice without building a separate front end per channel.
- ✓On-premises and air-gapped deployment
Runs fully in the customer's environment so regulated buyers keep data residency and compliance control in house.
Capabilities
Use Cases
- •Customer support agent over legacy order data
Expose order, billing and account tables to an agent that answers customer questions without migrating the transactional system.
- •Internal knowledge agent across several databases
Unify multiple SQL sources into one context layer so one agent can answer questions spanning systems that never talked to each other.
- •Regulated on-premises deployment
Run retrieval, memory and agents inside an air-gapped environment where sending enterprise data to a hosted AI vendor is prohibited.
- •Replacing an in-house RAG build
Swap a hand-assembled CDC, embedding, vector-store and permissions stack for one product, cutting time to production from many months to weeks.
- •Messaging-channel agents
Deliver the same governed agent through WhatsApp, Slack or Telegram for field staff and customers without separate integrations.
Ideal For
Best For
- ✓Deploying customer or internal support agents over legacy SQL systems that predate embeddings and vector search
- ✓Teams with no dedicated AI platform engineers who need retrieval, memory and governance as a product rather than a build
- ✓Regulated and air-gapped environments that need agents on premises with residency retained in-house
- ✓Unifying several separate SQL sources behind one context layer feeding multiple AI applications
- ✓Replacing a hand-assembled stack of CDC pipeline, embedding job, vector database and permissions glue
Not Ideal For
- ✗Estates built on Oracle, DB2, mainframe or NoSQL sources — Quill's CDC connectors cover PostgreSQL, SQL Server and MySQL only
- ✗Organisations that cannot accept a second synchronised copy of production data, since CDC replication adds a governance and residency surface even when self-hosted
- ✗Buyers who need a proven track record: Quill launched on 8 September 2026 with one named early adopter and no independent reviews anywhere yet
- ✗Chatty multi-agent workloads on a fixed budget, because agent messages count as billable write units and can push a plan past its allowance unpredictably
Deployment
Market & Ratings
RavenDB reports 12,000+ customers across 50 industries for its database products; Quill's own customer count is not public, with Albos Technologies and Holdings named as an early adopter
Market Analysis
Pros
- ✓No migration required — connects to the existing PostgreSQL, SQL Server or MySQL system of record and leaves it authoritative
- ✓Whole stack in one product: CDC, embeddings, vector index, full-text search, memory, agents and delivery channels
- ✓Transparent published pricing with free reads and an unusually generous three-month full-feature trial
- ✓Governance is per agent and independent of database ACLs, which is exactly where hand-built RAG deployments leak data
- ✓On-premises and air-gapped deployment available, backed by a vendor that has shipped production database software since 2010
Cons
- ✗Launched 8 September 2026 with no independent validation — no G2, Capterra or TrustRadius entry, and a Hacker News search for Quill returns zero results
- ✗Change data capture means a second synchronised copy of production data, which is an extra attack surface and an extra residency question even on-premises
- ✗Connector coverage is narrow: PostgreSQL, SQL Server and MySQL only, so Oracle, DB2, mainframe and NoSQL estates are out of scope
- ✗Write-request-unit billing counts agent messages as writes, so conversational and multi-agent workloads have a cost curve that is hard to forecast before running them
- ✗One named early adopter (Albos Technologies and Holdings) is the only public reference, so there is no evidence yet of behaviour at large enterprise scale
- ✗The vendor's own six-weeks-versus-18-months claim is marketing, not a measured benchmark, and should be treated as such in a business case
Pricing
Free trial
$0
- ✓3 months
- ✓All Pro features
- ✓Unlimited write request units
Starter
From $499/mo
- ✓1M write request units included
- ✓$0.60 per additional 1,000 WRU
- ✓Short-term memory
- ✓Image and document processing
- ✓Sub-agents
- ✓Email support
Pro
From $1,799/mo
- ✓8M write request units included
- ✓$0.30 per additional 1,000 WRU
- ✓Long-term memory and retention policies
- ✓Agentic watchdogs
- ✓Conversation forking and rewinding
- ✓Email and phone support
Enterprise
Contact for pricing
- ✓Everything in Pro
- ✓Dedicated support and SLA
- ✓SSO
- ✓On-premises and air-gapped deployment
- ✓Custom governance
Metered in write request units rather than seats: every document write counts as one WRU — ingesting a record, updating data, or an agent sending a message — while reads and queries are always free and document size and ingestion speed do not affect the bill. Starter is $499/month for 1M WRU with $0.60 per extra 1,000; Pro is $1,799/month for 8M WRU with $0.30 overage; Enterprise is quoted. LLM token costs are billed separately by whichever model provider you bring, and the three-month trial includes all Pro features with unlimited WRU.
Security & Compliance
Sources
This page was written from 5 sources, 2 on domains other than ravendb.net.
Stay Ahead of the Curve
Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.
SubscribeRelated Products
Twin1 AI
A permission-aware AI twin for every professional, networked so expertise moves across the firm
DeepJudge
Institutional-knowledge search and AI workflows for law firms, with no data migration
Jedify
The context graph for enterprise AI — give agents full business context, not just metadata.
LinqAlpha
Multi-agent AI research terminal for institutional investors