Simulation and engineering

Know before you build.

Simulate the line, the building, the crowd or the product before you spend on it. And when your product needs software that is simply faster than anyone else's, we write that too.

You know the feeling.

The decision costs more than a year of profit, and everyone in the room is guessing. The new line might bottleneck at station four. The venue might not clear in time. The product might not survive the drop. You can find out after it's built, or you can find out now.

What changes

01

The expensive question is answered first

Run the line, the building or the crowd on a screen, change one thing, run it again.

02

The answer is checked against reality

Every simulation is validated against measured data, with the error stated.

03

It runs where your people are

In a browser tab, at near-native speed, with nothing to install.

04

Your product gets faster than the competition

Engine modules, services and tools written in the languages built for speed.

05

It survives the big day

Everything we run is tested at ten times the expected peak.

What you get

01

Process and line simulation

Work flowing through a factory, warehouse or hospital, with the bottleneck found before it exists.

02

Crowd and traffic simulation

People and vehicles through a venue, a station or a district, for planning and safety.

03

Physics and product simulation

Rigid bodies, fluids and materials, for design and testing.

04

Engineering tools

Solvers, optimisers and analysis tools for your engineering team, documented and checked.

05

Heavy computation in the browser

C++ and Rust compiled to run in a tab, so the tool reaches everyone.

06

Services that stay flat under load

Queues, workers and APIs that keep their speed when the traffic arrives.

Three ways this goes

01

A bottling plant in Nashik

A new line planned on a spreadsheet. The simulation found the bottleneck at the labeller before the order was placed, and the layout changed on paper instead of on the floor.

02

A stadium operator in Manchester

Egress times were a guess. The crowd simulation showed which gates to open first, and the plan went to the safety authority with numbers.

03

A hardware start-up in San Jose

A browser-based design tool that was too slow to use. The core recompiled to WebAssembly ran twenty times faster, and the product shipped.

How it works

01

The question

What decision this must inform, and what accuracy it needs. Set as a number.

02

The prototype

Two weeks: the model running on your real data, with the first answer.

03

Validation

Checked against measured data and a reference implementation. The error written down.

04

Delivery

A tool your team runs, with documentation an engineer can follow.

05

Run

Updates as your system changes, with a named engineer.

Proof you can check

Every simulation we deliver comes with its validation: the measured data, the model's result and the gap between them. If we can't show the gap, we don't ship it.

Built with C++, Rust and Go, WebAssembly and SIMD, CUDA where it earns it, PostgreSQL.

Questions buyers ask

How accurate is a simulation?

As accurate as the data and the model allow, and we tell you the number. A validated line model is usually within a few percent of the real throughput.

How long does it take?

A first answer in two weeks. A validated tool your team runs in four to eight.

Can it run in a browser?

Yes. Heavy code compiled to WebAssembly runs at near-native speed in a tab.

Do you work with our engineering software?

Yes: file formats, APIs and plug-ins for the tools you already use.

Who owns it?

You do, with the source and the documentation.

Tell us what you need built.

An engineer reads it and replies within minutes, in your language. Every project starts with a two-week prototype at a flat price.

Simulation software and high-performance engineering — know before you build — eORB