CodeGuard FAQs – Common Questions

Yes - CodeGuard works the same way regardless of the type of website or platform you use! We are compatible with popular Content Management Systems like WordPress, Joomla, Drupal, and Magento, but there are many others that CodeGuard can work with.

If the platform you use meets the following criteria, CodeGuard can be used for your website and database backup needs:

  1. You must have access to your website's FTP/SFTP credentials in order to connect to CodeGuard.
  2. The website, if it uses databases, must be using either MS-SQL or MySQL databases.
  3. You website's FTP/SFTP and Database servers should be accessible via the Internet.
  4. Your website must not block these IP addresses:

If your website uses WordPress, you can use the WordPress plugin without any need for FTP/SFTP access or whitelisting IP addresses.

Try a no-obligation, free 7-day test plan to know for sure if your website can use the CodeGuard service.

CodeGuard keeps a backup of your site on our servers. Then, CodeGuard uses standard open protocols (FTP and SFTP) to monitor your site and check for changes.

If anything has changed from the backup CodeGuard has on file, CodeGuard takes a new backup and notify you by email.

If you ever want to go back to a previous version of your site, just use CodeGuard's restore functionality to choose the backup you want to revert to.

Not necessarily. Hosting companies tend to keep your backups in the same place as your primary files. You don’t carry around a copy of your birth certificate along with the actual one – you keep the real one safe at home for emergencies. So why not do the same for your backups?

CodeGuard provides safe, offsite backup that is 100% independent from your hosting provider.

And there are plenty of folks who agree.

"The back-up systems of most web-services providers leave a lot to be desired. The back-ups sound reassuring in theory – you are assured that your data is always 'backed-up' on a system that is completely separate from the main one … But then, when you dig, you often discover that that means the data is simply copied to another file on the same box or another box in the same data room." - Business Insider, 4/28/11

The CodeGuard application is built with single sites in mind, but there are several options that would work when it comes to WordPress Multisite

Option A: Use a single FTP account

The first approach is to back up all of your sites from your main FTP account, effectively treating your multi-site setup as one large website. In our initial activation process, we let the user choose which files on their account that they want to backup. Here you could select the main folder for each of the sites that are on your network. Each time a backup is run, all of these sites will be backed up. For restoring a site, you can use our selective restore feature so that not all of the sites on your network get rolled back. You can add the database to this account as well.

Option B: Use separate FTP accounts

Your other option would be to create separate FTP user accounts for each site with the FTP root being the root of the specific website. This way all of the sites would be backed up and restored independently of one another. For the database, you can back that up under your primary account.

CodeGuard uses Amazon Web Service’s Simple Storage Service (S3) to house website and database backup data. This service was selected because it provides 99.999999999% durability by storing data redundantly across multiple physical locations. In addition to being able to withstand two simultaneous datacenter failures, all customer backup data is encrypted using an AES-256 bit key.

If the data is physically stored in Amazon Web Services “U.S. Region,” which includes one or more datacenters in the following U.S. cities:

  • Ashburn, VA
  • Dallas/Fort Worth, TX
  • Hayward, CA
  • Jacksonville, FL
  • Los Angeles, CA
  • Miami, FL
  • New York, NY
  • Newark, NJ
  • Palo Alto, CA
  • San Jose, CA
  • Seattle, WA
  • South Bend, IN
  • St. Louis, MO

You can upgrade your plan at any time. We will automatically issue you a refund for the remainder of the existing plan, then immediately use those funds towards the purchase of the upgraded license. The billing cycle will now be set to this new purchase date (date of upgrade).

The option to downgrade a plan is not available as it could force random pieces of backups to get deleted if the existing license backups were over the allowed storage of the new plan.

If a customer wishes to manually downgrade their plan, they should download their backups, cancel their current subscription renewal, purchase a lower plan and upload their backup. There will be no refund or adjustment with the higher plan's price, and your higher plan's service will continue to work till expiry.

CodeGuard relies upon industry best practices to protect customers’ data. Amazon Web Services (AWS) handles key management and key protection for CodeGuard, with one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256). All backups and passwords are encrypted, secure connections (SFTP/SSH/SSL) are utilized if possible, and annual vulnerability testing is conducted by an independent agency. To-date, there has not been a data breach or successful hack or attack upon CodeGuard.

Two different types of passwords are stored on the system – customer account passwords to log in to CodeGuard, and passwords for customer server credentials (FTP/SFTP, MySQL). The customer account passwords are stored with a one-way salted hash. At rest, these passwords reside in Amazon’s Relational Database Service (RDS). Customer server credential passwords are stored in RDS with RSA 2048-bit key encryption.

Data Access
CodeGuard systems involved in performing backup or restoration activities have access to unencrypted customer data for the duration of these scheduled operations. Select members of the CodeGuard Engineering and Operations team have access to the systems that are used to perform these tasks. It is our policy that we only inspect a customer's data if we have explicit written permission from the customer.

GDPR Compliance
The GDPR regulations went into effect on May25, 2018. CodeGuard's systems are currently operating under these regulations and are in full compliance. For more information on GDPR regulations, please visit

CodeGuard’s systems perform at 99.9% levels, which means that roughly 1 out of 1,000 websites encounters an issue on a daily basis. Hosting providers perform maintenance on servers, customers change FTP login credentials, and IP whitelisting settings for database connections can change, based upon hosting provider server admin activity. These are common behaviors and not cause for concern, as CodeGuard determines the root cause for the lack of connectivity, and emails the customer so they can rectify.

CodeGuard was started in 2010, inspired by problems faced by small business owners. Technology angel investors and venture capitalists funded CodeGuard in the early stages and the company is now profitably growing – so there is no need to worry about your backups going anywhere!

You can find the CodeGuard Service Level Agreement, Master Service Agreement and Acceptable Use Policy below.

CODEGUARD_MSA-v1.0-2Dec16.pdf (100 KB)
CODEGUARD_SLA-v1.0-2Dec16.pdf (80 KB)
CODEGUARD_AUP-v1.0-2Dec16.pdf (70 KB)