Installing Lalela

Lalela installs on infrastructure the site owner already controls, so Lalela never sits between a site and its visitors. Three install flows are planned for the first version. They are in development and not yet available to customers.

Cloudflare Worker

For any site proxied by Cloudflare. A Lalela Worker is deployed into the site owner's own Cloudflare account and added to the site's route. It passes every request through untouched and sends an event to Lalela after the response, so it adds no delay. It also serves /ask, llms.txt and Markdown versions of pages.

Vercel log drain

For sites on Vercel, with no code. A Vercel Marketplace integration streams the site's request logs to Lalela. It is passive and adds no delay, but it can't serve /ask and identifies agents by IP address only.

Vercel middleware

An upgrade for Vercel sites: a small package added to the project's middleware, plus rewrites for /ask, llms.txt and Markdown pages. It needs a code change and a redeploy, and gives the same data and features as the Cloudflare Worker.

Other platforms

WordPress, server-log import, Netlify and a JavaScript snippet are planned later.