RushDB

# RushDB > Turn operational data into connected, searchable context in minutes—without a separate graph database, vector store, or synchronization layer. This index is generated at request time from the current website configuration and published CMS records. Use the linked documentation for exact API details. ## Core Pages - [Homepage](https://rushdb.com/): Open-source context infrastructure for agents, applications, and analytics, with connected records, live schema, semantic retrieval, and operational queries through one API. - [Context layer](https://rushdb.com/context-layer): What a shared context layer is, when it fits, and how RushDB consolidates connected operational context. - [Architecture](https://rushdb.com/architecture): How ingestion, live schema, relationships, semantic indexes, APIs, and deployment fit together. - [Applications solution](https://rushdb.com/solutions/applications): Build operational applications on the same connected context used by agents and analytics. - [Operational analytics solution](https://rushdb.com/solutions/analytics): Analyze current values, relationships, and evolving schema without a second operational model. - [Features](https://rushdb.com/features): RushDB capabilities and the infrastructure work they replace. - [Guides](https://rushdb.com/guides): Evergreen explanations of AI memory, graphs, retrieval, and vector search tradeoffs. - [Use cases](https://rushdb.com/use-cases): Implementation blueprints for agents, GraphRAG, an […truncated]