From a business idea to a management platform you can resell to your clients.
Better than starting from scratch: console and modules ready to assemble — you compose the vertical and ship it. How assembly works comes next.
Compose the vertical, ship white-label, keep licenses and fleet. You earn on the product — not on hours lost starting from scratch.
Tired of complex, expensive platforms? Run your own, in full autonomy, at a truly low cost — without a vendor locking you in.
Console, switchable modules and core updates always included. You choose what to turn off and what to ship.
We would love to become your supplier. Come try us..
novaFramework is an operating base made of preset, editable modules. Turn pieces on, off, and adapt them: from the same factory you get a CRM, a CMS, a vertical ops system, or the mix you need — without starting from zero and without a monolith you cannot split.
Users, settings, content, mail, licenses and more arrive with behavior and UI already in place. Use them as-is or evolve them: you always start from something that works.
Pick domain modules — sales, editorial, support, fleet… — and turn the rest off. Same factory, different products for clients or for your company.
Create an account or sign in: open the console, turn a piece off, watch it leave the menu. In minutes the model is clear — and it is already the product you will use.
It is not just “software to install”. It is a factory: assemble, ship and govern sites. Here is the cycle — plain language.
This is the factory “basic”: console, page shapes, languages, scheduled tasks and install. Required pieces — the minimum to work and resell without starting from scratch.
Login, users, roles and permissions: who enters and what they can do.
Home with useful tiles; area menu that only shows pieces left on.
Site, security, look: operational parameters in clear cards.
Buttons, tables, alerts, sections… the same language across the whole console.
IT/EN interface texts and checks for missing translations.
Timing engine and jobs: backups, reminders, background work.
Beyond the base you can turn on reusable services (engines) and product pieces (CRM, subscriptions, partners…). Turn them off and menus and features disappear — with no orphan leftovers.
Sending, templates, SMTP tests — only if the piece is on.
In-console alerts for staff (and linked channels).
Action history, archives, keys and cost estimates for external services.
Site identity, update packs, fleet health.
Public pages and content (when the site piece is in use).
Reseller console, blueprints, AI Assistant, packs to sites.
Four clear layers. Pieces do not call each other at random: they talk through messages (events). That makes soft-off safe. Data lives in one database, with tables per piece.
Access, database, files, security, events: the invisible engine under the console.
The console you use every day: menu, users, basic settings.
Email, logs, backup, licensing… shared services products reuse without copying code.
Your vertical (partners, subscriptions, site…): each in its own folder, updatable alone.
You have a factory of pieces. Now: build the vertical in the UI, package only what you need, deliver to sites — and govern what stays on.
Settings, UI objects, blueprints and Studio Forge. CRM, CMS or mix: the platform type takes shape where you already work — no parallel project. — See Forge →
Basics plus only what you need. Shared blueprints or private pieces after HQ quarantine: ship what matters, nothing else. — See path →
White-label, licenses, selective updates and fleet health. The partner resells assembled platforms; you remain the factory. — OEM Partner →
Real soft-off, events between packages, Mirror. Every piece has a clear owner and turns off without leftovers. — Modules →
This is where you live the platform after sign-in: one workspace where active modules appear in the menu. Dashboard with KPIs and widgets, same objects and language on every page — create an account or sign in and see it right away.
KPI tiles, charts and widgets tied to active pieces: see site status without opening ten screens.
Each area has a primary hub and sub-items — and if you turn a module off, the item disappears. The top bar keeps only page actions.
Palette and shapes follow the active theme: change look once, the whole console stays consistent.
Parameters for the platform you assembled: three families on the left — Platform, Maintenance, Extensions — typological cards on the right. Each package shows only its parameters; turn a module off and its entry disappears.
Who uses the assembled platform: accounts, roles and privileges in one area. Roles teach console pieces — not an abstract sheet, the real page.
You assemble different pieces, but the look stays one. Buttons, toggles, alerts, KPIs, tables, sections: platform objects. In System → Objects you tune colors and sizes; every page reuses the same typologies — whether CRM or CMS.
The home of the assembled platform is composed: KPIs, charts and lists that modules register when active. You enable and arrange them; Mirror decides if the block stays visible.
On the platform you assembled, Mirror opens the full console (real data) and with the dots you tune menus and objects for that role. Hidden does not delete the piece: it leaves a styled ghost — same shape, no data — so the layout does not collapse.
Assemblability is not a slogan. Required shell, switchable engines, domain modules. Integration goes through events: module off = zero menus, zero listeners, zero leftovers. You update a capability by shipping only the owner folder.
Forge turns composition into a vertical recipe: pick blueprints, attach ready pieces and evolve only what you need. Then AI Assistant adapts modules with plain instructions and publishes to the trial site — protected staging, delivery to the client site, no IDE in production.
Start from schemas and modules already assembled. Write what you want in plain language: a proprietary algorithm prepares the plan — only blueprint pieces and platform UI objects, no invented interfaces. AI Assistant publishes to the project trial site; if it looks good you confirm and continue until the work is complete. No usage fuel tank.
When the assembly is delivered, every site has an identity (UIP): keys, update pieces and fleet heartbeats. Without a license the site stays usable — the update channel does not. You control what reaches your clients’ installations.
Fixed conversion price, clear in the wizard Partner console → organizations → sites (UIP) AI Assistant: text → plan → trial site → confirm Fee tied to live sites — no usage surprises
Coherent console: users, settings, useful modules Selective updates without breaking the site Only modules left on: no dead weight Site identity and health under partner control
Partners start from the same modular factory. In the HQ site they assemble verticals for their clients, deliver packs to UIPs and monitor the fleet.
Sign in, try, then choose. Basics included, fixed-price conversion in the wizard, fee only on online sites — you see it before you start.
Shell, objects, scheduled tasks and factory basics: already in the platform.
In the wizard you pick blueprint and package: you see the amount right away — no usage tanks.
You pay for sites that stay online. First site includes months per the active price list.
First you sign in and understand the modules. Then, in the wizard, you see the clear cost: work in a dedicated folder, declare pieces and deliver — no consumption tanks.
In short: base always included, extras by piece, AI Assistant on the vertical, Mirror for permissions, OEM to resell. Clearer than an empty framework, more assemblable than a locked CMS, faster than custom from scratch.
Recommended
Access, HQ demo or a tailored blueprint. We reply with the best path — or create an account and try the modules right away, with no commitment.
Create an account, sign in and assemble: turn a module off, open Settings, look at the console. Then decide if you want to become a partner.
This site uses technical cookies required to work. We do not use profiling cookies without your consent. Continue only if you accept.