Elasticweb - the first adaptive virtual hosting

Good day, dear habravchane. I want to share with you the events of our life with colleagues of the Elasticweb project. For those who have not seen the first post about Elasticweb - this is virtual hosting with payment only for server resources used without restrictions on the number of domains, subdomains and databases.

I want to illustrate the fundamental difference between Elasticweb and other hosting sites on the example of a real case. There is a blog with a attendance of 2,000 unique per day, for whose service a tariff plan for 150 rubles is suitable. But there are peaks caused by habraeffektomu or Redit to 10 000 for several days. In such situations, the site begins to slow down and the hosting sends a letter with a warning about blocking and a request to switch to another tariff plan. Often, many begin to pay more, peaks fall and money is thrown to the wind (not every time you go back and forth). Elasticweb has no ad hoc limits and is billed daily based on the utilized capacity. It does not pay extra.
')

Numbers

For 2 months, nearly 1,000 people registered for the service, a quarter of them became our customers. Currently, Elasticweb serves more than 800 domains, which in total recruit 500,000 visits per day. We processed 400 tickets and answered almost 3,500 messages. The average response time is 15 minutes. Of course, we are working a lot on the functionality and are moving towards Heroku, but I want to emphasize that we focus on the quality of technical support. It seems to us that this is the most important thing for customers in a hosting company. I promise that in the future (with a larger number of clients) I will arrange a survey assessing the quality of our services.

It is important to mention that we use Nginx as a web server, Apache support and, accordingly, we do not have .htaccess. But we will help everyone to create a Nginx config for your project.

Nodes

The first conceptual change is the renaming of “hosting accounts” to “nodes”. For the convenience of working with nodes, the ability to create aliases for them has been added, and clients can now transfer nodes to each other. Also appeared the function of transferring funds to another account. By the way, by popular demand, you can replenish your account via PayPal, and very soon there will be a file manager and memcache.

Nginx editor

From the very beginning for us it was an important task to write an online editor for Nginx configurations with the appropriate syntax highlighting. And we did it. Now you can independently change your configs. The validator is currently running in beta mode and at first all changes will be checked manually.

Backup

For many clients, backing up is of particular importance, so our attitude to backups is very thorough and careful. I have already told that we produce it weekly and monthly. Plus, Elasticweb has an opportunity to make backups of node content from users and everyone can automate this process at a specified interval for themselves.

Offline limit

Judging by the comments on the first article, some people came up with the idea of ​​Elasticweb with some caution, fearing to lose money due to a sharp jump in attendance or bots. Therefore, I just want to say that we return the money at the first request of the client, without tedious procedures. We also added the function of offline limit - in case of exceeding the specified amount, the node will be transferred to offline mode. The data, of course, does not disappear anywhere and you can activate the node at any time.

API

There is still good news for studio owners and CMS - we have significantly expanded the API for working with Elasticweb and are actively continuing to work on it. You will be able to create your own conditions for your customers, operating with the functionality of our hosting for free.

New interface

Finally, we are pleased to announce that we have completed a full redesign of the control panel, trying to unify it with the main page. We hope that working with the new interface will become more pleasant and easier for you:









Thank you all for your attention. We look forward to hearing from you critics, questions and suggestions. We hope that next time you will hear about Elasticweb, as a registered company from our corporate blog.