Core Concepts
Learn how GLIK is structured under the hood. This section introduces key system layers that define how your apps, workflows, memory, and logic behave inside the GLIK platform.
GLIK Cloud vs. GLIK Open Core
GLIK Cloud is the fully managed, no-code orchestration environment hosted by Rivalz AI. It includes visual app building, runtime execution, memory, plugin support, and usage metering β all accessible via browser.
GLIK Open Core is the self-hosted version of GLIK, provided as an open core CLI and runtime engine. Itβs designed for engineering teams that want to run workflows in private infrastructure or embed GLIK in enterprise DevOps pipelines.
Hosting
Managed by Rivalz
Self-hosted (user-managed)
Setup
No setup required
Requires deployment
Best for
SaaS apps, partner resale
Custom infra, internal tooling
Access to Templates
Yes
Yes
Plugin Support
Marketplace only
Custom + Marketplace
GLIK Knowledge
GLIK Knowledge is GLIK's persistent memory system β a structured way to store, recall, and query information across user sessions and apps.
Key characteristics:
Information is stored as structured memory objects, often auto-tagged
Memories are scoped:
User
,App
, andOrg
Retrieval is done via Knowledge Retrieval blocks using tags or full-text queries
Writing is performed via Data Enrichment blocks
Example use cases:
Uploading strategy documents and tagging summaries per company
Persisting user queries or session history
Creating multi-user agents with scoped knowledge for each organization
Variables and Scoping
GLIK uses a robust variable system that enables context-aware execution and dynamic branching throughout a workflow.
Variable Types
User Input (
user_input
) β Captured from the UI or chat inputAssigned Variables β Created via the Variable Assigner block
System Variables β Runtime-assigned values like
last_query
,retrieved_tags
, etc.Conversation Variables β Persist across back-and-forth interactions in a chat or agent context. Used to hold evolving memory or user state during a conversation thread

Scoping Layers
Scope
Description
Example
Local
Lives only within a single block during execution. Not accessible outside it.
Temporary LLM response structure
Conversation
Persists across back-and-forth messages in a chat or agent context. Useful for conversational memory within a session.
user_goal
, current_topic
Session
Persists across all blocks within the same app session. Cleared on session end.
company_name
, report_year
Global
Accessible across apps, workflows, and users (admin-controlled).
Org-wide config flags, shared tags
Variables are passed through the workflow using bindings, evaluated dynamically by the Value Resolver, and injected into prompts and tools.
Last updated
Was this helpful?