Hosting and environment
We select resources for applications, traffic and data storage. We check the requirements of CMS, database and services needed.
Offer / BXM Multimedia
Servers and domains Stable back of your site.
Hosting, domain, post office and technical care should create one thoughtful system. We help you select the environment for the service and plan its maintenance.
Let’s discuss your projectServers and domainsIdea → project → implementation
Customised to your company
What can we prepare?
Domains and Mail
We organize the configuration of the domain, certificate and mailboxes. We establish access owners and the responsibility for renewal.
Copies and care
We agree on the scope of updates, monitoring and backups. Also important is the way to restore data and report the problem.
Implementation and further cooperation
Quiet service facilities.
Maintenance starts with the knowledge of what works on the server and who is responsible for the response. We agree on the range of care, permissions and how to report the failure.
Inventory
Domains, Post Offices, Applications and Certificates. We organize access and renewal dates.
Copying and playing
We determine the frequency of the copies, the storage period and the method of checking data restoration.
Updates and reaction
We plan to change the environment and the rules for reporting problems. The response time comes from an agreed agreement.
Service Guide
Hosting, servers and domains: site-matched facilities
The choice of the environment depends on how the website works, integration and accessibility requirements are. We order the domain, hosting, mail and copies so that it is known who is responsible for each item.
Load and technology parameters
A simple page, portal and store have different needs. We check the software used, the size of the data, background tasks and the expected traffic. The disk capacity itself does not say whether the environment will handle the application and database efficiently.
The choice of a solution takes into account the possibility of updating, monitoring and scaling. Too extensive infrastructure increases maintenance costs and too limited obstacles to development. The starting point should be measurement and requirements, not the overall promise of unlimited resources.
Expand Subject:
Domain, DNS and Post Office Need to Order
We set the domain owner, recorder account, renewal dates and access to DNS settings. The transfer of the page does not have to mean transferring the mail. Before changing, we check all services using the domain so as not to interrupt them accidentally.
The certificate and redirection to the correct version of the address should work coherently. In case of mail, we verify the settings required by the supplier and test dispatch and reception. Access data and configuration information should be available to the authorized person on the company's side.
Expand Subject:
Migration with switchover and withdrawal plan
We prepare a copy of files and data, set up a new environment and check the operation before changing public address. The test includes a page, panel, forms, cyclical tasks and integrations. For the store we need to determine how to transfer orders created during migration.
The moment of switching we select to the way the company works. We determine how to recognize the problem and when to return to the previous environment. We do not disable the old installation before checking that the new one supports the needed functions and has working backups.
Expand Subject:
Monitoring, copies and updates after startup
Monitoring can check page availability, application errors and resource usage. The alarm should go to the person who can react. The chart itself without established responsibility does not provide maintenance of the service.
The range of copies and playback tests is adjusted to the value and pace of data changes. Updates require compliance with the application, so we plan them together with page support. The conditions for availability and response are specified in the agreed range, without universal promise of no failure.
Expand Subject:
What to check before changing hosting
You need a list of services related to the domain: website, mail, forms, cyclical tasks and integrations. We check the required versions of the software and how files are stored outside the main directory. The omitted item may not be revealed until a few days after the task is performed less frequently.
We also set the size of the copy, the time it is played and the way the data is verified. The test account allows you to pass the most important functions before switching. After migration we check the certificate, server answers and mail independently. The fact that the main page is displayed does not yet confirm the proper operation of the entire environment.
Good start.
From Chatting
to a particular plan.
We set the goal, scope and way of receiving the work. We develop the project on the basis of agreed needs and materials.
See our realizationsWhat is worth preparing for the conversation?
- Page address and used CMS
- Hosting, domain and mail information
- Current problems and expected scope of care
You don't have to have the specifications in place, and we'll work out the most important decisions together.
Before the first conversation
It's worth knowing.
Will you move the existing site?
First we will check the technology, access to files and database and the conditions of current hosting. On this basis, we will determine the extent of migration, testing and switching time.
Which server parameters to choose?
They depend on CMS, the number of users, file size and integration. Selection starts with the actual requirements of the service, not one configuration for all.
What does technical care include?
The scope is determined for a specific project: it may concern updates, copies, monitoring and handling of applications. Before cooperation we define the responsibility and way of contact.
What does server care include?
The scope may include monitoring of availability, copies, updates and handling of applications. You need to specify separately the mail, application administration and response time. Hosting itself does not mean full care of the site.
Your next step
Quiet service facilities.
Maintenance starts with the knowledge of what works on the server and who is responsible for the response. We agree on the range of care, permissions and how to report the failure.
Let's start with your idea.
Write a few sentences about the project or call me.