Skip to article
/ docs

Search documentation

Popular starting points. Search all 37 articles.

  • Get startedProduct availability and preview limitationsUnderstand what works in the frontend and which product capabilities are not connected yet.
  • Get startedBuild your first RAG pipelineBuild and inspect your first seven-node Basic RAG graph and learn what validation means.
  • Build pipelinesBasic RAG and Hybrid Search templatesCompare Ragify's two starting graphs and decide which pattern to explore.
  • Node referenceUnderstand the node libraryBrowse the ten registered node types by role in the workflow.

↑ ↓ to navigate · Enter to open · Esc to close

Back to Ragify ↗
On this page

Documentation

Current limitation

Session state and persistence

Understand what remains in an editor session and what is not saved remotely.

Ragify's current graph state belongs to the active editor session. It is not connected to an authenticated backend account or a persistent pipeline database.

What this means #

You can interact with and modify the graph while using the editor. However, you should not assume the graph will be available in a new browser tab, on another device, or after a browser session ends. A UI label implying a saved pipeline must not be interpreted as verified backend persistence.

Onboarding handoff #

Onboarding uses temporary browser state to carry choices into the new editor. This handoff is local and session-scoped rather than a production save mechanism.

Avoid data loss during a preview #

Treat the current editor as an exploratory design environment. If you need a durable specification, separately record your template choice, diagram, and significant configuration decisions until saving is actually supported.

Planned direction #

Persistent pipeline storage, load/reopen support, and deployment are intended product capabilities, but they are not part of the reviewed implementation. Check the release status before relying on any persistence claim.