Looking for technical information?
Designed from the ground up with security, reliability, and high availability in mind.
Secure, encrypted communications between your browser and RoboHead ensure your data remains private and safe.
- Fully-secured browsing with HTTPS TLSv1.2 using 128-bit encryption keeps your data safe in transit
- Customers’ accounts are separated into their own domains, e.g., customer.robohead.com
- Configurable password policy allows you to match your organization’s IT policies
Amazon Web Services’ cloud platform is utilized as the foundation of our RoboHead solution. Access to AWS cloud resources is secured by multiple protocols.
- Public Key Infrastructure (PKI)
- Two-factor authentication
- Encrypted network communications
High Availability & Reliability
All redundant or clustered components span multiple data center facilities in the same region, known as availability zones, providing high availability and reliability.
- A load-balanced application server cluster provides high availability and scalability as needed, to meet demand
- The replicated database back-end is backed up incrementally on a continual basis with full backups occurring daily and retained for seven days
- Assets are stored on Amazon’s multi-redundant S3 cloud storage system
- The application is managed to an uptime of 99.9%
Already an Existing Customer?
RoboHead Technology FAQ Download
RoboHead runs on Amazon’s Elastic Computing Cloud (EC2) – part of a suite of hosting and storage services known as Amazon Web Services (AWS). Running RoboHead on EC2 allows Aquent to utilize Amazon’s proven computing environment and to configure and scale capacity with minimal interruption in services. Amazon EC2 allows us to create and deploy new server instances on the fly, allowing us to quickly scale capacity as our usage grows.
Using EC2 also allows us to distribute application functions across “availability zones.” Each availability zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. Common points of failures like generators and cooling equipment are not shared across availability zones. Additionally, they are physically separate, such that even extremely uncommon disasters such as fires, tornadoes or flooding would only affect a single availability zone. This gives us the ability to recover quickly from failures that would be crippling in a traditional data center environment.
Because we know you can’t work if we’re not working, we take uptime for RoboHead very seriously. We manage to 99.9% and guarantee 99.5% uptime during peak usage times (6am to 9pm CST).
RoboHead utilizes a multi-AZ RDS instance as well as a full read-replica to enhance both the availability and scalability of database services. This means that there are always three, fully in-sync copies of your data at any given time (the primary, the warm-standby, and the read-replica). If there is a failure of the primary database, the application will automatically switch to the warm-standby which is located ina different availability zone.
Files uploaded into RoboHead are stored in Amazon’s Simple Storage Service (S3) which utilizes the same highly scalable, reliable, fast data storage infrastructure that Amazon uses to run its own global network of web sites. Amazon S3 provides a highly durable storage infrastructure. Files are redundantly stored on multiple devices across multiple facilities in an Amazon S3 Region. To help ensure durability, Amazon S3 synchronously stores your data across multiple facilities before returning SUCCESS. Every file uploaded into RoboHead is stored across at least three availability zones, meaning even large-scale disasters such as fires, tornadoes or flooding will not threaten the safety of your files.
Once stored, Amazon S3 helps maintain the durability of your objects by quickly detecting and repairing any lost redundancy. Amazon S3 also regularly verifies the integrity of data stored using checksums. If corruption is detected, it is repaired using redundant data. In addition, Amazon S3 calculates checksums on all network traffic to detect corruption of data packets when storing or retrieving data.
AWS has completed independent third-party audits ensuring that procedural security safeguards are in place, and the data centers themselves are secured with a variety of physical barriers to prevent unauthorized access. Network access to servers is protected by configurable firewall settings that control network access to and between groups of instances. Dual security keys are required in order to access any of the servers or data within the AWS environment.
The RoboHead database is backed up with a combination of log archives and nightly snapshots – this allows us to restore the DB to any point in time during the last seven days.
Files uploaded into RoboHead are automatically stored across multiple physical locations (see questions above) and versioning is enabled to track and rollback any changes made to files.
If an EC2 instance fails it is automatically removed from the application server pool and all requests are routed to other healthy instances – this process is transparent to the user and does not interfere with normal usage of the application. Additionally, file and database storage is isolated from the server instance itself so the failure of an EC2 instance does not require any time-consuming data restoration process.
RoboHead API FAQ Download
While RoboHead does not provide any out-of-the-box integration with other solutions, it does offer an API that allows clients to build middleware to connect RoboHead to other solutions. Using the API will allow you to access and update data stored in RoboHead through a REST programming interface.
The API can only be used by a programmer. Almost any programming language can be used with the API and code can be executed on any platform.
It allows a programmer to write code that puts data in or gets data out of RoboHead. The programmer can write code that can retrieve, update, and create campaigns, projects, tasks, reviews, files, notes, etc. This code can run as a standalone application on a server the client has set-up. Or it can run as part of some other application owned or controlled by the client.
The API does NOT allow functionality to be added or changed in RoboHead and you cannot write any code that runs on the RoboHead server as part of the RoboHead application.
Request A Free Demo