FathomDB instance sizes determine the memory allocation and other resource shares of your MySQL database server. Disk storage space is unlimited on all plans. Higher memory and CPU shares give you a higher performing database.
You can change the instance size freely; currently this involves restarting MySQL and often moving to a new server. We allow complex database operations to happen at user configurable maintenance schedules.
All pricing is in US dollars
| Size | Cost / Hour | Memory (approx.) |
EC2 Equivalent |
| Pico | $0.016 | 200 MB | 1/8 EC2 Small Instance (Shared) |
| Nano | $0.032 | 400 MB | 1/4 EC2 Small Instance (Shared) |
| Micro | $0.064 | 800 MB | 1/2 EC2 Small Instance (Shared) |
| Kilo | $0.11 | 1.7 GB | EC2 Small Instance (Dedicated) |
| Mega | $0.22 | 3.7 GB | 1/2 EC2 Large Instance (Shared) |
| Giga | $0.44 | 7.5 GB | EC2 Large Instance (Dedicated) |
| Tera | $0.88 | 15 GB | EC2 Extra-Large Instance (Dedicated) |
| Peta | $1.55 | 34 GB | EC2 Double-Extra-Large Instance (Dedicated) |
| Exa | $3.10 | 68 GB | EC2 Quadruple-Extra-Large Instance (Dedicated) |
We store your databases on Amazon's Elastic Block Storage, and is priced per Amazon's pricing + 20%:
| Disk Space | I/O requests |
| $0.12 / GB / month | Not charged |
Amazon charge for bandwidth, even where the bandwidth is within the same datacenter. Due to the nature of database transactions, this bandwidth utilization is unlikely to be significant. Right now, we simply don't charge for bandwidth, but if you do abuse this somehow we might have to notify you that we'll have to pass on Amazon's charges. We've never had this happen though!
Database backups are stored on Amazon S3, and we charge based on Amazon's pricing + 20%:
| Disk Space | I/O requests |
| $0.18 / GB / month | Not charged |
All pricing is in US dollars