E-commerce.
Ready when the campaign takes off.

Storefronts that scale for sale days, product media in object storage, and shopper data that stays in Frankfurt.

What changes.
From scramble to headroom.

TodayOn enum

Sales, drops and campaigns spike traffic

Workloads scale horizontally; node pools are sized for your peak

Product images outgrow ad-hoc storage

S3-compatible object storage in Frankfurt, no fees for API requests

Shopper data has to stay under GDPR

Compute, storage and networking run in Frankfurt

Checkout must not go down when the ads work

A highly available control plane with a 99.9% availability target

How shops run on enum.
From catalog to campaign day.

01

Put media in object storage

Product images, feeds and backups in S3-compatible buckets, with your CDN or image pipeline in front.

02

Run the shop on Kubernetes

Storefront, APIs and workers on Kubernetes. Add replicas when the campaign lands.

03

Keep checkout separate

Separate node pools behind their own load balancer keep checkout apart from browsing.

What you run it on.

PeaksRollout peaks absorbed automatically, on enum in Frankfurt.Read the story

Questions.
About e-commerce on enum.

Can enum handle sale-day peaks?

Workloads scale horizontally with demand. You size node pools for your peak, and the control plane is highly available with a 99.9% availability target.

Where should product images live?

In enum Object Storage: S3-compatible and in Frankfurt. Most teams put their CDN or image pipeline in front of the buckets.

Does shopper data stay in the EU?

Yes. Compute, storage and networking for your shop run in Frankfurt under German and EU law.

How is seasonal traffic priced?

You pay per resource in euros. Scale up for the campaign and down afterwards; one- to three-year commitments are optional.

Planning your next peak?
Let's size it together.

Tell us about your traffic and your catalog. We help you plan the capacity.