Status
Pending
Finish the steps below to make the core operational.
Core installation
Install the SaaS control plane in one guided, supportable sequence.
This flow prepares the database, applies the canonical schema and baseline catalog, and confirms when the supervisor workspace is ready for package publication and tenant onboarding.
Wizard steps
Run the setup in the same order every time.
The installer stays strict on purpose. It avoids partial bootstrap states and keeps the control plane deterministic before any tenant package is sold or activated.
01
Environment
Confirm the core environment
The installer expects a prepared application URL plus database host, port, name and user. This keeps the setup deterministic and supportable.
02
Database
Reach the database server and create the application database if needed
The wizard verifies connectivity first. If the target database is still missing, the installer creates it before migrations run.
03
Migrations
Apply the canonical core schema and package catalog
Schema migrations remain the single source of truth. The installer runs the same migration service used by normal operations.
04
Seed
Load baseline modules, plugins, currencies and commercial packages
The baseline seed prepares the marketplace, reusable plugins and default commercial packages so the control plane is operational immediately.
Keep installation, marketplace publishing and tenant activation on one governed platform flow.
The public, supervisor and tenant surfaces stay easier to operate when the control plane starts from one clean installation contract and one shared UI shell.