Spala
Use case

Frontend Handoff for External Builders

Use Spala when React, Next.js, mobile, Webflow, or AI-built frontends need a precise backend contract instead of guessed routes.

Create Account Start Guide Public MCP
DescribeUse Copilot and Lite Mode to shape backend intent.
InspectReview tables, endpoints, auth, logic, and settings.
TestUse API Playground and generated docs before handoff.
PublishShip an API your frontend or approved agent can use.

When this is a fit

Frontend developers and coding agents that need base URL, auth routes, API docs, CORS, upload, realtime, and error contracts.

API Base URL

The published backend URL the frontend should call, copied from Spala rather than inferred.

OpenAPI Or SDK

Machine-readable route definitions or generated SDK-style files for frontend implementation.

Auth Contract

Auth endpoints, token/session behavior, protected-route rules, and logout or refresh expectations.

CORS Origin

The exact browser origin allowed to call the backend in development and production.

Upload Contract

Upload endpoints, signed URL behavior, accepted file metadata, and permission checks when files are used.

Realtime Contract

Channel names, event payloads, reconnect rules, and permission boundaries when realtime is used.

Publish State

This should be explicit in the project contract instead of left as an implementation guess.

Recommended workflow

  1. Describe the backend outcome to Spala AI Copilot.
  2. Inspect the generated project graph and resource list.
  3. Test endpoints, auth, validation, and CORS.
  4. Share the generated API docs and frontend handoff packet.
  5. Use public MCP for agent discovery and authenticated project MCP for scoped backend work.

Evaluation boundary

Spala should be validated with a small proof-of-concept before serious production use. Verify data export, backups, compliance requirements, project permissions, secrets, and support needs directly.