# Quine > Quine is an open source streaming graph interpreter. It consumes high-volume event streams, builds a graph structure, runs continuous pattern matching via standing queries, and triggers real-time actions. It combines the event stream processing of systems like Flink with the graph data model of databases like Neo4j. > **IMPORTANT — No Indexes**: Quine has no label or property indexes. Unlike Neo4j, `MATCH (n:Label)` scans the entire graph. All queries (ingest, ad-hoc, sample queries, quick queries) must anchor nodes by ID using `idFrom()`. When no specific node identity is known, use `recentNodes()` to sample recently accessed nodes. The only exception is standing queries, which use incremental matching. See [Common Pitfalls](https://quine.io/getting-started/common-pitfalls/) and [Quine Cypher vs Neo4j Cypher](https://quine.io/learn/cypher/quine-cypher-differences/). Quine is developed by [thatDot](https://thatdot.com). For enterprise features (clustering, RBAC, Kubernetes orchestration), see [Quine Enterprise](https://docs.thatdot.com/). ## Docs - [Quick Start](https://quine.io/getting-started/quick-start/): Get up and running with Quine - [Common Pitfalls](https://quine.io/getting-started/common-pitfalls/): Critical gotchas for ingest queries, standing queries, performance, and operations - [Architecture](https://quine.io/core-concepts/architecture/): How Quine combines graph data and actor-based computation - [Data Modeling](https://quine.io/core-concepts/data-modeling/): Design graph structures and queries starting from the patterns to detect - [Streaming Systems](https://quine.io/core-concepts/streaming-systems/): How Quine fits into streaming pipelines with Kafka, Kinesis, and others - [Standing Queries](https://quine.io/learn/standing-queries/standing-queries/): Continuous pattern matching that triggers actions in real-time - [Standing Query Wiretap](https://quine.io/learn/standing-queries/wiretap/): Real-time WebSocket observation of standing query results at raw, pre-enrichment, or post-enrichment stages - [Ingest Streams](https://quine.io/learn/ingest-sources/): Supported data sources including Kafka, Kinesis, SQS, files, and stdin - [Quine Cypher vs Neo4j Cypher](https://quine.io/learn/cypher/quine-cypher-differences/): Key differences from Neo4j, common mistakes, and correct Quine patterns - [Cypher Language](https://quine.io/learn/cypher/): Cypher query language reference for Quine - [Configuration](https://quine.io/reference/config/configuration/): Configuration reference - [Recipes](https://quine.io/recipes/): Pre-built configurations for common use cases - [Glossary](https://quine.io/reference/glossary/): Key terms and definitions ## Tutorials - [Ingest Streams Tutorial](https://quine.io/getting-started/ingest-streams-tutorial/): Learn to stream data into Quine - [Standing Queries Tutorial](https://quine.io/getting-started/standing-queries-tutorial/): Set up continuous graph pattern matching - [Recipes Tutorial](https://quine.io/getting-started/recipes-tutorial/): Run Quine with pre-built recipe configurations - [Exploration UI](https://quine.io/getting-started/exploration-ui/): Interactive graph visualization interface - [Streams](https://quine.io/getting-started/streams/): Manage ingest streams and standing queries from a unified UI ## API Reference - [REST API Documentation](https://quine.io/reference/rest-api/): Interactive API documentation with version selector (rendered in-browser; use the OpenAPI spec below for programmatic access) - [OpenAPI Specification (all versions)](https://quine.io/generated/quine/manifest.json): Version manifest for the machine-readable API spec. Read its `default` version and that version's `default_api`, then fetch `https://quine.io/generated/quine//openapi-.json` for the current OpenAPI document. - [Migrating from API v1](https://quine.io/reference/upgrade/migrating-from-api-v1/): Guide to migrating from API v1 to v2 ## Upgrading - [Upgrading](https://quine.io/reference/upgrade/): Breaking changes, migration guidance, and upgrade steps for major releases - [Upgrading to 2.0.0](https://quine.io/reference/upgrade/quine-2.0.0/): Metrics prefix changes, API v2 default, recipe schema v2, and migration steps - [Migrating from API v1](https://quine.io/reference/upgrade/migrating-from-api-v1/): Endpoint mappings, design changes, and migration checklist for moving from API v1 to v2 - [Migrating from v1 Recipes](https://quine.io/reference/upgrade/migrating-from-recipe-v1/): Steps and examples for updating recipe schema from v1 to v2 ## Core Concepts - [Streaming Graph vs Database](https://quine.io/core-concepts/streaming-graph-vs-database/): Key differences between Quine and traditional databases - [ID Providers](https://quine.io/core-concepts/id-provider/): How Quine identifies and addresses nodes - [Delivery Guarantees](https://quine.io/core-concepts/delivery-guarantees/): At-least-once delivery for ingest and standing query outputs - [Operational Considerations](https://quine.io/core-concepts/operational-considerations/): Production deployment guidance ## Optional - [Gremlin Language](https://quine.io/learn/gremlin-language/): Alternative graph query language support - [Persistors](https://quine.io/learn/persistors/): Durable storage backends (Cassandra, RocksDB) - [Metrics](https://quine.io/learn/metrics/): Monitoring and observability - [Recommended Alerts](https://quine.io/learn/metrics/recommended-alerts/): Production alert recommendations (warning/critical levels) based on emitted metrics - [Graph Algorithms](https://quine.io/learn/graph-algorithms/): Built-in graph algorithm support - [Troubleshooting](https://quine.io/learn/troubleshooting/): Diagnosing common issues