About

CompanyTorus

A small team of engineers who got tired of being paged at night.

We build Torus so infrastructure can look after itself, and people can look after the product.

7: Years running infrastructure, from Amsterdam
48: Engineers and designers
640: Teams running on Torus
11: Regions worldwide

Process

003Torus

Four steps from the first call to a stack that runs itself.

Most teams are live within two weeks.

How it works

Step 1 - Connect

Torus reads your cloud accounts, clusters and pipelines through read-only keys. Nothing changes yet, we only listen.

Step 2 - Map

In a few days Torus learns what a normal Tuesday looks like for every service, queue and database you run.

Step 3 - Tune

We switch on fixes one group at a time. You approve each rule once, then Torus applies it whenever it is needed.

Step 4 - Guard

Lattice Guard watches access and patches around the clock and learns from every attempt it blocks.

See the four steps run on a copy of your stack.

20^min

Average connection time

4^days

Average learning time

38^%

Fewer pages in month one

9^sec

Average threat response

Book a demo

Team

007Torus

The engineers behind Torus. Builders, operators, fixers.

We have all carried the pager. Torus is the tool we wanted then.

Torus team

Ada Varela

Co-founder, CEO

I spent ten years running infrastructure for payment companies, mostly at three in the morning. I started Torus so the next generation of engineers can sleep through the night while their systems quietly fix themselves.

Bastian Castellane

Co-founder, CTO

I lead the model that sits at the heart of Torus Core. My job is to make sure it learns fast, explains every decision it makes and never touches anything it does not fully understand.

in

Clients

008Torus

Teams that stopped firefighting and started shipping.

Short stories from people who run Torus every day.

**Matteo Ruskin**Head of PlatformNorthwell Pay

Reviews

Work with us