Our engineering heritage

Every generation. Still part of the work.

Thirty years of infrastructure experience. Fifteen years of software engineering. Production AI since 2023. Each step added to the way we understand, build and operate systems today.

Explore the eras
Engineering focus
30 years / infrastructure
15 years / software
Production AI / since 2023

New capabilities, with the earlier experience still in use.

Depth over time

Six layers. Used together today.

Our work spans these six disciplines. The earlier layers remain part of the systems we build and support.

  1. Physical infrastructuresince 1990s
  2. Virtualisation & securitysince 2000s
  3. Cloud & hybridsince 2008
  4. Software engineeringsince 2011
  5. Automation & DevSecOpssince 2013
  6. Production AIsince 2023
Each bar shows when a discipline joined our work and how it continues today.

The six eras

The engineering experience behind Toltec.

1990s

Physical infrastructure

Server rooms, physical networks and Novell-to-NT migrations taught us to follow dependencies before changing a system. That habit still guides an estate review or migration: find what relies on the platform, then plan the work around it.

What this taught us

Find the dependency. Then find the fault.

2000s

Virtualisation & security

Shared platforms made identity and isolation central to the design. The same questions now apply to an application or an agent: who is acting, what can they reach, and where is the boundary? Our security engineering follows that path.

What this taught us

Design the boundary into the platform.

From 2008

Cloud & hybrid

Cloud brought more choices about where systems run and who operates them. We still weigh those choices against the workload: capacity, cost, recovery and ownership. Cloud, hybrid and on-premises designs each have a place.

What this taught us

Choose the operating model, not just the host.

From 2011

Software engineering

Building applications and APIs brought the business rules into view. Infrastructure experience helped us understand what the software needed to run. Today we use both in software delivery and integration, including changes to established applications.

What this taught us

An interface needs a contract, not an assumption.

From 2013

Automation & DevSecOps

Repeatable configuration and controlled releases made changes easier to inspect and recover. That discipline carries into our engineering standards: test the important behaviour, record the change and prepare the route back before release.

What this taught us

Automate the change. Check the result.

2023 onwards

Production AI

Since 2023, production AI has added retrieval, agents and model integration to the work. The surrounding questions remain familiar: connect the data, limit the authority, check the outcome and make recovery practical.

What this taught us

The answer is only part of the result.

That accumulated experience is useful in application modernisation: understand the old system, capture the behaviour people rely on and move it forward in tested stages.

The platforms change.
The experience stays useful.

See the sectors we work in