Seedboxes.cc- New platform, new plans

New platform, new plans

We are very excited to announce that few days ago our new seedbox platform that we have been working on for the past 6 months has been officially launched. The new platform, is more of a “technical behind the scenes upgrade” for our seedboxes. It does not provide any important end user features out of the box, but provides more security and isolation of the seedbox on the server side, allows us to manage our infrastructure more efficiently and at a lower cost, and provides the backbone for new important features to come.
Along with the new platform, we released revamped plans to reflect the increasing demand of disk space in our industry.
The differences of the v2 plans are:

The new plans are based on our new platform
They have bigger disk space allowance
They have a lower upload traffic allowance
They have differences in pricing


Due to the above differences it is not technically possible for us to migrate older plans on these new plans automatically because:

-They are based on a different technical platform, which is incompatible with the old one. There is no way at the moment to switch to a new plan and stay on the same server

-Discounts and promotions that our clients might have acquired over time on the older plans, are not transferable to the new plans

-Pricing is completely different and more expensive in most cases

For that reason we will not migrate the accounts on the older plans to the new plans and pricing automatically since we cannot know if a client actually wants to upgrade or not. We also pledge, that the old accounts will continue operating under the same pricing and plans for as long as a client keeps it.

Our suggestion to our old clients is, that if they do not need the extra disk space urgently, it is better to keep their old plan because it provides more traffic, and a cheaper price which is locked until the client cancels the plan.

However this does not mean that you cannot switch to the new plans if you feel that they are more suitable to you.

In order to do that you can cancel your old plan, and order a new one afterwards.


Due to the limited availability of the new plans at the moment, and to the excessive work load because of the launch of the new platform (we are still ironing out several bugs discovered) and the Christmas holidays, we have decided that we will not be able to migrate clients from older plans to the new ones for the next 2-3 weeks. If you urgently want to get a new plan, you are free to do so, but we cannot currently assist you in migrating your data.

We suggest to our clients that want to migrate from the older plans to the new ones to wait 2-3 weeks in order for us:

-To iron out all the bugs discovered on the new platform

-Install and setup new servers already ordered and to be delivered beginning of the new year, so that we have plenty availability

-To be able to perform automatic migrations from older plans to the new ones, without losing your data

For the clients that want to renew their old plans for prepaid periods, and are worrying that if they do so, they will not be able to later upgrade to the new plans: Don’t worry :) You will always be able to switch to the v2 plans upon request.


We would like to thank everyone for their support and understanding, and wish everyone a Merry Christmas and happy holidays!

I hope my friend @poker won't mind that i post here this additional news:

Details on our new seedbox platform

We are very excited to announce that few days ago our new seedbox platform that we have been working on for the past 6 months has been officially launched. In this blog post, we will provide additional information, for our technical-savvy clients that are interested to read about it.

Our new platform is built on top of linux containers. If you do not know what linux containers are, you can read all about them here.

Linux containers were a perfect fit for our service because:

• They have little no none performance overhead because there is no emulation or an intermediate virtual machine involved. Seedboxes require to have as direct access to the hardware as possible in order to get the best performance possible from it
• They provide very good user and network isolation
• With the use of Docker, it is very easy to separate seedbox function into separate application images, easily maintainable and distributable to all servers

So what are the benefits in using containers in our setup?

• Each seedbox is completely isolated on the server. It feels like a dedicated server, but in fact it uses the shared resources of the whole server, providing more power and resources during times that are needed. This would not be possible on a dedicated Server
• Better security. Each user is contained and can see only his processes and his own seedbox structure. Each action of a user posses less threat to the integrity of the whole server and it is more difficult to affect the performance of others. It is also possible now to specifically limit the cpu priority and ram available to a specific seedbox on the server, in rare cases that this might be needed (abusive users for instance).
• The network is also isolated, meaning that we have full control on what a client runs on his/hers account. For instance, a client now cannot run a 3rd party application (server) that requires an external port. In the past inexperience users running 3rd party apps on their slots, were interfering with system ports or other user’s ports causing issues in the service. This is no longer a problem anymore.
• A wild range of apps. Apps are more easy to be distributed and maintained, which allows us to be able to add more and more of them into our catalog. Apps that previously were only able to run once per server (ex. Teamspeak, Plex) are now able to run once per user. Apps that required server wide installation and were not possible to be installed on a shared hosting platform, are now possible to be used in containers, once per user.
  The advantages of the dockerised images for apps, makes distribution and upgrades for them even easier. Just creating a new app container image with the new version, allows us to upgrade all containers over all our servers, simultaneously with 1 command within minutes and virtually only seconds of downtime for the client.
  Furthermore allows us, to migrate accounts from one server to the other without the need of changing configuration of the apps and settings afterwards. Just copy the data of the client on the new server and re-run the container applications and everything is exactly as before. Containers are server agnostic, meaning their configuration and the final result, is the same on any server that they will run.
• we no longer need to use URLs for the service that are server specific. We plan to make the service as server agnostic as possible. We can now migrate account from server to server and the service URL links will remain EXACTLY the same for the end client. This means that we can make migrations with minimal downtime if needed.

In our new platform, we made security our top concern. All service links are now always over SSL. Applications, http access, SSH, FTP, torrent client webUIs, are now always SSL enabled (protected by our own valid SSL certificates) and not with self signed certificates. Even if an application does not support SSL by its own, is now served over SSL on our servers.

Also, there are no more service links with ports inside (ex. http://server.seedboxes.cc:34523). All service links are now semantic, in order to be memorable and easily accessible from everywhere. We use a standard url form for everything -> https://username-app.cloud.seedboxes.cc

These were just a few of the new changes that we introduced on our new platform. We will keep you updated with more technical blog posts in the future on developments of our seedbox platform

So what about our old platform seedboxes ? Will they be migrated eventually in our new platform?

The answer is of course yes. Beginning of the new year we plan to migrate all our servers, one by one to the new platform. However we want to do this change as transparently as possible, and we are still working on migration scenarios to debug our migration procedure in order to have minimal downtime.

When the time comes, we will post a migration schedule for our servers, and notify customers in advance for the expected downtime and procedure of these migrations.