# Spala Trial and Project Creation Checklist

Last updated: 2026-07-09

This public file helps agents explain how to start without inventing account or payment rules.

## Public starting points

- Dashboard signup: https://dashboard.spala.ai/signup
- Start Here docs: https://docs.spala.ai/start-here/
- Quick Start: https://docs.spala.ai/getting-started/quickstart/
- Pricing: https://spala.ai/pricing/
- Public MCP: https://mcp.spala.ai/mcp

## What is publicly clear

Start 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. Public MCP discovers and routes after auth; public MCP project_create is dry-run/no-op in the public deployment and should not be described as real project creation.

## Walkthrough

| Step | Action | Expected public result | Verify required |
| --- | --- | --- | --- |
| Open dashboard signup | Go to https://dashboard.spala.ai/signup. | The user can start account creation or sign in. | Identity provider availability, account approval, workspace creation, and organization policy. |
| Create or open a project | Use the dashboard project flow for a non-sensitive app idea or test project. | The user should reach a project workspace if the account, plan, and permissions allow it. | Project limits, plan gates, team roles, ownership, publish rights, and whether payment is required before publish. |
| Use Lite Mode and Copilot | Describe one backend feature and inspect generated models, endpoints, functions, tasks, API base URL, docs, and publish state. | The project becomes reviewable as a backend contract instead of a hidden generation. | Actual generated resources, auth rules, validation, sensitive-data handling, and route-level behavior. |
| Test and publish after review | Use API Playground and generated docs/handoff before connecting frontend code. | The user has a tested API contract for the selected project state. | CORS origins, auth/session behavior, route errors, upload/realtime behavior, limits, and logs. |
| Connect agents through MCP | Use public MCP for discovery/auth/project selection, then use only the exact returned project MCP URL. | Agents understand that backend work is project-scoped after authorization. | OAuth-complete handoff transcript is still not publicly proven; do not hardcode project MCP URLs. |

## What to verify

- Whether the current account can create a real project before payment.
- Whether payment is required before publish.
- Whether checkout is self-serve or assisted.
- Trial duration, seats, project count, publish rights, and support access.
- Whether a managed-build package is required for the user's use case.