For this review of 20i, I tested Reseller 50, a plan designed for selling hosting to clients. I approached it as if I were setting up a small agency’s hosting service: I signed up, created a reusable hosting package, launched a working WordPress site, and tested the tools I would need to manage it once a client’s site was live.
My findings on signup, the My20i control panel, package creation, WordPress, staging, backups, performance, and support all come from hands-on testing with Reseller 50. I also cover 20i’s wider hosting range to help you decide which product fits your needs, while clearly distinguishing those overviews from the features and services I tested myself.
I used HostAdvice’s hosting rating methodology to keep the scoring consistent with our other hosting reviews. The table below shows how 20i performed across pricing, features, performance, ease of use, and support based on the evidence from my hands-on test.
| Parameter | Score | Why This Score |
|---|---|---|
| Prices | 9.0/10 | Strong introductory offer and reseller value |
| Features | 9.4/10 | Deep reseller, WordPress, billing, and white-label tools |
| Performance | 8.0/10 | Stable site, but baseline speed needed optimization |
| Ease of Use | 8.8/10 | Clear workflow after learning the package model |
| Support | 8.5/10 | Fast human reply; accurate but not fully complete |
| Overall | 8.7/10 | Strong reseller workflow with a few real rough edges |
The reseller controls, WordPress workflow, and support experience were the strongest parts of my test. The weaker points were the unoptimized performance baseline and the fact that my first combined files-and-database restore did not complete without a manual recovery path.
Before getting into the hands-on tests, it helps to separate 20i’s product families. The company sells several types of hosting, and the infrastructure and level of control are not identical across them.
I tested Reseller Hosting, but a VPS buyer, a Managed Cloud Server customer, and someone buying Managed WordPress are solving different problems.
| Plan Name | Space | Bandwidth | OS | Panel | Price | |
|---|---|---|---|---|---|---|
| Reseller 25 | 30 GB | Unlimited | MYR 110 | Details | ||
| Reseller Hosting 50 | Unlimited | Unlimited | MYR 219 | Details | ||
| Reseller Hosting 500 | Unlimited | Unlimited | MYR 383 | Details | ||
| Reseller Hosting Unlimited | Unlimited | Unlimited | MYR 547 | Details |
| Plan Name | Space | CPU | RAM | OS | Price | |
|---|---|---|---|---|---|---|
| 1 Core | 25 GB | 1 x 2.2GHz | 1 GB | MYR 77 | Details | |
| 2 Coress | 50 GB | 2 x 2.2GHz | 2 GB | MYR 110 | Details | |
| 4 Cores | 75 GB | 4 x 2.2GHz | 4 GB | MYR 181 | Details | |
| 6 Cores | 100 GB | 6 x 2.2GHz | 8 GB | MYR 361 | Details | |
| 8 Cores | 200 GB | 8 x 2.2GHz | 16 GB | MYR 579 | Details | |
| 10 Cores | 400 GB | 10 x 2.2GHz | 32 GB | MYR 1,442 | Details | |
| 12 Cores | 800 GB | 12 x 2.2GHz | 64 GB | MYR 2,884 | Details |
| Plan Name | Space | CPU | RAM | Bandwidth | OS | Price | |
|---|---|---|---|---|---|---|---|
| Micro | 25 GB | 1 core | 1 GB | 1 TB | MYR 61 | Details | |
| Small | 50 GB | 1 core | 2 GB | 2 TB | MYR 121 | Details | |
| Medium | 80 GB | 2 cores | 4 GB | 4 TB | MYR 241 | Details | |
| Large | 160 GB | 4 cores | 8 GB | 5 TB | MYR 481 | Details | |
| X Large | 320 GB | 8 cores | 16 GB | 10 TB | MYR 721 | Details | |
| 2X Large | 640 GB | 12 cores | 32 GB | 20 TB | MYR 1,382 | Details | |
| 4X Large | 640 GB | 16 cores | 32 GB | 30 TB | MYR 2,404 | Details | |
| 8X Large | 1.25 TB | 24 cores | 64 GB | 40 TB | MYR 4,206 | Details | |
| 16X Large | 1.4 TB | 32 cores | 96 GB | 40 TB | MYR 6,008 | Details | |
| 32X Large | 1.88 TB | 48 cores | 128 GB | 40 TB | MYR 9,613 | Details |
| Plan Name | Space | CPU | RAM | Warranty | Price | |
|---|---|---|---|---|---|---|
| Startup | 10 GB | - | MYR 0.00 | MYR 82 | Details | |
| Plan 1 | 10 GB | - | MYR 0.00 | MYR 164 | Details | |
| Plan 2 | 20 GB | - | MYR 0.00 | MYR 328 | Details | |
| Plan 3 | 40 GB | - | MYR 0.00 | MYR 547 | Details | |
| Plan 4 | 50 GB | - | MYR 0.00 | MYR 1,093 | Details | |
| Plan 5 | 100 GB | - | MYR 0.00 | MYR 2,185 | Details |
Here is everything you need to know about 20i pricing:
Money-back guarantee: Eligible reseller and managed hosting plans carry a 30-day money-back guarantee. The terms have exclusions, including domain registrations and renewals, private SSL certificates, virtual nameservers, VPS, and some add-ons.
Payment methods: My checkout used Stripe card fields. 20i also supports major cards, Apple Pay, and Google Pay. PayPal can be used to add credit to the account rather than as the normal direct checkout method.
Data-center costs: The first reseller origin you choose becomes the default location for the account. Additional reseller locations are a separate monthly cost, so a multi-region reseller setup can cost more than the plan headline suggests.
Website Turbo: Website Turbo is a paid performance add-on that uses Turbo credits. I left it disabled because I wanted my benchmark to reflect the base setup rather than an extra optimization purchase.
There is also a useful commercial angle if you sell more than shared hosting. Reseller customers receive discounts on some other 20i services, including Managed Cloud Servers and self-managed VPS. That means the reseller account can sit above several types of client infrastructure rather than limiting you to standard WordPress or Linux hosting.
I first saw the reseller pricing as four tiers on the US site. Each tier scales the number of hosting accounts, while the page keeps the first-month offer, normal recurring price, no-contract wording, and 30-day guarantee close together.
After choosing Reseller 50, the checkout summary kept both the introductory charge and the normal recurring amount visible. I liked that because it made the post-promotion cost harder to overlook.
For a reseller, the important pricing question is not just the monthly fee. I would also budget for any extra origin locations, Website Turbo credits, domains, paid SSL products, or server products you plan to bundle into your own service.
I did not want to benchmark an empty WordPress install because that would make the numbers look cleaner without telling me much about a real client site. After WordPress was running, I imported the Phlox Corpora business demo.
It gave me a full homepage with large images, Elementor, Depicter, WPForms, a slider, and the normal mix of front-end assets you would expect from a polished theme demo.
The hosting origin was Dallas, Texas. I left Website Turbo disabled and did not install WP Rocket, LiteSpeed Cache, or another third-party performance plugin. 20i’s StackCache integration stayed active because it was already part of the hosting environment.
I also kept the site on 20i’s temporary us.stackstaging.com URL instead of moving the production domain’s DNS. That is an important limitation. These are real measurements from the test environment I used, but I would not claim that every custom-domain production site will produce exactly the same numbers.
With the site ready, I ran the same URL through GTmetrix from San Antonio and London. I kept the page and hosting configuration unchanged so the test location was the main variable.
| Metric | San Antonio | London |
|---|---|---|
| GTmetrix Grade | C | E |
| Performance | 56% | 33% |
| Structure | 90% | 84% |
| TTFB | 1.5s | 1.6s |
| FCP | 2.0s | 2.3s |
| LCP | 3.3s | 4.7s |
| TBT | 257ms | 808ms |
| CLS | 0 | 0 |
| Time to Interactive | 3.4s | 6.3s |
| Onload Time | 3.2s | 4.8s |
| Fully Loaded Time | 4.5s | 6.3s |
The San Antonio run was the better of the two. GTmetrix returned Grade C, 56% Performance, 90% Structure, and a 4.5-second Fully Loaded Time. TTFB was 1.5 seconds, First Contentful Paint was 2.0 seconds, and Largest Contentful Paint reached 3.3 seconds.
The 90% Structure score next to a 56% Performance score is the part I paid most attention to. GTmetrix was not simply telling me that the page was badly assembled.
The page structure scored well, but the loading experience was still slower than I would want for a service sold around speed.
The server response also consumed a noticeable share of the wait. A 1.5-second TTFB meant the browser had already spent significant time before the main rendering work began. Once the page started rendering, Total Blocking Time was 257ms, and CLS stayed at 0.
That zero layout shift is a positive result. The demo has a large slider, images, and several moving visual components, yet the page did not jump around while loading.
After recording the US result, I changed only the GTmetrix test location and ran the same temporary URL from London. I wanted to see how much the experience changed for a visitor farther from the Dallas origin without altering the WordPress build in between.
London dropped to Grade E and 33% Performance. Fully Loaded Time rose to 6.3 seconds, Largest Contentful Paint reached 4.7 seconds, and Total Blocking Time increased to 808ms.
I would not attribute the entire gap to distance from Dallas. TTFB moved only from 1.5 seconds to 1.6 seconds. The larger deterioration happened after the initial response, especially in blocking time and the point at which the largest visual element finished rendering.
That makes the heavy front end part of the story. Elementor, the slider, theme assets, and normal run-to-run variation can all affect a single GTmetrix result. The London test still matters because it shows what I measured from that location, but it would be too strong to say geography alone caused the weaker grade.
CLS remained 0, so the site kept the same visual stability I saw in Texas. The weaker experience was about waiting longer, not content moving around the page.
Across the two runs, 20i kept the page visually stable but did not give me a strong out-of-the-box performance result on this full demo. The better run still needed 4.5 seconds to finish loading, while London reached 6.3 seconds.
There is plenty I could change from here. I did not enable Website Turbo, replace the theme, strip out Elementor, remove the slider, or add a third-party optimization plugin. That is intentional. I wanted a baseline first, because a reseller needs to know what the platform gives you before extra tuning hides the starting point.
For ease of use, I followed the reseller journey in the order it happened. I started at the public site, created the account, entered My20i, defined a hosting package, provisioned a WordPress site, cloned it to staging, then tested backup and recovery. That sequence made it easier to see where 20i saves time and where its reseller model asks you to make more decisions than a normal shared hosting account.
I began on 20i’s US Reseller Hosting page. Reseller Hosting sits in the main navigation, so I did not have to work through a generic hosting selector first. The landing page explained the core reseller pitch and linked directly to the reseller plans.
After this, I selected Reseller 50. The signup flow showed four stages across the top: Sign in, Details, Payment, and Complete. The first page asked for an email address and password while the order summary remained visible on the right.
Once the account credentials were set, I moved to the Details stage. Here 20i asked if I was signing up as an individual or business, then collected my name, country, phone number, and address information.
The order summary stayed on the page while I moved through those fields. That sounds minor, but it keeps the plan and billing context visible instead of forcing you to go backward to confirm what you selected.
The last stage I needed to complete was payment. 20i used Stripe card fields and again kept the order summary beside them. I did not run into a long chain of upsells before I could finish the order.
After payment, I landed in My20i. This is the main reseller dashboard, and the first screen immediately made it clear that I had bought something broader than one hosting account.
The page is dense. Hosting Management, Customer Management, Marketing Resources & Guides, Migration Centre, and Support & Customer Services all sit on the same dashboard, with shortcuts for tools such as Manage Hosting, Hosting Package Types, SSL Certificates, Domain Names, Website Turbo, Timeline Backups, WordPress Manager, StackCP Users, HostShop, and WHMCS.
Because my account was still unused, the Account Usage panel was helpful. It showed zero websites, zero databases, zero mailboxes, no disk usage, and no bandwidth usage. The account card also identified the plan as Reseller 50.
The dashboard looked busy for a few minutes, but I did not need documentation to find the main paths. Hosting work sat under Hosting Management, customer-facing tools were grouped together, and support had its own section.
The next step taught me the main difference between 20i and the cPanel/WHM pattern many resellers already know. Instead of creating a customer account first and deciding the limits later, I started by defining a reusable hosting package.
I opened Hosting Package Types. With nothing assigned yet, My20i showed Linux Unlimited, Managed VPS, Web Builder, and WordPress Unlimited as the available package templates.
I clicked Add Package Type and chose WordPress. The next screen exposed a long list of controls: webspace, bandwidth, FTP accounts, subdomains, additional domains, email limits, PHP settings, welcome emails, WordPress tools, backups, Git, SSH, SSL, DNS options, malware scanning, logs, and more.
This is where 20i starts to feel like a reseller platform rather than a normal hosting plan. I could decide not just how many resources a customer receives, but which tools appear in the customer’s environment.
I created a package called Business WordPress. I kept the limits sensible for a small business site and left Website Turbo disabled because the form warned that it consumes a Turbo credit and can trigger a purchase if no credit is available.
After saving the package definition, I moved straight into creating the actual hosting account. My20i offered four paths: create a new hosting package, clone an existing package, create from a WordPress blueprint, or migrate from another provider.
I chose a new package, selected Business WordPress, and then picked Dallas as the data center. The page also explained that this first reseller location becomes the account default and that additional locations can be enabled separately.
I hit one rule before I could finish. When I tried 20i.hostadvice.tech, the panel told me I first needed a hosting package for the parent hostadvice.tech domain. Rather than change DNS or create an extra parent package, I used hostadvice.tech for this test.
Once I confirmed the details, 20i created the hosting package immediately. It appeared as Active in Manage Hosting, with Business WordPress as the package and Dallas as the data center.
With the hosting account active, I opened hostadvice.tech from Manage Hosting. The site-level panel grouped WordPress tools, CDN controls, files, email, PHP and database tools, domains, security, logs, and account information on one page.
I had not pointed hostadvice.tech to 20i, so the temporary URL shown in the account was especially useful. It let me keep testing without changing the DNS setup I was already using elsewhere.
WordPress was not installed by default. I opened the WordPress Install Wizard, which led into the normal WordPress setup screen for the site title, administrator username, password, and email.
What I did not have to do was create a database, database user, or edit wp-config.php manually. 20i handled that part behind the installer.
The setup completed successfully and returned the normal WordPress success screen with a login link.
After logging in, I reached a standard WordPress dashboard. StackCache was already visible in the admin interface, which confirmed that 20i’s caching integration was part of the hosting environment rather than a plugin I installed for the benchmark.
At this point I could have stopped with a default theme, but that would not have given the later tests much weight. I imported the Phlox Corpora business demo so the site had a full homepage, images, sliders, Elementor, Depicter, WPForms, and enough front-end work to behave more like a real customer site.
After the demo import, I wanted to test a feature I would actually use before editing a client site: staging. I went back into My20i, opened WordPress Staging, and chose Clone live into Staging.
Before I clicked Create, the page explained what would happen. 20i would make a complete clone, rewrite the WordPress URLs for the staging environment, create a separate staging directory and database, and keep staging requests outside its StackCache edge-caching path.
The clone took about three minutes. Because the custom domain was not pointed at 20i, the normal staging subdomain could not resolve. The panel detected that and provided a temporary staging URL instead of leaving me with a broken workflow.
I opened the staging copy and made a deliberately obvious change. The homepage hero headline became “STAGING TEST – THE LARGEST BUSINESS EXPERT.”
After this, I opened the original live temporary URL in another tab. It still showed the original “THE LARGEST BUSINESS EXPERT” headline, which confirmed that the staging edit had not leaked into production.
Once staging was working, I moved to recovery. That order mattered because I wanted the backup test to include a real WordPress install, imported demo content, plugins, and the extra staging state I had already created rather than a nearly empty account.
20i exposes two different backup routes. The manual Backup/Restore tool creates downloadable file and database archives, while Timeline Backups provides snapshot-based recovery. I started with the manual tool because I wanted to create a backup myself, download it, change the site, and then prove that I could return to the earlier state.
The manual screen let me choose Files, Databases, or both. I selected both.
The combined backup finished in about two minutes and appeared under Previous Backups with a Download option.
Next I needed a visible change that would make recovery easy to verify. I edited the live homepage headline to “BACKUP RESTORE TEST.” If the earlier backup returned correctly, that wording should disappear.
I then attempted the most obvious full recovery path. In Backup/Restore, I selected Delete all files and restore the zip file and enabled Restore Databases. The job entered the queue, but it did not complete. The history changed to “MySQL database limit reached.”
A moment later, the failure state was explicit.
This turned out to be a useful edge case rather than a dead end. Because I had already created staging, the account now had the live WordPress database and a staging database. Twentie later inspected the package and reported a one-database allowance for Business WordPress. The combined restore was trying to create a database instead of overwriting the existing live database.
I did not want to leave the review at the error screen, so I followed the recovery path that 20i support later confirmed. I restored the files with Restore Databases disabled, then imported the SQL backup into the existing live database through phpMyAdmin.
After the import, I reloaded the live site. The “BACKUP RESTORE TEST” wording was gone and the original homepage headline was back.
By the end of the workflow, My20i made much more sense than it did on the first login. The sequence is consistent: define the product you want to offer, create a hosting account from it, then manage the site through the same reseller environment.
The learning curve comes from breadth, not from hidden navigation. Package creation asks you to make many decisions, and rules such as the parent-domain requirement only become obvious when you encounter them. After that initial setup, hosting creation, WordPress installation, and staging moved quickly.
The backup test is the main reason I would not call the whole experience effortless. Creating the backup was simple, but recovering both files and the database after staging existed required more knowledge than the first restore screen suggested.
20i offers 24/7 technical support through live chat and support tickets. My20i also includes Twentie, a support database, and getting-started material. Phone support is positioned for sales rather than technical troubleshooting.
I did not invent a simple pre-sales question for this test. The failed backup restore gave me a real technical problem, so I used that as the support case. That let me judge not only response time but also how much account context the support system could use and if the answer actually helped me recover the site.
I started from Help & Support and chose Create Support Ticket. From there I selected Backups & Restores, selected hostadvice.tech, and described the exact restore path and the “MySQL database limit reached” error.
Before the issue reached a human, Twentie analysed the account. It identified the live WordPress database, the staging database, the Business WordPress package, the package database allowance, Timeline Backups availability, and the current system status.
Its explanation matched what I had just observed in the control panel. The file restore does not remove the existing database, so enabling Restore Databases can cause the restore job to try to create another database when the package has no spare capacity.
Twentie suggested two practical routes. The first was to restore the files without Restore Databases enabled, then import the SQL into the existing live database through phpMyAdmin. The second was to use Timeline Backups, where the database restore can target the existing database.
I still wanted a human to confirm the supported route. I chose escalation, and Twentie prepared the ticket with the service name, package ID, package type, database names, restore error, and the diagnostics it had already gathered.
I submitted ticket #497584011 at 7:17:58 PM EAT on October 6, 2026.
Jake E from 20i Support replied at 7:26:25 PM. That made the human response time 8 minutes 27 seconds.
Jake recommended the same recovery route Twentie had given me: run the manual restore with Restore Databases disabled, then restore the database separately through phpMyAdmin.
The answer was technically useful because it confirmed the path I could actually follow. It was also incomplete. My ticket asked how the live and staging databases should be handled and if the failed job could be recovered or needed a backend adjustment. Jake did not answer those parts directly.
The important result is that the advice worked. I followed the files-only restore and manual SQL import route and confirmed that the earlier homepage returned.
| Support Stage | Result | What It Meant |
|---|---|---|
| Twentie analysis | Immediate during ticket flow | Used real account and database context |
| Ticket submitted | 7:17:58 PM EAT | Included diagnostics and restore history |
| Human reply | 7:26:25 PM EAT | 8 minutes 27 seconds to a human answer |
| Answer quality | Correct recovery path | Useful, but did not answer every sub-question |
| Final outcome | Site recovered | Files-only restore plus manual SQL import worked |
Yes, if your main goal is reseller hosting for client websites and you want more control over the customer package than a normal shared hosting account gives you.
The strongest part of 20i is the workflow around the hosting itself. I could create a reusable package, control the tools a customer receives, provision WordPress, give clients separate StackCP access, connect HostShop or WHMCS, create staging copies, make backups, and keep the work inside one My20i environment.
WordPress provisioning was quick once the package existed, and staging was one of the best parts of the test. My complete Elementor demo cloned in about three minutes, and the visible staging change stayed isolated from the live site.
The two areas I would plan around are performance and recovery. My baseline GTmetrix runs were not strong enough for me to sell the default setup as a performance-first service. I would optimize and retest a production site before making speed promises to clients.
Recovery also deserves a written procedure. The manual files-and-database backup completed in about two minutes, but my first combined restore failed after staging existed. I did recover the site by restoring files separately and importing the SQL into the existing live database, and support confirmed that route.
For agencies, developers, and hosting resellers, those trade-offs are reasonable if the package controls, white-label tools, billing integrations, and customer management features match how you work. If you only need one simple website, Reseller 50 gives you much more tooling than you need. If you need root access or a custom operating system, I would look at 20i’s VPS range instead.
| Plan Name | Space | CPU | RAM | OS | Price | |
|---|---|---|---|---|---|---|
| 1 Core | 25 GB | 1 x 2.2GHz | 1 GB | MYR 77 | Details | |
| 2 Coress | 50 GB | 2 x 2.2GHz | 2 GB | MYR 110 | Details | |
| 4 Cores | 75 GB | 4 x 2.2GHz | 4 GB | MYR 181 | Details | |
| 6 Cores | 100 GB | 6 x 2.2GHz | 8 GB | MYR 361 | Details | |
| 8 Cores | 200 GB | 8 x 2.2GHz | 16 GB | MYR 579 | Details | |
| 10 Cores | 400 GB | 10 x 2.2GHz | 32 GB | MYR 1,442 | Details | |
| 12 Cores | 800 GB | 12 x 2.2GHz | 64 GB | MYR 2,884 | Details |
| Plan Name | Space | CPU | RAM | Bandwidth | OS | Price | |
|---|---|---|---|---|---|---|---|
| Micro | 25 GB | 1 core | 1 GB | 1 TB | MYR 61 | Details | |
| Small | 50 GB | 1 core | 2 GB | 2 TB | MYR 121 | Details | |
| Medium | 80 GB | 2 cores | 4 GB | 4 TB | MYR 241 | Details | |
| Large | 160 GB | 4 cores | 8 GB | 5 TB | MYR 481 | Details | |
| X Large | 320 GB | 8 cores | 16 GB | 10 TB | MYR 721 | Details | |
| 2X Large | 640 GB | 12 cores | 32 GB | 20 TB | MYR 1,382 | Details | |
| 4X Large | 640 GB | 16 cores | 32 GB | 30 TB | MYR 2,404 | Details | |
| 8X Large | 1.25 TB | 24 cores | 64 GB | 40 TB | MYR 4,206 | Details | |
| 16X Large | 1.4 TB | 32 cores | 96 GB | 40 TB | MYR 6,008 | Details | |
| 32X Large | 1.88 TB | 48 cores | 128 GB | 40 TB | MYR 9,613 | Details |
| Plan Name | Space | Bandwidth | OS | Panel | Price | |
|---|---|---|---|---|---|---|
| Reseller 25 | 30 GB | Unlimited | MYR 110 | Details | ||
| Reseller Hosting 50 | Unlimited | Unlimited | MYR 219 | Details | ||
| Reseller Hosting 500 | Unlimited | Unlimited | MYR 383 | Details | ||
| Reseller Hosting Unlimited | Unlimited | Unlimited | MYR 547 | Details |
| Plan Name | Space | CPU | RAM | Bandwidth | Warranty | Price | |
|---|---|---|---|---|---|---|---|
| Startup | 10 GB | - | 49.97 GB | MYR 0 | MYR 82 | Details | |
| Plan 1 | 10 GB | - | 99.94 GB | MYR 0 | MYR 164 | Details | |
| Plan 2 | 20 GB | - | 199.99 GB | MYR 0 | MYR 328 | Details | |
| Plan 3 | 40 GB | - | 299.93 GB | MYR 0 | MYR 547 | Details | |
| Plan 4 | 50 GB | - | 499.92 GB | MYR 0 | MYR 1,093 | Details | |
| Plan 5 | 100 GB | - | 1 TB | MYR 0 | MYR 2,185 | Details |
Yes. My Reseller 50 account included custom package types, StackCP customer access, HostShop, WHMCS support, migrations, WordPress management, staging, backups, CDN controls, and white-label settings. The main cautions from my test were the baseline performance and the extra recovery step needed after the combined restore failed.
No. 20i uses My20i for reseller and account management, with StackCP as the customer-facing hosting panel. The workflow is different from cPanel or WHM because you create reusable package types and provision customer hosting from them.
The reseller setup I tested offered London, Dallas, and Singapore origin locations. The much larger 60-plus-location claim applies to Managed Cloud Server deployment across 20iCloud, AWS, and Google Cloud rather than every reseller hosting account.
Yes. I cloned my complete WordPress demo from live to staging in about three minutes. A visible headline change on staging did not appear on the live copy.
Yes. 20i provides a manual Backup/Restore tool and a separate Timeline Backups system. My manual files-and-database backup completed in about two minutes. The first combined restore failed after staging existed, but I recovered the site through a files-only restore and manual SQL import.
Yes. 20i offers 24/7 technical support through live chat and support tickets. In my test, Twentie diagnosed the restore failure and prepared the escalation. Jake E replied 8 minutes 27 seconds after I submitted the ticket.
Yes. 20i advertises a 30-day money-back guarantee on eligible reseller and managed hosting plans. Its terms exclude items such as domain registrations and renewals, private SSL certificates, virtual nameservers, VPS, and some add-ons.
Answer a few simple questions and find the perfect solution for you!
Start Hosting Search
