Skip to main content

AI Builders

Coming Soon

The AI builder integration is not ready yet. It stays locked until it passes a proven end-to-end acceptance.

Use an AI builder for the interface without handing it your authentication boundary. Authenik8 continues to own identity, OAuth, refresh rotation, Redis-backed sessions, revocation, roles, administrator operations, audit events, application data, and secrets.

Lovable

Lovable

Vibe-code the interface in Lovable. Authenik8 stays the only identity, session, authorization, and data authority.

Authenik8 Project Planner (MCP)

Plan and validate an Authenik8 project in ChatGPT, then generate the Lovable integration workflow. Read-only, no repository writes.

The boundary​

AI builder ownsAuthenik8 owns
Layout, forms, application screens, loading and error states, responsive styling, accessible interactionsRegistration, login, OAuth, tokens, refresh cookies, CSRF, sessions, authorization, database access, audit events, and secrets

Frontend route guards improve the experience; they are not authorization. Every protected action must still pass Authenik8 middleware and resource policy on the API.

The one manual step​

The AI builder does not run your backend. After the frontend is built you deploy the generated Authenik8 API separately and point the frontend at it:

  • frontend env var VITE_AUTHENIK8_API_URL=<your API origin>
  • API env var WEB_ORIGIN=<your exact frontend origin>

Everything else happens through the contract. The frontend calls the API only through the Authenik8 client, so the builder can never reimplement authentication even if it tries.