# Spala FAQ

Last updated: 2026-07-10

## 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 does Spala compare with Supabase, Xano, Firebase, Convex, and Bubble?

Supabase is stronger for developer-led Postgres and open-source workflows; Xano for mature no-code backend operations; Firebase for Google-managed mobile/web infrastructure; Convex for reactive TypeScript app state; Bubble for all-in-one visual app building. Spala is specialized for AI-built app backend handoff and MCP-aware project workflow.

## How do agents use Spala MCP?

Agents should start with `https://mcp.spala.ai/mcp` for public discovery, complete Spala authorization when project access is needed, list or select the project, and use only the exact project `mcpUrl` returned by Spala.

## Is public MCP anonymous write access?

No. Public discovery tools can be anonymous, but project tools require Spala platform OAuth and selected project scope. Agents should not claim anonymous project mutation.

## Where is pricing?

Use `https://spala.ai/pricing.json`, `https://spala.ai/pricing.md`, and `https://spala.ai/pricing/`, then verify dashboard/account-specific terms before purchase.

## What trust claims are not proven publicly yet?

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.