What Syncratic is
A Knowledge Assurance System
Syncratic reveals the relationships across data entities, their dependencies, and changes over time. This interweaves them into a governed living knowledge structure that people and other knowledge-dependent entities and workflows can reason over.
What counts as enterprise knowledge
Enterprise knowledge spans an information continuum.
Data → documents → conversations → events → knowledge → context → intelligence. Syncratic connects these forms while maintaining evidence, provenance, relationships, and organizational context.
Documents
Policies, contracts, filings, research
Syncratic provides governed ingestion of documents and enterprise repositories today: classification, relationships, deltas, and citations, with ACL-aware boundaries preserved end to end.
Live today
Structured data
Systems, transactions, operational datasets
Databases, ERP, transactions, and market data hold knowledge as structure. Syncratic is designed to bring structured systems into the same governed knowledge lifecycle as documents.
Designed for
Verbose unstructured
Transcripts, briefings, commentary
Long-form language contains entities, claims, relationships, decisions, commitments, contradictions, and emerging themes. Syncratic is designed to transform this information into structured, traceable knowledge while maintaining provenance to the underlying evidence.
Designed for
Continuous signals
Telemetry, markets, security events
Time-sensitive information is knowledge in motion. SignalOps turns versioned algorithms and normalized events into deterministic signals that carry their own evidence, live today for markets and security.
SignalOps today
Platform surfaces
One workspace, every knowledge motion
Each surface exists to make one kind of knowledge work inspectable: discovery, reasoning, relationship review, change review, and operations.
Search / Ask
A unified discovery-to-reasoning surface. Search finds evidence across accessible scopes; Ask reasons over it with citations, provenance, and memory threads.
Insights
Graph-derived relationship narratives: live streams, multi-source signals, and document deltas clustered into readable, subject-driven insights.
Explorer
Document inspection with metadata, graph context, and change history: see the evidence behind every answer at the document level.
Document Delta Engine
Version lineage and deterministic deltas. When a contract, policy, or filing changes, see what moved, when, and why it matters.
AI Gateway
Applications call Syncratic Ask through a governed API, with tenant policy, privacy checks, spend limits, and audit evidence on every call.
Connectors
Governed source synchronization with schedules, sync state, per-file visibility, and administrator-controlled configuration.
Privacy Engine
Runtime context governance that masks, reduces, or withholds sensitive evidence before it reaches a model; canonical artifacts stay intact.
Audit & Admin
Boundary diagnostics, event inspection, and operational traceability. RBAC-controlled administration of users, roles, licensing, and models.
Semantic search and retrieval
Retrieval that follows meaning
Syncratic decomposes every query into its semantic parts, so retrieval follows meaning across the enterprise corpus, at scale, through relationship structure.
The result is search that understands context: direct questions, reverse questions, and follow-ups all retrieve the right evidence, because the system models how facts connect.
- Hybrid retrieval: lexical, vector, and graph evidence, ranked together
- Document-family-aware enrichment for contracts, filings, cases, and datasets
- Direct, reverse, and follow-up questions all retrieve the right evidence
How a query is understood
Every query is decomposed into its semantic parts:
Knowledge association across subjects, objects, and verbs: the system understands relationship structure algorithmically.
Governed connectors
Unstructured sources in. Governed knowledge out.
Syncratic turns unstructured and semi-structured enterprise documents into governed, searchable, explainable, and evolving organizational intelligence. Enterprise systems (SharePoint libraries, Google Drive, OneDrive, Gmail, and file shares) participate as governed knowledge sources.
- ACL-aware SharePoint ingestion: source access signals travel with content, so downstream visibility respects what each user is allowed to see.
- File-share estates: deployment-mounted NFS, SMB, and CIFS shares ingest with governed sync, provenance, and downstream boundaries.
- A shared lifecycle: every connector runs the same governed flow of source-appropriate authorization, scoped synchronization, staged ingest, and continuous refresh.
Sources
- Google Drive
- Gmail
- Salesforce
- OneDrive
- SharePoint Online
- NFS / SMB / CIFS
Google Drive, Gmail, and Salesforce are live in production. OneDrive and SharePoint are supported as scoped deployment tracks when enabled.
Connector lifecycle
- Source-appropriate authorization, per provider
- Scoped synchronization with schedules you control
- Staged ingest with per-file state and retries
- Sync observability and stale-run recovery
Governance
RBAC and data boundaries, enforced at query time
Access control in Syncratic is enforced at query time across every store: documents, graph, and insights. Tenant and user scopes define what can be retrieved; object-level access defines what can be seen; role-based access governs who administers what.
- Identity through Keycloak/OIDC with role and identity context on every request
- Tenant/user scope and object-level access enforced across all data stores
- RBAC-controlled administrative surfaces: users, roles, licensing, models, privacy
- Privacy Engine gates sensitive evidence at the model context: mask, reduce, suppress, or deny
- Boundary diagnostics in Audit: see exactly when and why a boundary was applied
Principle
Every answer should be defensible. A system is production-ready when you can explain why it answered this way.
What boundaries mean here
A user searching in tenant scope sees only what object-level access permits: private material stays private, and cross-user leakage is prevented by boundary controls. The Privacy Engine protects model context while canonical artifacts stay intact.
Deployment posture
Sovereign by architecture, model-agnostic by design
Sovereign deployment
Offline-safe licensing and entitlement enforcement keep the deployment self-contained while premium capabilities stay governed and auditable. Run air-gapped, own your infrastructure, and keep operational control, with admin bootstrap, SMTP-backed invitations, license update, and readiness evidence included.
Model-agnostic by design
Separate enterprise knowledge from model dependency. The model layer is intentionally replaceable. SLMs and LLMs are replaceable execution components: model roles can be bound to private, deployment-local LLMs or external public endpoints, with a trust zone available to Privacy Engine policy. You choose the deployment posture per role, across model locations and providers. The knowledge architecture persists independently of whichever model reasons over it.
One platform, three functions
Three planes, one platform
Conceptually, everything Syncratic does belongs to one of three functions. The planes explain the platform as one system.
Control Plane
Governs access and production
Gateway, identity, tenant isolation, RBAC, policy, model routing, audit, observability.
Knowledge Plane
Acquires and maintains knowledge
Connectors, knowledge graph, classification, provenance, knowledge evolution.
Intelligence Plane
Produces contextual intelligence
Ask, Insights, SignalOps, reasoning, agents.
See how the planes map onto the deployment: the architecture, plane by plane.
What's included
Production capabilities, shipping today
- Evidence-based answers with source-aligned citations and provenance estimates
- Tenant and user data-boundary controls enforced at query time
- Role-based access for administrative surfaces, via Keycloak/OIDC identity
- Human-guided knowledge evolution: feedback becomes durable improvement
- Continuous, governed connector sync across approved enterprise sources
- API-first observability with audit trails and boundary diagnostics
- Sovereign deployment: offline-safe licensing and air-gapped operation
- Model-agnostic by design: bind model roles to private or public endpoints
- API-first access for applications and agents: the same governed path, permissions, and audit trail
Questions
Frequently asked
Which sources does Syncratic connect to?
Google Drive, Gmail, and Salesforce are live in production. OneDrive and SharePoint Online 365 are supported as scoped deployment tracks when enabled, and deployment-mounted NFS/SMB/CIFS shares are supported for file-share estates. Every source runs through the same governed connector lifecycle.
Where does our data live?
In your deployment. Syncratic runs as a tenant-controlled platform with Helm/K3s production posture; the workspace, its stores, and its licensing remain self-contained. There is no dependency on a vendor SaaS to operate.
Can we run Syncratic air-gapped?
Yes. Offline-safe licensing and entitlement enforcement are built in, so premium capabilities stay governed and auditable without external calls. Model roles can be bound to deployment-local LLMs for fully sovereign operation.
Do answers cite their sources?
Yes. Generation is citation-constrained: answers are built strictly on retrieved evidence with provenance estimates, and you can inspect the prompt evidence window to see exactly which evidence was admitted or excluded.
What happens when a source document changes?
The Document Delta Engine captures version lineage and deterministic deltas. Material changes surface in Insights and Explorer, including contract and procurement deltas, so review focuses on what actually moved.
Are we locked into one model provider?
No. The model layer is intentionally replaceable. Model roles (basic reasoning, deep reasoning, classification, evaluation) can be bound to private, deployment-local LLMs or external public endpoints, so you choose the deployment posture per role across providers.
Can applications and agents use Syncratic alongside people?
Yes. Every capability is an API surface: compact /api/v1 facades expose Search, Ask, Explorer, Graph, Insights, document deltas, and threads. Applications, automation, and agents call the same governed path a person uses, with owner-bounded permissions, the same privacy gates, and the same audit trail.
Governed knowledge assurance
See Syncratic on your own data.
A 30-day pilot: scoped ingest baseline in week one, adoption with citation review in week two, feedback-driven quality iteration in week three, and a value review in week four.