iNTECH Cloud Hosting is now ZevCloud
Why we rebuilt our hosting product for the way developers actually ship in 2026, what it means for existing iNTECH Cloud Hosting customers, and what stays the same.
If you have an account on iNTECH Cloud Hosting, this is the post that explains what is happening. If you do not, this is the public version of why we rebuilt the product.
iNTECH Cloud Hosting is winding down. ZevCloud is what we built in its place. Same team, very different product.
Why we rebuilt
Look at how a developer ships software in 2026 versus how they did it five or six years ago. Code is written with an AI agent in the loop. Repos live on GitHub from day one. A working app is one git push or one click in a dashboard away from a live URL. People are vibe coding, pairing with agents in their editor, and treating their environment as something they describe rather than something they configure by hand. The shape of “I have a project, I want it live” looks nothing like it did when traditional shared hosting was the default answer.
Cpanel-era shared hosting was not built for any of that. It was built for FTP, manual file uploads, and a control panel for poking at your space. That model still works for some people, but it does not bend to the way most developers actually ship today, and we did not want to keep reshaping it to fit.
So we rebuilt the product around what work actually looks like now:
- Git-driven deploys. Connect a repo, push to a branch, get a live URL. No FTP. No “upload files via the panel.”
- A real CLI.
zevcloud login,zevcloud deploy,zevcloud logs -f,zevcloud rollback. Anything you can do in the dashboard you can do from the terminal, and that is the surface most senior developers actually want. - Agent-friendly by default. Because there is a CLI and an API behind it, your editor, your CI runner, or your AI coding agent can drive a deployment the same way you can. No screen-scraping a control panel to ship a build.
- Isolated resources per service. Your app gets its own allocation of CPU, RAM, and storage. You are not splitting a server with two hundred other sites and hoping nobody else writes a runaway script.
That last point matters more than it sounds. The whole reason traditional shared hosting was cheap is because you were sharing, with everything that comes with that: noisy neighbours, security boundaries that depend on someone else’s configuration, performance that depends on whoever is on the same box. ZevCloud’s model gives every project its own resources, with a free tier that still costs nothing. You get the modern boundary without paying for it.
WordPress is still first-class
A lot of our iNTECH Cloud Hosting customers run WordPress, and we did not leave that audience behind. ZevCloud’s WordPress product is a real upgrade, not an afterthought: one-click WordPress, isolated per site, with snapshots, staging environments, automatic SSL, and SFTP. The parts of cPanel that were genuinely useful for WordPress (easy installs, free SSL, scheduled backups) are all here. The parts that were painful (shared resources with strangers, the WHMCS account hop, plugin behaviour that depended on which CloudLinux setting your host had configured) are not.
If you came to us for WordPress and you want to stay on WordPress, you do not lose anything in the move. You gain isolation, deployment workflows that work with Git, and a billing surface in your own currency.
One brand, across the family
There is also a brand reason for the change, and it is not a small one. Our parent company rebranded from iNTECH to ZevOP, and ZevCloud is one product in a family that already includes ZevID (the account layer) and ZevPay (the billing layer), with more on the way. The “iNTECH” name was widely contested, both with international companies operating under similar marks and with local outfits trading off the name in this region. We made the call to consolidate under a brand we own end-to-end. ZevOP and the products under it (ZevCloud included) are trademarks held by us, not borrowed and not at risk of being someone else’s tomorrow.
For customers, what this means in practice is simple: one identity (ZevID) signs you into every product in the Zev family, one billing surface (ZevPay) handles the invoices, and the product names you read on a dashboard, an invoice, and a support email all line up with the company that ships them. That alignment is hard to do retroactively. It is much cleaner to do as part of a clean rebuild, which is exactly what we did.
And the license math
There is a quieter reason behind the rebuild. Every license in the cPanel-era stack (cPanel, WHMCS, JetBackup, CloudLinux, Imunify) is sold in dollars, billed per server, and the rate moves the wrong way every quarter for a Nigerian operator. The license tax compounds with growth.
The shortcut most regional hosts take is to run cracked or nulled versions of those licenses. The price drops to zero. The cost is that customer sites end up on control panels with disabled signing, third-party patches, and unverified updates, sitting on shared servers next to other customers’ sites. It is one of the most consistent and underdiscussed sources of compromise in the regional hosting market. We were not willing to take that shortcut, and the licensed economics did not work, so the math agreed with everything else: rebuild.
What changed
The mental model is different. Instead of a server account and a control panel, ZevCloud gives you a project, the surface of your choice (dashboard, CLI, git push, or our API), and a live URL. That covers web applications, WordPress, databases, static sites, and domain registration, all under one workspace.
A few things we changed by design:
- Naira-native billing. Every charge generates an invoice through ZevPay. No card-on-file in dollars, no FX surprise on renewal.
- Single sign-on across the Zev family. ZevID is the account, ZevCloud is one product on top of it, ZevPay handles the money.
- Monthly billing only. No annual prepay. You pay for what you ran in a given month.
- Same registrar accreditation. We are still a NiRA-accredited .ng registrar. That part stays.
What this means if you are still on iNTECH Cloud Hosting
We are not migrating accounts automatically. The environment is too different (different account system, different billing surface, different deployment model) for us to do that responsibly. Instead:
- You will get an email from us shortly with the wind-down notice. If your account is still active, that email is the source of truth on dates and your specific situation.
- All current iNTECH Cloud Hosting subscriptions are monthly. When your current billing cycle ends, you will not be able to renew.
- You have through May 31, 2026 to either move your sites to ZevCloud, move them somewhere else, or export what is yours. After that, we are decommissioning the iNTECH Cloud Hosting environment.
- Our support team is available to help you transition. If you want to come over to ZevCloud, we will walk you through it. If you want to go somewhere else, we can still help you export.
If you want to come over to ZevCloud, the dashboard is open today and there is a free tier on most products. The docs cover the deployment flows for the kinds of sites that used to run on iNTECH Cloud Hosting.
What stays the same
The team is the same. The accreditation is the same. The commitment to the Nigerian dev market is the same. The thing that changed is the product, because the old shape stopped serving the way our customers actually build, and the new one does.
If you are reading this with no iNTECH history, none of the above changes anything for you. We just owed our existing customers the long version of why this happened, and the blog is the right place to leave it on the public record.
Related posts
Hello, ZevClouders
Welcome to the ZevCloud blog. What we are publishing here, who it is for, and what to expect.
What actually breaks when you migrate WordPress off cPanel
The honest version of a WordPress migration. The seven things that actually broke during a real cPanel-to-PaaS move this week, and how to fix each, whether you end up on ZevCloud or somewhere else.