FAQ

You do not need a card. Pay by bank transfer or a local payment method available in your country, in dollars or your local currency: choose a plan, we send you the amount and how to pay, you transfer it and send us proof, and we activate your account.

Most shared hosting puts dozens of accounts on the same resources, so one busy site slows every site around it. Here every site runs within its own CPU and memory limit: two cores and 2 GB per site on all three plans. A site that reaches its limit is held there — it cannot push past it and take the server's resources at the expense of other sites.

Within one working day. Activation is manual today because verifying the transfer is manual: we check your proof of transfer, create the account, and send you your control panel login. A request that arrives outside working hours counts from the next working day.

Yes, and at no charge. Send us access to your current hosting and we move the files, the databases and the mailboxes. Your old site keeps running until we have confirmed the copy here is sound, and only then does the domain point at us — so your visitors see no outage. The steps are under migration and support.

Frankfurt, Germany. The servers sit in a datacentre with stable power and network, so your site stays reachable for its visitors wherever they are.

Storage, monthly data transfer, number of sites, databases and mailboxes, Node.js, SSH and Git on Business and Premium only — plus a free domain for the first year on Business and Premium. CPU and memory are the same on all three plans: two cores and 2 GB per site, so every extra site on a plan runs under its own limit. The full table is on the hosting plans page.

Nothing is deleted. But at the disk limit new writes stop, and a site that needs to write files to work — uploading images, saving its cache — can stop working until space is freed. That is why we contact you as you approach the limit wherever we can, and you have two options: free up space, or move up a plan. An upgrade happens on the same account, with no migration and no downtime.

Bank transfer, and the local payment methods available in your country, in dollars or your local currency. No international card needed. Tell us your country and the method that suits you before ordering, and we send you the transfer details.

Prices are published in dollars. Pay in dollars and that is the amount. Pay in your local currency and we convert it at your country's exchange rate on the day of payment, and send you the figure before you transfer. The dollar price is the same for every customer, and no margin is added on the way.

No. The amount is fixed on the day you pay and holds until the end of the term you paid for, however the exchange rate moves afterwards. That is the practical difference between paying monthly and yearly: yearly fixes your price for a full year.

The plan price in dollars is fixed, and we do not sell at a low introductory rate and raise it at renewal. If you pay in your local currency, the only figure recalculated is the amount in it, at the rate on the day of renewal. And if we ever do change a dollar price, you hear about it before your renewal, not after.

A full refund within 14 days of the subscription starting, on the hosting itself. A domain is not refundable once registered, because it is registered in your name and stays yours even if you leave us. The details are in the refund policy.

Stop renewing, and that is the whole of it: no cancellation fee, no notice period, no contract holding you. Ask before your term ends and we hand you a complete copy of your files and databases — your data is yours, and we are not in the business of holding it to keep you.

Several, and you choose the version per site from the control panel — so an older client site and a current one run on the same account without conflict. What we will not publish here is the version list by number before we have verified it on the live account; ask us and you will get the list available today.

Yes, on Business and Premium — not on Start: you create a Node.js application from the control panel, and it keeps running and restarts on its own if it stops. Before you start: the application takes over the whole site's domain, so it cannot share a site with WordPress or a PHP site — give it a site of its own, which means a plan with more than one site if you want both. Python, Docker and root access are not available on shared hosting; a project that needs them belongs on a managed VPS, which we are still preparing.

On Business and Premium: connect to your site over SSH and deploy from your repository with git pull instead of uploading files by hand. Start has no SSH or Git — you upload files through the file manager or FTP.

No, and that is a limit of shared hosting rather than a decision of ours: Docker needs root on the server, which is not granted to a hosting account others share. We say so plainly rather than let you find out after buying. Projects that need containers belong on a managed VPS, which we are still preparing.

Yes, on both sides. On the hosting: it installs over SSH with Composer, so it belongs on Business or Premium rather than Start, and runs on PHP and MySQL — pick a plan with room for its files and media. On the services side: Drupal is one of the technologies we actually build with, not a name on a supported list. That work is described under web development.

After an analysis session, not before one. We learn the problem, the audience and the constraints, then put a proposal in front of you setting out the scope, the technologies, the timeline and the price. We do not quote before we understand a project, because a number given that early is either padded to be safe or low enough to win the work and raised halfway through.

The timeline is set in the architecture proposal after the analysis session, and a content site and a full system differ far too much for one number here to be honest. What is fixed in every project is the shape: staged delivery, with a review with you at the end of each stage — so you see something working early instead of waiting until the end to discover it is not what you wanted.

Yes, all of it: the code, the technical documentation and the deployment pipeline. We do not build systems that need us in order to run — you, or any other developer, can carry on from where we stopped. That is a fixed condition on every project, not a term to be negotiated.

Yes. Every project includes a month of support after handover, in which anything that surfaces in real use is fixed at no extra cost. After that you choose: a monthly maintenance contract covering updates, backups and monitoring, or keep what you were handed and carry it yourself.

Yes. We come in to review code, to assess the architecture of a system already in production before the decision to rebuild it, or to take on deployment and monitoring while your team builds features. Starting from scratch is not a condition of our working on a project. The full list is on the services page.

In four steps: choose a plan and pay, send us access to your current hosting, we copy the files, databases and mailboxes and test the site on our servers over a temporary link, then you change the nameservers at your domain registrar. None of it costs extra, and none of it asks you to take your site down.

The copy and the testing are usually done the same day for a site of ordinary size. What takes longer after that is not on our side: a nameserver change propagates across the internet over some hours, and can take a full day depending on your registrar and your visitors' providers. Your old site keeps running throughout, so nobody sees an outage.

Sat – Thu, 10:00 AM – 7:00 PM GMT+3. A message sent outside those hours is answered in the first working hour after it. Support is from a technical team, in Arabic or English: no canned replies, and nobody relaying your question somewhere else.

There is no ticket system today, and we will not pretend otherwise. Support runs over WhatsApp or by email to info@qasioun.cloud, and both reach the same team. When the client area opens it will carry a ticket system that tracks a request from opening to close, and we will tell you then.