Assemble your business from modular capabilities.
VioletNexus is a marketplace of modules that all run on one platform. Install exactly what you need, configure each independently, and leave the rest. Nothing is stitched together after the fact — every module shares the same customers, permissions, and audit trail.
14+
Modules on one platform
Independently installable and configurable
1
Shared data & permission model
Customers, roles, and audit trail across everything
0
Integrations to wire yourself
Modules react to each other's events natively
Everything the public sees, and the content behind it.
Website & Pages
Professional pages, SEO metadata, forms, and content blocks.
Files
Central storage for documents, media, and customer attachments.
Marketing
Customer funnel metrics, campaigns, and engagement tracking.
Turn visitors into customers and orders into revenue.
Customers / CRM
Contacts, leads, activity history, and a unified customer view.
Intelligent Store
Products, services, variants, cart, and checkout in one storefront.
Payments
Stripe, PayPal, and manual methods with clean reconciliation.
Invoicing
Invoices, line items, statuses, and reconciliation.
The systems that keep the day-to-day running.
Work Orders
Field jobs, statuses, and automation-ready events.
Inventory
Stock levels, low-stock flags, and an immutable movement ledger.
Events & Bookings
Scheduling, availability, and event operations.
Projects & Tasks
Plan work, assign owners, and track delivery.
Money in, money accounted for.
Invoicing
Billing, statements, and payment status at a glance.
Payments
A single payment abstraction across providers and manual methods.
Analytics / Reports
Revenue, funnel, and operational reporting.
See further and let the platform do the busywork.
Automations
Trigger → condition → action workflows with run history.
Analytics / Reports
Operational dashboards and exportable reports.
AI assistant + insights
In-context help and insights that surface the next best action.
Every module declares how it fits the platform.
Modules aren't loosely coupled plugins bolted onto a template. Each one declares a contract — the plan and permissions it needs, the routes and navigation it adds, its settings, and the events and automations it participates in.
Required plan & permissions
Each module declares the plan it needs and the granular permissions it introduces, all checked server-side.
Routes & navigation
Modules register their own routes and navigation entries so the workspace grows coherently as you install them.
Settings
Configure a module independently — its options live alongside its capabilities, not scattered across the app.
Events
Modules emit domain events (order paid, form submitted, invoice overdue) that other modules can react to.
Automations
Any module's events can drive automations — no glue code, no external orchestration layer.
One shared platform
The same customers, permissions, audit trail, and design system underpin every module you enable.
Start small. Add capabilities as you grow.
Begin with a website and core customer management, then enable commerce, payments, scheduling, and automation when you're ready. Because everything shares one platform, adding a module never means a migration or a re-integration.
A typical growth path
Launch
Website & Pages, Customers / CRM
Sell
Intelligent Store, Payments, Invoicing
Operate
Work Orders, Inventory, Bookings, Projects
Scale
Automations, Analytics, AI insights
Editable at every step — this is a starting point, never a lock-in.
Pick your modules and get building.
Start with the essentials and expand the moment you need more.