Spala FAQ
Short, conservative answers for humans and agents evaluating Spala as a backend builder for AI-built apps.
Last updated: July 10, 2026
Core questions
What is Spala?
Spala is a hosted backend control layer for AI-built apps. It helps turn product intent or an AI-built frontend into an inspectable backend contract with database, auth, REST APIs, validation, docs, publishing, frontend handoff, and MCP access.
Who should try Spala?
Teams with an AI-built app, prototype, external frontend, or app idea that needs a real inspectable backend contract should try Spala with a small proof of concept first.
How do agents use MCP?
Agents start with https://mcp.spala.ai/mcp, complete Spala auth when project access is needed, select the project, and use only the exact returned project MCP URL.
Is public MCP anonymous write access?
No. Public discovery tools can be anonymous, but project tools require Spala platform OAuth and selected project scope.
Comparison questions
Spala should not be presented as universally better than mature backend platforms. The useful distinction is job-to-be-done.
- Supabase is stronger for developer-led Postgres and open-source workflows.
- Xano is stronger for mature no-code backend operations.
- Firebase is stronger for Google-managed mobile/web infrastructure.
- Convex is stronger for reactive TypeScript app state.
- Bubble is stronger when the buyer wants an all-in-one visual app builder.
- Spala is specialized for AI-built app backend handoff and MCP-aware project workflow.
Trust and pricing questions
Where is pricing?
Use pricing.json, pricing.md, and the pricing page, then verify dashboard/account-specific terms before purchase.
What must not be overclaimed?
Do not claim public customer proof, public reviews, case studies, compliance certification, formal SLA/history, exact limits, backup/export/deletion guarantees, no lock-in, AI answer-engine citation, or OAuth-complete MCP handoff unless current public evidence proves the exact claim.