Built for the output of AI tools — not despite it.

AI builders generate real, working code. But they generate it fast, and the output doesn’t always match what standard hosting platforms expect. MoonBase is the layer that bridges that gap.

What AI tools generate

AI-generated projects are often structurally correct but deployment-quirky:

• Build artifacts in non-standard locations
• Missing environment variable declarations
• Framework versions with subtle configuration differences
• Output directories that don’t match hosting expectations
• Mixed static and dynamic content without explicit routing

Standard hosting platforms either fail silently or require manual configuration to work around these patterns. MoonBase expects them.

Supported origins

MoonBase accepts projects from any tool that generates code:

AI coding tools

• Claude (claude.ai, Claude Code)
• Cursor
• Lovable
• Bolt
• v0 (Vercel)
• Replit
• GitHub Copilot Workspace
• Any other AI tool that exports a project

Manual exports

• ZIP from any local project
• Build pipeline output (GitHub Actions, CI/CD)
• Direct upload from any development environment

If it runs, MoonBase can host it. There is no compatibility checklist.

Supported frameworks

MoonBase’s Inspector identifies and deploys:

• Next.js — full support including App Router, API routes, server components
• React — CRA, Vite, static export
• Vue — Vite, Nuxt
• Svelte / SvelteKit
• Astro
• Vanilla HTML/CSS/JS — any static project
• Node.js backends — Express, Fastify, and others
• Python backends — Flask, FastAPI (via adapter)

Framework detection is automatic. You don’t declare your stack.

What MoonBase repairs automatically

The Compatibility Engine handles the most common AI-builder output patterns:

What MoonBase doesn’t do

MoonBase doesn’t rewrite your application logic. If the code itself has bugs, MoonBase will tell you — but fixing them is your job (or your AI tool’s job).

MoonBase handles the infrastructure layer. Everything above that is yours.