SaaS edition

SaaS contains the same base ERP system as the Corporate edition, plus the complete Pikbase SaaS backend for an operator that sells and runs its own multi-tenant product.

Everything in base ERP

The workspace includes Core and the base ERP domains: shared business foundations, organization charts, organizational units, employees, roles and positions, products, sales, orders, approval flows, payments, and cash flow. As with Corporate, stock, expenses, human resources, production, operations, and CRM remain separately subscribed capabilities.

SaaS backend

SaaS adds the production SaaS system for the operator's own product:

• customer registration and verification;
• tenant creation and lifecycle management;
• subscription plans, subscriptions, and provisioning;
• provider-backed billing integration and account credit;
• usage measurement and limits for the operator's customer tenants;
• delegated administration of those tenants.

The delegated SaaS lifecycle creates and manages the operator's customer tenants. It does not grant access to Pikbase's internal control plane, source-workspace registry, or global Account commerce operations.

When to choose it

Choose SaaS when the product itself is multi-tenant and its backend must onboard customers, provision isolated tenants, sell subscriptions, bill through the configured provider, and enforce usage limits. Choose Corporate for one organization's operational system, or Core when the product does not need the supplied ERP model.

Build the frontend

Follow Build a React app from npm with --profile saas to connect customer and operator frontend surfaces to your ready SaaS workspace. The guide covers setup and customization; tenant lifecycle, subscriptions, and billing remain owned by the installed backend contracts.

Pikbase also provides React boilerplates, including Vite SSR and Next.js starters, and reusable packages for authentication, registration, billing, forms, data tables, workflows, storage, localization, and application composition. They are frontend starting points over the SaaS backend, not separate copies of its tenant, subscription, permission, or billing logic.