A message from our CEO, René Hämmerli

When we built VELOX, a powerful ecommerce product was only half the goal. The other half was making sure it runs well for every type of customer, on every kind of cloud, without wasting money or creating operational headaches.

That meant making deliberate choices about how we manage infrastructure. Two of the most important: Infrastructure as Code and Kubernetes. Neither is new. But how you apply them matters. Here's how we think about it, and why it makes a difference for our customers.

‍

Everything is code, nothing is guesswork

In the early days of cloud, setting up a system meant logging in, clicking around, creating servers, installing software, configuring access rules, all by hand. It worked, until something broke and nobody could remember exactly what had been done. Or until you needed to replicate the setup for a new environment and had to start from scratch.

We don't work that way.

‍

Every piece of VELOX infrastructure is written as code using Terraform. That means every server, every network rule, every database connection is defined, versioned, and tracked. We know what changed, when it changed, who changed it, and why. Security policies and access controls are part of the definition, not an afterthought.

The practical result is that VELOX setups are consistent, repeatable, and auditable. When something goes wrong, we can identify the cause quickly. When a customer needs a new environment, we're not starting over — we're reusing a proven, tested baseline.

‍

Built to run anywhere

‍Not every customer wants the same cloud. Some are on AWS. Others prefer Azure. Some, especially in Switzerland and Europe, need their data to stay local, whether for GDPR, Swiss data protection law, or internal policy.

Terraform makes VELOX cloud-independent. We can deploy to public cloud, on-premise, or data-local setups using the same infrastructure definitions, customised per customer. You're not forced into our preferred setup. Instead, we adapt VELOX to your existing setup.

‍

Scale up, scale down, stay stable

VELOX is built from independent services that need to run together reliably and scale based on actual demand. Kubernetes handles this. It starts and stops services automatically based on traffic, keeps the system stable if something fails, and deploys updates without downtime.

For our customers, this means the platform handles traffic peaks without manual intervention and without over-provisioning for headroom you only need a few times a year for seasonal campaigns, flash sales, sudden growth.

‍

Cost efficiency is a design principle

Cloud costs can spiral quickly if infrastructure isn't managed carefully. We treat cost efficiency as something to architect in from the start, not optimise for later.

Specifically, we don't run unnecessary services, we implement safeguards for auto-scaling to prevent unexpected bill spikes, and we only build what each customer actually requires. Nothing more.

‍

What this means for you

Whether you're running a large established operation or scaling up quickly, the infrastructure underneath VELOX is designed to stay out of your way: stable, adaptable, and transparent about what it's doing and what it costs.

‍

If you'd like to see how this works for your specific setup, we're happy to walk you through it.