---
title: "Optimi documentation"
description: "Technical documentation for the Optimi edge platform and open-source projects: onboarding, CDN, WAF, MCP, Kodama, oauthsonas and clusterpath."
canonical_url: https://optimi.com/en/docs
md_url: https://optimi.com/en/docs.md
last_updated: 2018-10-20
---

# Optimi documentation

Everything you need to run your web properties on the Optimi edge platform —
and our open-source projects for agent execution, local development and analytics.

## What you will find here

### Edge platform

- **[Getting started](/en/docs/getting-started)** — the onboarding sequence, from
  the initial analysis to the production cutover.
- **[CDN caching](/en/docs/cdn-caching)** — how the edge caches your content, and
  how to control TTLs, cache keys, and purges.
- **[WAF rules](/en/docs/waf-rules)** — managed and custom rules to keep threats
  away from your origin.
- **[MCP setup](/en/docs/mcp)** — connect your coding assistant to Optimi for
  read-only analytics and job diagnostics.

### Open source

- **[Open source overview](/en/docs/open-source)** — our projects and their
  publication status.
- **[Kodama](/en/docs/kodama)** — API-first software factory in Go: work items,
  Git workspaces, durable pipelines, agents and human review. Six pages cover
  concepts, architecture, setup, development and operations.
- **[oauthsonas](/en/docs/oauthsonas)** — in-memory OpenID Connect provider for
  local development and integration tests.
- **[clusterpath](/en/docs/clusterpath)** — bounded-memory URL clustering for
  ClickHouse and other analytics stores.

## The Optimi edge in one paragraph

Optimi acts as a single orchestration layer between your audience and your
origin. Every request — users, crawlers, and bots — passes through the edge,
where it is accelerated (**Performance**), filtered (**Security**), and measured
(**Visibility**). You keep your existing hosting; we make it fast, safe, and
more visible.

## Who this documentation is for

These pages are written for the people who operate the platform day to day:
developers, DevOps and SRE teams, security engineers, and technical SEO
specialists. Each page aims to be safe to follow in production — every change
is described with its validation and rollback path.