DEV3 Technologies home

Launch Offer: up to 50% off

This item is 50% off: $24.50 instead of $49

Ends in
--
Days
--
Hrs
--
Min
--
Sec

DEV3 Rackbill – Hosting Billing & Client Area Laravel Script with Provisioning, Domains, Dunning & SLA

A self-hosted billing and client area for one hosting company on Laravel 12 and Filament 4: plans on billing cycles, domains, recurring invoices, dunning with suspension and termination, provisioning drivers, tax, tickets with SLAs and an API. Web installer and demo data included. No mobile apps.

by DEV3 TechnologiesVerified Author(0) 0 sales 0 viewsUpdated 08 Nov 2026

Video tour. Pick a section below to browse 109 screenshots in 8 sections.

App & phone tours

Tap play to watch each app. Nothing downloads until you do.

  • Mobile web1:09

Rackbill is a hosting billing and client-area platform that one hosting company installs for itself, built by DEV3 Technologies on Laravel 12 and Filament 4. Your company is the merchant: you sell hosting plans on billing cycles, domains and add-ons, and Rackbill invoices, collects, reminds, suspends and terminates for you. There are no teams or plans to manage.

What it does

  • A store and an order flow. Product groups, plans with a price table per currency and cycle (monthly to triennial), setup fees, configurable options (dropdown, quantity, yes/no), a cart with promo codes and live tax, domain search, and sign-up at checkout. The price shown is the price charged: the preview and the order use the same function.
  • Recurring invoicing. One invoice per client for everything due, generated before the due date, charged to the saved card shortly before it is due, with due dates anchored to the registration day (31 Jan, 28 Feb, 31 Mar). A re-run or a parallel run can never double-bill a period.
  • Dunning and automation. Reminders, a late fee added once, suspension and termination at the days you set, each as a queued module command with retries and a staff alert. Paying at any point un-suspends the service.
  • Provisioning behind a driver. A ProvisioningDriver interface with a complete simulated panel and cPanel/WHM, Plesk and DirectAdmin driver classes ready to finish. Commands carry idempotency keys; a timeout is treated as "unknown" and the panel is asked before the command runs again.
  • Domains. Register, transfer and renew through a registrar driver; renewals extend from the expiry date; grace and redemption periods with fees and staff approval; failures return the money as credit.
  • Money you can audit. Integer minor units, a credit wallet per client, payments, refunds (durable, retried, never lost) and revenue and tax wallets that a daily check ties back to the invoices.
  • Upgrades and downgrades. Prorated by the day, applied only when paid; a downgrade becomes credit.
  • Tax. Rules by country and region, two levels, exclusive or inclusive per currency, EU reverse charge for valid business numbers, a snapshot on every invoice.
  • Support. Departments, canned replies, private attachments, a knowledge base, announcements and SLA deadlines in business hours that pause while a ticket waits for the client.
  • Quotes, promotions and sub-accounts. Client contacts with billing, services, domains, tickets and contacts permissions.
  • A client area built for phones. Pay in one tap, open the control panel with single sign-on, preview an upgrade before committing, reveal an EPP code after a password check, and turn on two-factor authentication. Light and dark, English and Arabic (right-to-left).
  • Five staff roles (owner, billing, support, sales, tech) and a staff panel with the Renewal Runway: ninety days of renewals, one bar a day, split by auto-charge, invoice sent, overdue and suspension risk.
  • An API with OpenAPI: public prices and domain search, client tokens for the client area, and scoped staff API keys.

Install and demo data

A web installer checks the server, writes the configuration, migrates and either loads the demo company or an empty install. The demo shows the fictional Kestrel Ridge Hosting of Harrowmere: 620 clients in nine countries, about 2,150 services in every status, 900 domains, about 14,000 invoices over 14 months, tickets, quotes and promotions. Every demo password is password. Node.js is not needed because the compiled assets are included.

Good to know before you buy

  • Control panels and registrars are simulated until you add credentials and finish the driver class. The cPanel/WHM, Plesk, DirectAdmin and registrar drivers throw driver_not_configured until then.
  • Charging stored cards on real gateways is complete only for the simulated gateway; the Stripe, Razorpay and PayPal chargers are guarded stubs you finish. The VAT number check is simulated.
  • Single company install: no teams, plans or tenant billing. You are the merchant of record.
  • No email-to-ticket and no mobile apps. Tickets come from the client area and the API.
  • Name: Rackbill is a working name checked by a web search only, not a trademark clearance. Check it before launching under it.
  • No hosted demo. The brand, people, products and addresses in the screenshots are fictional.

Quality checks

Rackbill 1.0.0 passed the seven release gates of the DEV3 Laravel suite on the final code: static analysis (Larastan level 6, 0 errors), the Pest suite, a front-end size budget, migrations and seeding on MySQL 8 and SQLite, a headless-browser pass over the public site, the client area and the staff panel with seven race checks on MySQL (parallel invoice runs, Pay now three times, payment against suspension, two upgrades, two provisioning runners, two credit applications, the last use of a promo), an installer test from the package and a secret scan. Lighthouse mobile on the home page scored 97 for performance and 100 for accessibility on the development machine.

#hosting-billing#client-area#provisioning#domain-registrar#recurring-billing#dunning#laravel#filament#php-script#invoicing#sla-tickets

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Rackbill passed before release.

The engineering behind Rackbill: invoice lines that cannot be billed twice, provisioning commands with idempotency keys, a payment settle that refunds duplicates, and a daily check that ties invoices, credit, revenue and tax together.

The problem it solves

Hosting billing is a clock with consequences. Invoices are raised on dates that depend on the registration day, cards are charged, accounts are created and paused on servers the billing system does not control, and a client can pay at the very moment a suspension runs. The system has to stay correct when jobs run twice, when a panel times out after doing the work, when a payment arrives late, and when two staff members click at once.

Architecture and approach

Rackbill is a Laravel 12 application with a Filament 4 staff panel, Blade pages for the store and the client area and a REST API. It builds on the shared DEV3 Laravel core for settings, roles, wallets, audit and gateways.

Dates as pure functions

Billing cycles, proration and SLA deadlines are pure classes with vector files: due dates follow the registration day (31 Jan, 28 Feb, 31 Mar), an upgrade is prorated by the day with half-up rounding, and a ticket due Friday 16:30 plus 120 business minutes is Monday 10:30 across a daylight-saving change.

Lines that cannot be billed twice

The invoice generator locks the client, re-reads, and writes lines with a unique key per item and period. A re-run, a parallel run or an hourly retry adds nothing, and a cancelled invoice frees its keys so the period can be billed again.

Provisioning that survives a timeout

Every state change queues a module command with an idempotency key. The runner claims a row with a conditional update, calls the panel outside any transaction, and moves the service only after the panel confirms. A timeout is treated as unknown: the next attempt asks the panel whether the account exists before it runs the command again.

One lock order

Everything locks in the same order: client, credit wallet, invoice, product, services, domains, server group, promotion. A test records the real FOR UPDATE statements and compares them with that order, and a MySQL race runs a payment against the suspension job.

Money on confirmation

An attempt row is written first under the invoice lock and the gateway call runs after commit. Duplicate and late payments are refunded through a durable queue that retries and finally falls back to account credit, so a refund is never lost.

Books that must tie out

Client credit, the unearned wallet, revenue and tax are ledger wallets. A daily check compares them with invoice totals and payments and fails loudly if they differ.

Quality gates and results

Rackbill 1.0.0 passed the seven release gates on the final code, including Larastan level 6 with no errors, a full Pest suite, a headless-browser pass and seven race checks on MySQL. Lighthouse mobile on the home page scored 97 for performance and 100 for accessibility. The demo seed holds about 14,000 invoices and the daily check passes on it.

Known limits are listed on the item page: real control panels, registrars and stored-card charging need driver work, and the VAT number check is simulated.

Tech stack

Area Technologies
Application Laravel 12, Filament 4, Blade, REST API
Billing Cycle and proration maths, Simulated gateway, Dunning, Credit and revenue ledger
Automation Provisioning driver interface, Registrar driver interface, Idempotent module commands
Concurrency Fixed lock order, Row locks, MySQL race checks
Quality Pest, Larastan level 6, Headless browser smoke, Installer test

Inside the build

Home page: A photograph of a server aisle, the pitch, and a real client-area screen overlapping its edge. Home page — A photograph of a server aisle, the pitch, and a real client-area screen overlapping its edge.

Home in dark mode: The same page for visitors who prefer a dark theme. Home in dark mode — The same page for visitors who prefer a dark theme.

Guides & articles

Practical guides and engineering write-ups for DEV3 Rackbill.

Hosting billing software: 7 things to check before you pick one

Last updated
Hosting billing software: 7 things to check before you pick one: DEV3 Rackbill

Hosting billing looks like invoicing until the first suspended account, the first duplicate charge and the first domain that expired because a job ran twice. Here are seven things to check before you pick software, with DEV3 Rackbill as the worked example.

Video tour — store to renewal

Rackbill home page: a photograph of a server aisle with the headline and a real client-area screen

1. When is the invoice raised, and can it be raised twice?

Invoices should exist before the due date, group everything a client owes, and survive a job that runs twice. Rackbill raises one invoice per client 14 days before due, with a unique line per item and period, so a re-run or a parallel run adds nothing.

2. What happens when a payment fails?

A decline should lead to reminders, a late fee once, suspension and finally termination, at days you control, and a payment at any point should bring the service back at once.

The dunning queue with the stage each overdue invoice has reached

3. Does provisioning survive a timeout?

A panel that did the work and then timed out must not get a second account. Rackbill sends an idempotency key with every command and asks the panel before it retries.

4. Can clients help themselves?

Pay, upgrade with an exact preview, open the control panel, renew a domain and open a ticket should all work on a phone.

Client home on a phone: the next invoice and a Pay button

5. Is tax right?

Rules by country, exclusive or inclusive per currency, EU reverse charge and a snapshot on every invoice, so a rate change never rewrites history.

6. Do support deadlines count business time?

A ticket due Friday evening is due Monday morning, and the clock should pause while you wait for the client.

7. Does the money tie out?

Credit, revenue, tax and refunds should reconcile to the invoices. Rackbill checks this every night.

Limits

Control panels and registrars are simulated until you finish the driver classes, stored-card charging on real gateways is a guarded stub, the VAT number check is simulated, and Rackbill is a single-company install with no mobile apps.

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Buying guides: Laravel scripts with Filament panels and a web installer · Next.js or Laravel for a SaaS script?

More from this author

View all

Related in Web Scripts & Software

View all