<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mirsad Zonic</title>
    <description>The latest articles on DEV Community by Mirsad Zonic (@zonicmirsad).</description>
    <link>https://dev.to/zonicmirsad</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4123175%2F7add7a4c-d3ca-4dca-ab47-2491c5ed04b9.png</url>
      <title>DEV Community: Mirsad Zonic</title>
      <link>https://dev.to/zonicmirsad</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zonicmirsad"/>
    <language>en</language>
    <item>
      <title>Why I made my WordPress backup app self-hosted, not SaaS</title>
      <dc:creator>Mirsad Zonic</dc:creator>
      <pubDate>Wed, 07 Oct 2026 19:19:46 +0000</pubDate>
      <link>https://dev.to/zonicmirsad/why-i-made-my-wordpress-backup-app-self-hosted-not-saas-56p7</link>
      <guid>https://dev.to/zonicmirsad/why-i-made-my-wordpress-backup-app-self-hosted-not-saas-56p7</guid>
      <description>&lt;p&gt;Most backup tools for agencies are SaaS. When I built SiteVault, the app I use to back up client WordPress sites, I went the other way. Here's the reasoning, and what it changed technically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The credential problem&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A backup service needs access to the site: FTP/SFTP for files, database credentials for the dump. In a SaaS model, the provider stores those for every client of every agency using it. That's a high-value target, and as a solo developer I didn't want to be responsible for it.&lt;/p&gt;

&lt;p&gt;Self-hosted flips that. Each agency runs its own instance, so the credentials never leave their infrastructure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How the backups actually run&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of pulling everything over FTP from the outside, SiteVault installs a small MU plugin connector on the WordPress site. The connector runs the backup server-side and the app orchestrates it. That makes it faster and more reliable on large sites.&lt;/p&gt;

&lt;p&gt;Each run is logged step by step (size, status, duration), and after it completes, the client gets an email report. Email goes through Resend.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Packages instead of manual cron&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Backups are scheduled by maintenance package instead of per site: Basic (monthly), Pro (weekly), Agency (daily + monitoring). Each package defines its frequency and how many backups to keep, so retention is handled automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The trade-offs&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Self-hosted means the buyer handles hosting and updates. In return, they own the code, can customize it, and pay once instead of monthly.&lt;/p&gt;

&lt;p&gt;I'm selling SiteVault with full source code on &lt;a href="https://market.designzonic.com/product/sitevault" rel="noopener noreferrer"&gt;https://market.designzonic.com/product/sitevault&lt;/a&gt;. If you've built something similar, I'd like to hear how you handled backup storage and retention.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>wordpress</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
