<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>support systems — LowEndSpirit</title>
        <link>https://lowendspirit.com/index.php?p=/</link>
        <pubDate>Fri, 05 Jun 2026 00:46:41 +0000</pubDate>
        <language>en</language>
            <description>support systems — LowEndSpirit</description>
    <atom:link href="https://lowendspirit.com/index.php?p=/discussions/tagged/support-systems/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Decentralised vs. centralised external billing?</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/8964/decentralised-vs-centralised-external-billing</link>
        <pubDate>Thu, 09 Jan 2025 19:36:27 +0000</pubDate>
        <category>Industry News</category>
        <dc:creator>AGXL</dc:creator>
        <guid isPermaLink="false">8964@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hi,</p>

<p>Some time ago, for data protection reasons (<em>my company has to be GDPR compliant</em>), an expensive management consultant suggested that I decentralise the billing system and manage it for each server location via the upmind platform. With hindsight, I don't know if this was a good idea. I created 50 brand accounts with upmind. These accounts all need to be managed individually. Some time ago I got a free Clientexec licence for a private VPS. I also have a WHMCS licence somewhere.</p>

<p><strong>To cut a long story short:</strong> My question to you would be whether I should run the billing portal decentrally with upmind, which is of course much more time-consuming and cost-intensive, as I have to manage each one individually, or whether I should use a central billing portal for all server locations with e.g. Clientexec or WHMCS? Which is better?</p>

<p>I would appreciate your expertise.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
