Cloud, your data centre or both
We design environments in Azure, AWS or GCP, or on your premises. We compare total costs, including migration and administration, data location requirements and dependencies on systems you already use.
Azure, AWS, your own data centre or a combination. We design infrastructure, set up deployment and monitoring, and prepare your team to manage it. We move systems into the cloud and back out.
We start with what needs to run, the load you expect and how much downtime you can accept. This guides service selection, capacity planning and cost estimates.
We design environments in Azure, AWS or GCP, or on your premises. We compare total costs, including migration and administration, data location requirements and dependencies on systems you already use.
We build Kubernetes environments in the cloud and in your data centre, and also work with OpenShift. We configure networking, storage, access and application deployment, including the update process.
We define environments in Terraform, Pulumi or platform-specific tools. We keep changes in Git and apply them through pipelines so they can be reviewed and repeated.
We map dependencies, prepare the target environment and test data transfers. Before switching over, we agree downtime, checks and a rollback procedure in case problems arise.
We configure metrics, logs and alerts for the operations team. We set up backups and verify recovery. We document procedures for common operational problems.
We establish permissions, change approval and ownership of individual services. We allocate costs by team or application so you can see what you are paying for and where usage is growing. We identify unused capacity and propose changes that account for availability and performance.
We run AI on our own GPUs and work with cloud models too. We select the environment for your solution based on its tasks, request volume, data handling and costs. The design also covers who will manage the models and infrastructure.
What we build with AI on this infrastructureWe prepare GPU servers and model deployment based on capacity needs and licence terms. We check response times and behaviour under concurrent requests.
Through an AI gateway, we configure application access to selected models, limits and usage records. We connect the rules to company identities and permissions.
We track GPU utilisation, response times and model call costs. We adjust capacity and operational limits based on actual load.
We adapt the process to your applications and operational constraints. Before the move, we agree who decides on the cutover and how we will confirm that it has succeeded.
We examine applications, data, networks and connections to other systems. We identify dependencies and constraints, availability requirements and current operating costs.
We build the target environment and verify data transfers, access and application behaviour. A trial migration establishes the time needed and the issues still to resolve.
We follow the agreed procedure and check data and application features. We prepare rollback criteria and steps in case the checks fail.
We check performance, logs, backups and costs. Your team receives documentation and practical training. We agree ongoing support and responsibilities together.

Changes to core system architecture, DevOps practices and Kubernetes deployment. Infrastructure automation and service selection with attention to costs.
What we did for O2The address service runs in AKS. GitLab and Argo CD support deployment; Grafana, Loki and Azure Monitor provide monitoring.
What we did for Packeta Bizerba Váhy a Systémy s.r.o.Product recognition runs on the device. Azure supports image data, model training, version management and monitoring.
What we did for BizerbaPlanning a migration, dealing with operational problems or preparing infrastructure for AI? We will review your current setup and propose next steps.
Tell us what costs you the most time, money or operational effort. Together, we will choose a first step and a way to measure its benefits.
info@cloudfield.czThe site does not work without strictly necessary cookies, so those are always on. Traffic and LinkedIn campaign measurement only switch on with your consent. Rejecting is as easy as allowing – no hard feelings. Privacy policy
The site does not work without them. We set just one, and it remembers what you chose in this banner.
cf_consent · cloudfield.cz · 1 year — Stores your cookie settings choice.Google Analytics shows us how many people visit the site and what they read. It does not tell us who you are.
_ga · Google · 2 years — Distinguishes visitors for traffic statistics._ga_2FE6EFFNHT · Google · 2 years — Keeps session state for Google Analytics 4.The LinkedIn Insight Tag measures whether our LinkedIn campaigns are any good. LinkedIn may link the visit to your profile while doing so.
li_sugr · LinkedIn · 3 months — Probabilistic browser identifier for campaign measurement.bcookie · LinkedIn · 1 year — Identifies the browser for LinkedIn services.lidc · LinkedIn · 1 day — Routes requests to LinkedIn's servers.UserMatchHistory · LinkedIn · 30 days — Syncs identifiers for LinkedIn advertising.AnalyticsSyncHistory · LinkedIn · 30 days — Time of the last sync with the lms_analytics cookie.li_fat_id · LinkedIn · 30 days — Attributes a site visit to a click on a LinkedIn ad.