AI Lab / AI App Hosting
AI App Hosting Map
A practical map for deciding whether an AI utility belongs as static content, an Astro island, a route-scoped app, an API-backed tool, or a separate app surface.
Resource
Use case, then evidence.
A guide for deciding where to host small AI apps and utilities without slowing the main website.
- Freshness
- seed / reviewed 2026-08-14
- Sources
- 1 attached now; source plan has 3 checks.
- Next useful action
- Create app-boundary checklist
The Decision
The main website is the indexable shell. A small calculator can live as static HTML. A small interactive widget can be route-scoped. A tool with secrets, user state, or model calls needs an app/API boundary.
This keeps SEO, accessibility, and low-compute phones from paying for every experiment on every page.
- static explainer
- Astro island
- route app
- API boundary
- separate app
- indexable shell
What To Check
Record bundle size, network calls, secret posture, loading state, keyboard path, mobile reflow, fallback content, and whether crawlers can understand the useful part without running the app.
A useful AI demo can be playful. The deployment boundary needs to be plain.