Your country & currency

Make yourself at home. Choose your preferred shopping currency.

Your selected country opens its KickHost website. Your shopping currency is saved. Visit country website .

PLAN YOUR DEPLOYMENT

Hosting deployment requirements.

Check your application before you order. List the runtime, database, build commands and background services your application needs. Use this checklist to compare hosting environments and prepare a practical deployment discussion.

Developer checking PHP version, database, memory, storage and cron requirements before ordering hosting
Deployment RequirementsPlan the environment before you order.

START WITH WHAT YOU KNOW

The requirements come first.
The server follows.

A first deployment, a growing application and a project being moved from another host each arrive with different demands. Working through the software, activity and responsibilities first makes the hosting conversation shorter and the environment more accurate. You do not need every answer ready; a clear outline is enough to begin.

WHAT TO BRING

Three areas.
A complete picture.

Share as much as you already know. Anything missing can be worked through with our team before you order.

REQUIREMENTS AREA

Your application stack

Describe what will run, not only the language it is written in. Versions, databases and services shape the environment as much as the code does.

  • Runtime, language and framework versions
  • Database, storage and file handling
  • Build steps, integrations and background services
Review developer hosting

REQUIREMENTS AREA

Capacity and activity

Estimate how the project will be used so resources can be sized with the workload in view.

  • Expected visitors and concurrent activity
  • Scheduled jobs, webhooks and API traffic
  • Storage growth, media and retention
Explore Performance VPS

REQUIREMENTS AREA

Operations and responsibilities

Decide who looks after what before launch. Clear responsibilities make the ongoing cost of a project easier to assess.

  • Access, accounts and administration
  • Updates, backups and monitoring
  • Licences and third-party services
Discuss management scope

Requirements differ by project. The environment, resources, service scope, licences, availability and price for your deployment are confirmed by our team before any order is placed. No specific hardware is implied unless explicitly included in your proposal.

Business owner and solutions engineer discussing a one-page project brief
DEPLOYMENT BRIEFAlign stack, traffic & supportRuntime versionDatabase sizeManagement scope

THE BRIEF MAKES THE DIFFERENCE

A short brief.
A better proposal.

Include runtime and framework versions, the database behind the application, expected activity, storage growth and any services you depend on. Note who will maintain the project after launch and which responsibilities should sit with your hosting provider. The clearer the outline, the more precisely the environment, scope and full cost can be reviewed with you.

Send my requirements

SEE YOUR NEXT MOVE

Where are you starting from?

01

A first deployment

Bring your software, audience and launch expectations together so the first environment is shaped around the project, not the other way round.

02

A project being moved

Document the current setup, data and dependencies, then agree backups, testing and DNS changes before anything moves.

03

A client or team rollout

Settle access, maintenance duties and support expectations so everyone involved understands where responsibility sits.

FROM REQUIREMENTS TO RELEASE

A good launch starts
with a practical plan.

Bring us the application, the audience and the outcome. We will help you work through the environment before you commit.

Explore hosting locations
  1. List the stack

    Runtimes, databases, integrations, background services and expected activity.

  2. Confirm the environment

    Resources, location, access, licences, backups and management scope.

  3. Agree the launch plan

    Installation, migration, testing, DNS changes and responsibilities.

GOOD QUESTIONS. CLEAR ANSWERS.

Hosting deployment requirements questions, answered.

Let’s find the right starting point for your workload.

Ask our team →
Questions, answered
What should a deployment brief include?
Note your software and versions, database, expected activity, storage needs, integrations and who will maintain the project. Anything you are unsure of can be worked through with our team.
Which server configuration do I need?
Requirements vary by workload. Share your stack and activity and we will discuss an appropriate route, then confirm the exact resources, availability and price before you order.
Can you review requirements before I order?
Yes. Send your requirements through the contact form and our team will review the environment, service scope and complete price with you before any order is placed.
Is management included?
Management is agreed separately. Confirm who installs and updates the operating system, application and supporting services, and who handles monitoring, backups and incidents.
Can you move an existing project?
Share your current setup so we can review the move. Agree backups, data transfer, testing, any IP or DNS changes and the expected service impact before starting.
Where will my service be hosted?
Review the available locations for your selected product with our team, then confirm the region before ordering.

Your next deployment.
Planned with care.

Talk about my requirements

Keep exploring: Cloud servers · Data centres · Developer hosting

TALK TO KICKHOST

Tell us about your project.

Share a few details and our team will reply by email. For account or technical support, please open a ticket in your client area so you can track the conversation securely.

We’ll use these details to respond to your enquiry. See our Privacy Policy. Please do not include passwords, payment card details or other sensitive account credentials.