Hosting for web applications that require an environment compatible with Laravel or Node.js. Start by identifying your application’s requirements before selecting a plan.
This category provides hosting for Laravel or Node.js applications within the features of the selected plan. Requirements depend on your application’s versions, runtime, databases and background tasks.
| Application type | Information to prepare |
|---|---|
| Laravel | Laravel and PHP versions, required extensions, database type, and any Composer, scheduled task or queue requirements. |
| Node.js | Node.js version, installation, build and start commands, the application entry point, and any persistent process or WebSocket requirements. |
Ask the team whether your chosen plan supports the application’s needs, particularly versions, permissions and services not listed on the plan page.
A description of your requirements is enough for the initial assessment. Do not include passwords or API keys in a general enquiry.
Open the Laravel and Node.js plans and compare storage, databases, website allowances and resources with your requirements. Ask the team about any required feature that is not listed, then order the appropriate plan.
At the service period step, choose an available billing period that suits you, such as monthly or annual billing. Review the amount for the full period, then select Continue.
An advertised monthly equivalent may apply to a longer subscription. Check the subscription length and total amount due, and review any discount and renewal conditions attached to the offer.
At the domain selection step, choose the option that matches your situation:
| Your situation | Option to choose | What to do |
|---|---|---|
| You need a new domain | Register a new domain | Enter the name and extension, then check availability. Choose an available name, review its fees, and complete the options shown. |
| You already own a domain | Use an existing domain | Enter the correct domain and select the option to use it. Connect it to the service using the activation instructions. |
Enter only the domain name, such as example.com, without https:// or a page path. Check its spelling and extension: a single different character can identify a different domain.
Entering an existing domain does not automatically migrate website files or email. Coordinate migration and connection, and use the DNS settings supplied for your service in its activation instructions or by support. Preserve the records needed for existing email and other services.
An additional services step may offer options such as backups or managed hosting. Read each option’s description and price. Leave unwanted options unselected, or choose the option to decline them where shown, then select Continue.
Seeing a backup option during checkout does not mean every plan includes backups automatically. Refer to your plan description and the add-ons you select.
If you select a management service, agree on who handles deployment, updates, database migration and application follow-up, and which tasks remain with your development team.
Before continuing, review the cart: the service or plan, domain, billing period, add-ons, currency, and any discount or tax. Use the final total shown, and check renewal charges separately from the introductory offer.
Contact support with the invoice number and transaction reference before paying again, so the result of the first attempt can be confirmed.
For help, open Support Requests using the account linked to your service, or use the Contact page if you cannot sign in. Include the service, domain and order or invoice number, then describe the problem, when it started, and the error message.
Add updates to the same request. Attach a clear screenshot if helpful, hiding passwords, verification codes and payment details. Track the service, domain and add-on renewal dates separately, and keep your contact email up to date to receive notices.
For technical support, include the application type, versions and the step where the error occurs. Add a relevant error excerpt with secrets removed. Ask whether the issue requires a hosting configuration change or an application code change.
Do not assume this. Review the permissions provided by the plan and confirm that your deployment method is supported before paying.
Confirm your required versions with the team. The hosting category does not imply support for every version or library.
Coverage depends on the service description and agreement. Clarify management, deployment and support responsibilities before selecting add-ons.
Ready for the next step?
View Laravel & Node.js Plans
Yemen (AR)
Worldwide (English)
