Managed Hosted Services FAQ

Let’s find an answer to your question! These are some of the most popular questions we receive about our Managed Hosted Services.

Learn more about
deployment options.


Find your question…



I’m not sure how big of an environment my company needs – we don’t have good data right now on how many simultaneous users we need to support. How do we size our environment?

Often, you’ll have a pretty good idea of how many total users your system has. With that number, we can figure out a good starting size for your setup. And if we discover that you’ve got a LOT more users than you thought, that’s great! Success! We can upsize your environment in a matter of minutes to meet demand.

My company needs to serve a user base of about 100,000 people right now, but we have big expansion plans on the immediate horizon. Can our Managed Hosted account scale with us?

Totally. We designed both elasticity and scalability into our Managed Hosted environments.

They’re elastic: our environments are capable of intelligently scaling up and down to meet spikes and lulls in traffic.

They’re scalable: if you need to enlarge your environment because your baseline levels of traffic have outgrown your plan, we can flip a few switches and upsize your environment without downtime or effort on your part.

My company has a global footprint, and we want to provide a high quality of service to our users around the planet. Do you provide a solution for this?

Definitely! We have integrated Amazon’s CloudFront Content Delivery Network into our Managed Hosted services. CloudFront allows us to cache content in data centers around the globe, which speeds up delivery to your users in a big way.

We want to have application and database servers located around the globe along with our content delivery nodes. Can you do this?

We don’t have a protocol for doing this right now. It is possible, but there are a few problems with this setup:

  • It is really really expensive.
  • It doesn’t provide a significant performance improvement for end-users.
  • Did we mention it was expensive?

In our experience, we serve a global audience via the CloudFront CDN at a very high level of service, and placing application and database servers around the globe isn’t beneficial enough to justify the cost.

My company is based in the EU, and data privacy is really important to us. Where will my data live?

By default, we host your data in the US, but we can place your data in the EU, UK, Australia, Singapore and many other places besides. Talk to us if you have special requirements and we’ll find the right place for you.

We’re concerned about security. How do you handle security for your Managed Hosted environments?

Here’s how we handle security for Managed Hosted:

  • All infrastructure is hosted in an ISO 27001-compliant, SOC-2 datacenter at Amazon Web Services.
  • All infrastructure is provisioned within Private Clouds at AWS (they call these VPCs), and are isolated from other networks.
  • No logical network connections save via port 443 are permitted between the public internet and any hosts. Customers may elect to allow unencrypted access via port 80, but this is by special request only.
  • All remote administrative access takes place via an IPSec or TLS VPN tunnel.
  • All hosts are patched as a part of each release.
  • Critical OS and software patches are deployed on an as-needed basis if they are released in between release cycles of Content Controller.
  • Our continuous integration system builds your hosts from scratch every time we deploy an update. This ensures total consistency during the build process, enforces our security update process and provides change control over every aspect of the build and update process for both hosts and the network infrastructure upon which the hosts run.
  • Public facing hosts are scanned for vulnerabilities weekly, and any identified critical vulnerabilities remediated within 1 week.
  • SIEM logs are retained for 35 days in the active index, and are stored in an archive for 400 days.
We want a highly-available system with a solid disaster-recovery plan. How do you all do high availability and DR?

We manage high availability and disaster recovery in these ways:

  • Your application servers and database servers live in multiple, geographically separate data centers. We can lose an entire datacenter and your application will keep running just fine. Our content data lives in Amazon’s S3, which has 99.9999% durability.
  • Your database runs on two servers simultaneously. If one of the database servers is damaged or offline for some reason, the secondary server makes itself the master and takes over without human intervention.
  • We snapshot your content and database servers daily just in case something truly awful happens and we have to recover from backups. We perform regular disaster recovery tests to ensure that the backed up-data is quickly recoverable.
What kind of SLA do you provide for Managed Hosted Applications?

We provide a 99.95% SLA for all of our Managed Hosted Applications. If your use case has different SLA requirements, no problem – we’re able to support SLAs of up to 99.99%

In practice, we operate under the assumption that downtime isn’t acceptable, and our processes are designed to facilitate zero-downtime upgrades. We know you and your clients depend on our services being up and running 24×7, and we’ve engineered them to be self-healing.

What should I do from here?

When considering Engine or Content Controller, remember you have options when it comes to who handles deployment. You can learn more about Pricing here. And reach out to us if you have questions about how you can use Managed Hosted Services in your Rustici Software product implementation.