Skip to main content
SaaS (Software as a Service) means multiple customers use the same online application. Customers get accounts and access, but not a separate project copy.

​
How it differs from other delivery modes

  • Copy project: Creates an independent copy for the customer; they can keep copying after receiving it.
  • Transfer project: Hands ownership to the customer; they can keep copying after takeover.
  • App marketplace: Customers fork a project from the marketplace; marketplace forks cannot be copied again.
  • SaaS: All customers use one app, operated by the creator, without delivering project copies.
If you need ongoing maintenance, unified releases, and per-customer data and permissions, build it as SaaS.

​
Core modules

  • Sign-up, login, and account management
  • Roles and permissions (admin, member, end user)
  • Multi-tenant data isolation
  • Plans and usage limits
  • Admin console
  • Notifications and operations capabilities
  1. Clarify target customers and core scenarios.
  2. Finish page prototypes and main flows first.
  3. Design accounts, roles, permissions, and data isolation.
  4. Build the admin console and customer-facing app.
  5. Use code review and automated tests for critical flows.
  6. Publish and connect a custom domain.
Copying or transferring a project does not automatically make it SaaS. Accounts, multi-tenant isolation, and operations capabilities must be built into the project separately.