Nexus SaaS – Multi-Tenant HR, CRM Project Management Platform

Nexus SaaS lets you sell Nexus as a subscription. Every customer signs up on your landing page, picks a plan, and gets their own workspace on their own subdomain with its own private database – provisioned in under a minute, without you touching a server. You run the platform from a super-admin panel: plans, subscriptions, payments, gateways, support, the landing page and the updater. They run their company from inside the workspace: employees, attendance, leave and payroll; leads, deals, quotes, invoices, contracts and tickets; projects, tasks, sprints and time.

One codebase, two panels. The apex domain is the platform – marketing site, sign-up, super-admin. Each subdomain is a complete Nexus: the full HR, CRM & Sales and Projects product, with its own users, settings, uploads and language, isolated in a database of its own. Nothing is shared between customers except the code.

Provisioning needs no queue worker. A new workspace’s database is created and migrated in a job that runs after the sign-up response has been sent, so the customer sees a “preparing your workspace” page that polls until the login link appears. No Redis, no Horizon, no php artisan queue:work. Taking a payment, activating a subscription and locking an expired one all happen inside the request. A cron entry is optional and only needed for reminder emails and for reclaiming abandoned sign-ups.

Why buyers pick Nexus SaaS

• A private database per workspace. Not a workspace_id column on shared tables — a separate MySQL database, created at sign-up, dropped when the workspace is deleted. A customer’s data can even live on a different database server, with credentials set and tested from the super-admin panel.
• Self-serve sign-up with trial-or-pay-first. A plan with trial days builds the workspace immediately. A plan without one reserves the subdomain and builds nothing until the first payment lands — so a free-tier tyre-kicker never costs you a database.
• Six ways to get paid. Stripe, PayPal, Paystack, Flutterwave, Mollie and bank transfer. Credentials are encrypted at rest; gateways that cannot settle your platform currency are simply hidden from checkout.
• Seat limits that are actually enforced. A plan carries an employee limit and a staff limit. They are checked where accounts and employees are created, with a message that names the limit and points to the billing page — not a number that only appears on the pricing grid.
• Expiry that locks gently and unlocks itself. A configurable grace period, a banner that counts down, and then a lock page that still lets the workspace admin sign in and pay. A renewal — by card or confirmed by you — reopens the workspace the moment it lands.
• The whole product underneath. Every workspace is the full Nexus: three systems sharing one directory of people, 12 permission sections, a client portal, a public careers page, a REST API, 8 languages with full RTL Arabic and a built-in translation editor.

Feature list — the platform

1. Landing page & pricing, edited from the panel

• One marketing page at the apex domain with a hero, feature grid, how-it-works steps, live pricing, stats, testimonials, FAQ, call-to-action and footer — every section editable from a Landing CMS in the super-admin panel, plus SEO fields and standalone privacy-policy and terms pages.
• Pricing is the live plans table. Change a price, a limit or a feature bullet in the panel and the public grid changes with it; each plan’s button deep-links into sign-up with that plan pre-selected. Monthly and yearly prices sit side by side.
• The landing page follows the visitor’s language across all 8 locales, Arabic in right-to-left.

2. Sign-up & provisioning

• The form asks for a company name, a subdomain, a phone number, a plan and billing cycle, and the administrator’s name, email and password. Subdomains are 3–30 characters, lowercase letters, digits and hyphens, and a reserved list (www, app, api, mail, admin, cdn…) that you can extend from settings.
• With a trial the workspace is built at once: a database is created and migrated, the reference data seeded, the administrator created, and the customer lands on a Preparing your workspace page that polls until the sign-in link for {subdomain}.yourdomain.com appears.
• Without a trial sign-up reserves the subdomain and takes the customer to checkout. Nothing is built until the payment is confirmed — by the gateway’s return URL, by a webhook, or by you marking a bank transfer as received. Bank transfer never leaves the site: it shows your bank details and records a pending payment for you to confirm.
• Abandoned sign-ups are released by an hourly saas:purge-unpaid command, so a reserved subdomain that never paid becomes available again.
• Provisioning runs after the response, not on a queue. A failure is recorded against the workspace with the error text, and Reprovision in the panel retries it. An unknown subdomain answers 404, a workspace whose database is not yet built shows a holding page rather than an error.

3. Plans

• A plan is a name, a slug, a monthly and a yearly price, an employee limit, a staff limit, trial days, a list of feature bullets for the pricing grid, an active flag and a sort order. Either limit can be left blank for unlimited; trial days can be zero for pay-first.
• Four ship as examples — Starter, Business, Enterprise and a Pay-As-You-Go plan with no trial — edit or replace them.
• Employees are accounts with the employee role; staff are everybody else (administrators, HR, sales, project managers, accountants). Both counts are read live from inside the workspace’s own database.

4. Subscriptions, payments & gateways

• Subscriptions move pending → trial → active → cancelled, with expired computed from the end date. Filter by search, status, plan and cycle; open one to change the plan or cycle, record a manual payment — which extends the end date by the cycle paid — or cancel.
• Transactions lists every payment across every workspace — amount, currency, gateway, status, reference — with totals for this month and all time, counting only what was actually paid.
• Payment gateways — Stripe, PayPal, Paystack, Flutterwave, Mollie and bank transfer, each switched on individually with its own credentials, stored encrypted. Built-in currency presets keep a gateway off the checkout when it cannot settle your platform currency.
• Webhooks for every gateway at /webhooks/subscriptions/{gateway} sit outside the workspace middleware, so a renewal can always land — even on a locked workspace. Completing a payment is idempotent: the return URL and the webhook can both fire and the subscription is extended once.
• Renewal from inside the workspace — the administrator’s Plan & Billing page shows the current plan with live usage against its limits, lets them renew or switch plan through checkout (paying for a different plan switches both the subscription and the workspace), and lists their payment history.