Loxley AI Changelog — Platform and Content Releases
Shipped, dated, and checkable.
Changelog of Loxley AI platform and content releases: security hardening series, billing funnel, CSRF layer, partner analytics, GEO documentation wave and telemetry publication.
Everything on this site and platform ships in small, verifiable releases. This is the public log. Dates are UTC; production behavior was verified live after every entry.
November 2026 — Documentation & trust wave
- 04-11 (web7): GEO/AIO release — comparison pages (vs Maestro, vs Banana Gun, vs MevX), public /docs hub with six technical engine documents, sitewide JSON-LD (Organization, SoftwareApplication, Article, FAQPage), llms.txt rewrite, robots.txt newline bug fixed.
- 04-11 (web8): glossary launch (Telegram trading bot, V4 hooks, trailing stop-loss, white-label, rug pulls) + full ES/FR/NL translation of core pages.
- 04-11 (web9): ES/FR/NL translations for all comparisons and remaining engine docs.
- 04-11 (web10): first database-verified telemetry case study published; founding-cohort numbers public.
- 04-11 (web11): six long-tail guides, four additional engine docs (quoting/routing, custody, AI mode, analytics), Portuguese and German translations, /feed.xml RSS.
- 04-11 (web12): SEO polish — per-language
lang attributes, article OG types, sitemap lastmod, llms-full.txt full-text corpus, site-wide resources footer.
- 04-11 (web13): trust cluster — verification page, comparison hub, about page, this changelog.
October 2026 — Platform hardening & growth foundations
- Late Oct: white-label launch — operator tiers (Free/Starter/Pro/Scale/Empire), partner program with attributed referrals, 48-hour operator onboarding runbook.
- 27-10–04-11 (web1–web6): security and correctness series — secret-decryption fix, Stripe webhook atomics and reconcile loop, rate-limited auth forms, CSRF layer across session types, affiliate-upload isolation (IDOR/XSS), bot-traffic filtering for honest funnel analytics, test-data hygiene.
How releases work here
Every change ships as: backup → one logical fix or feature set → build → health-checked deploy → live end-to-end verification → tagged rollback image. No silent patches. If a wave introduces a regression, the previous image is one tag away.
Read the docs →
Built for operators, not slippage goblins. Talk to us →