Cloud migration for Swiss companies: architecture, phased migration, CI/CD and operations. Data residency in Switzerland or the EU, in contract.
The migration is rarely the problem. What comes after — cost, provability, dependency — decides whether the move was worth it.
Nobody can explain what the increase pays for. Resources keep running because nobody dares to switch them off.
Releases happen manually, outside business hours, with a rollback plan in someone's head instead of a script. So they happen rarely.
A customer or auditor asks for the storage location — and the answer requires a support ticket to your provider. For regulated industries that's a dealbreaker.
The architecture depends on one provider's proprietary services. Switching would be a rebuild — which weakens your position at every contract renewal.
Permissions have grown historically, secrets sit in config files, and the last penetration test was two years ago.
No defined on-call, no runbook, no recovery time anyone has signed off. In an incident, everyone improvises.
From the first assessment to ongoing operations. Each focus area can be engaged on its own — or as the whole journey.
Migration to AWS, Azure or GCP with a plan that defines the way back first. We migrate workload by workload instead of in one leap — every step individually verifiable, every step individually reversible.
AWS · Azure · GCP · Exoscale · Infomaniak · Terraform
Infrastructure as versioned code instead of console configuration that grew over time. Every environment reproducible, every change traceable — the foundation of any serious audit.
Terraform · Pulumi · Kubernetes · Vault · CSPM · OPA
Delivery becomes routine instead of an event. We automate the path from commit to production and give your developers a platform where they reach infrastructure without filing a ticket.
GitHub Actions · GitLab CI · ArgoCD · Prometheus · Grafana · OpenTelemetry
Ongoing operations when you don't want to build a platform team of your own. Monitoring, patching and cost control as a service — with agreed response times instead of best intentions.
Datadog · PagerDuty · Grafana Cloud · AWS Cost Explorer · Azure Cost Management
Moving everything at once sounds faster and rarely is. We migrate in small waves with a defined rollback plan — the business keeps running through the entire transition.
We map workloads, dependencies, costs and regulatory requirements. The result is a chart with effort and risk per workload — not a blanket recommendation.
Account and network structure, access model, data locations and cost centres are set up before the first workload moves.
Workloads move in small waves, each with a test run, a cutover window and a rollback plan. The business stays available throughout the migration.
After the move we take over monitoring, patching and cost optimization — or hand over to your team, runbook and onboarding included.
Four things that are different after a clean cloud and DevOps setup.
Resources are mapped to cost centres and idle capacity becomes visible. You get a monthly cost report your finance team can actually follow.
Automated pipelines with tests and rollback move deployments into the working day. Smaller changes mean smaller risks.
You can tell a customer, an auditor or a regulator in writing which region holds which data and who can access it.
Monitoring, alerting, on-call and runbooks are established and rehearsed. Recovery time is an agreement, not a hope.
We'll review cost structure, data locations and delivery pipeline and name the three biggest levers — no obligation, no sales pressure.
Request an assessmentPalisis of Switzerland is our strongest European reference — here is the infrastructure and security side of the project.
In cloud engagements the critical question isn't IP, it's dependency. So we settle it first.
We build on Kubernetes, Terraform and open standards. Managed services are used deliberately, with a documented replacement path. Switching stays a decision, not a rebuild.
Operations in Swiss regions (Zurich, Geneva) or EU regions — including Swiss providers such as Exoscale and Infomaniak where the requirement goes beyond the EU.
Infrastructure as code, logged access and versioned changes. ISO 27001 and ISO 9001 certified, SOC 2 Type II audited.
The cloud accounts run in your name and your contractual relationship. We work inside them with assigned permissions — and when the engagement ends, you revoke the access.
We're tied to no hyperscaler and take no reseller margins. The recommendation follows your requirements on data location, cost and existing know-how.
The points that come up in every procurement process — answered up front.
Yes. AWS, Azure and GCP operate Swiss regions (Zurich, Geneva); we also work with Swiss providers such as Exoscale and Infomaniak. Which data lives where is recorded in the operations handbook, so you can prove it to customers and regulators. Data processing is governed under revDSG and GDPR.
By making portability an architecture decision: containers instead of provider-specific runtimes, Terraform instead of console clicks, open data formats. We use managed services where they bring clear value — but with a documented replacement path, so a switch stays a calculable move.
Cloud costs run directly through your own accounts — you see them unfiltered and we add no margin. Our work is billed separately: a project price for migration and build-out, a monthly flat rate for managed operations, in CHF or EUR and cancellable quarterly.
Both are possible, and we recommend deciding only after the assessment. If you have a platform team, we build the platform and hand it over with a runbook and onboarding. If you don't, we operate it — with the option to hand over later.
Response times are agreed in the service contract and tiered by severity, with round-the-clock on-call through the teams in Udaipur and Pune. We deliberately quote times we can hold at 3 a.m. — not the shortest number that reads well.
