GenCMS is iGears' model-agnostic AI workspace and runtime direction for building assistants, document extraction, content and internal agent solutions on an organisation's own data.

It is for developers and organisations that need custom or privately deployed AI with explicit tenant, data and permission boundaries.

Account and tenant administration, workspace records, scoped API keys and Guard scanning are available. Composer can run through a tenant's region-locked AIHK or AICA gateway after its AI key is ready.

Request managed workspace access or ask iGears to scope a 30-day MVP. Project services are fixed-price, with the scope, fee and acceptance checks stated in a quotation.

Get started

Core concepts

Models, Memory, Skills, Agents, Workflows, Apps, API and Guard — and how they fit together.

Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.

Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.

Eight layers. Each one is useful alone and worth more in combination — that combination is what GenCMS sells.

Layer	What it is	What it gives you
Models	Provider families behind one interface	Choose how the AI thinks
Memory	Knowledge, memory and rules in a workspace	Context that survives the session
Skills	Versioned, permission-aware capabilities	Reusable ability, not a copied prompt
Agents	A model plus memory, skills, goals and a schedule	Work that happens without you
Workflows	Steps, conditions and human approval	A repeatable process
Apps	A finished experience over the components	Something a non-technical user can run
API	The same capabilities as HTTP endpoints	Everything embeddable elsewhere
Guard	Static analysis over packages and integrations	Knowing what you are about to run

The relationship

                 Memory
                   │
                   ▼
Models ───────► Agent ◄────── Skills
                   │
                   ▼
                Workflow
                   │
                   ▼
                  App
                   │
                   ▼
                  API

Read it as capability flowing downward. A Skill tested in Composer can be used by an Agent, added to a Workflow, packaged into an App and called through the API without being rewritten at any step.

Context is three things

Knowledge   what you gave it      (documents, URLs, repositories, notes)
+
Memory      what it learned       (decisions, project state, prior outcomes)
+
Rules       what always applies   (brand tone, coding standards, prohibitions)
=
Context

← PreviousGetting started Next →Skills