Organization, workspace & capacity
Your paid install is one organization. Workspaces split operations inside it. Landing page, storefront (ecommerce), and blog are organization-wide — one of each, no matter how many workspaces you add.
Organization
Your company on inveazy — one install, one subscription, one public site. Branding, domain, and billing sit here.
Workspace (tenant)
An isolated operating unit inside your organization — for example a warehouse, retail store, branch, or division. Own users, inventory, orders, and CRM data. Switch workspaces after sign-in when you belong to more than one.
CRM organization
A customer or partner company you track in CRM — not a workspace and not your subscription. Do not confuse with your Organization above.
Landing page, storefront & blog
One public landing page, one B2B ecommerce storefront (catalog, cart, web orders), and one blog per organization — not per workspace. Extra warehouses or divisions still use the same public site, shop, and blog.
Direct database access
Unlike most SaaS apps that lock you into their UI and APIs only, your install includes optional read-only SQL connectivity (e.g. Power BI, SSMS, reporting tools) against your own database — tenant-isolated.
Scale-up (vertical)
Make one app or database instance larger — more CPU, memory, or Azure SQL DTUs/vCores on the same service. Example: moving from a small Container App / S0 database to a larger SKU because traffic or data grew.
Scale-out (horizontal)
Add more instances or capacity units — extra Container App replicas, read scale, or additional infrastructure — rather than only enlarging one machine. Used when you need more concurrent load or resilience.
Standard capacity vs pricing
List price covers a standard managed footprint. App / DB scale-up or scale-out is only if needed — then we may adjust the subscription. On Self-hosted you pay your own infrastructure for those changes.