Ninja$5 /month Billed Annually No monthly billing available
Bloggers & Novices
- 1 website*
- Unlimited databases
- Up to 5 GB per site
- Daily backup and monitoring
- Email support
Ronin$39 /month Billed Annually
Small Teams & Freelancers
Samurai$79 /month Billed Annually
Designers & Developers
Free Daily Backups - $0/month, $20/restore
Free daily backups for 1 website, 1 database and up to 5 GB of space. Pay only when you need us - restores begin at $20.Create Account
|Websites||Up to 10||Up to 12||Up to 25||Up to 100|
|Backup Retention||30 Days, 60 Days, 90 Days or Infinite||30 Days, 60 Days, 90 Days or Infinite||30 Days, 60 Days, 90 Days or Infinite||30 Days, 60 Days, 90 Days or Infinite|
|Daily Site-Change Monitoring|
|Custom Notification Filtering|
|White Label Settings More info|
|Initial Backup/Activation Tracking|
|Daily Backup Tracking|
How reliable is CodeGuard?
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 remediate.
How secure is CodeGuard?
CodeGuard relies upon industry best practices to protect customers’ data. 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.
How long has CodeGuard been around?
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!
Where are the backups stored?
Backups are stored on Amazon Web Services Simple Storage System, known as S3. S3 boasts object durability levels of 99.999999999%, achieved by storing redundant copies of data across multiple geographies and facilities. S3 is not the cheapest alternative for data storage, but it is one of the most reliable.
Are the backups encrypted?
Our data stored on Amazon Web Services (AWS) is stored utilizing Server Side Encryption (SSE). AWS handles key management and key protection for us, with one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256).
How are passwords stored?
Two different types of passwords are stored on our system – customer account passwords to log into 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.
How does it work?
All file content is retrieved for the first backup using the “get” command over FTP or SFTP. Disk I/O is utilized as each file is retrieved and transferred to our servers. CPU and memory needs are minimal.
Subsequent backups are differential and do not entail transferring all content. This is achieved by utilizing the “ls – list” command and examining the metadata for each file: name, size, timestamp, file type, permissions, and last modified date. If any of these have changed, or a new file has been added, we will transfer the changed or added file to our servers. If a file has been deleted, we take note and adjust our repository accordingly. Since only changed file content is transferred, the vast majority of subsequent backups cause minimal memory, CPU, and I/O server needs.
How does the restore/undo work?
When a customer seeks to restore a previous version of their website, the first thing CodeGuard does is to check the live website to see what content is on it. This enables us to quickly push (or pull) the differences to or from your site. For instance, you might experience a hack that changes your .htaccess file and nothing else. Rather than reload your entire site, CodeGuard would simply replace the infected .htaccess file with your old clean copy.
Will it bog down my server?
Short answer: No. Long answer: See "How It Works" section, or the “How It Works” question on this page.
Will I have to set up cron jobs?
Will it be easy?
How are the features different between plans?
All plans allow for daily automatic backups, monitoring, and restores without limitation. The main difference is that with the Shogun plan you are allowed the option of a concierge restore. A concierge restore is when our developer team takes personal time to oversee the process of your restore from beginning to end to ensure its success.
What if I want to switch plans?
Switching plans is easy! At any time you have the option to upgrade to a different plan through the customer dashboard when you log in.
What about a free plan?
CodeGuard offers a 14 day free trial on all of our current plans. Feel free to signup and test our service to see if it's the right fit for you or your company. If it isn't, no hard feelings! You can cancel at anytime.
How does payment work with the plans?
The Ninja (Personal) plan is the only plan billed on an annual basis. The Ronin, Samurai, and Shogun plans are all billed on a monthly basis. For each plan, you will not be billed until your 14 day free trial is complete!
How much storage do I get with each plan? How long are backups stored?
The Ninja plan allows you to have one website for up to 5 GB of storage for that site. For an additional $5.00 per month per site though, you can add up to 10 websites total with the Ninja plan. The Ronin plan allows for 12 websites and up to 50 GB of space. The Samurai plan allows you to have up to 25 sites and a total account storage limit of 125 GB. The Shogun plan allows you to have up to 100 sites and a total account storage limit of 500 GB. When it comes to determining how large your account is, the number of backups that you have does play a part. CodeGuard currently has two backup retention settings to choose from. You can choose to only keep 90 days of backup history for all of your websites (good setting for saving space), or keep your entire backup history.
Can I backup multiple websites?
Yes, you can! Multiple websites can be backed up with CodeGuard, and if you have more than two or three, we highly recommend the Ronin, Samurai, or Shogun Plans. These plans are feature rich with tools for managing and overseeing multiple backups for different clients, and are intended for small businesses, designers, developers, and agencies.
How do I set up a White Label account?
For those with the Ronin, Samurai, or Shogun plan getting a white label account set up is easy. After purchasing or upgrading to one of these plans a "Branding" link will appear in your Settings drop-down when you are logged in. On your White Label Settings page you will be able to enter a custom subdomain (ex: yourcompany.codeguard.com), upload a logo to replace the CodeGuard logo in the dashboard, enter an email address in case your clients need to contact you, and enter a Support Center URL for when your clients need troubleshooting assitance. When your clients log in through your subdomain they will only see your branding in the dashboard, giving you full control over the experience!
Do you have a WordPress plugin?
Yes! For those using WordPress we have a WordPress plugin for daily automatic website/database backups and automatic restore. Setup takes less than 1 minute.
Do you backup databases?
Yes, we do. You have several options in backing up your databases. CodeGuard can connect directly to your MySQL database, typically through Port 3306, or by tunneling over SSH with your FTP credentials or different credentials.
How does it work?
A mysqldump command is executed each time we retrieve the database content. Most MySQL databases are not large enough to create noticeable server load.