Code is the
Source of Truth.
The Axolot SDK is a zero-runtime bridge that turns your Astro components into AI-editable, multi-tenant assets — without touching your architecture.
npm install @axolot/sdk 100%
Zero client JS
MIT
Open License
<1ms
Edge latency
∞
Sites per codebase
AI breaks layouts
because it's blind.
In 2026, developers use AI assistants daily to edit code. But when you ask Cursor or Claude to "change the hero title", it sees a sea of <div> tags with no semantic meaning. It guesses. It breaks the layout. It's a context gap that wastes hours every week.
The Axolot SDK solves this by creating a semantic contract between your code and the AI. Every editable element is explicitly named and bounded. The AI doesn't guess — it knows exactly what it can and cannot touch.
<div class="container"> <div class="wrapper"> <h1>← Which one is the title? <p>← What should I change? </div> </div>
<Slot key="hero.title"> <h1>The Future is Native</h1> </Slot> // AI now understands: "hero.title" is // the primary headline. Touch nothing else.
Result: Zero layout breakage. The AI operates within defined boundaries, every time.
The CMS adapts
to your code.
With the Axolot SDK, you never leave your editor. Add a Slot to your component, and the field is automatically registered in the cloud the next time your dev server starts. Types are inferred. Schema is synced. Zero dashboard required.
Visual editing shouldn't cost
you your Lighthouse score.
Lighthouse Score
~40
JS Bundle Size
+340kb
Time to Interactive
6.8s
Core Web Vitals
FAIL
Visual editors inject a runtime JavaScript layer that intercepts every render. It's unavoidable with traditional CMS architectures.
The editor lives in our dashboard. Your site ships as pure, static HTML. No compromise.
The architectural insight
Traditional CMSs need to be on the client to enable editing. Axolot separates concerns: editing happens in our dashboard, and serving happens in Astro. Two separate systems, zero performance cost.
One codebase.
Infinite clients.
Agencies deploying 50 client sites today maintain 50 separate codebases. A component update means 50 deployments. A design token change means 50 PRs. It's unsustainable.
The Axolot SDK solves this with a multi-tenant architecture. One Astro codebase, one deployment — and the SDK routes each request to the correct client data using the SITE_ID, serving completely isolated content from separate database schemas.
AXOLOT_SITE_ID="site_acme_corp" AXOLOT_API_URL="https://api.axolot.io" // That's it. The SDK handles the rest. // Different content, same codebase.
Your Astro codebase
one deployment
Axolot SDK routes by SITE_ID
Each client = isolated DB schema · same codebase
Get Started
The infrastructure for the
next generation of the web.
Free forever. Open source. A single package between your Astro project and the future of content management.
npm install @axolot/sdk MIT License · No credit card required · Works with any Astro project