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.

Typical developer experience when working with GLIK Open Core. From cloning the runtime and configuring a self-hosted setup, to customizing agent templates and deploying workflows via CLI or Docker, this path highlights GLIK’s support for open, developer-controlled environments.

Feature	GLIK Cloud	GLIK Open Core
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, and Org

• 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

🛒 GLIK Marketplace (Coming June 2025)

The fastest way to deploy enterprise solutions.

The GLIK Marketplace is launching in June 2025 as the central destination for discovering, deploying, and customizing prebuilt AI agent templates. It will allow users to:

• 🔍 Browse production-ready templates across industries and workflows

• ⚙️ Deploy instantly into GLIK Studio with minimal setup

• 🧠 Explore logic, memory, and orchestration patterns by example

• 🤝 Empowers partners and service providers to publish white-labeled templates

• 💼 Access solutions for real enterprise scenarios, including SAP integration, expense automation, compliance agents, and more

How a GLIK agent writes structured memory into the GLIK Knowledge system, tags it with metadata, and later retrieves relevant context on future queries. The agent uses this memory to generate decisions or outputs — enabling reusable, auditable, and context-aware automation across workflows.

Variables and Scoping

GLIK uses a robust variable system that enables context-aware execution and dynamic branching throughout a workflow.

Implementation Support & Expert Guidance

Need assistance deploying or customizing this GLIK template for your organization?

Our team offers dedicated coaching and technical walkthrough sessions to ensure successful adoption and alignment with enterprise requirements.

Typical areas of support include:

• Template onboarding and orchestration strategy

• Workflow configuration and logic review

• Memory variable setup and session handling

• Custom integration guidance (e.g. plugins, APIs)

• Request a Session

Variable Types

• User Input (user_input) – Captured from the UI or chat input

• Assigned 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

Scoped Variable Usage in GLIK Workflows: how GLIK workflows leverage different variable types — including user inputs, assigned variables, and system-defined metadata. Variables are passed into decision blocks, enabling dynamic execution paths based on structured context.

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.

📣 Try GLIK

Explore and deploy your first app at app.glik.ai