Curiosity

Curiosity

Home

Learn Curiosity Workspace

Build, query, and extend the graph + search + AI platform.

Deploy and manage

Roll out Curiosity to Docker, Kubernetes, or your cloud of choice.

Build enterprise AI apps

Ship domain-specific AI apps with custom UIs, endpoints, and connectors.

Model your data as typed nodes and edges with stable keys.

Query with text, vector, and hybrid retrieval — permission-aware.

Ground LLMs, embeddings, and agents in your own graph.

Compose UIs in C# with our front-end component library.

Transpile C# to JavaScript and run it in the browser.

Test, ingest, sync, and promote workspaces from any shell.

Open Source Projects

Browse every open-source project Curiosity maintains.

Support

Salesforce

Ingests Salesforce leads, contacts, accounts, opportunities, and custom objects.

variant=info text="CRM / business apps" variant=success text="OAuth" variant=success text="Maps owners"

What gets ingested

Element	Mapped to
Lead	`_Lead`
Contact	`_Contact`
Account	`_Account`
Opportunity	`_Opportunity`
Custom object	A node type derived from the SObject definition
Object owner	`_Contact` linked via `_OwnedBy`

Authentication

Type: Salesforce OAuth 2.0 (per-user). Stores a refresh token; the connector refreshes the access token before each run.

Access control mapping

Per-user — each connected user has an access group; ownership relations create per-owner links. Custom Salesforce sharing rules are not modeled directly today.

Sync cadence

Default cron: daily at 00:00 UTC.
Incremental sync: LatestUpdated per object type. Concurrent runs are guarded with per-user locks so two workers can't double-write the same account.

Notable

The connector creates _Contact nodes for every Salesforce user it encounters as an owner, so cross-source queries (e.g. "every artifact owned by Alice across Salesforce + Jira + GitHub") work naturally.