rushdb
ProductSolutionsDevelopersPricingResourcesCompanyGitHub
Sign InStart building

Understand

Context layer

Why shared operational context needs its own infrastructure layer.

Product overview

Create, inspect, retrieve, use, and operate connected context.

Architecture

See the data model, query surfaces, and deployment boundaries.

Build

Ingestion and live schema

Turn evolving payloads into typed, inspectable structure.

Graph and relationships

Preserve known links and review suggested patterns.

Semantic retrieval

Combine similarity, exact filters, and connected records.

Smart Search

Generate inspectable SearchQuery from natural language.

Operate

Query and analytics

Use one query shape across records, schema, and metrics.

Deployment options

Use managed cloud, an External Database, or self-hosted infrastructure.

Security

Review privacy, controls, and deployment posture.

Explore the product →

Primary workflows

Agent context and memory

Durable state, decisions, tool output, and semantic recall.

GraphRAG

Retrieve connected evidence, not only similar chunks.

Applications

Build operational software on connected context.

Operational analytics

Analyze current values, relationships, and change.

Solution patterns

Customer intelligence

Connect customer, product, support, and event data.

Search and discovery

Power semantic, faceted, and connected discovery.

Evidence and compliance

Keep operational evidence connected and inspectable.

Blueprints

Agent systemsConnected applicationsAnalytical systemsAll blueprints
Explore all solutions and blueprints →

Documentation

Concepts, tutorials, deployment, and API guides.

Quickstart

Create a project and run your first query.

TypeScript SDK

Type-safe access for browser and Node.js applications.

Python SDK

Sync and async access for services and data workflows.

MCP server

Expose RushDB operations to MCP-compatible clients.

Agent skills

Install task guidance for memory, querying, and modelling.

Open documentation →

Guides

Evergreen explanations and implementation paths.

Comparisons

Evaluate RushDB against graph, vector, and memory tools.

Blog

Product updates and technical articles.

Architecture

Understand the data path and current boundaries.

Changelog

Follow product and platform releases.

LMPG research

Separate the property-centric implementation from research direction.

Explore resources →

Contact

Discuss product, architecture, or enterprise requirements.

Security

Security, privacy, and responsible disclosure.

Open source

Review the source, open issues, and contribute.

Contact RushDB →

Cookie Policy

Effective date: June 17, 2026

This Cookie Policy explains how Collect Software Inc. ("RushDB", "we", "us", or "our") uses cookies and similar technologies when you visit rushdb.com, use RushDB Cloud, use app.rushdb.com, or interact with related RushDB services.

This policy should be read together with our Privacy Policy and Terms of Service.

What Cookies Are

Cookies are small text files placed on your device when you visit a website. Websites and applications use cookies, local storage, and similar browser technologies to remember information, keep sessions secure, measure usage, and improve product functionality.

In this policy, "cookies" includes cookies, local storage, session storage, pixels, tags, SDK storage, and similar browser or device technologies.

Types of Cookies and Storage We Use

Necessary cookies

Necessary cookies and storage are required to operate RushDB websites and cloud services. They may be used to:

  • keep you signed in;
  • protect authentication, administration, and account sessions;
  • remember security, consent, and interface state;
  • route requests and maintain service reliability;
  • prevent fraud, abuse, or unauthorized access.

These cookies are required for the service to work and cannot be disabled through our cookie banner.

Preference and functional storage

We may use browser storage to remember choices you make, such as:

  • theme preferences;
  • cookie consent choices;
  • interface preferences;
  • language or documentation display preferences.

For example, rushdb.com stores cookie consent state in local storage and uses that choice to update analytics consent.

Analytics cookies

We use Google Tag Manager and Google Analytics-style events to understand website and product usage, improve pages, measure conversion, and debug user flows.

Analytics may include events such as page views, CTA clicks, pricing plan clicks, signup-start events, documentation clicks, blog interactions, language-switch events, and limited code-copy events.

rushdb

Open-source context infrastructure for agents, applications, and analytics, with connected records, live schema, semantic retrieval, and operational queries through one API.

GitHubDiscord

Product

Context layerProduct overviewArchitecturePricingSecurityDeployment

Solutions

Agent contextGraphRAGApplicationsOperational analyticsBlueprint library

Developers

DocsQuick startAPI reference

© 2026 Collect Software Inc.

PrivacyTermsCookies
TypeScript SDK
Python SDK
MCP server
Agent skills

Resources

GuidesComparisonsBlogChangelogOpen sourceContactSelf-hosting

Where required, analytics storage is denied by default until you accept cookies through the cookie banner. If you decline cookies, analytics storage remains denied.

Error tracking and diagnostics

We may use tools such as Sentry or similar diagnostics providers to identify errors, crashes, and performance issues. These tools help us improve reliability and troubleshoot technical problems.

Diagnostic events may include technical information such as browser type, device information, page URL, error stack traces, timestamps, and limited context needed to reproduce or understand an issue. We do not intentionally send Customer Content to diagnostics providers.

Payment and billing cookies

If you use paid RushDB Cloud plans, checkout, billing portal, or payment workflows, payment processors such as Stripe may set cookies or use similar technologies to:

  • process payments;
  • prevent fraud;
  • manage checkout and billing portal sessions;
  • comply with payment, security, and legal requirements.

Stripe and other third-party providers process their own cookies under their own policies.

How We Use Cookies

We use cookies and similar technologies to:

  • provide and secure RushDB websites and services;
  • authenticate users and maintain secure sessions;
  • remember consent, theme, and interface preferences;
  • measure website and product usage;
  • understand which pages, documentation, and pricing flows are useful;
  • improve performance, reliability, and user experience;
  • detect, troubleshoot, and fix errors;
  • support billing, checkout, and payment workflows.

Third-Party Providers

Cookies and similar technologies may be set by RushDB or by third-party providers we use to operate the service, including:

  • analytics and tag-management providers, such as Google Tag Manager and Google Analytics;
  • error tracking and diagnostics providers, such as Sentry;
  • payment processors, such as Stripe;
  • authentication or infrastructure providers used to provide RushDB Cloud.

These providers may process information according to their own privacy and cookie policies.

Your Choices

When the cookie banner is shown, you can accept or decline non-essential cookies.

If you accept, analytics consent is updated to allow analytics storage. If you decline or dismiss the banner, analytics storage remains denied. You can also control cookies through your browser settings.

Most browsers allow you to block or delete cookies. If you block necessary cookies, some parts of RushDB may not work correctly, including account login, dashboard sessions, checkout, or security features.

Browser cookie controls are usually available here:

  • Google Chrome
  • Mozilla Firefox
  • Safari
  • Microsoft Edge

You can also use the Google Analytics Opt-out Browser Add-on for supported browsers.

Do Not Track

Some browsers offer "Do Not Track" signals. There is no common industry standard for how websites should respond to these signals, so RushDB does not currently respond to them separately. We use the cookie banner and browser controls described above.

Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in our services, cookie practices, providers, legal requirements, or operational needs. If we make material changes, we will update the effective date and provide notice where required.

Contact

Collect Software Inc.

Email: hi@rushdb.com

Website: https://rushdb.com