Workspace editions

A workspace edition selects the backend capabilities present when Pikbase creates a workspace. It does not select a frontend framework, visual theme, or finished application. Every edition is a governed workspace with its own data, users, permissions, functions, workflows, documents, audit, and operational boundary.

Workspace and tenant refer to the same platform context. The console calls it a workspace; backend APIs use tenantCode and CLI commands use --tenant. An edition selects what is installed in that context. It does not create another account or a second isolation boundary. See core concepts and authentication and workspace access.

Compare the editions

Edition	Backend included	Choose it when
Core	The standard Pikbase platform	You are defining your own business model and workflows without the ERP domain model.
Corporate	Core plus the base ERP system	You need sales, orders, products, organization structure, positions, approval flows, payments, and cash flow as a starting point.
SaaS	The same base ERP plus the complete SaaS backend	You operate a multi-tenant SaaS product and need registration, tenant lifecycle, subscriptions, billing, metering, and delegated provisioning.

Corporate includes a base ERP system, not a claim that every ERP domain is included. Stock, expenses, human resources, production, operations, and CRM are separate capabilities rather than part of the base edition.

Frontend choices

The edition is independent from the frontend. Pikbase provides React boilerplates for supported application shapes, including Vite SSR and Next.js starters, plus reusable @gsb-core/* React packages for authentication, forms, schema-driven data tables, references, workflows, billing, storage, localization, SSR, and application composition.

Follow Build a React app from npm to choose the matching core, corporate, or saas frontend profile and initialize your app. You can also compose the packages into an existing React project. Both approaches call the workspace through the established client and authentication contracts. The frontend does not duplicate the workspace's permissions, workflow rules, subscription logic, or other backend behavior.

What can be added later

An edition establishes the workspace baseline. Separately sold capability packs can extend that workspace later without changing what the original edition means. This keeps the initial choice clear: select Core for a custom business backend, Corporate for the base ERP domain, or SaaS when your product must operate its own customer tenants and subscriptions.

Those SaaS customer contexts (subtenants) belong to the application you operate. Keep their subscriptions distinct from the paid platform workspace purchase. Account signup is identity-only and does not provide a free workspace.

Next steps

After purchasing a workspace, connect a React starter or inspect the backend from the CLI. Use the workspace code wherever the integration asks for a tenant code.