All Activity

@Web Host Pro, as far as the current docs go, there's still no native Turnstile option. The 9.1 Captcha Protection page lists the built-in captcha types as the default 6-character image code, reCAPTCHA v2 (checkbox and invisible), reCAPTCHA v3, hCaptcha and Invisible hCaptcha, so Turnstile only comes in through a third-party module or your own hooks for now. Before buying anything, I'd try the native options properly, because a lot of the "captcha is a mess" pain I've seen on WHMCS installs comes from the setup around it rather than the captcha itself: 1. Switch to reCAPTCHA v3 or Invisible hCaptcha and tune the score threshold. WHMCS's own docs recommend reCAPTCHA v3 or hCaptcha over the older types, and with an invisible type most real customers never see a challenge. Start a bit lenient and tighten it if spam orders get through. 2. Only protect the forms that actually get abused. Under Captcha for Select Forms, tick checkout, registration, login, contact and tickets as needed, and set Captcha Form Protection to "Enabled for Unauthenticated Visitors Only" so logged-in clients aren't challenged at all. 3. If the site is behind Cloudflare, make sure Rocket Loader and script minification are off for the WHMCS hostname. WHMCS calls these out as incompatible, and Rocket Loader rewrites how page scripts load, which can stop the captcha widget from rendering or submitting properly. That looks exactly like "captcha is broken". 4. Also behind Cloudflare: add Cloudflare's ranges as trusted proxies under the same Security tab, otherwise every login, order and fraud check sees a Cloudflare IP instead of the visitor. If you still want Turnstile, there are a couple of modules for it on the WHMCS Marketplace now. When picking one, I'd check three things: that it verifies the token server-side (siteverify) and doesn't just render the widget, that it covers checkout and not only login and registration, and that it lists your exact WHMCS 9.x version and your template, since these modules hook into the order form and client area templates and are the first thing to break after an upgrade. Test it on a staging copy first. Either way, if you add Turnstile, set the native Captcha Type back to off for the same forms so customers don't get two challenges stacked on top of each other.

WhatsApp Notification WHMCS Module – v1.1.3 Released Automate WhatsApp notifications from WHMCS to keep customers informed about important account activities, service updates, and billing events. Changelog highlights: Updated the module for compatibility with WHMCS 9.1. Added support for PHP 8.4.x. Added support for ionCube Loader 15.x. Updated the module for compatibility with the latest Twilio API. Compatibility: WHMCS 9.1, PHP 8.4, ionCube Loader 15.x Buy Now | View Changelog

Hetzner Cloud WHMCS Provisioning Module – v1.4.2 Automate Hetzner Cloud server provisioning and management directly through WHMCS. Changelog highlights: Updated the module for compatibility with WHMCS 9.1. Added support for PHP 8.4.x. Added support for ionCube Loader 15.x. Compatibility: WHMCS 9.1, PHP 8.4, ionCube Loader 15.x Buy Now | View Changelog

Your hook will work, but I wouldn't run it in production as is. It fires a hidden iframe GET at the admin "close client" URL for each row, so you get no error back if one fails, several requests can run in parallel if you add bulk selection, and you depend on an internal admin URL and token handling that can change between versions. The cleaner way is to call the official API instead of replaying the admin page: 1. Build it as a small addon module (or at least a dedicated admin-only endpoint). An addon gives you an admin page plus access control by admin role, so not every staff member gets a "close clients" button. 2. Your list button only collects the selected client IDs and POSTs them, with the CSRF token, to that addon page. 3. On the server side, loop over the IDs and call localAPI('CloseClient', ['clientid' => $id]) for each one, collecting the result per client so you can show "closed 14, failed 1 (reason)" instead of reloading blindly. Per the API docs, CloseClient does the same thing as the Close button: it closes the client, cancels their invoices and sets all their products to Cancelled or Terminated. It also fires the ClientClose hook, so anything else you have tied to closing still runs. One thing to test on a single client first: the docs only talk about statuses, so check whether the account is actually removed from the server (cPanel/Plesk etc.) or whether you still need to run Terminate on those services separately. About SQL: please don't do it by setting the status to Closed in tblclients. That only changes the label. Services stay Active, unpaid invoices stay open, the cron keeps generating renewals and sending reminders, nothing is written to the activity log and no hooks run. Going through CloseClient avoids all of that. If you just need this occasionally rather than daily, the same loop works as a one-off script that reads a list of client IDs. Take a database backup before the first big batch either way.

Passkey Authentication Module v1.1.2 Released We’ve released version 1.1.2 of our Passkey Authentication Module with latest WHMCS 9.1 compatible and supported PHP 8.4.' More details: https://whmcsglobalservices.com/whmcs-modules/passkey-authentication/ Update the module to latest. Upgrade to Open Source and avail 50% flat off today.

WGS VMware Module v5.1.2 Released! We're pleased to announce the release of WGS VMware Module v5.1.2, bringing several bug fixes, security improvements, and compatibility updates. This update focuses on improving snapshot management, VM operations, console functionality, and overall module stability. What's New & Improved? Snapshot Management: Added individual snapshot revert functionality and fixed issues with snapshot deletion and revert operations. Client Area Fixes: Resolved blank tabs and loading issues affecting Snapshot, Migrate, Console, Reinstall, and Backup. VM Termination: Improved handling of suspended VMs and the "Enable suspend VM on terminate" setting. Security Enhancements: Improved security across the client area, VNC console, and admin area. Console PIN Security: Added PIN expiration and account lockout after repeated incorrect attempts. Cron Security: Restricted module cron execution to command-line access. PHP 8 Compatibility: Fixed PHP 8 errors affecting VM upgrades, OS reinstalls, IP cron, cart, and admin pages. Compatibility Updates WHMCS 9.1x PHP 7.4 – 8.4 jQuery 4 ionCube 15x We've also cleaned up unused files from the module package. Release Date: 11 November 2026 Version: 5.1.2 For the complete changelog and module details, visit: https://whmcsglobalservices.com/vmware-whmcs-module/ If you're already using our VMware Module, we recommend updating to the latest version to benefit from these improvements. Upgrade Notes - Back up the existing files & Database before uploading. - After uploading, go to Utilities > System > System Cleanup and click Empty Template Cache. Upgrade your license to Open source and save flat 50% OFF on open source (One time) service. Thank you for your continued support!

At 40-60 clients WHMCS is worth it mainly for the boring parts you're already fighting: recurring invoices, overdue reminders, suspensions, and domain renewals that line up with the registrar. Most of the "overhead" is a one-off setup weekend, not ongoing work. I run hosting billing day to day, and the switch goes fine if you treat it as a data import, not as placing new orders. What I'd check before committing: 1. Export everything from your tool first: clients, each service with its billing cycle, recurring amount and next due date, and each domain with its registrar expiry date. That spreadsheet is your source of truth for the move. 2. Set up products, pricing, payment gateway, currencies/tax and email templates before importing anyone. Make sure each product's billing cycles match what clients actually pay today. 3. Import without triggering anything. Either add orders from the admin area with invoice generation, the order confirmation email and module create unticked, or script it with the API (AddClient, then AddOrder with noinvoice and noemail). Then set the real next due date and registration date on every service and domain (UpdateClientProduct / UpdateClientDomain take nextduedate, regdate and, for domains, expirydate). This step is what keeps renewals from breaking: WHMCS bills off the next due date, so if that's wrong you either double-bill or miss a renewal. 4. Check the recurring amount on each service. If someone is on an old price, keep that amount on the service rather than letting it recalculate to the current product price. 5. Hook up your registrar module and run domain sync so expiry dates come from the registrar, not from memory. Decide per domain whether it should auto-renew. 6. Keep invoice generation and emails cautious for the first cycle. Look at the invoice generation lead days in Automation Settings, let the cron run for a day or two, and look at what it would invoice before clients start getting emails. Running the old tool in parallel for one billing cycle is cheap insurance. 7. Card details generally can't be moved from a home-built tool. Plan for clients to re-enter them, or use a gateway that stores them on its side, so the first auto-charge doesn't fail. Things that usually surprise people: how much time goes into email templates and the order form, and that the cron has to run every 5 minutes for automation to behave. Plan for a weekend of setup plus a week of checking, not more.

I run a small hosting setup for local clients here in Portland, Maine, and I've been putting together an internal billing tool with an AI app builder to keep track of accounts and renewals. It works fine for what I need, but I keep running into limits as soon as I try to handle recurring invoices and domain renewals properly, and I can't keep patching it myself. I'm weighing whether a WHMCS license makes sense for someone at my scale, maybe 40–60 active clients, or if the overhead of a full billing platform would be more than I actually need right now. My biggest worry is migration — I don't want to lose client records or break existing renewals during a switch, and I'm not sure how much manual setup the initial configuration really takes. Has anyone moved from a home-built or lightweight tool to WHMCS at a similar size? What surprised you during the switch, and what would you check before committing?

is there an issue with your servers? my installs are refusing to register their licences after upgrading and your site is not coming up only a cloudflare page

As is the fact you're touting the exact same site as he is. Paid spammers, looks like. At least three on this site that I've seen. Sad.

The paste mix-up is worth flagging, sure, but the export question matters more for my situation. I'm in Portland, Maine, weighing a paid AI builder plan for a small trail-condition log I'd share with a local hiking group, and I'm uneasy about paying monthly if the entry tier caps database reads. Even at low volume, I'd rather not discover a limit after the group starts relying on it. What I'd decide first is whether export is included so I could fall back to a static site if costs creep. I came across AI App Builders vs Traditional Development https://aibuildercompare.com/blog/ai-app-builders-vs-traditional-development which compares approaches, though I haven't verified the numbers. Does anyone know how entry tiers handle export?

Did you perhaps log in with the wrong account to reply to this post and quietly name drop the site there? Or perhaps you used AI to write them both and missed where it answered you with your own name and simply pasted it here? Very odd.

Nathan, the export question is the one I'd nail down before paying anything — some tiers only let you pull code on higher plans, which quietly locks you in once the project grows. I'm weighing a similar choice for a small inventory helper and leaning toward starting on a free tier just to see how fast credits actually burn. I came across a comparison at Best Framer Alternatives (2026) https://aibuildercompare.com/alternatives/framer that lists plan differences, though I can't vouch for how current the numbers are. My worry is that monthly credit limits bite faster than the marketing suggests once database calls are involved.

Thanks for writing this up properly, the repro steps are clearer than most tickets I've seen. Nobody's replied in a while, so a few things that might help anyone else who lands here while it's open. On the expiry part: I don't think that piece is a separate bug. Per the Promotions docs, the expiry date only stops the code being used on new orders. Anything that already has a recurring promo attached keeps it on future invoices until the "Set Recur For" count runs out, and if that's 0 it keeps it forever. So once promoid gets written to the domain, the expiry won't save you. The real bug is the first half, the promo getting associated with a TLD it never applied to. Until it's fixed, what I'd do on a live install: 1. Audit it. Take a DB backup, then pull every row in tbldomains where promoid isn't 0 and join it to tblpromotions on the promotion id so you can see the code and its Applies To list next to each domain. Any domain linked to a promo whose Applies To has no TLDs (or not that TLD) is affected. On most installs that list is short enough to check by hand. 2. Clean it. Set promoid back to 0 on those domains only. Then check for unpaid renewal invoices that already went out with a PromoDomain line, because clearing the field won't touch invoices that already exist. Edit those or cancel and regenerate them. 3. Limit the damage going forward. For hosting-only recurring promos, give "Set Recur For" a real number instead of leaving it unlimited, so even if one leaks onto a domain it stops on its own. If you run promos for marketing, it's also worth telling staff not to apply them in the cart when a client is only renewing domains. 4. Recheck after each cron run for a while. A saved query you rerun weekly is enough to catch new ones until a fix ships. Have you opened a ticket with this repro? If support gives you a case ID, please post it here so others can track it in the changelogs. Did you also test this on 9.x, or only 8.13?

I'm Nathan, based in Cheyenne, and I'm exploring an AI app builder for a small side project. Before committing to a monthly subscription, I'm trying to understand how the pricing tiers stack up for a solo user who mainly needs basic app scaffolding and maybe occasional database integration. The tiers seem to range from free plans with limited generations to paid plans that unlock more credits and export options. One concern is whether the entry-level paid plan is enough for a simple project, or if I'd quickly hit usage limits and need to upgrade. I also wonder if free tiers restrict exporting the code, since that would matter if I later want to move things elsewhere. I haven't signed up for any trial yet and am just gathering third-party pricing info. For those who've compared these tools, how did the real monthly costs play out for small projects, and were there hidden limits I should watch for? Any input would help.

Still weighing this - checking Best AI Mobile App Builders (2026) https://aibuildercompare.com/best/ai-mobile-app-builders to see how these platforms handle API calls and authentication, since that's the part I'm least sure about. Not confident it settles the WHMCS question, but it gives me more to compare before committing to a builder.

@Michael Wilson I'd go 2 GB as the floor, and here's why from running a few of these. At your size WHMCS itself isn't heavy. What eats memory is PHP-FPM workers plus MySQL/MariaDB with a sane InnoDB buffer pool, plus whatever panel you bolt on. On 1 GB it works until the cron, a backup and a few client logins overlap, and then you're swapping right when the invoice run is going. 2 GB with a small swap file gives you breathing room. Get NVMe or at least SSD storage. Cheap plans on spinning disk or heavily oversold storage are where cron jobs crawl, and you can usually tell by testing disk speed in the first week. Before you move, check why the invoice runs struggle now. On shared hosting it's often not raw power but the account limits: CloudLinux LVE caps on CPU or entry processes, a short max_execution_time, or the cron being run through wget/curl over HTTP instead of the PHP CLI, so it gets killed partway. Your Activity Log and the cron output will usually show it. That tells you whether you need a bigger box or just your own limits. On the panel: I'd keep WHMCS on its own server, separate from the cPanel server your clients are on. That way a client site getting hacked or hammered doesn't take billing down with it, and you're not paying for a cPanel licence just to host WHMCS. A plain Linux VPS with nginx or Apache, PHP-FPM, MariaDB and the ionCube Loader is plenty. If you don't want to manage it from the command line, a free or low-cost panel is fine. Just make sure it supports the PHP version your WHMCS release needs, since some lag behind. Things I'd do differently looking back: 1. Set up off-server backups of the database and the attachments/downloads folders from day one, not after the first scare. 2. Run the cron as the site user with the PHP CLI, using the exact command shown under Automation Settings. 3. Plan the licence move. Your licence is tied to the server IP and directory, so reissue it from your WHMCS client area when you switch. 4. Put the admin area behind an IP allowlist or at least 2FA, since it's now on a box only you look after. 5. Pick a provider that lets you upgrade RAM in place. That's what saves you from migrating twice, more than guessing the perfect size now. What PHP version and WHMCS version are you on? That narrows which OS image I'd start from.

WS WHMCS Secure Credentials Pro for WHMCS module. We help you to protect your customers' data which also helps to protect your business. Why do hundreds of businesses trust the original WHMCS Secure Credentials Pro? The answer is simple. Our WHMCS Module allows you to collect and encrypt customer data with a unique encryption key. That means every installation of WSC Pro is unique. No other WHMCS support module can provide this level of security. For more information and Screenshots: Click Here The next ten (10) people who purchase this module will get $5.00 off the Sales Price. To get this $5.00 discount, you must use this discount code, WSC, when you order. If you do not use this discount code when you order, you will NOT get the 5.00 off. Please remember to use the discount when you order. Sale Price: Owned License: $29.99 USD Order Here Click Here To View All WHMCS Addons By WHMCSServices Do You Need Custom Development For Your Business? Click Here Remember to check out also the list of our other new versions released since: WS SMS Manager v8.3.0 WS Services Fee v3.4.2 WS Email Verification Pro v8.0.0 WS 2FA Security v2.0.2 WS CleanTalk v1.0.1 Coming Soon: WS Close Account 4.0.0 WS Ticket Count Restriction 2.0.0 WS Trial Promotions 1.0.0 WS MailerSend with WhatsApp 2.1.0 Our Social Media: Twitter Here Facebooks Here Instagram Here LinkedIn Here

I run a small WHMCS install for a handful of clients from South Dakota, and the current shared setup is starting to show its limits during invoice runs. Nothing fancy here — just a handful of cPanel accounts and a couple of addons. I'm looking at moving to a budget VPS instead, but I'm not sure where to draw the line on specs. Some hosts push 1 GB RAM plans, others say 2 GB minimum just for PHP and MySQL to stay comfortable. I also worry about disk I/O during cron jobs and whether a cheap control panel is worth the tradeoff. I'd rather not get stuck migrating twice. If you've moved a similar-sized WHMCS install to a budget VPS, what RAM, storage type, and panel did you settle on, and what would you do differently?

🤣🤣🤣 Well if it were my first day, maybe

You are correct and this is what we wound up doing in the end: Product Add-on. Our needs are unique so it involves some manual intervention. Since these are actually hidden options - sold rarely and only upon request - it works for our purposes. Just to be clear, we solved this several months ago but since your answer now is spot on what we did, I've tagged it as a solution for others to refer to.

The ticket-threading point matches what I ran into planning a small WHMCS client app for a Sioux Falls side project: I settled on keeping WHMCS authoritative and having a thin backend fetch replies per ticket rather than mirroring threads, mainly because I can't yet prove webhook delivery stays reliable when a host's server sleeps or rate-limits. My open worry is uploads — attachment size and timeout limits through the middle layer seem like the first thing to break. I've been weighing whether a lighter tool fits; this Best Dyad Alternatives (2026) https://aibuildercompare.com/alternatives/dyad came up while comparing options. Has anyone kept polling instead of webhooks without stale threads?

I run a small hosting setup on WHMCS and keep getting requests from clients for simple dashboards and status pages that WHMCS doesn't really cover out of the box. I don't have a dev background, so I've been looking at AI app builders like Lovable and Emergent to spin up lightweight front-end tools that pull data from the WHMCS API. What I'm unsure about is whether either of these realistically produces something I can maintain, especially around API authentication and keeping client data secure. I'm also worried about ending up locked into a platform I can't export from later. Cost at low volume matters to me too, since this is a side operation in South Dakota, not a large agency. Has anyone here built client-facing add-ons or dashboards with these tools and connected them to WHMCS? I'd like to hear what actually worked and what broke.

Give your support, billing and technical team a real-time chat inside the WHMCS admin area. Staff Chat adds a floating widget to every admin page, so your team can talk, share files, mention each other and search past conversations without leaving WHMCS or paying for a separate chat tool. It works with ordinary AJAX polling, so there is no daemon, no extra port and no Socket.IO server to install or maintain. Every message travels through WHMCS itself, so nothing needs to be set up on your server beyond the module folder. If your admin area loads, Staff Chat works. The widget sits in the corner of every admin page and can be collapsed into a small launcher with an unread badge, so it stays out of the way until you need it. Your team can chat in a shared Group Chat, open private one-to-one conversations, react to messages, send images and files, and be notified when a colleague mentions them. Built for staff privacy and control Chat conversations often include client details, so Staff Chat is built to keep them protected. Chat history and attachments are encrypted at rest using the WHMCS encryption helpers, and attachments are downloaded only through an authenticated endpoint, never from a public URL. All chat actions are protected against cross-site request forgery. Full Administrators can review everything from a dedicated Chat History page, search across every room, and export results to CSV. A separate activity log records important actions with the admin, IP address and browser, and it never stores the text of a chat message. Owned License ($45.00) - https://www.hardsoftcode.com/cart/link/staff-chat-for-whmcs/owned Source Code License ($320.00) - https://www.hardsoftcode.com/cart/link/staff-chat-for-whmcs/source Why you need it Staff stop switching between WHMCS and an outside chat app. Conversations stay on your own server instead of a third-party service. Chat history and attachments are encrypted at rest. Full Administrators can review, search and export everything. Read-only roles, ghost mode and rate limiting let you control who can say what. Features Chat and rooms Shared Group Chat room for every approved admin Optional private 1:1 rooms between two admins Floating widget on every admin page, with expanded and collapsed launcher modes Online admin list with presence dots and per-room unread badges Configurable polling interval from 1 to 60 seconds Message timestamps and an unread count in the browser title Configurable message length and number of messages loaded per request Automatic retention and a per-room message cap Messages and interactions @mentions with autocomplete, highlighted names and a title marker when you are mentioned Emoji picker with the common chat emojis Reactions with live counts: 👍 ❤️ 😂 🎉 😮 😢 Typing indicator showing which admin is typing Edit your own messages within a configurable time window Delete messages with a confirmation dialog (Full Administrator only) Clickable links that open in a new tab Optional notification sound with a per-admin mute Files, images and links Image and file attachments, one per message Allowed types: JPG, PNG, GIF, WebP, PDF, TXT and ZIP Configurable maximum file size, with a hard ceiling of 50 MB Configurable total attachment storage quota Inline image previews and a full-size lightbox Authenticated downloads, with no public attachment URLs Attachments encrypted at rest Text-only link previews with SSRF protection History, search and export Encrypted chat history that survives page refreshes and admin logins Chat History page with a room selector, sorting, paging and filtering Global search across rooms, admins, message text and attachment names Reaction counts shown next to messages in history and search results Attachment previews and downloads in history and search results CSV export of chat history and of the activity log Retention applied when messages are written, when pages are viewed and by the daily cron Dashboard analytics 30-day message volume line chart Time-of-day chart showing your peak communication hours Group Chat versus private room distribution Top mentioned admins, ranked Attachment count, encrypted storage used and a breakdown by file type KPI cards for 30-day volume, active admins, attachments and peak hour Activity log Records widget connects, room switches, settings changes, message edits and deletions, cleared history, cleared log and denied access attempts Filters by action, admin and date range IP address and browser details, with IP logging switchable Session grouping, CSV export and retention pruning Full Administrator clear action Message content is never written to the log Access and safety Full Administrator-only module pages Read-only roles that can view and react but cannot send Ghost mode: selected admins are hidden from presence and their names are masked Per-admin message rate limiting Blocked words filter and optional link blocking CSRF protection, AJAX-only endpoints and POST-only chat actions Notifications Configurable default sound, volume and sound-on setting Desktop notifications through a service worker Chrome and operating-system permission diagnostics Built-in test notification button Admin area only. Staff Chat has no client-area pages and no client templates, and it works with WHMCS 8.x and 9.x. Changelog Version 2.0.0 Added: Group Chat and private 1:1 rooms Added: AJAX polling with a configurable interval Added: Mentions with autocomplete and highlighting Added: Emoji picker, reactions and typing indicator Added: Message edit window and Full Administrator message deletion with a SweetAlert2 confirmation Added: Encrypted image and file attachments with inline images and a lightbox Added: Text-only link previews with SSRF protections Added: Chat History with room selector, DataTables, attachment previews and CSV export Added: Global search across rooms, admins, message text and attachment names Added: Reaction counts in Chat History and CSV output Added: Activity Log with retention, filters, CSV export, session grouping and a clear action Added: Read-only roles, ghost mode, rate limit, blocked words and link rules Added: Desktop notifications with a service worker and Chrome/OS diagnostics Added: Dashboard analytics with 30-day message volume, time-of-day activity, room distribution, top mentioned admins and attachment storage breakdowns Added: Configurable aggregate attachment quota Updated: Module pages are now Full Administrator-only Updated: Chat history and attachments are now encrypted at rest Updated: Attachments are served only through an authenticated download endpoint, and legacy plaintext files are migrated Improved: Encrypted analytics cache that invalidates automatically, with a Full Administrator-only, CSRF-protected refresh endpoint Improved: Per-admin rate limiting shared across sessions Improved: Anti-framing headers and activity-log integrity events for encrypted data failures

Hello WHMCS Community, We’re introducing Weeby Studio — a complete WHMCS theme with a visual website builder, custom client area, and matching orderform and checkout, created by Hostk. The idea is simple: give hosting businesses a consistent brand experience and practical control over their website. Your pages, product presentation, customer workspace, and checkout share one design, with a dedicated Studio inside WHMCS to make it your own. Your hosting website. Your brand. Your Studio. Meet the Visual Studio Update your website from a focused visual workspace inside the WHMCS administration area. Edit visually: change website text, images, links, buttons, and supported styling. Build your pages: create or duplicate public pages, add content blocks, and arrange editable sections. Find every detail: navigate page structure through Pages and Layers. Manage your assets: upload images and replace editable visuals. Preview across devices: review desktop, tablet, and mobile layouts. Control shared elements: customize website navigation, headers, footers, and brand settings. Manage on-page SEO: edit browser titles, search descriptions, and image alternative text. Publish when ready: save an unpublished draft, review your changes, then publish. Keep a recovery path: export editable project backups and revisit saved published versions. Everyday content changes can be made in the visual editor, while native WHMCS forms, live prices, permissions, and transactions retain their original behavior. One design, from first visit to checkout Weeby Studio includes three connected parts of your customer experience: 1. Your public website A responsive hosting website with service landing pages, product presentations, comparison sections, and shared navigation. 2. Your client area A branded customer workspace for services, domains, invoices, support tickets, account information, and everyday account tasks. 3. Your orderform A matching product selection, configuration, cart, and checkout experience using native WHMCS ordering. The result is a consistent visual identity as customers move between your website, their account, and their next purchase. 23 starting pages. Room for your own ideas. The included public collection contains 23 pages, including 14 service landing pages, a homepage, service directory, and policy pages. Hosting & compute: Web Hosting, Cloud Hosting, Reseller Hosting, VPS Hosting, Dedicated Servers, and Game Servers. Business & security: Domains, Professional Email, SSL Certificates, and VPN. Expert services: Web Design, Backup & Recovery, Website Migration, and Managed Services. Customize the included content or create additional public pages through the Studio. 12 color palettes + your own brand colors Start with the original Weeby blue, navy, and white identity, choose one of 12 coordinated palettes, or create a custom palette. Set your brand accents, buttons, navigation, headings, text, backgrounds, surfaces, and borders. Customize your logo, typography, content width, and button corners from the shared design controls. Supported bundled visuals and the default favicon follow the selected palette. Your uploaded photos, custom logo, and custom favicon keep their original artwork. Product presentation connected to WHMCS Your real catalog stays central to the website. Connect website plan slots to specific WHMCS products or product groups. Display product names, descriptions, prices, and available billing cycles from WHMCS. Use the currencies and pricing configured in your installation. Customize supported CPU, RAM, storage, transfer, and other resource display labels. Presentation labels remain separate from the actual service specifications and allowances defined in WHMCS. A client area that feels part of your brand The custom client area brings key customer tasks into a coordinated layout: Dashboard with service overview and account updates. Sidebar navigation and account shortcuts. Product and service management screens. Domain listings and supported management actions. Invoices, billing information, and payment-related account views. Support tickets, Knowledgebase, and announcements. Login, registration, password recovery, and account details. Available actions follow the customer’s permissions and your enabled WHMCS functionality. Checkout with the details customers need The matching orderform supports product configuration, available billing cycles, domain choices, configurable options, add-ons, and guest or existing-customer checkout. Its itemized order summary presents the information supplied by WHMCS, including products, domains, selected options, billing periods, and recurring charges where available. Native discounts, taxes, credits, and totals remain authoritative. Multilingual content. RTL & LTR layouts. Translate public website content, navigation, and supported theme labels through the Studio, with a reading direction for each language. Prepare English LTR and Arabic RTL presentations, while native account and checkout fields use your installed WHMCS language packs. Language and currency controls follow your WHMCS configuration. Installation & documentation The package includes the website theme, matching orderform, Studio administration addon, and English and Arabic HTML documentation. Installation guidance covers activation, branding, products, languages, publishing, updates, and recovery. Editable project backups, saved published versions, and factory design recovery tools help you manage future changes. Weeby Studio requires an existing, licensed, self-hosted WHMCS installation. Confirm compatibility with your WHMCS release before purchasing. Hosting, WHMCS licensing, payment gateways, registrars, and provisioning services are configured separately. Explore Weeby Studio Live website demo https://hostk.com/weeby-demo/ Live Client Area demo https://hostk.com/weeby-demo/clientarea.php Email Address: test@hostk.com Password: test Special Price: $49.99 USD — reduced from $120 USD One-time purchase. Website-bound activation for one installation. Get Weeby Studio https://hostk.com/weeby/ We’d love to hear your feedback on the visual Studio, the customer workspace, and the ordering experience. Questions are welcome in this thread. Weeby Studio by Hostk Your website. Your client area. Your checkout. One connected brand.