§00
engineering · managed services

built for the worst case

Counting down to 03:14:07 UTC on 19 January 2038, when the signed 32-bit Unix clock overflows.

A firm for the failure modes other shops treat as someone else's problem.

§01
two practices

one discipline, two ways to hire it

the code you ship and the systems you run on fail the same way: at the boundary. we work both.

01 / 02

edge-case engineering

For software teams. We find the failure modes in your code before production does: the boundaries, the clocks, the limits, and the paths nobody tested.

  • 01overflow & boundary conditions
  • 02resilience & failure modes
  • 03time, dates & the long horizon
  • 04audits of the cases others skip
02 / 02

managed services

For organizations that run on their technology. We take over the day-to-day IT, from the helpdesk to the backups, and plan for the bad day before it arrives.

  • 01helpdesk & end-user support
  • 02network & server management
  • 03backup & disaster recovery
  • 04cybersecurity & monitoring
  • 05cloud, email & identity
  • 06strategy & planning
§02
why 2038

a deadline deferred

03:14:07 UTC · 19 Jan 2038

The signed 32-bit counter that has tracked Unix time since 1970 reaches its maximum. A small, certain, well-documented catastrophe, waiting on a known date; the kind of problem the industry prefers not to think about. We named the firm after it.

signed int32 · unix time_tcounting
2147483647
seconds elapsed since 1 january 1970, approaching the signed 32-bit ceiling.
§03
closing

someone has to be there when the numbers run out

Whether it is the code you ship or the systems your organization runs on, start with the part you would rather not think about.

2038.systems
worst-case // rev.2038