Payment methods
- M-Pesa
- Visa and Mastercard
- Bank transfer
All methods are handled inside the StackHost billing portal.
These terms cover ordering, payment, cancellation and refunds, acceptable use and what happens when something goes wrong. They are deliberately short, and where a detail matters to a specific order, the order you signed wins.
Plain languageNo lock-in clausesLast updated 7 October 2026
StackHost Africa is a managed hosting business operating from Nairobi, Kenya. We run websites, applications, virtual servers, private compute pools and a management layer over customer infrastructure, and every commitment on this site is one we make ourselves — there is no reseller chain behind the service.
Everything runs through one StackHost account in our billing portal. You create the account, pick the product, and a person confirms the details before anything is invoiced.
Billing is handled by our billing portal, so card details go to the payment processor — not to us.
All methods are handled inside the StackHost billing portal.
If a payment fails, we retry and email the account before anything else happens. Services are suspended only after repeated failed attempts and notice — see suspension.
The offer applies to the Starter Managed Hosting plan. It is a real free period, not a discounted one — and the rules around it are short.
You can cancel any time from the billing portal — no email chain, no retention call. Cancellation takes effect at the end of the period you have already paid for, and the service stays live until then.
Shared lanes sit on shared infrastructure, so the rules there protect other customers first. On dedicated capacity the floor is lower — the law, and the health of the platform.
Most suspensions are avoidable, and the path to one is long on purpose.
| Trigger | What happens first | What happens next |
|---|---|---|
| Failed payment | Retry, then an email to the account | Suspension after repeated failures and notice; cancellation and data cleanup follow after 14 days |
| Acceptable-use breach | We contact you and ask for it to stop | Suspension only if it continues, or immediately where the law or an active attack requires it |
| You ask to leave | Cancellation in the portal, effective at period end | Export window to the end of the paid period; backups roll off on the published schedule |
A suspended service is stopped, not deleted. Data is removed only after the notice period above, or when the law requires removal sooner.
Backup schedules and retention are written into each plan or order. What is common across all of them: the backups are yours to ask for, and restores are charged only when you request one.
We do not publish an uptime percentage; the reasoning is on the support and service levels page. Commitments are written per order, and monitored automation runs on every plan regardless.
When something here changes, we update this page and the date at the top. If a change is material to hosting customers, we tell you directly before it takes effect. If a change does not work for you, the cancellation rules above are the exit — used the same way as always.