Axolot Logo

Architecture

A deep dive into the high-performance, multi-tenant engine behind Axolot CMS.

Axolot is built on a Hybrid Infrastructure model. We provide the management intelligence (the Studio) while you maintain control of your data and codebase.

The Surgical Parser

The core innovation of Axolot is our AST-aware regex parser. When a content update is triggered from the Studio:

  1. The Axolot Bridge identifies the specific .astro file containing the target data-slot.
  2. Our engine performs a surgical replacement. It doesn't overwrite the file; it only modifies the content inside the tagged element or the specific attribute (like src or href).
  3. This preserves your code formatting, comments, and logic perfectly.

Data Isolation (Multi-tenancy)

Axolot is built for agencies managing hundreds of sites. We handle this via PostgreSQL Schema Isolation.

  • Every site has its own isolated database schema (e.g., site_acme_corp).
  • Your content, media references, and module data are logically separated.
  • One Axolot API instance can securely serve infinite tenants without data cross-over.

The Request Flow

In production, Axolot acts as a lightning-fast data provider.

Build Time (SSG)

The SDK fetches all slot values and module data during the build process. The result is pure, static HTML.

Request Time (SSR)

Using Astro's SSR mode, the SDK fetches fresh data from the Axolot Edge API with sub-50ms latency.