fortrabbit blog

fortrabbit uses AWS, about EU data sovereignty and privacy trends.

Artificial Intelligence is a good spammer.

Coupled websites with PHP and JS.

Decoupled websites with PHP and JS.

Mixed feelings about Google Chrome.

Good luck if you still create websites for a living.

It's complicated. The relation between open source and web hosting from our point of view

Verbs first for interfaces with more natural language.

Why we plan to drop a signature feature of the Pro Stack.

Is something missing to bring together JS and PHP?

A field guide on image transformation and optimization providers

The Privacy Shield is no longer valid. How to proceed?

PHP 5.6 and PHP 7.0 deadlines: Why is so much old PHP around? What we will do!

Props to the OSS communities and highlighting some of our open source contributions.

Successful communication in customer support chat channels.

Why to use a service for transactional e-mails.

Our real-live practices on auto-generated client e-mail communication.

Thoughts on flat file CMS and static site generators, mostly PHP-related.

How we tried to test the speed benefits of the new internet protocol.

Insights why we will not offer an Add-On program soon and what we have instead

Trends, pivots & troubles in PaaS hosting 2015

What's going on in e-commerce?

HTTP/2 expectations and pitfalls

Are content management systems ready for the cloud?

Value-based VS cost-based pricing for a hosting service.

A stubborn analysis of hosting solutions for developers.

How hustling with accounting keeps us away from developing our service.

Just a fancy info-graphic to say happy birthday to PHP.

A state of the PHP cloud hosting scene overview.

Breaking news, fortrabbit releases a brand new stack.

What we have learned on the Laracon conference 2013 in Amsterdam.

We've recently upgraded our fortrabbit.com website, including a complete overhaul of our pricing visualization. The visualization is one thing, the other is our Map your App decision-helper: One of the major problems all hosting providers have to solve (or should at least try) is to make it transparent to the customer what kind of resources she needs.

What's more important in hosting? Performance or convenience?

A case study.

Flat, unlimited and forever it shall be.

Modularize everything!

IaaS, PaaS, bare metal, shared hosting, managed hosting — Quo vadis?

The cloud: economically attractive, but what the about ecological impact?

What the hosting- and the meat-market have in common.

Our iterative approach.

Some links on newish PHP.

Bootstrapping in Berlin.

Looking for the perfect PHP hosting platform.

Analysing the answers of our questionnaire.

Musings about the comon www. subdomain.

Web IDEs everywhere! Are they any good? What's the buzz?

Is there such actually free web hosting?

How bound are you to your hosting provider? Does this really matter?

New-school cloud or legacy LAMP style — what's state of the art in PHP hosting?

What PHP cloud platforms are currently actually out there?