Frequently Asked Questions

No. Migration here is self-service, and we would rather say so than advertise a service we cannot staff. What we do instead is make the move safe: every website is created on its own temporary address, so you copy the site across, test every page on that address, and only change DNS when it is right. Your old host keeps serving visitors the whole time.

Create the website here, then bring your files and database across with a migration plugin such as Migrate Guru, All-in-One WP Migration or Duplicator, or by hand over SFTP and WP-CLI. The help centre walks through both routes step by step.

Not if you follow the order. The copy is built and tested on a temporary address while your old host is still live, and the switch is one DNS record at the end. Visitors whose DNS has not refreshed keep reaching the old server until it has.

No, and this catches people out. Mailboxes are separate from hosting, and Oxyforge does not host mailboxes at all. If your mail currently sits with your old host, move it to Google Workspace or Microsoft 365 before you switch the domain, and keep the MX records pointing there.

Yes. A free account can create one temporary website at a time. It lasts 24 hours on the real platform and then deletes itself, and you can create another once it is gone.

Build is $24 a month for one website, Grow is $48 for up to three and Scale is $96 for up to ten. Annual billing gives you two months free. Prices are in US dollars.

How many websites you run and how much room they share. The speed, the backups, the staging and the support are identical on all three. A site on Build performs exactly like a site on Scale.

Your files and your database added together, pooled across every website on the account. Backups are kept separately and do not count against it.

You are warned as you approach the limit. If the account passes it, the websites on that account are suspended until the next billing period begins or you move up a plan, and they come back automatically once usage is inside the allowance. Nothing is deleted, and your files, databases and backups are untouched. Storage works differently and never suspends anything.

Yes. You can set a cap on any individual website from its usage page. A cap is a ceiling inside the shared pool rather than an allowance of its own, and you can change or remove it at any time.

Yes. Open a ticket from the members area and we move you; your sites, domains and backups stay where they are. Card payments and self-service plan changes are coming.

No. All fees are non-refundable, which is why a free trial website exists and why we encourage you to use it before paying.

Every website is backed up automatically once a day and the last 30 days are kept. You can restore the whole site, only the files or only the database, and take a backup on demand before a risky change. Treat them as a safety net rather than a guarantee, and keep your own copy of anything you could not recreate.

Yes, on every plan. One click copies your live site to a password-protected staging address, and when you are happy you push it back to live, choosing files, database or both.

No, and you should remove the one you have. A full-page cache and a Redis object cache run for you and clear themselves when you publish. A caching plugin on top of that causes problems rather than solving them.

Yes, on every plan. Each website has its own SFTP account with SSH keys, and WP-CLI over SSH.

No. You get a dashboard built for WordPress, plus SFTP and WP-CLI for the technical work. If you need a server you can do anything with, a VPS is a better fit.

Yes. Any website can be put behind a password from its protection page, which keeps it away from visitors and search engines until you are ready.

Yes, for the mail a website actually needs: password resets, order confirmations and contact-form notifications. It is included with your plan. For a shop or anything that sends a lot of mail, connect your own SMTP provider; it gives you delivery logs and your own sending reputation.

No. We host websites, not email. For mailboxes at your own domain, use Google Workspace, Microsoft 365 or a dedicated mail provider.

Not through the included sending, which is for transactional mail only. Connect your own SMTP provider with a plugin such as WP Mail SMTP and your mail goes out under your own sending reputation.

Each website runs in its own isolated container under its own system user. Nothing on the platform can read another customer’s files.

Yes, every night. Findings go to our team first, and a person contacts you if your site needs attention. Common attack doors such as XML-RPC answer Jetpack only by default. A scan finds known bad files; it is not a guarantee, and keeping WordPress, themes and plugins updated is still the main defence.

Yes. Every connected domain gets a certificate automatically and it renews itself. There is nothing to buy or install.

Restore a backup from before the infection, then update everything and change your passwords. Open a ticket and we will help you work out when it happened and which backup to use.

Open a ticket from the members area. It reaches the people who run the platform, with your websites already in front of them. The help centre covers most things without waiting for a reply.

Anything to do with the platform: the server, caching, backups, staging, domains, certificates, limits and access. We will also point you in the right direction on a WordPress problem, but we do not build or fix websites, write code or debug third-party plugins for you.

We are a small team in Singapore. Tickets are answered by the people who built the platform rather than a first line reading from a script, and we would rather be honest about hours than promise a number we cannot hold.