Platform reference
One page per platform in the Synedrix OS tech stack: what it is, what it is normally used for, and how and why Synedrix OS uses it.
These pages are descriptive reference, not normative specification. Platform responsibilities are set by Tech Stack and the layer assignments by Layer Taxonomy Table. Where a page here and a canonical document in docs/os/ disagree, the canonical document wins and the page is a bug.
Every factual claim about a third-party platform on these pages is sourced from that platform’s official documentation. Each page carries an Official documentation section so the claims can be checked.
The twelve platforms
Ordering follows canonical/architecture.yaml, the machine-readable facts layer.
| # | Platform | OS layer | Role |
|---|---|---|---|
| 1 | n8n | 3 | Orchestration |
| 2 | LangGraph | 4 | Agent runtime |
| 3 | Hookdeck | 8 | Ingress gateway |
| 4 | Hookdeck Outpost | 8 | Egress gateway |
| 5 | Redis | 7 | Coordination bus, hot state |
| 6 | Supabase PG17 | 7 | Canonical relational truth |
| 7 | QuestDB | 7 | Temporal data |
| 8 | Neo4j | 7 | Context graph, lineage |
| 9 | Qdrant | 7 | Semantic memory |
| 10 | Langfuse | 10 | LLM engineering |
| 11 | PostHog | 10 | Behavioural analytics |
| 12 | Grafana LGTM Stack | 10 | Operational monitoring |
Conditional component. Local model inference (Ollama / vLLM) is active in deployment Modes 2 and 3 only and is not counted among the twelve. It is specified in Tech Stack §12 and Deployment Model Spec.
Lab components
Neither counted among the twelve nor conditional — lab components are third-party software under time-boxed evaluation in the governed lab lane, running in structural isolation from every production system. They are not part of the tech stack and are never citable as authority by a canonical document.
| Component | Role | Evaluated under |
|---|---|---|
| EverOS | Local-first agent-memory runtime | LAB-001 |
| Semantica | GraphRAG / knowledge-graph toolkit | LAB-002 |
| Laya | System One decision model, self-hosted | LAB-003 |
| Jev | System One decision model, managed API | LAB-003 |
| LanceDB | EverOS’s embedded vector index | LAB-001 |
| SQLite | EverOS’s embedded relational state | LAB-001 |
How to read a platform page
Each page follows the same shape:
| Section | What it answers |
|---|---|
| What it is | The platform in its own documentation’s words, with core concepts defined |
| What it is normally used for | General industry usage, independent of Synedrix OS |
| How Synedrix OS uses it | What it owns, what it explicitly does not own, and how it is operated |
| Why | The rationale for selecting it, tied to the principles and architecture decisions |
| Deployment and licensing | Self-hosting paths and the verified licence position |
| Official documentation | Primary sources for every claim on the page |
| Related Synedrix OS documents | The canonical specifications the platform touches |
The what it does not own table is the part worth reading closely. Non-overlapping responsibility is the design rule for this stack, and that table is where each boundary is stated.
Open items
Several pages carry an Open item callout where a platform’s verified licence or self-hosting position does not match what Tech Stack currently records. These are flagged, not silently corrected — the canonical document is the place to resolve them, and some require a product decision rather than an edit.
Synedrix OS · Platform reference · index