Software operations you can count on.

Sandro Brandt

Project Manager

+41.. Show number

Expert knowledge for your project

Sandro Brandt studied electrical engineering at HSR and works as a project manager at soxes. His technical understanding and his intuition for people make him a reliable link between customer expectations and implementation. He ensures clarity, structure, and good cooperation.

It’s only when an incident occurs that you can truly gauge how secure your business really is

As your software becomes increasingly important to your business, you hardly notice it in your day-to-day operations. It’s only when something stops working as usual that questions arise that were never asked before. Who is responsible? Where does the problem originate? How quickly can the situation be assessed?

Systems that have evolved over the years provide stability. At the same time, they ensure that knowledge remains with individual people, responsibilities aren’t clearly defined, and connections become hard to trace. As long as everything is running smoothly, this goes unnoticed. When a problem arises, you suddenly lose the big picture.

Are you interested in how your software works? Then select the section that best fits your situation and get started there.

/1.1 DevOps
This might be of interest to your company if releases are causing too much stress these days, or if operations and development aren't on the same page.
/1.2 Cloud Computing
You've come to the right place if your performance is inconsistent, scaling is unpredictable, or deployments and environments aren't properly automated.
/1.3 Operational transparency
This is important if you notice problems too late, spend too much time trying to find the cause, or no one can say for sure why there’s a fire right now.
/1.4 Dependencies, Risks, and SLAs
Visit this page if you want to reduce risks but lack a clear understanding of operational risks and responsibilities.
/1.5 Knowledge Ownership
Click here if your business relies on a few key individuals and your team lacks the capacity to handle both operational issues and business development at the same time.
/1.6 Security & Backup
This is relevant for your business if recovery objectives are unclear or if the restore process has never been tested under realistic conditions.

Typical signs that action is needed

Outages last too long because the causes and interdependencies are unclear
Releases have a greater impact on operations than expected
SLAs are defined but cannot be measured or controlled
Third-party systems affect operations without clear accountability
Operations depend on individuals or external partners
Restore has not been tested or verified

This is how we take responsibility in our operations

Analyze. Stabilize. Operate. These three phases are part of our structured approach. The goal is not only stability, but also the genuine assumption of responsibility for operations and further development.

Phase 1: Analyze

In the first phase, we gain a thorough understanding of your system so that we can operate, further develop, and secure it independently.

What we do specifically

Identifying dependencies, risks, and operational bottlenecks
Analyzing observability, alerting, and operational processes
Documenting architecture, interfaces, and critical workflows
Identifying quick wins with immediate impact

Result
A clear basis for decision-making, prioritized measures, and the ability to take ownership.

Phase 2: Stabilize

Based on the analysis, we make operations resilient and reduce the greatest risks.

What we do specifically

Close critical gaps in operations and architecture
Establishing clear operational processes
Improving alert quality and operational transparency
Define restore procedures and recovery objectives
Prepare potential modernization steps, if necessary

Result:
A system that runs stably and is prepared for disruptions.

Phase 3: Operation

In the final phase, we take over day-to-day operations with clearly defined responsibilities.

What we do specifically

Operation with clearly defined SLAs and responsibilities
Measurable operations with KPIs, SLOs, and reviews
Ensuring knowledge transfer, handover, and coverage
Continuous improvement instead of mere troubleshooting
Restore and emergency response as a well-practiced routine

Result
Stable operations, predictable development, and a partner who takes responsibility.

What changes are taking place in your processes?

Fewer disruptions and shorter downtime
Greater transparency and improved decision-making
Less reliance on individuals
Predictable releases without surprises
Long-term security for operations and further development

Who is our business approach best suited for?

SMEs with mission-critical software

Companies with legacy systems

Organizations with distributed knowledge

Teams without clear operational responsibilities

DevOps

Cloud Computing

Operational transparency

Dependencies, Risks, and SLAs

Knowledge Ownership

Security & Backups

Digitalization and

Individual Software

Software operations you can count on.

Contents

It’s only when an incident occurs that you can truly gauge how secure your business really is

Are you interested in how your software works? Then select the section that best fits your situation and get started there.

Typical signs that action is needed

Outages last too long because the causes and interdependencies are unclear

Releases have a greater impact on operations than expected

SLAs are defined but cannot be measured or controlled

Third-party systems affect operations without clear accountability

Operations depend on individuals or external partners

Restore has not been tested or verified

This is how we take responsibility in our operations

Phase 1: Analyze

Phase 2: Stabilize

Phase 3: Operation

What changes are taking place in your processes?

Who is our business approach best suited for?

SMEs with mission-critical software

Companies with legacy systems

Organizations with distributed knowledge

Teams without clear operational responsibilities

Trusted by Leading Brands

This might interest you

Do you have any questions? Would you like to find out more about our services?
We look forward to your enquiry.

Top Rated Service

Digitalization and

Individual Software

Software operations you can count on.

Contents

It’s only when an incident occurs that you can truly gauge how secure your business really is

Are you interested in how your software works? Then select the section that best fits your situation and get started there.

Typical signs that action is needed

Outages last too long because the causes and interdependencies are unclear

Releases have a greater impact on operations than expected

SLAs are defined but cannot be measured or controlled

Third-party systems affect operations without clear accountability

Operations depend on individuals or external partners

Restore has not been tested or verified

This is how we take responsibility in our operations

Phase 1: Analyze

Phase 2: Stabilize

Phase 3: Operation

What changes are taking place in your processes?

Who is our business approach best suited for?

SMEs with mission-critical software

Companies with legacy systems

Organizations with distributed knowledge

Teams without clear operational responsibilities

Trusted by Leading Brands

This might interest you

Do you have any questions? Would you like to find out more about our services? We look forward to your enquiry.

Top Rated Service

Your request

Do you have any questions? Would you like to find out more about our services?
We look forward to your enquiry.