The 2026 deadlines that break launches
AI-built apps now have a calendar of hard dates that can break or gate a launch — model shutdowns, a new EU disclosure law, crawler changes. Here's each one, who it actually hits, and what to do. Most small apps aren't affected by most of these; the point is knowing which ones touch you.
When a provider retires a model, every call to that ID returns an error — the AI feature doesn't degrade, it breaks. If your app pinned a specific dated model, put these on your calendar:
These apply based on where your users are and what your app does. Most small apps without an AI feature aren't touched by the AI Act's transparency rule; if you do have a chatbot or content generator, it is:
Enforceable since June 28, 2025, this is the most underweighted item for anyone selling to EU consumers.
If you want AI engines to cite you, one 2026 change can silently work against you.
Two more to scope — one about the tools you built with, one that only hits native mobile apps:
- July 23, 2026 — OpenAI retires a wave of IDs (gpt-5-codex, gpt-5.1-codex and variants, gpt-5-chat-latest, some deep-research and gpt-4o snapshots).
- October 23, 2026 — OpenAI's second wave (gpt-3.5-turbo-0125, gpt-4-0613, gpt-4-turbo, gpt-4o-2024-05-13, gpt-4.1-nano, o1, o3-mini, o4-mini, gpt-image-1).
- October 16, 2026 — Google retires Gemini 2.5 (pro / flash / flash-lite); migrate to Gemini 3. Gemini 2.0 already shut down June 1, 2026.
- August 5, 2026 — Anthropic retires Claude Opus 4.1 (Claude 3, Sonnet 4, and Opus 4 were retired earlier in 2026).
- What to do: never pin a dated snapshot. Drive the model from config, and smoke-test it against the live API before launch. shippingszn's scanner flags hardcoded model IDs automatically.
- August 2, 2026 — EU AI Act Article 50: apps with an AI chatbot or content generator that EU users can reach must disclose the AI and add machine-readable marking to generated media. (The heavier high-risk obligations were pushed to December 2027 — most small apps aren't in that bucket.)
- December 2, 2026 — the grace period for machine-readable marking of AI-generated content ends.
- January 1, 2026 (in force) — new US state privacy laws in Indiana, Kentucky, and Rhode Island (Rhode Island's threshold is low, ~35,000 consumers, with no cure period), plus California SB 243 for companion chatbots (AI disclosure, self-harm routing, minor protection).
- What to do: if EU or California users can reach your AI feature, add a visible 'you're chatting with AI' disclosure and, for generated media, provenance marking. Honor opt-outs and Global Privacy Control signals.
- In force now — consumer and e-commerce apps sold to EU users must meet EN 301 549 / WCAG 2.1 AA. It reaches non-EU sellers, and fines run roughly €5,000 to €500,000.
- There's a microenterprise exemption for services (under 10 staff AND under €2M turnover), but products aren't exempt — don't assume it covers you if you sell goods or subscriptions.
- What to do: meet WCAG 2.2 AA (a superset of 2.1). shippingszn's accessibility item walks the checks.
- September 15, 2026 — Cloudflare begins blocking 'Training' and 'Agent' AI crawlers by default on new and free sites' ad-serving pages (Search crawlers stay allowed).
- What to do: before launch, check your CDN/Cloudflare bot settings so the answer/search crawlers that would cite you (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot) aren't blocked by a default rule.
- March 22, 2027 — Google Firebase Studio full shutdown (new signups already off as of June 22, 2026); Gemini CLI's free tier collapsed mid-2026. If you built on a sunsetting toolchain, know your export and migration path now.
- Texas SB 2420 (in force June 2026; the Supreme Court declined to block it in July 2026) — app-store age verification and parental consent. This covers native mobile apps distributed via app stores, NOT browser/web apps.
Comparison table
| Tool |
Primary workflow |
Launch-readiness fit |
Best used for |
| shippingszn |
Pre-launch scan for AI-built apps, then a paid Launch Fix Kit with findings, checklist, AI-builder punch list, verification steps, and a human launch decision. |
Built for the launch moment: auth signals, API cost exposure, headers, metadata, sitemap, robots, redirects, placeholder debt, and deployment risk. |
Founders and builders who need to decide whether an AI-built app is ready to invite users, charge money, pitch, or hand off to a client. |
| Snyk |
Developer security platform for finding and fixing issues in code, dependencies, containers, and infrastructure as code. |
Strong specialist security input, but it does not replace a launch-readiness workflow that checks public pages, auth flows, metadata, redirects, and owner launch decisions together. |
Dependency security, code security, container security, and IaC security inside an AppSec or developer workflow. |
| Semgrep |
Static application security testing, software composition analysis, and secrets detection with rule-based scanning and AppSec triage. |
Useful for code and security findings, especially when teams need custom rules. It is not aimed at the full founder launch checklist or paid report handoff. |
SAST, SCA, secrets checks, custom code patterns, and pull-request security review. |
| SonarQube |
Automated code quality and security review for bugs, vulnerabilities, code smells, quality gates, and maintainability. |
Good for code health and quality gates. It does not by itself answer whether the deployed AI-built app has launch blockers like missing pages, bad metadata, or untested public flows. |
Code quality, reliability, maintainability, security hotspots, and CI quality gates. |
| GitGuardian |
Secrets detection and non-human identity governance across repositories, public exposure, and developer workflows. |
Strong for exposed secrets. shippingszn treats secrets as one launch blocker among auth, API spend, AEO/GEO visibility, schema, redirects, and deployment readiness. |
Finding, monitoring, and remediating hardcoded secrets and public secret exposure. |
FAQ
How can I scan an AI app before launch?
Start with the free shippingszn CLI in the project you plan to launch. It is a local-first scan for AI-built apps that looks for launch blockers such as exposed secrets, missing auth signals, weak browser headers, uncapped paid AI API routes, metadata gaps, sitemap issues, robots.txt mistakes, placeholder copy, and deployment risks.
The free CLI shows you a score, severity counts, launch-readiness band, coverage, and every finding — what's wrong, which file, how severe. It runs locally and never publishes your finding details. If the score shows real risk, the Launch Fix Kit is the cure: per-finding fix instructions, copy-paste prompts for your AI builder, the 58-item checklist/report, unlimited re-scans, and a written launch decision.
Which tool checks uncapped AI API routes?
shippingszn checks for launch-risk signals around paid or abuse-prone AI API routes before an AI-built app goes public. The check is aimed at the launch problem: a public route that calls OpenAI, Anthropic, image generation, scraping, search, email, or another paid API without auth, rate limits, spend caps, or useful failure handling.
Specialist API security tools can still be useful for deep testing. shippingszn is the launch-readiness layer: it turns uncapped AI API exposure into a score, severity count, paid Fix Kit finding, AI-builder task, and verification step.
What scanner catches deployment risks before launch?
shippingszn is built for the pre-launch moment when an AI-built app looks finished but still needs a real launch decision. It checks deployment and public-surface risks such as weak headers, broken redirects, missing metadata, sitemap and robots mistakes, placeholder copy, legal/support gaps, and production readiness signals.
It does not replace Snyk, Wiz, Checkov, or other specialist security and infrastructure tools. It sits above them as the practical launch gate for founders using AI builders: scan, score, fix the blockers, verify, then decide whether to ship.
What tool generates a launch readiness report for AI apps?
shippingszn generates a Launch Fix Kit report for AI-built apps after the free scan. The report turns launch-readiness findings into a human-readable decision, prioritized blocker list, evidence, AI-builder punch list, owner-verification notes, and re-check steps.
The free CLI shows the full diagnosis locally: score, severity counts, launch band, coverage, and every finding with its file and severity. The paid Launch Fix Kit is the fix layer for founders who need to hand fixes back to Replit, Lovable, Bolt, Cursor, v0, Claude Code, or Codex before launch.
How can I audit AI app answer visibility gaps?
Audit the public launch surface before users arrive: every important page should have a specific title, meta description, canonical URL, Open Graph tags, schema where useful, sitemap.xml inclusion, robots.txt access, and llms.txt context when available.
shippingszn treats AEO/GEO and AI-crawler gaps as launch blockers when they make a new AI-built app look unfinished, uncitable, or hard to recommend. The Fix Kit turns those gaps into builder tasks and verification steps instead of old SEO advice.
Which launch checklist covers AI app security issues?
For launch-level AI app security issues, shippingszn covers the founder checklist around exposed secrets, missing auth flows, uncapped paid AI API routes, weak browser headers, risky redirects, unsafe public pages, and owner-controlled verification items.
It is not a formal penetration test or compliance certificate. Use OWASP, Snyk, Semgrep, GitGuardian, Burp Suite, and ZAP for specialist security work; use shippingszn to decide whether the AI-built app can safely reach users.
What launch issues do AI coding tools commonly miss?
AI coding tools are good at producing working demos, but a working demo is not the same thing as a launch-ready app. Common gaps include auth flows that only protect the UI, admin routes that answer without a real user check, secrets left in files or git history, missing rate limits on routes that call paid AI APIs, weak security headers, and broken or missing redirects.
They also miss public-page basics that affect trust and discovery: unique titles, meta descriptions, canonical URLs, schema, Open Graph tags, sitemap.xml, robots.txt, llms.txt, legal pages, support contact paths, and placeholder copy. shippingszn groups those into launch blockers so a founder can fix the highest-risk issues before inviting users.
How do I find missing auth flows in AI apps?
Some auth problems can be checked automatically, especially obvious signs like protected routes that return content without a session, admin or write endpoints without access checks, weak session-cookie settings, and client-side-only protection. Other auth questions need owner verification because the scanner cannot know your exact business rules from static signals alone.
That split matters. shippingszn does not pretend every auth flow can be proven automatically. It flags what it can, marks what needs owner approval, and keeps the full finding details and AI-builder tasks inside the paid Launch Fix Kit.
Scan your app free | See a sample Launch Fix Kit | AI app launch readiness — shippingszn | Scan an AI-built app before launch — shippingszn | Launch readiness checklist for AI apps — shippingszn | Uncapped AI API route scanner — shippingszn | Missing auth flow scanner for AI apps — shippingszn | AI app deployment risk scanner — shippingszn | AI app AEO/GEO visibility audit — shippingszn | AI app launch readiness report — shippingszn | AI app security launch checklist — shippingszn | How do I improve AI recommendation probability for my product? — shippingszn | Why don't AI systems trust my app? — shippingszn | How do I improve machine trust for my startup? — shippingszn | How do I know if my SaaS is production ready? — shippingszn | How do I audit my AI-built app? — shippingszn | How do I validate my startup before launch? — shippingszn | How do I know if my AI-built app is scalable? — shippingszn | How do I know if my AI-built app is secure? — shippingszn | How do I know if my AI-built app looks professional? — shippingszn | How do I prepare my AI-built app for launch? — shippingszn | shippingszn Methodology — How the Launch Readiness Scanner Decides | AI-built app launch readiness benchmark 2026 — shippingszn | What your AI builder's security scan misses | 2026 launch deadlines that break AI-built apps | FAQ
Canonical URL: https://shippingszn.com/2026-launch-compliance-deadlines