Corporate Starter
For your company’s corporate website.
1Website in the same account
3 coresCPU
3 GBRAM
Starting resources for sites managed by the same business. If you need custom software, critical processing or system access, let’s assess server alternatives together.
Websites are managed in the same hosting account; CPU and RAM are account resources.
Compare all plansFor your company’s corporate website.
For company websites, brand websites and campaigns.
For multiple brands and intensive content management.
For teams managing a broad website portfolio.
The features show the reference configuration used for quotes. Resource implementation, backup retention, additional services and the total fee are clarified in writing before you order.
Scroll the table sideways to see other plans; feature names stay fixed.
| Plan featuresResources and included platform | Corporate StarterTailored quote quoted | Corporate BusinessTailored quote quoted | Corporate ProTailored quote quoted | Corporate PlusTailored quote quoted |
|---|---|---|---|---|
| Resources and capacity | ||||
| Website | 1 | 3 | 10 | 20 |
| CPU | 3 cores | 4 cores | 6 cores | 8 cores |
| RAM | 3 GB | 4 GB | 6 GB | 8 GB |
| Storage | Unmetered* | Unmetered* | Unmetered* | Unmetered* |
| InodesNumber of files and folders. | Unmetered* | Unmetered* | Unmetered* | Unmetered* |
| Monthly trafficNo numerical transfer quota is published in the source. | No numerical quota specified | No numerical quota specified | No numerical quota specified | No numerical quota specified |
| Platform and management | ||||
| Control panel | cPanel | cPanel | cPanel | cPanel |
| Operating system | Linux | Linux | Linux | Linux |
| Web server | LiteSpeed | LiteSpeed | LiteSpeed | LiteSpeed |
| Application support | Node.js / Python | Node.js / Python | Node.js / Python | Node.js / Python |
| BackupsRestore points and retention periods are defined separately. | Weekly | Weekly | Weekly | Weekly |
| Email and project accounts | ||||
| Email account | No count limit* | No count limit* | No count limit* | No count limit* |
| MySQL database | No count limit* | No count limit* | No count limit* | No count limit* |
| Subdomain | No count limit* | No count limit* | No count limit* | No count limit* |
| FTP account | 1 | 3 | 10 | 20 |
| Choose your plan | Get a quote | Get a quote | Get a quote | Get a quote |
Inside the platform
Options for 1, 3, 10 or 20 websites are planned for brand, campaign and company pages belonging to the same business. Sites in the same account share the total CPU and RAM resources.
Options range from 3 cores / 3 GB to 8 cores / 8 GB. Assess appointment, form, catalog and content management tasks alongside peak-hour usage.
Archive size, MX records and SPF / DKIM / DMARC configuration matter as much as mailbox count. Decide whether to keep the existing email provider when migrating the website.
cPanel, LiteSpeed, Linux and Node.js / Python support are part of the reference configuration. Business applications requiring a custom daemon or root privileges need a server model.
Match weekly backups to the amount of data loss your business can accept. For frequently changing client records, plan more frequent independent copies and restore tests.
Record the business account owner, agency technical contact and billing contact separately. When a team member or agency changes, review panel access and license ownership.
Read resources correctly
Assess storage and account counts together with CPU, RAM, how the application runs and backup needs.
A business migration inventory includes more than web files. It should also list domain records, the email provider, contact forms, analytics tools and third-party verifications.
Test forms that contact your company and email delivery in the new environment. Follow a checklist for DNS changes; verify critical pages and business connections before closing the old account.
Business migration planFor example, you can host your website here and keep using your current mail provider. The preparation below separates these two services; the target environment is verified before any DNS records change.
| Component | Check to perform | Information to add to the quote |
|---|---|---|
| Website | Test the application in the new environment; plan only the relevant web A/AAAA or CNAME destination. | Domain name, application version, data size and authorized technical contact. |
| Keep existing MX, SPF, DKIM and DMARC records; if NS records change, verify them in the new DNS zone too. | Mail provider, mailbox/alias structure and DNS administrator. | |
| Forms and business applications | Check the SMTP/API connection, sending authorization and delivery of the test message. | The sending service used and the team managing the application. |
The business approves the service owner and migration timing; the agency or software team tests application and form workflows; migration and DNS actions by the infrastructure provider are defined in the written scope.
Explore the trust centerThe business email migration guide explains archives, pilot accounts and final synchronization. For form message issues, use delivery diagnostics; a working website does not replace an email test.
Assess resources, business continuity and account management in the same table when reviewing a business hosting quote. This aligns the service accepted by the technical team with the scope recorded by purchasing.
You can scroll the table horizontally to see all columns.
| Decision area | Information to add to the quote | Handover check |
|---|---|---|
| Application and capacity | Site list, required versions, periodic data transfers and peak-hour usage. | Working applications, forms, integrations and scheduled tasks. |
| Where data is stored | Required hosting location, backup location, data types and your organization’s vendor requirements. | Verified service location and written data processing/retention scope. |
| Backup and recovery | Acceptable data loss interval, backup retention needs and authorized restore contact. | A suitable restore point, restoration method and the organization’s independent copy. |
| Security and support | Certificate management, access roles, incident communications and any custom service-level request. | Authorized access, HTTPS, support channel and a written record of responsibilities. |
| Billing and renewals | Company details, purchasing contact, billing period and license/additional service items. | Initial term total, renewal terms and service owner record. |
If you need a particular data center location, custom SLA, specific security product or certificate, include these in your quote request; achievable conditions are verified per service. The trust center and service agreement support your purchasing assessment.
Share your business requirementsThe plan name describes the intended working model and resource option. Teams managing multiple brands, agencies and individual professionals can also request a quote for a configuration that suits their needs.
No specific availability or response-time commitment is provided by default. If you have such requirements, the measurement method, service scope and applicable conditions are assessed and stated separately in the written quote.
A separate email infrastructure can be considered for heavy email usage, large archives, team calendars or specific security requirements. The right setup is determined by reviewing existing mailboxes and your workflow.
You can use separate providers for your website and email. MX and authentication records are preserved; web forms’ SMTP or API sending permissions are tested in the new environment. User licenses, shared mailboxes and archive services are assessed separately from hosting resources.
VDS may be more suitable if you need custom server software, root access, separate services or resource management beyond standard hosting. System administration and license costs should also be included in the decision.
Migration, access and scope can be planned with technical contacts authorized by the business that owns the project. The account owner, application maintenance contact and support contact should be defined from the start.
FROM SELECTION TO SETUP
Share your business needs, current infrastructure and purchasing requirements. Let’s prepare a quote with a clear scope.