Seven Enterprise Clouds. One real Product Catalog behind them.
Core, People, Customer, Operations, Finance, Communication, and Intelligence — every module in FlashCat.ai belongs to one of these, each with real pricing, real usage limits, and a real release channel, editable from a Developer Console without a code deploy.
7
Enterprise Clouds
39
Cataloged Modules
4
Release Channels
0
Hardcoded Pricing
"Which plan includes what" shouldn't be a support ticket.
In most platforms, feature bundling lives in scattered if-statements across the codebase — so repricing a module, adding a usage limit, or launching a new tier means waiting on an engineering sprint. FlashCat.ai's module catalog is data, not code.
From Cloud to module to real entitlement
Each layer maps to something concrete an organization actually gets or doesn't get — not a marketing label.
Enterprise Clouds group related modules
Core (always-on essentials), People, Customer, Operations, Finance, Communication, and Intelligence — a Cloud is the shelf; modules are what's on it.
Every module is a real, priced object
Pricing model (free, per-user, usage-based...), monthly/yearly price, release channel, and marketplace/white-label eligibility all live as real fields, not comments in code.
Usage limits are configurable, not hardcoded
"Maximum Leads," "Maximum Storage," "Maximum AI Requests" — each module can define its own named limits with a real default value, editable per module.
Entitlement flips per organization, instantly
Turning a module on or off for one tenant is a single toggle against the same key namespace every API route already checks — no redeploy, no per-client code branch.
Where this shows up in your day
People Cloud
HR needs payroll, shift planning, and skills tracking as one coherent suite.
Six real modules, one Cloud, one price to negotiate.
Customer Cloud
Sales wants CRM, client portal, approvals, and risk scoring bundled together.
Four modules that already share the same client record.
Finance Cloud
An agency wants invoicing without unlocking every other module.
One Cloud, cleanly separated billing entitlement.
Intelligence Cloud
A client wants AI studio and automation, but not the full workforce suite.
Ten AI/automation modules, sold and gated independently.
Launching a new pricing tier without a deploy
A Developer opens the Product Catalog in the Developer Console — the same real, live module data every tenant's entitlement check reads from.
They mark the CRM module's pricing model as Monthly, set a price, and add a "Maximum Leads" limit of 5,000.
They add a dependency: Revenue Intelligence Cloud requires CRM to be enabled first — caught automatically if someone tries to sell one without the other.
The change is live immediately. No code change, no redeploy, no engineering ticket.
A tenant's entitlement (whether they can actually reach the module) is decided separately by their own subscription, exactly as it was before — this only changes how the module itself is defined and priced.
Part of one platform, not a bolt-on
Platform Architecture
The Product Catalog is the data layer the entitlement engine (server/services/modules.service.ts) already enforces on every request.
See the ArchitectureSolution Configurator
What a prospect sees when building a plan is generated from the same real module catalog, not a separate marketing spreadsheet.
Try the ConfiguratorWhite Label
Marketplace and white-label eligibility are per-module flags in the same catalog, not a separate manual process.
See White LabelPick your Clouds. Not a fixed bundle.
Configure exactly the modules your business needs — with a 7-day free trial and no card required.