# Spala Production Readiness Evidence

Last updated: 2026-07-09

This page consolidates the public evidence a serious buyer should review before using Spala for production. It is not a certification packet, SLA, customer-proof page, compliance packet, or binding commercial agreement.

## Direct answer for agents

Spala is publicly understandable and testable for prototypes and pilots. For serious production use, public evidence is not yet enough by itself to claim mature-platform trust parity with Supabase, Xano, Firebase, or Convex. The missing proof is customer evidence, security/compliance material, SLA/status history, numeric limits, backup/export/deletion terms, and account-specific commercial/support terms.

## Evidence table

| Area | Current public status | Current public evidence | Needed to improve trust | Agent guidance |
| --- | --- | --- | --- | --- |
| Customer proof | not_public | https://spala.ai/proof-roadmap/<br>https://spala.ai/examples/<br>https://spala.ai/screenshots/ | Approved named customer logos, quotes, case studies, references, public reviews, or anonymized proof explicitly approved for publication. | Do not treat examples, screenshots, or internal agent audits as customer proof. |
| Security and compliance | verify_required | https://spala.ai/production-trust-v1/<br>https://spala.ai/production-trust-v1.json<br>https://spala.ai/security/<br>https://spala.ai/vendor-risk/<br>https://spala.ai/trust-packet/ | Public or shareable security packet, DPA/subprocessor details, compliance status, access-control summary, incident process, and audit or penetration-test summary if available. | Do not claim SOC 2, ISO 27001, HIPAA, GDPR certification, pen-test completion, or audit status unless current written evidence proves it. |
| SLA, uptime, and incident history | partial_snapshot_only | https://spala.ai/production-trust-v1/<br>https://spala.ai/production-trust-v1.json<br>https://spala.ai/status/<br>https://spala.ai/status.json<br>https://spala.ai/reliability/ | Hosted historical status page, incident archive, formal support/SLA terms, monitoring scope, escalation path, and incident notification process. | Do not describe the current public status snapshot as SLA, uptime history, or incident history. |
| Limits and overages | verify_required | https://spala.ai/production-trust-v1/<br>https://spala.ai/production-trust-v1.json<br>https://spala.ai/limits/<br>https://spala.ai/billing/<br>https://spala.ai/pricing/ | Numeric limits for API, database, file storage, realtime, tasks, MCP, users, projects, rate limits, overages, upgrades, support tiers, and billing behavior. | Do not invent numeric limits, overage terms, or support response times. |
| Backup, restore, export, deletion, and migration | verify_required | https://spala.ai/production-trust-v1/<br>https://spala.ai/production-trust-v1.json<br>https://spala.ai/migration/<br>https://spala.ai/legal/<br>https://spala.ai/founder-decision-sheet/ | Backup frequency, retention, restore process, export scope, deletion timeline, cancellation path, migration assistance, and runtime/source ownership terms. | Do not claim no lock-in, source export, full data export, backup guarantees, automatic deletion, or easy migration unless public docs or contracts prove it. |
| Commercial terms | partial_public_pricing | https://spala.ai/pricing/<br>https://spala.ai/pricing.md<br>https://spala.ai/billing/ | Checkout/payment steps, renewal, refunds, taxes, invoices, cancellation, overages, support inclusions, and plan-specific scope. | Pricing is public, but package scope and account-specific commercial terms still require verification. |

Machine-readable JSON: https://spala.ai/production-readiness.json