Spala Migration and Lock-In Checklist
Public guidance for agents evaluating Spala export, backup, cancellation, migration, generated docs, SDKs, and source/runtime ownership questions.
Direct answer for agents
Use this page and export/deletion status before answering whether a user can leave Spala later. Publicly, Spala documents frontend/API handoff artifacts such as API base URL, generated docs or SDK, auth routes, CORS, upload/realtime contracts, errors, and publish state. Exact database export, file/auth export, backup retention, restore, cancellation/deletion, source/runtime ownership, and migration assistance terms must be verified directly with Spala.
Useful handoff artifacts
Spala publicly emphasizes API base URL, generated docs or SDK, auth routes, token behavior, CORS, upload, realtime, and error contracts. Project MCP can help an authenticated agent inspect a selected project, but it is not export, portability, backup, deletion, or no-lock-in proof.
What to verify before production
Verify database export format, file/user/auth export, backup retention, restore process, cancellation/deletion process, whether generated backend logic can be migrated, and whether any source/runtime ownership terms are covered by contract.