Documentation
Start with the story, then learn the system
Kaidera started as a way to build an ambitious aviation product by first building the machine that could build the machine. These docs explain the customer journey: access, projects, Workbench, FileVault, AI workers, Cortex, models, controls, review, backup and recovery, the Kaidera OS local control plane, Kaidera Infrastructure, and Project Marlow Marketing OS.
Current access
Enterprise onboarding first
Self-service sign-up is the long-term path. For now, customers start through an enterprise account so users, roles, billing, model access, and review gates are set up correctly.
Read account setup guide →Kaidera Infrastructure
Design, deploy and run the enterprise estate
Follow the complete service path across discovery, architecture, the AI infrastructure team, deployment, platform operations, cybersecurity, resilience, FinOps and evidence.
Marketing OS
Run an accountable marketing operating function
Follow Project Marlow from team roles and bounded autonomy through verification, approval, publishing, reporting, and the first discovery scope.
Backup and recovery
Protect one project with a clear recovery path
Kaidera Backup Service keeps backup and restore scoped to a single project. During the current rollout, enablement starts with Sales and a guided recovery plan.
Start here
Getting started with Kaidera
A practical orientation for teams evaluating Kaidera: why it exists, how to get access, what the platform does, and what to review first.
Open guide →
Start here
Why Kaidera exists
The plain-language origin story: Kaidera was built because building ambitious software needed a new kind of machine.
Open guide →
Start here
Access and enterprise account setup
How customers currently get access, what the self-service path will become, and what to prepare before the first project.
Open guide →
Documentation journey
Follow the product path
Start Here
Getting started with Kaidera
A practical orientation for teams evaluating Kaidera: why it exists, how to get access, what the platform does, and what to review first.
Why Kaidera exists
The plain-language origin story: Kaidera was built because building ambitious software needed a new kind of machine.
Access and enterprise account setup
How customers currently get access, what the self-service path will become, and what to prepare before the first project.
Product surfaces
A map of the main Kaidera product surfaces: project workspace, AI worker team, Cortex memory, admin controls, docs, and review gates.
Backup And Recovery
Kaidera Infrastructure
Kaidera Infrastructure overview
The public operating guide for Kaidera Infrastructure: an AI-run team that designs, deploys and operates cloud, datacenter and hybrid estates.
Infrastructure design method
How discovery, maturity assessment, function selection and architecture decisions produce a customer-specific cloud, datacenter or hybrid design.
The AI infrastructure team
The named AI workers, deterministic agents, ownership model and escalation ladder behind the service.
How Kaidera Infrastructure works
The five-phase service loop, autonomy model, work routing, change gates and evidence flow from request to verified outcome.
Deployment and connection model
How the turnkey Kaidera Infrastructure team is instantiated, connected to customer environments and moved through controlled deployment.
Enterprise infrastructure operations
The full Run-phase service catalog: platform, network, identity, observability, ITIL, resilience, internal tooling and continual improvement.
Security, SIEM and compliance
How cybersecurity, security operations, authorized testing, risk management and compliance evidence are integrated into infrastructure operations.
FinOps, evidence and management visibility
How cost control, action evidence, audit trails and management reporting become continuous operational capabilities.
Get started with Kaidera Infrastructure
A practical customer journey from the first discovery conversation to a connected, evidence-producing infrastructure service.
Marketing OS
Marketing OS overview
The operating guide for Project Marlow: an approval-led AI marketing function that turns a clear business goal into accountable, channel-ready work.
Marketing OS team and roles
How Marlow, Saul, Gem, narrow specialist workers, and named human approvers divide marketing responsibility without losing a clear release authority.
Approval and publishing controls
The boundaries that keep public marketing work attributable, consent-aware, on-brand, and subject to named human release authority.
Operating rhythm and evidence
How a focused cadence keeps research, drafting, verification, approvals, publishing, and learning visible rather than hidden inside one long-running task.
Get started with Marketing OS
What to prepare for an initial Marketing OS discovery conversation and how to stage a safe first operating scope.
Kaidera OS
Kaidera OS documentation
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.
Get started with Kaidera OS
Install Kaidera OS, start the local console, confirm the runtime is healthy, and understand the first-run setup flow.
Install, update, and run Kaidera OS
Install the commercial macOS package, complete guided setup, start the local runtime, and use repair and recovery tools.
Create and run your first project
Register a project, set the workspace root, seed the first worker roster, and run work through approval before enabling autonomy.
Run AI worker teams
Understand leads, orchestrators, AI workers, deterministic jobs, dispatch, handoffs, approval, and run-state evidence.
Cortex memory in Kaidera OS
How Kaidera OS uses Cortex for project memory, registry data, decisions, handoffs, evidence, and boot context.
Configure providers and models
Set up model providers, choose model routes, understand the catalog, and keep API keys out of code.
License, account, and editions
How Kaidera OS download, license activation, feature unlocks, account state, and edition boundaries are expected to work.
How Kaidera OS works
A deeper look at the local console, Cortex API, app database, worker harnesses, run-state streaming, packaging, and extension boundary.
Security, troubleshooting, and operations
Operate Kaidera OS safely: local access, secret handling, project boundaries, remote access, health checks, and common failure modes.
Projects And Workbench
Create your first project
How to turn a business idea into the first Kaidera project request without needing to write a technical specification.
Workbench overview
The main operating surface for following project work, reviewing evidence, and understanding what the AI worker team is doing.
FileVault overview
How project files, diagrams, notes, generated outputs, and customer-provided material are organised in Kaidera.
Draw And Design-First Workflow
AI Workers
AI worker teams and roles
Kaidera uses a team of specialised AI workers rather than a single generic assistant. Each role has its own lane, tools, and completion expectations.
Built-in AI workers
The default Kaidera roles customers will see first: product intake, coordination, implementation, QA, knowledge, and review support.
Custom AI workers
How customers define specialist AI workers for their own business functions, knowledge, review style, and approved tools.
Cortex And Platform Services
Cortex memory and project intelligence
Cortex is the memory and retrieval system behind Kaidera workers. It stores decisions, lessons, handoffs, documents, code intelligence, and project context.
Cortex memory
A plain-language guide to how Cortex helps Kaidera remember projects across long-running work.
Cortex knowledge graph
How Kaidera connects project concepts so users and AI workers can understand relationships, not just isolated notes.
Cortex handoffs and evidence
How Cortex makes AI work reviewable by recording ownership, next steps, verification, and residual risk.
PROMI orchestration
PROMI turns goals into scoped work, routed handoffs, verification evidence, review gates, and resumable project progress.
Harness engineering
How Kaidera runs worker tasks inside bounded workspaces with scoped tools, evidence packages, pause and resume points, and human review gates.
Live Testing And Demos
Models And Providers
Steering, Guardrails, And Approvals
Skills, Tools, And Integrations
Admin And Settings
Provider setup and BYOK
How administrators configure AI providers, bring their own keys, discover available models, and control which models customers can use.
Customer admin and settings
What customer admins configure: organisation details, people, roles, teams, security, models, billing, support, and usage controls.
Billing, Plans, And Usage
Support And Troubleshooting
Trust And Enterprise
Trust and security
How Kaidera keeps work reviewable: project boundaries, credentials, approval gates, public/private separation, and evidence trails.
Enterprise controls
Enterprise options for stronger boundaries: self-hosted branches, managed model programs, data residency, isolated deployments, and air-gapped scenarios.
IDE Extension And Developer Workflows
Guides
Website bridge
Use the website for the story, docs for operation
The main website explains the business narrative. The docs explain how customers use and configure the product, one practical guide at a time.