@intlayer/docs 9.0.0-canary.10 → 9.0.0-canary.12

package/docs/en-GB/releases/v9.md

@@ -1,14 +1,17 @@
 ---
 createdAt: 2026-06-14
-updatedAt: 2026-06-26
+updatedAt: 2026-06-30
 title: New Intlayer v9 - What's new?
-description: Discover what's new in Intlayer v9. Introducing drop-in compatibility packages for popular i18n libraries and support for Collections and Variants.
+description: Discover what's new in Intlayer v9. Introducing drop-in compatibility packages for popular i18n libraries, support for Collections and Variants, and self-hosting via Docker Compose.
 keywords:
   - Intlayer
   - Compatibility
   - Migration
   - Collections
   - Variants
+  - CMS SDK
+  - Self-Hosting
+  - Docker
   - i18next
   - next-intl
   - vue-i18n
@@ -198,24 +201,6 @@ const product = useIntlayer("product-copy", {
 
 ---
 
-## Dynamic Loading & Bundle Size Optimisations
-
-To keep bundles extremely small, Intlayer v9 supports dynamic lazy loading.
-
-In your configuration, set `importMode` to `'dynamic'` or `'fetch'`:
-
-```ts fileName="intlayer.config.ts"
-export default {
-  dictionary: {
-    importMode: "dynamic", // "static" | "dynamic" | "fetch"
-  },
-};
-```
-
-At build time, `@intlayer/swc` and `@intlayer/babel` scan your files and replace `useIntlayer` / `getIntlayer` calls with tree-shakeable wrappers (`useDictionary` / `useDictionaryDynamic`). Only the content required for the selected collection item, variant, or locale is loaded, preventing your production bundle from containing unused translations.
-
----
-
 ## Vite Plugin: Bundled Compiler & Proxy
 
 The `intlayer()` Vite plugin now bundles the **compiler** and the **locale-routing proxy** directly, so most projects only need a single plugin in `vite.config.ts`:
@@ -295,6 +280,46 @@ npm install intlayer react-native-intlayer
 
 ---
 
+## CMS SDK: use Intlayer as a headless content database
+
+Intlayer v9 ships a clean, auto-authenticating SDK in `@intlayer/api` to interact with the CMS programmatically — fetch projects, fetch dictionaries, and push or update them from your own server, scripts, or CI. Authentication (OAuth2 `client_credentials`) is handled and refreshed for you.
+
+The SDK is split into **two separate imports** so your bundle includes only the domains you actually use:
+
+1. `createIntlayerCMS` — a lightweight **authenticator** holding the credentials and the managed token (no domain client bundled).
+2. `dictionaryEndpoint`, `projectEndpoint`, … — per-domain **endpoint binders**, each imported from its own subpath.
+
+```ts fileName="cms.ts"
+import { createIntlayerCMS } from "@intlayer/api";
+import { dictionaryEndpoint } from "@intlayer/api/dictionary";
+
+// Config is optional: credentials fall back to INTLAYER_CLIENT_ID /
+// INTLAYER_CLIENT_SECRET resolved by `@intlayer/config/built`.
+const cms = createIntlayerCMS();
+
+// Read
+const { data: dictionaries } = await dictionaryEndpoint(cms).getDictionaries();
+
+// Write — use the CMS like a database
+await dictionaryEndpoint(cms).pushDictionaries([myDictionary]);
+```
+
+> Security: the CMS credentials grant write access to your content. Only ever create the authenticator on the **server side** — never ship `clientId` / `clientSecret` to the browser.
+
+---
+
+## Self-Hosting
+
+Intlayer v9 ships first-class support for running your own Intlayer instance with a single command — no Intlayer Cloud account required.
+
+```sh
+curl -fsSL https://intlayer.org/install.sh | sh
+```
+
+The installer downloads a `docker-compose.yml` and a `.env`, auto-generates the required secrets, and runs `docker compose up -d`. Everything — the dashboard, the API, the database, object storage, and transactional email — runs locally in containers.
+
+---
+
 ## Migration notes from v8
 
 If you are upgrading from v8, note that the v9 does not include breaking changes. But here are the key changes:
@@ -310,3 +335,5 @@ If you are upgrading from v8, note that the v9 does not include breaking changes
 - [Compat Adapter Packages Guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/index.md)
 - [Dynamic Dictionaries - Collections & Variants](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md)
 - [Configuration Reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md)
+- [CMS SDK - Programmatic access with @intlayer/api](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)
+- [Self-Hosting Guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/self_hosting.md)

package/docs/en-GB/self_hosting.md

@@ -0,0 +1,350 @@
+---
+createdAt: 2026-06-30
+updatedAt: 2026-06-30
+title: Self-Hosting Intlayer
+description: Run a complete Intlayer instance on your own infrastructure with a single command. No Intlayer Cloud account required.
+keywords:
+  - Self-Hosting
+  - Docker
+  - Docker Compose
+  - Intlayer
+  - CMS
+  - Installation
+  - Infrastructure
+slugs:
+  - doc
+  - self-hosting
+author: aymericzip
+---
+
+# Self-Hosting Intlayer
+
+Intlayer can run entirely on your own infrastructure — no Intlayer Cloud account required. A single command boots a production-ready stack:
+
+```sh
+curl -fsSL https://intlayer.org/install.sh | sh
+```
+
+The installer downloads a `docker-compose.yml` and a `.env`, auto-generates the required secrets, and starts all containers with `docker compose up -d`.
+
+## Table of Contents
+
+<TOC/>
+
+---
+
+## Architecture
+
+```
+                ┌─────────────────────────────┐
+ browser ──────▶ │  app  (TanStack Start)  :3000│ ──┐
+                └─────────────────────────────┘   │ VITE_BACKEND_URL
+                ┌─────────────────────────────┐   │
+                │  backend (Fastify/Bun)  :3100│ ◀─┘
+                └──────────────┬──────────────┘
+          ┌──────────┬─────────┼──────────┬───────────┐
+          ▼          ▼         ▼          ▼           ▼
+     mongo:27017  redis:6379  minio:9000  mailpit:1025  Chromium
+     (1-node RS)             (S3 API)     (SMTP)        (in-image)
+                             minio:9001   mailpit:8025
+                             (console)    (web UI)
+```
+
+Chromium (used for Puppeteer screenshot generation) is bundled inside the backend image — no separate container is needed.
+
+---
+
+## Prerequisites
+
+- **Docker** ≥ 24 and **Docker Compose** ≥ v2. If either is missing, the installer prints the install link and exits.
+- Ports `3000`, `3100`, `8025`, `9000`, and `9001` available on the host.
+- A Linux or macOS host (or WSL2 on Windows).
+
+---
+
+## Quick start
+
+```sh
+curl -fsSL https://intlayer.org/install.sh | sh
+```
+
+What the installer does:
+
+1. Checks that `docker` and `docker compose` are present.
+2. Downloads `docker-compose.yml` and `.env.example` into `./intlayer/`.
+3. If no `.env` exists, copies the example and generates random secrets for `BETTER_AUTH_SECRET`, `S3_ACCESS_KEY_ID`, and `S3_SECRET_ACCESS_KEY` via `openssl rand`.
+4. Runs `docker compose pull` + `docker compose up -d`.
+5. Prints the URLs: dashboard `:3000`, API `:3100`, email UI `:8025`, MinIO console `:9001`.
+
+After the stack is up, open **http://localhost:3000** and create your first account.
+
+---
+
+## Services
+
+| Service     | Image                                | Host port(s)                   | Purpose                                                  |
+| ----------- | ------------------------------------ | ------------------------------ | -------------------------------------------------------- |
+| **app**     | built from `apps/app/Dockerfile`     | `3000`                         | TanStack Start dashboard (CMS UI)                        |
+| **backend** | built from `apps/backend/Dockerfile` | `3100`                         | Fastify REST API (`/health` endpoint)                    |
+| **mongo**   | `mongo:7`                            | internal                       | Single-node replica set (`rs0`)                          |
+| **redis**   | `redis:7-alpine`                     | internal                       | Job queues (BullMQ) and caching (ioredis)                |
+| **minio**   | `minio/minio`                        | `9000` (S3), `9001` (console)  | S3-compatible object storage for avatars and screenshots |
+| **mailpit** | `axllent/mailpit`                    | `1025` (SMTP), `8025` (web UI) | Local transactional email sink                           |
+
+Internal ports (mongo, redis) are not exposed to the host by default.
+
+> MinIO port `9000` must be reachable by the browser because uploaded assets (avatars, screenshots) are loaded directly from `S3_PUBLIC_URL=http://localhost:9000/intlayer`.
+
+---
+
+## Environment variables
+
+The installer generates a ready-to-use `.env`. The table below describes every variable.
+
+### Required (auto-generated or prompted)
+
+| Variable               | Example                                         | Description                                        |
+| ---------------------- | ----------------------------------------------- | -------------------------------------------------- |
+| `NODE_ENV`             | `production`                                    | Runtime environment                                |
+| `PORT`                 | `3100`                                          | Backend listening port                             |
+| `BACKEND_URL`          | `http://localhost:3100`                         | Public URL of the backend API                      |
+| `APP_URL`              | `http://localhost:3000`                         | Public URL of the dashboard                        |
+| `DOMAIN`               | `localhost`                                     | Cookie domain                                      |
+| `MONGODB_URI`          | `mongodb://mongo:27017/intlayer?replicaSet=rs0` | Full MongoDB connection URI                        |
+| `REDIS_URL`            | `redis://redis:6379`                            | Redis connection URL                               |
+| `BETTER_AUTH_SECRET`   | _(generated)_                                   | 32-byte secret for session signing                 |
+| `MAIL_PROVIDER`        | `smtp`                                          | Mail transport: `smtp` or `resend`                 |
+| `MAIL_SMTP_HOST`       | `mailpit`                                       | SMTP hostname (Mailpit container name)             |
+| `MAIL_SMTP_PORT`       | `1025`                                          | SMTP port                                          |
+| `MAIL_FROM`            | `Intlayer <no-reply@localhost>`                 | Sender address                                     |
+| `S3_ENDPOINT`          | `http://minio:9000`                             | S3-compatible endpoint                             |
+| `S3_PUBLIC_URL`        | `http://localhost:9000/intlayer`                | Public URL for browser asset loading               |
+| `S3_BUCKET_NAME`       | `intlayer`                                      | Bucket name                                        |
+| `S3_ACCESS_KEY_ID`     | _(generated)_                                   | MinIO access key                                   |
+| `S3_SECRET_ACCESS_KEY` | _(generated)_                                   | MinIO secret key                                   |
+| `VITE_BACKEND_URL`     | `http://localhost:3100`                         | Backend URL baked into the dashboard at build time |
+| `VITE_DOMAIN`          | `localhost`                                     | Domain baked into the dashboard at build time      |
+
+### Optional (features degrade gracefully when absent)
+
+| Variable                                                 | Feature                                                     |
+| -------------------------------------------------------- | ----------------------------------------------------------- |
+| `OPENAI_API_KEY`                                         | AI-assisted translation and content audit                   |
+| `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`, `STRIPE_*` | Billing and subscription management                         |
+| `RESEND_API_KEY`                                         | Transactional email via Resend (overrides Mailpit when set) |
+| `GITHUB_CLIENT_ID`, `GITHUB_CLIENT_SECRET`               | GitHub OAuth login                                          |
+| `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`               | Google OAuth login                                          |
+| `GITLAB_CLIENT_ID`, `GITLAB_CLIENT_SECRET`               | GitLab OAuth login                                          |
+| `MICROSOFT_CLIENT_ID`, `MICROSOFT_CLIENT_SECRET`         | Microsoft OAuth login                                       |
+| `LINKEDIN_CLIENT_ID`, `LINKEDIN_CLIENT_SECRET`           | LinkedIn OAuth login                                        |
+| `ATLASSIAN_CLIENT_ID`, `ATLASSIAN_CLIENT_SECRET`         | Atlassian OAuth login                                       |
+
+---
+
+## Connecting your Intlayer project
+
+Once the stack is running, point your project at the self-hosted backend and dashboard instead of `intlayer.org`.
+
+### Project configuration
+
+```typescript fileName="intlayer.config.ts" codeFormat={["typescript", "esm", "commonjs"]}
+import type { IntlayerConfig } from "intlayer";
+
+const config: IntlayerConfig = {
+  editor: {
+    clientId: process.env.INTLAYER_CLIENT_ID,
+    clientSecret: process.env.INTLAYER_CLIENT_SECRET,
+
+    /**
+     * URL of the self-hosted CMS dashboard.
+     * Default: https://app.intlayer.org
+     */
+    cmsURL: process.env.INTLAYER_CMS_URL, // e.g. http://localhost:3000
+
+    /**
+     * URL of the self-hosted backend API.
+     * Default: https://back.intlayer.org
+     */
+    backendURL: process.env.INTLAYER_BACKEND_URL, // e.g. http://localhost:3100
+  },
+};
+
+export default config;
+```
+
+Set the environment variables in your project's `.env`:
+
+```sh
+INTLAYER_CMS_URL=http://localhost:3000
+INTLAYER_BACKEND_URL=http://localhost:3100
+INTLAYER_CLIENT_ID=<your-client-id>
+INTLAYER_CLIENT_SECRET=<your-client-secret>
+```
+
+Create access credentials in your self-hosted dashboard under **Projects → Access keys** at `http://localhost:3000/projects`.
+
+### `@intlayer/api` SDK
+
+When using the `@intlayer/api` SDK programmatically, pass `backendURL` explicitly:
+
+```typescript fileName="cms.ts" codeFormat="typescript"
+import { createIntlayerCMS } from "@intlayer/api";
+import { dictionaryEndpoint } from "@intlayer/api/dictionary";
+
+const cms = createIntlayerCMS({
+  editor: {
+    clientId: process.env.INTLAYER_CLIENT_ID,
+    clientSecret: process.env.INTLAYER_CLIENT_SECRET,
+    backendURL: process.env.INTLAYER_BACKEND_URL, // http://localhost:3100
+  },
+});
+
+const { data: dictionaries } = await dictionaryEndpoint(cms).getDictionaries();
+```
+
+---
+
+## Upgrading
+
+Re-running the installer on an existing deployment performs a rolling upgrade:
+
+```sh
+curl -fsSL https://intlayer.org/install.sh | sh
+```
+
+This pulls the latest images and restarts containers with `docker compose pull && docker compose up -d`. Existing volumes (`mongo-data`, `redis-data`, `minio-data`) are preserved — no data loss.
+
+To upgrade manually from inside the `./intlayer/` directory:
+
+```sh
+docker compose pull
+docker compose up -d
+```
+
+---
+
+## Backup and restore
+
+All persistent data lives in three named Docker volumes.
+
+### Backup
+
+```sh
+docker run --rm \
+  -v intlayer_mongo-data:/data \
+  -v "$(pwd)":/backup \
+  busybox tar czf /backup/mongo-data.tar.gz /data
+
+docker run --rm \
+  -v intlayer_redis-data:/data \
+  -v "$(pwd)":/backup \
+  busybox tar czf /backup/redis-data.tar.gz /data
+
+docker run --rm \
+  -v intlayer_minio-data:/data \
+  -v "$(pwd)":/backup \
+  busybox tar czf /backup/minio-data.tar.gz /data
+```
+
+### Restore
+
+```sh
+docker run --rm \
+  -v intlayer_mongo-data:/data \
+  -v "$(pwd)":/backup \
+  busybox tar xzf /backup/mongo-data.tar.gz -C /
+
+# Repeat for redis-data and minio-data
+```
+
+---
+
+## Using a reverse proxy (Nginx / Caddy)
+
+For production deployments, place a reverse proxy in front of the app and backend containers instead of exposing them directly.
+
+### Nginx example
+
+```nginx
+server {
+    listen 80;
+    server_name cms.example.com;
+
+    location / {
+        proxy_pass http://localhost:3000;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+    }
+}
+
+server {
+    listen 80;
+    server_name api.example.com;
+
+    location / {
+        proxy_pass http://localhost:3100;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+    }
+}
+```
+
+Update the following `.env` variables to match your public domains:
+
+```sh
+BACKEND_URL=https://api.example.com
+APP_URL=https://cms.example.com
+DOMAIN=example.com
+VITE_BACKEND_URL=https://api.example.com
+VITE_DOMAIN=example.com
+```
+
+> `VITE_*` variables are baked into the dashboard image at build time. If you change them after the image is built, you need to rebuild the `app` image (`docker compose build app`) or use runtime config injection.
+
+---
+
+## Troubleshooting
+
+### Backend crash-loops on first start
+
+MongoDB and Redis must be healthy before the backend starts. The compose file uses `depends_on` with `condition: service_healthy`. If you see repeated backend restarts, check that the `mongo` and `redis` healthchecks pass:
+
+```sh
+docker compose ps
+docker compose logs mongo
+docker compose logs redis
+```
+
+### Dashboard cannot reach the API
+
+Verify that `VITE_BACKEND_URL` matches the URL where the backend is reachable from the **browser** (not the Docker network). If you changed the backend port or added a reverse proxy, rebuild the dashboard image:
+
+```sh
+docker compose build app
+docker compose up -d app
+```
+
+### Email not sending
+
+By default, all outbound email is captured by Mailpit. Open `http://localhost:8025` to see sent messages. To send real email, set `MAIL_PROVIDER=resend` and `RESEND_API_KEY=<your-key>` in `.env`, then restart the backend:
+
+```sh
+docker compose restart backend
+```
+
+### MinIO bucket missing
+
+If the `minio-init` one-shot service didn't run (or ran before MinIO was ready), create the bucket manually:
+
+```sh
+docker compose run --rm minio-init
+```
+
+---
+
+## Useful links
+
+- [Intlayer CMS documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)
+- [Configuration reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/configuration.md)
+- [CMS SDK — `@intlayer/api`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md#programmatic-access-with-the-intlayerapi-sdk)
+- [Docker Image (aymercizip/intlayer-selfhost)](https://hub.docker.com/repository/docker/aymercizip/intlayer-selfhost/general)

package/docs/es/bundle_optimization.md

@@ -231,6 +231,9 @@ Next.js requiere el complemento `@intlayer/swc` para la fase de optimización (r
 
 > Este complemento no se instala por defecto ya que los complementos SWC son experimentales en Next.js. Podría cambiar en el futuro.
 
+<Tabs>
+ <Tab value="npm">
+
 ```bash packageManager="npm"
 npm install -D @intlayer/swc
 ```
@@ -247,6 +250,19 @@ pnpm add -D @intlayer/swc
 bun add -d @intlayer/swc
 ```
 
+ </Tab>
+ <Tab value="Crates.io (rust)">
+
+```toml fileName="Cargo.toml"
+[dependencies]
+intlayer-swc-plugin = "*"
+```
+
+[View on Crates.io](https://crates.io/crates/intlayer-swc-plugin)
+
+ </Tab>
+</Tabs>
+
 Una vez instalado, Intlayer detectará y utilizará automáticamente el complemento.
 
 Para las fases de **purga y minificación** (eliminación de campos y renombramiento), instala de manera adicional `@intlayer/babel` y añade los complementos de Babel. Debido a que Next.js usa SWC para la transformación pero aún evalúa `babel.config.js` para la configuración, estos complementos de Babel se ejecutan en un paso previo antes de SWC.

package/docs/es/cli/scan.md

@@ -150,10 +150,10 @@ await scan("https://example.com", {
 });
 ```
 
-Para un acceso de nivel inferior, `scanWebsite` de `@intlayer/chokidar/scan` devuelve un objeto `ScanResult` estructurado:
+Para un acceso de nivel inferior, `scanWebsite` de `@intlayer/engine/scan` devuelve un objeto `ScanResult` estructurado:
 
 ```ts
-import { scanWebsite } from "@intlayer/chokidar/scan";
+import { scanWebsite } from "@intlayer/engine/scan";
 
 const result = await scanWebsite("https://example.com", { deep: false });
 console.log(result.score, result.totalPageSize, result.events);

package/docs/es/how_works_intlayer.md

@@ -218,9 +218,9 @@ El paquete `@intlayer/mcp` proporciona un servidor MCP (Model Context Protocol)
 
 Los paquetes `@intlayer/dictionaries-entry`, `@intlayer/unmerged-dictionaries-entry` y `@intlayer/dynamic-dictionaries-entry` devuelven la ruta de entrada de los diccionarios de Intlayer. Dado que buscar en el sistema de archivos desde el navegador es imposible, no es posible usar empaquetadores como Webpack o Rollup para obtener la ruta de entrada de los diccionarios. Estos paquetes están diseñados para ser aliasados, lo que permite la optimización del empaquetado en varios empaquetadores como Vite, Webpack y Turbopack.
 
-### @intlayer/chokidar
+### @intlayer/engine
 
-El paquete `@intlayer/chokidar` se utiliza para monitorizar archivos de contenido y regenerar el diccionario modificado en cada modificación.
+El paquete `@intlayer/engine` se utiliza para monitorizar archivos de contenido y regenerar el diccionario modificado en cada modificación.
 
 ### @intlayer/editor
 

package/docs/es/intlayer_CMS.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-08-23
+updatedAt: 2026-06-30
 title: Intlayer CMS | Externaliza tu contenido en el Intlayer CMS
 description: Externaliza tu contenido en el Intlayer CMS para delegar la gestión de tu contenido a tu equipo.
 keywords:
@@ -18,6 +18,9 @@ slugs:
   - cms
 youtubeVideo: https://www.youtube.com/watch?v=UDDTnirwi_4
 history:
+  - version: 9.0.0
+    date: 2026-06-30
+    changes: "Añadida sección de Auto-alojamiento: bootstrap Docker Compose, inventario de servicios, configuración SDK, características opcionales y notas de actualización"
   - version: 6.0.1
     date: 2025-09-22
     changes: "Añadida documentación de sincronización en vivo"
@@ -385,6 +388,119 @@ Notas y restricciones:
 
 - El editor visual utiliza un iframe para mostrar tu sitio web. Asegúrate de que la Política de Seguridad de Contenidos (CSP) de tu sitio web permita la URL del CMS como `frame-ancestors` ('https://app.intlayer.org' por defecto). Revisa la consola del editor para cualquier error.
 
+## Auto-alojamiento
+
+Intlayer puede ejecutarse completamente en tu propia infraestructura — no se requiere cuenta de Intlayer Cloud. Un solo comando arranca toda la pila (panel de control, API, base de datos, almacenamiento de objetos y correo electrónico) mediante Docker Compose:
+
+```sh
+curl -fsSL https://intlayer.org/install.sh | sh
+```
+
+Esto descarga un `docker-compose.yml` y un `.env`, genera automáticamente los secretos necesarios (`BETTER_AUTH_SECRET`, credenciales de MinIO) y arranca todos los contenedores con `docker compose up -d`. Volver a ejecutar el mismo comando en una instalación existente realiza una actualización progresiva sin pérdida de datos.
+
+### Servicios iniciados
+
+| Servicio                   | Puerto(s)                            | Propósito                                             |
+| -------------------------- | ------------------------------------ | ----------------------------------------------------- |
+| **app** (panel de control) | `3000`                               | Interfaz CMS TanStack Start                           |
+| **backend** (API)          | `3100`                               | API REST Fastify                                      |
+| **MongoDB 7**              | interno                              | Base de datos principal (replica set de un solo nodo) |
+| **Redis 7**                | interno                              | Colas de trabajos y caché                             |
+| **MinIO**                  | `9000` (S3), `9001` (consola)        | Almacenamiento de objetos compatible con S3           |
+| **Mailpit**                | `1025` (SMTP), `8025` (interfaz web) | Sumidero local de correo transaccional                |
+
+Chromium (para la generación de capturas de pantalla con Puppeteer) está incluido en la imagen del backend — no se necesita ningún contenedor adicional.
+
+### Conectar tu proyecto a una instancia auto-alojada
+
+Apunta tu configuración de Intlayer a tu propio backend y panel de control en lugar de `intlayer.org`:
+
+```typescript fileName="intlayer.config.ts" codeFormat={["typescript", "esm", "commonjs"]}
+import type { IntlayerConfig } from "intlayer";
+
+const config: IntlayerConfig = {
+  editor: {
+    clientId: process.env.INTLAYER_CLIENT_ID,
+    clientSecret: process.env.INTLAYER_CLIENT_SECRET,
+
+    /**
+     * URL del panel de control CMS auto-alojado.
+     * Por defecto: https://app.intlayer.org
+     */
+    cmsURL: process.env.INTLAYER_CMS_URL, // ej. http://localhost:3000
+
+    /**
+     * URL de la API backend auto-alojada.
+     * Por defecto: https://back.intlayer.org
+     */
+    backendURL: process.env.INTLAYER_BACKEND_URL, // ej. http://localhost:3100
+  },
+};
+
+export default config;
+```
+
+Establece las variables de entorno correspondientes en tu proyecto:
+
+```sh
+INTLAYER_CMS_URL=http://localhost:3000
+INTLAYER_BACKEND_URL=http://localhost:3100
+INTLAYER_CLIENT_ID=<your-client-id>
+INTLAYER_CLIENT_SECRET=<your-client-secret>
+```
+
+Crea credenciales de acceso en tu panel de control auto-alojado en `http://localhost:3000/projects`.
+
+### SDK `@intlayer/api`: apuntar a un backend auto-alojado
+
+Al usar el SDK de forma programática, pasa `backendURL` explícitamente a `createIntlayerCMS`:
+
+```typescript fileName="cms.ts" codeFormat="typescript"
+import { createIntlayerCMS } from "@intlayer/api";
+import { dictionaryEndpoint } from "@intlayer/api/dictionary";
+
+const cms = createIntlayerCMS({
+  editor: {
+    clientId: process.env.INTLAYER_CLIENT_ID,
+    clientSecret: process.env.INTLAYER_CLIENT_SECRET,
+    backendURL: process.env.INTLAYER_BACKEND_URL, // http://localhost:3100
+  },
+});
+
+const { data: dictionaries } = await dictionaryEndpoint(cms).getDictionaries();
+```
+
+### Características opcionales
+
+Estas características requieren cuentas externas y funcionan correctamente cuando sus claves no están presentes en el `.env` auto-alojado:
+
+| Característica                         | Variable(s) de entorno                          |
+| -------------------------------------- | ----------------------------------------------- |
+| Traducción / auditoría con IA          | `OPENAI_API_KEY`                                |
+| Facturación                            | `STRIPE_SECRET_KEY`, `STRIPE_WEBHOOK_SECRET`, … |
+| OAuth de GitHub                        | `GITHUB_CLIENT_ID`, `GITHUB_CLIENT_SECRET`      |
+| OAuth de Google                        | `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`      |
+| OAuth de GitLab / Microsoft / LinkedIn | `GITLAB_*`, `MICROSOFT_*`, `LINKEDIN_*`         |
+| Correo transaccional via Resend        | `RESEND_API_KEY` (por defecto: Mailpit SMTP)    |
+
+### Persistencia de datos y actualizaciones
+
+Tres volúmenes de Docker contienen todo el estado persistente: `mongo-data`, `redis-data` y `minio-data`. Sobreviven a los reinicios y actualizaciones de contenedores. Volver a ejecutar el instalador descarga las últimas imágenes y realiza un `docker compose up -d` progresivo.
+
+Puertos expuestos en el host:
+
+| Puerto | Servicio                                                            |
+| ------ | ------------------------------------------------------------------- |
+| `3000` | Panel de control                                                    |
+| `3100` | API Backend                                                         |
+| `8025` | Interfaz web de correo Mailpit                                      |
+| `9000` | API S3 de MinIO (necesaria para la carga de assets en el navegador) |
+| `9001` | Consola de MinIO                                                    |
+
+Para una referencia completa de todas las variables de entorno disponibles y opciones avanzadas (proxy inverso, dominios personalizados, respaldo/restauración), consulta la [Guía de Auto-alojamiento](https://github.com/aymericzip/intlayer/blob/main/docs/docs/es/self_hosting.md).
+
+---
+
 ## Depuración
 
 Si encuentras problemas con el CMS, verifica lo siguiente:

package/docs/es/intlayer_with_adonisjs.md

@@ -60,19 +60,23 @@ Ver la [Plantilla de la Aplicación](https://github.com/aymericzip/intlayer-adon
 Para comenzar a usar `adonis-intlayer`, instala el paquete usando npm:
 
 ```bash packageManager="npm"
-npx intlayer-cli init --interactive
+npx intlayer@canary init --interactive    # v9
+# npx intlayer init                       # v8
 ```
 
 ```bash packageManager="pnpm"
-pnpm dlx intlayer-cli init --interactive
+pnpm dlx intlayer@canary init --interactive   # v9
+# pnpm dlx intlayer init                      # v8
 ```
 
 ```bash packageManager="yarn"
-yarn dlx intlayer-cli init --interactive
+yarn dlx intlayer@canary init --interactive   # v9
+# yarn dlx intlayer init                      # v8
 ```
 
 ```bash packageManager="bun"
-bunx intlayer-cli init --interactive
+bunx intlayer@canary init --interactive   # v9
+# bunx intlayer init                      # v8
 ```
 
 > la bandera `--interactive` es opcional. Usa `intlayer-cli init` si eres un agente de IA.