Connect with meaning
Define record types and relationships with named participants. Keep an account, product, and plan together in one subscription.
Explore the data modelA graph database for connected data
Connected data.
Clearer answers.
Connected data and source context, traceable evaluation, and controlled changes for applications and agents. Keep your records, relationships, and history together.
The demo runs in this browser. No account or API key.
A workspace you can actually use.
Import records, define relationships, run queries, and inspect earlier revisions. Enable JavaScript to try the sample here, or read the walkthrough.
Read the walkthroughYour data is the interface. Select a record, run a query, or change the sample.This preview is separate from your full demo workspace.
The whole relationship matters
More than records.
The context between them.
A customer subscribes to a product. The product depends on a service. A change to that service matters somewhere else. Model the connection, then ask the question.
Keep change in view
Update a record and inspect what changed. Run the same query against an earlier revision without overwriting the present.
See how history worksFollow the sources
Move from a result to its records, relationships, and retained inputs. Understand where the data came from, not just what matched.
Trace the evidenceBuild from the ground up
Your model.
Your data. Your questions.
Start with the connected sample or build an empty workspace. The graph and query results follow the data you put into it.
Define what matters.
Create record types, fields, and relationships with explicit participant roles.
Open the modelBring in the records.
Import CSV or JSON, or load the sample datasets one source at a time.
Explore sourcesFollow the connections.
Filter the records, traverse relationships, and inspect the evidence for each match.
Run a questionSee what changed.
Edit the underlying data, rerun the query, and compare earlier revisions.
Inspect historyDifferent sources. One connected model.
Ask the question that
crosses the boundaries.
Which enterprise customers depend on a degraded service? The answer needs more than a customer table. Connect the directory, subscriptions, products, and service observations to follow the complete path.
Walk through the exampleCustomer directory
Accounts and the people behind them
Application catalog
Products, plans, and service dependencies
Subscription ledger
Account + product + plan
Service observations
Recorded incidents and subsequent updates
One connected sample workspace
Built around application questions
Different products.
The same need for context.
Use the database model as the foundation. Keep your domain logic, integrations, and customer experience in your application.
Keep the model connected.
Make ownership, subscriptions, and product relationships explicit instead of reconstructing them in every view.
Connected applicationsUnderstand the impact.
Follow a service condition through dependencies to the products and customers connected to it.
Dependency analysisGive context a history.
Assemble source-backed records for an application or agent, with earlier states available to inspect.
Persistent contextA few practical questions.
What can I do in the demo?
Create a model, import JSON or CSV, add and edit records, connect participants, run queries, inspect sources, compare revisions, and export your workspace. It is a working local application, not a video or a guided click-through.
Can I start with my own data?
Yes. Choose “Build from empty” and define your own types, or import a flat JSON or CSV dataset. Use synthetic or non-sensitive test data. Your workspace is stored in this browser on a best-effort basis; export it to retain a backup.
Is this connected to a hosted SolarflareDB account?
No. The demo runs a local reference engine in your browser. It does not create a hosted account, provide a production API, or demonstrate production access controls. The demo guide explains the scope.
Does SolarflareDB only support agent-memory use cases?
No. The product direction is a reusable database for connected, changing application data. Agent context is one use case, alongside connected applications and dependency analysis.
Build the model. Ask the question.
Explore the connected sample or start with your own records.