What Our Cloud Infrastructure Services Include
- Architecture: choosing the services your project will run on, such as virtual machines or containers, a managed database, file storage and network access, and separating production from staging.
- Migration from your own or rented servers, in stages, with checks at every step and the option to roll back.
- Azure setup for ASP.NET Core projects and for companies already using Microsoft services and accounts.
- Autoscaling that adds resources during peak load and scales down in quiet hours.
- Cost control: budgets and alerts, resource tagging by project, and regular cleanup of forgotten test servers, disks and snapshots.
- Security setup: least-privilege access, two-factor authentication, no direct internet access to databases and storage, encryption and backups.
Infrastructure is defined as code, for example in Terraform, so it can be reproduced, reviewed and changed without manual console tweaks.
Who the Cloud Is For, and Who Should Stay on a Server
The cloud delivers the most value to online services and apps with fast or uneven growth, ecommerce stores with sharp seasonal peaks, companies with several connected systems that need separate staging environments, and projects with high availability requirements.
For a corporate website or a small store with steady traffic, a rented server with good administration is often the better deal, and the cloud would only make infrastructure more complex and more expensive. We say so upfront and run the numbers on both options.
Azure, AWS or Google Cloud
The major platforms offer a similar set of core capabilities. Microsoft Azure is usually the most convenient choice if your company already uses Microsoft products and single sign-on corporate accounts, and your applications are written in C#. AWS and Google Cloud are often chosen when the team already has experience with them, specific services are needed (for example, analytics on BigQuery), or there are attractive startup programs. We choose the platform based on your needs, not our own preferences.
How Cloud Migration Works
We migrate in stages so your business doesn't notice any disruption on the site.
- We inventory what currently runs on your servers and how the parts connect.
- We build the new cloud infrastructure alongside the existing one.
- We migrate a copy of the data and test the application on it.
- We schedule the cutover for the lowest-traffic window, move the latest data and update DNS settings.
- We keep the old system on standby until we are sure everything runs reliably.
Sometimes it makes sense not to move everything at once, but to start with individual pieces such as file storage or backups.
What to Prepare on Your Side
- Access to your current servers and, if you have one, your cloud account.
- Traffic details: how many visitors, when the peak periods are and how fast the project is growing.
- Data residency requirements, if your industry has any.
- A rough infrastructure budget so we can propose a realistic solution.
What Affects the Cost
- Project complexity: one website or many services, databases and integrations.
- The volume of data to migrate and cutover time requirements.
- Reliability requirements: one zone or several, database redundancy, separate staging environments.
- Engagement model: one-time design and migration or ongoing infrastructure management.
You pay the cloud provider directly for cloud resources, and we break down our own work separately.
Frequently asked questions
Is the cloud always more expensive? Not always. For projects with uneven traffic, the cloud is often cheaper. For steady traffic, a rented server may cost less. We'll run the numbers on both options.
Can we combine the cloud with a regular server? Yes. For example, the website runs on a rented server, while backups, files or individual services live in the cloud.
Will we remain the owners of the infrastructure? Yes. We recommend registering the cloud account to your company and granting us limited-permission access that you can revoke at any time.
Do we need to rewrite the application for the cloud? In most cases, no. Most websites migrate without code changes. Some rework is needed if you want to take full advantage of the cloud, such as autoscaling.
How do you keep our cloud bill under control? We set up budgets and alerts, tag resources so you can see what costs what, and regularly look for resources you are still paying for but no longer use.
Can you take over an existing Azure account that has grown messy? Yes. We start by reviewing what runs there, who has access and what it costs, then propose cleanup and changes in stages.
Why Promodex
Promodex has built websites and online services since 2015, so cloud infrastructure is designed around what the application actually needs: where it will slow down, what matters most in it and how it will grow. The work stays with our in-house team and is never outsourced. You see both the provider's bill and a breakdown of our work, and you make the spending decisions.