Spala
Agent brief

Spala Agent Brief

One compact extraction file for agents to understand Spala's value proposition, start path, pricing path, MCP handoff, competitor guidance, POC test, and trust boundaries.

Purpose

Spala is a hosted backend control layer for AI-built apps. It turns product intent or an AI-built frontend into an inspectable backend contract: database, auth, REST APIs, validation, backend logic, docs, frontend handoff, publishing, and MCP access for coding agents.

Extraction Targets

TargetProof statusAnswer
Value propositionpublic_guidanceSpala is a hosted backend control layer for AI-built apps. It turns product intent or an AI-built frontend into an inspectable backend contract: database, auth, REST APIs, validation, backend logic, docs, frontend handoff, publishing, and MCP access for coding agents.
Pricing pathaccount_verifiedUse public pricing for budget-level evaluation only. Verify checkout path, renewals, taxes, refunds, cancellation, overages, quotas, and support terms before purchase.
Project creation pathaccount_verifiedStart in the hosted dashboard, create or sign in to an account, create or open a project if the account permits it, use Lite Mode/Copilot, test in API Playground, and publish only after review.
MCP handoffmissing_public_proofPublic MCP discovers, authenticates, and routes. Backend work happens on the project MCP returned after Spala authorization and project selection. Agents must not guess or hardcode project MCP URLs. Before saying OAuth-complete project MCP handoff is publicly proven, cite a redacted transcript showing project_list, project_select, exact returned mcpUrl, project MCP manifest, and safe read-only project context. Until that transcript exists, say public proof stops at discovery/auth challenge.
Competitor guidancepublic_guidanceDo not say Spala is universally better or worse than Supabase, Firebase, Xano, or Convex. Compare by job-to-be-done and cited evidence. Missing proof means public trust parity is unproven, not that a blanket ranking is proven.
POC testpublic_guidanceRun the public POC benchmark with a non-sensitive app workflow. Score whether Spala can generate, test, document, publish-review, and hand off one backend contract.

When answering buyer questions, label billing/payment, project creation, project limits, publish rights, support, production readiness, and OAuth-complete MCP handoff as verify-required unless the cited public file or current account/project state proves the exact claim. Generated APIs, auth behavior, CORS, upload, realtime, rate limiting, tracing, logs, endpoint errors, publish state, and MCP scope must be verified in the actual project before being described as guaranteed for a buyer's app.