Learn The Details Behind The Technology

A practical orientation for teams evaluating Kaidera: why it exists, how to get access, what the platform does, and what to review first.

The plain-language origin story: Kaidera was built because building ambitious software needed a new kind of machine.

How customers currently get access, what the self-service path will become, and what to prepare before the first project.

A map of the main Kaidera product surfaces: project workspace, AI worker team, Cortex memory, admin controls, docs, and review gates.

The operating guide for Kaidera OS: what it is, how to install it, how to bring a project online, and how the local control plane works.

Install Kaidera OS, start the local console, confirm the runtime is healthy, and understand the first-run setup flow.

Operating notes for public install paths, local runtime startup, upgrades, rollback expectations, and cleanup.

Register a project, set the workspace root, seed the first worker roster, and run work through approval before enabling autonomy.

Understand leads, orchestrators, AI workers, deterministic jobs, dispatch, handoffs, approval, and run-state evidence.

How Kaidera OS uses Cortex for project memory, registry data, decisions, handoffs, evidence, and boot context.

Set up model providers, choose model routes, understand the catalog, and keep API keys out of code.

How Kaidera OS download, license activation, feature unlocks, account state, and edition boundaries are expected to work.

A deeper look at the local console, Cortex API, app database, worker harnesses, run-state streaming, packaging, and extension boundary.

Operate Kaidera OS safely: local access, secret handling, project boundaries, remote access, health checks, and common failure modes.

How to turn a business idea into the first Kaidera project request without needing to write a technical specification.

The main operating surface for following project work, reviewing evidence, and understanding what the AI worker team is doing.

How project files, diagrams, notes, generated outputs, and customer-provided material are organised in Kaidera.

How teams use Kaidera Draw for secure project whiteboards, diagrams, collaboration, and requirements planning.

Kaidera uses a team of specialised AI workers rather than a single generic assistant. Each role has its own lane, tools, and completion expectations.

The default Kaidera roles customers will see first: product intake, coordination, implementation, QA, knowledge, and review support.

How customers define specialist AI workers for their own business functions, knowledge, review style, and approved tools.

Cortex is the memory and retrieval system behind Kaidera workers. It stores decisions, lessons, handoffs, documents, code intelligence, and project context.

A plain-language guide to how Cortex helps Kaidera remember projects across long-running work.

How Kaidera connects project concepts so users and AI workers can understand relationships, not just isolated notes.

How Cortex makes AI work reviewable by recording ownership, next steps, verification, and residual risk.

PROMI turns goals into scoped work, routed handoffs, verification evidence, review gates, and resumable project progress.

How Kaidera runs worker tasks inside bounded workspaces with scoped tools, evidence packages, pause and resume points, and human review gates.

How users review or demonstrate finished work in a temporary environment before promotion.

How Kaidera uses available AI models across text, reasoning, vision, voice, embeddings, and routing.

How customers guide AI worker behaviour with organisation, project, and worker-level steering.

How Kaidera separates routine work from actions that need human review.

How customers add approved capabilities, tools, and integrations to Kaidera workers.

How administrators configure AI providers, bring their own keys, discover available models, and control which models customers can use.

What customer admins configure: organisation details, people, roles, teams, security, models, billing, support, and usage controls.

How customers understand plans, credits, usage, invoices, top-ups, and suspended account states.

How customers get help, create tickets, work with the support assistant, and escalate when a human response is needed.

A first-stop guide for common Kaidera issues: login, MFA, projects, AI workers, FileVault, Draw, models, billing, and support.

How Kaidera keeps work reviewable: project boundaries, credentials, approval gates, public/private separation, and evidence trails.

Enterprise options for stronger boundaries: self-hosted branches, managed model programs, data residency, isolated deployments, and air-gapped scenarios.

How developer users connect Kaidera workflows to their IDE, project files, and selected-code questions.

How Project Marlow gives an enterprise customer a ready-made AI marketing worker team with a CMO, creative director, motion specialist, human approval, and channel-aware publishing.

How Cortex commands support project memory, handoffs, verification, graph review, and operating evidence.

Practical workflows for using Kaidera: start a project, review work, approve a release, configure models, and inspect evidence.

Concise answers to the questions buyers and users ask first: what is possible, what is not, and how Kaidera stays safe.