This article collects the questions that come up regardless of which product you use, mostly the kind you only discover once you are using it. For questions specific to one product, see that product's FAQ.
Subscriptions and data retention
Q: When I cancel, is my data deleted immediately?
No, there is a buffer in between. The instance keeps running all day on the expiry date, and the day after expiry it is suspended (the container stops, but the data volume is kept intact), so renewing at that point brings everything back untouched; only after 3 months of suspension is it permanently deleted, with no way to recover it. In other words, you have 3 months between expiry and your data disappearing to decide whether to renew.
Q: After I cancel, can I still use the remaining days of this billing cycle?
Yes. Canceling stops the next automatic charge; it does not disable the service on the spot. The cycle you have already paid for runs to its end, and only then does the suspension-and-retention process described above begin. The period you have already paid for is not refunded or prorated, and there is no cancellation fee.
Q: How many instances can I run on one plan?
One plan corresponds to one dedicated instance. If you need two environments isolated from each other (a production one and a staging one, for example), that means buying two plans, each with its own subdomain, data and billing cycle.
Resources and performance
Q: What happens if I go over my memory limit? Does it slow down or break?
It is terminated, not slowed down — and that distinction matters. A container's memory is a hard ceiling, and we deliberately set swap to the same value as memory, which means swap is never used. When a process inside the instance asks for more memory than the limit, the system kills that process outright rather than using disk as memory (which would make the whole service unusably slow).
What that means in practice: if your workload can consume a large amount of memory in a burst (loading tens of thousands of records into memory at once before processing them, for example), switch to processing in batches, or move up to a plan with more resources.
Q: Can someone else's instance affect my speed?
No. Every instance is a separate Docker container with its own memory limit, CPU limit and dedicated Docker network, and containers cannot reach each other by default. This is a different architecture from traditional shared hosting, where many accounts share the resources of one machine — a neighbor's traffic spike cannot drag you down, though by the same token you cannot use resources beyond your own plan.
Q: Are the 1-core and 2-core CPU figures a guarantee or a ceiling?
They are a ceiling, set with the --cpus parameter. Your instance can use up to the stated amount of compute, and no other instance can take it from you, but you cannot exceed it either.
Managing an instance
Q: Something is wrong with my service — can I fix it myself?
Yes. The dashboard gives you four actions — start, stop, restart, and rebuild from scratch — with no need to wait for support. For most connection problems and broken configurations, "restart" is enough.
Q: What is the difference between restart and rebuild from scratch?
The difference is whether your data survives, and it is irreversible. "Restart" stops the container and starts it again with the data fully intact; use it when connections are failing or the service is unresponsive. "Rebuild from scratch" deletes the container and recreates it from the latest image, and the data inside the container is wiped; use it when upgrading a version or when the configuration is beyond repair. Before rebuilding, make sure the data you need has already been exported.
Q: Can I upgrade my existing plan to a higher tier directly?
Yes, for services that have a higher plan: WordPress (Basic → WP × Roamer AI Pro) and OpenClaw (Pro → Advanced) can be upgraded with one click from the dashboard. Upgrades stay within the same billing cycle (monthly to monthly, yearly to yearly; accounts that started on a free trial upgrade to yearly), take effect as soon as payment goes through, and start a new billing period from the payment date. Your existing instance carries over, so there is no rebuild and no data to move.
There is currently no self-service downgrade; if you need one, email support. New WordPress and n8n subscriptions are yearly only. An existing monthly subscription can stay monthly or switch to yearly when you renew, but once it is yearly it cannot go back to monthly.
URLs and connections
Q: Does my service URL have to be xxx.roamerhost.com?
WordPress can use your own domain; the other services currently use a subdomain assigned by the platform. Either way, HTTPS works out of the box — the platform uses a wildcard certificate, so a new instance is on a secure connection as soon as it is created, with no certificate to request and no signing to wait for.
Q: Do certificates expire? Do I have to renew them myself?
No. The platform renews certificates automatically 30 days before expiry, and also runs a weekly certificate health check; a failed renewal raises an alert that we act on.
Still have not found your answer?
For questions specific to a product, see that product's FAQ, or simply contact us.
Further reading
- WordPress hosting pre-purchase FAQ: migration, multisite and traffic
- Managed n8n pre-purchase FAQ: execution counts, data residency and community nodes
Want someone to build it for you?
If you would rather not build these workflows yourself, or the scale is large enough that you want someone planning alongside you, Roamer Tech (RoamerHost's parent company) takes on contract work in business process automation and AI agents:
