Our current hosting product freistilbox is highly scalable, and compared to other enterprise hosting platforms, its pricing is unrivaled. But more often than not, customers tell us that not everyone actually needs a full Drupal or WordPress cluster which can scale to hundreds of websites. That’s why, after five years, we decided to launch freistilbox Solo, our new plan for web developers who need powerful managed hosting for a single website.
Today, we’re going to tell you the details of what we’re up to.
freistilbox Solo is designed from the ground up to support and enhance the workflow of Drupal and WordPress shops.
Development speed is one of the most important aspects in web projects, so it’s vital that your hosting platform offers an efficient way to deploy changes. That’s why freistilbox Solo will use the same instant deployment approach as its bigger sibling: the moment you push a change to your Git repository, it’ll be published on freistilbox Solo.
In order to support the usual development phases of development, staging and production, each freistilbox Solo account comes with three separate website instances. You can base all three on the same Git repository because our deployment process will automatically enable the correct configuration for each staging environment.
Alternatively, you can assign a specific branch of your application repository to each instance. For example, you could simultaneously work on and deploy from a “development”, “testing” and “production” (aka “master”) branch.
All your website visitors, human beings and search engines alike, put a high value on performance. Being able to generate and deliver content quickly has a direct impact on both your sales and search engine rankings.
We will offer freistilbox Solo in three tiers that differ in capacity:
- freistilbox Solo S with 8 Processing Units and 10 GB of storage space,
- freistilbox Solo M with 12 Processing Units and 20 GB, and
- freistilbox Solo L with 16 Processing Units and 40 GB.
In case you’re not familiar with the term “Processing Units”, that is our metric for how many concurrent Drupal or WordPress requests freistilbox can handle, so another fitting term would be “application workers”.
In freistilbox Solo, we use the same technology that serves our current freistilbox customers, only on less complex IT infrastructure. This includes a high-performance LAMP stack plus
- Memcache for maximum application performance,
- Varnish for delivering static content at 300 requests per second,
- an SSL terminator that enables caching of encrypted web sessions, and
- Apache Solr for high-speed content search.
As with freistilbox Enterprise, all these system components are optimised for running Drupal and WordPress. And since they connect without any network latency, freistilbox Solo will deliver your website content with amazing speed.
While freistilbox Solo does not require the same infrastructure complexity as freistilbox Enterprise does, there is still a lot to do in order to let our customers work efficiently and sleep peacefully. freistilbox Solo is fully managed and our operations team will take care of all the work required to run your websites at full performance. For example, we’ll make sure that the hosting software is updated regularly, that your data is backed up and that performance bottlenecks get eliminated. If there’s some new technology that can benefit our customers significantly, we’ll try and integrate it into our hosting platform. And if (well, rather “when”…) something breaks, our ops team will get on it immediately, day or night.
We are convinced that web projects are the most successful when developers and operations folks work towards the same goal. That’s why freistilbox Solo customers will enjoy the same competent technical support as our freistilbox Enterprise customers. We won’t leave you alone when you need help running your website.
We’re a bit behind schedule but the launch of freistilbox Solo is getting nearer and we’re already very excited! Soon, we’ll reveal the pricing and the exact date when we’re going to make freistilbox Solo available.
We hope to see your website fly freistilbox Solo soon!
04 May 2015
When we announced the Qualys SSL Labs A rating we got for the encryption quality of our Edge Routers in March, we knew that there still was room to improve. Our ops team kept tweaking the SSL configuration and we’re proud to present the result:
SSL Labs now rates our SSL security with A+!
17 Apr 2015
TL;DR: This change affects the naming of your staging instance configuration files on freistilbox.
Staging has been built into freistilbox from the start. Being able to test changes on a staging instance before launching them in production has been an important feature for the majority of our customers, Drupal agencies and WordPress shops alike.
freistilbox makes it convenient to manage separate configuration files for staging environments within the same Git repository. In order for this to work, staging instances need to have a unique name that differentiates them from the “production” instance. So far, we’ve allowed our customers to choose this name freely. There’s “stage” and “staging”, “test” and “testing”, and one customer uses “stfu_stoopid_client” for reasons we don’t know.
A few weeks ago, we were shocked to learn that by giving our customers this freedom, we’re actually causing them what psychologist Barry Schwartz calls “The Paradox of Choice”. In Schwartz’s estimation, choice has made us not freer but more paralysed, not happier but more dissatisfied. Here’s his TED talk on this topic:
It became clear to us quickly that we can’t be a part of this. We’re here to take stress off our hosting customers, not to cause them additional pressure. That’s why we decided to stop forcing you to choose a stage name again and again.
In order to implement this change, we first had to endure the analysis paralysis mentioned in Schwartz’s research ourselves: what name should we choose? Doing a quick statistical analysis to find the most frequently used name in existing freistilbox websites was an obvious option. Instead, we decided to do a multi-week study of how our customers integrate the freistilbox staging process into their daily workflows, and the result will surprise you.
After sifting through a heap of conversation transcripts during a few late-night on-call shifts, we found that the most common conversation among website developers during user acceptance testing went like this:
“Did you make the change we’ve discussed yesterday?”
“Yup, I did.”
“And does it work?”
“Well, yeah, it’s working in theory.”
With these results, defining the new mandatory stage instance name became easy and we’ve already renamed all existing staging instances to “theory”.
01 Apr 2015
Looking at its pricing, it’s not obvious that freistilbox is an enterprise-class hosting platform; it’s no secret that we’ve made running Drupal and WordPress websites on a multi-server infrastructure affordable. Our customers, web agencies and development shops, are amazed how quickly they reach ROI.
Many of them start with a small cluster setup, for example with a pair of freistilbox S. Combined with the content cache, its 20 PU (Processing Units, basically PHP worker processes) deliver enough processing power for a few small and medium websites, and thanks to the redundancy we build into every hosting component, they enjoy great uptime. Scaling up is easily done by adding or replacing boxes, so the agency has full control over capacity and hosting cost at any time.
But sometimes, this model doesn’t work out as well, and that’s when the customer needs separate hosting for only a single website. There can be several valid reasons to do this:
- customers that would like to test the waters called freistilbox
- customers that want us to bill every website individually
- customers that want the website to run as isolated from others as possible
In these cases, the power of a full freistilbox cluster is just overkill. While freistilbox is the most cost-effective Enterprise Hosting Platform for Drupal and WordPress, there is actually still a gap between conventional hosting and the entry-level freistilbox setup.
It’s about time that we close this gap.
In April, we’re going to launch freistilbox Solo , a single-website hosting solution that has the power of freistilbox, only at a much lower price point.
 Yes, we’ve stolen the name from the development VM that we’ve published in 2012 and which we’re going to relaunch later this year under a new name.
18 Mar 2015
In just a few days, the freistil IT team will again be packing their bags for our next company retreat, the freistil Days Spring 2015 . Next Monday, we’ll all meet in Rome!
5 months after our first freistil Days in Barcelona, it’s again time to meet in person and spend a few days at the same place. And after last time’s success, we’re pretty excited what we’ll learn this time living and working together!
We’re going to use this opportunity to focus for a full week on our most important projects. Of course, freistil Days are not only about work, and taking a few strolls around the Eternal City will certainly spark our team spirit and creativity. We’ve also made sure to reserve time for daily business during each day, so there’s no need for our customers to worry about being able to reach us. We might answer support requests a little bit slower than usual (and we apologise in advance) but we’ll make an effort to be as responsive as possible.
We’re going to update our Twitter account regularly (for real this time…), so keep an eye on @freistil next week!
17 Mar 2015
The risk that unencrypted web communication creates for both website owners and individual website users can be significant. That’s why encrypting traffic via SSL (Secure Socket Layer) and TLS (Transport Layer Security) has become indispensable for both B2C and B2B websites. If you are transmitting sensitive private data over the internet, SSL is an important additional security layer.
But simply enabling SSL in a web server configuration file isn’t enough any more. Over time, the SSL/TLS protocol suite has become more complex and, unfortunately, a popular target. BEAST, Heartbleed, POODLE and now FREAK - these are only the better publicised exploits that threatened encrypted communication on the web over the recent years.
Additional to performance and availability, security is also a key factor that defines the quality of our Managed Hosting Platform. That’s why we’re putting significant effort into continuously optimising the setup of our dedicated SSL offloaders. These machines run at the edge of our infrastructure and take the compute load that decrypting traffic to and encrypting traffic from our customers’ websites creates off your Drupal and WordPress boxes.
The result of our efforts is that Qualys SSL Labs gives freistilbox an excellent A rating:
With the Qualys SSL Server Test, you can see for yourself how well other hosting providers secure their customers’ web traffic:
Acquia: The ELB engineers at Amazon obviously have done their homework.
Pantheon: Solid but room for improvement
WPEngine: Very good with only a tiny flaw
Your customers trust that you take their security seriously, and losing this trust can break your business. That’s why running your Drupal and WordPress websites on our managed hosting platform is the right thing to do. Our engineering team has only one goal: to let you work efficiently and — just as important — sleep peacefully.
04 Mar 2015
In the past, trouble with asset file permissions caused us a lot of support requests. The emphasis here lies on “in the past” because we’ve finally sorted that issue out once and for all.We’ve simplified the file permissions on the shared storage system so that all asset files have a single owner regardless of how they’ve been created, be it by the web application itself or by a developer logging in via SSH. This change finally puts an end to file access problems and, we hope, makes asset file maintenance much less annoying.If you have any questions about this change, we’d love to hear from you in the comments!
02 Mar 2015
Every freistilbox customer gets their own dual-node Varnish cluster, so we have a lot of experience in tuning the cache configuration for Drupal or WordPress websites. I’ve distilled some of our most important best practice tips into a talk called “Getting the most out of Varnish”.
Here’s a recording from DrupalCamp Galway in November 2014:
And here are my slides:
If you have any questions about Varnish tuning, just leave me a comment!
23 Jan 2015