Skip to content
Language
DE EN FR
Start a project

From project to running platform

Go-live is not an end but a transition. We take your platform into production in a controlled way and support it in operations over the long term, with the same team that built it.

The illustration shows five containers going into operation one after another and taking on the accent colour; below them runs a steady operations line with the current state highlighted.

Starting point

Acceptance with a system, not under pressure

Before your platform goes live, your key users check in acceptance testing, under real conditions, whether their business processes work in the platform.

Abstract graphic: four parallel green tracks of light running through a shared bottleneck.

Test scenarios

Prepared together, covering your most important processes.

Abstract graphic: two identical cyan line frameworks side by side, the right one fainter.

Realistic data

A test environment that matches production.

Abstract graphic: a violet scale with evenly spaced marks, one of them clearly highlighted.

Clear criteria

Defined in advance: when a test counts as passed.

Abstract graphic: scattered yellow points of light on the left, the same points in an orderly row on the right.

Findings recorded traceably

Whatever comes up during testing reaches us via the service desk or a test log. We review every finding, prioritise it and implement it.

Controlled deployment

Your go-live without surprises

The go-live follows an agreed checklist: no surprises on the day.

Go-live checklist

DNS configuration, SSL certificates, monitoring, backup strategy, rollback plan. Every item is verified before the switch is flipped.

Data migration

If existing data has to be migrated, this happens in a tested process with validation. A trial migration before go-live uncovers problems early.

Training on request

On request, we train editors, administrators and power users before go-live so that your team can use the platform independently. Training is not included in the project and is quoted separately.

Rollback plan as a safety net

In the unlikely event that something goes wrong at go-live, there is a documented rollback plan. Safety before speed, always.

Closer support

The first months deserve attention

In the first months after go-live, our team monitors the platform especially closely and fixes critical findings immediately.

The goal: a platform that runs as stably in everyday use as in the test environment.

  • 1 to 3 months: the typical duration of closer support after go-live.
  • Shorter response times: your project is prioritised during this phase.
  • Intensive monitoring: performance, error rates and user behaviour under close watch.
Operations view in the cloudtec Stack during the rollout of a customer portal: response time, error rate and active users at a glance, with findings per day falling. A critical finding with an upload in a form was detected by monitoring and fixed after 38 minutes. Closer support is in week 2 of 4, with prioritised response times.

We operate what we build

After go-live, your platform needs ongoing care, maintenance and further development. We take this on as a service of its own: Operations & cloud.

Hosting in the Swiss VDC

Your platform runs on our virtual servers in the Swiss Virtual Data Center. Certified to ISO/IEC 27001, with redundant infrastructure and round-the-clock monitoring.

Maintenance & updates

Security patches, framework updates and dependency maintenance. We keep your platform up to date so that it stays secure and stable for years.

Monitoring & incident resolution

Proactive monitoring of performance, availability and errors. When incidents occur, defined processes kick in: you are informed before you notice it yourself.

Further development

New features, adjustments, integrations: the team that built your platform operates it and develops it further. Whoever writes the code also carries responsibility in operations.

Debriefing

Learning from every project

After go-live we hold a structured debriefing, internally and, if you wish, together with you. What went well? What will we improve next time? Where was there friction?

This reflection is how we develop our methodology further: the insights feed directly into our processes.

  • What went well: we record what has proven itself in writing.
  • What we improve: concrete measures instead of general intentions.
  • Where there was friction: uncomfortable points are put on the table too.
A debrief in the cloudtec Stack after go-live, with three columns: what went well, what we improve and where there was friction. In front of it, an agreed action to plan training from phase 3 in future, and the list of how the insight flows into the methodology.

Thinking about operations from day one

Let’s discuss how your platform will run stably over the long term after go-live.