IaaS

Infrastructure as a Sacrifice

Bare-metal, virtualised, or "borrowed" servers, provisioned by whichever troop member found a spare rack. Redundancy is achieved through hope and a second banana.

SLA: best effort, effort not guaranteed

PaaS

Panic as a Service

A fully managed platform layer that automatically pages your on-call engineer at 3am for reasons that resolve themselves by 9am, right before the retro.

Incident response: vibes-based

SaaS

Stress as a Service

A subscription product that does exactly what the last vendor's did, but the login button has moved, and support now only responds in Pascal.

Cancel anytime, we will not process it

DaaS

Dreams as a Service

Our flagship offering. Development happens entirely within the dreams of our developers, before the ticket is written, before the meeting is scheduled, before the problem exists.

Standup occurs during REM sleep

VPS

Very Poor Support

A dedicated virtual server paired with a support contract that guarantees a response, but never a solution, and definitely never in your timezone.

Ticket status: "looking into it" (2019–present)

HOSTING

Artisanal Bare-Metal Hosting

Your production environment, hosted on a rack in a shed behind our CTO's house in Auckland. Cooling is provided by an open window and low expectations.

Uptime affected by rugby, rain, and rats

THE DEVOOOPS METHODOLOGY

Shift Far Left: development before the problem exists.

Everyone shifts testing left. We went further. Our engineers now write the code in their sleep, the night before the client even has the idea. By the time you send the brief, it's already three sprints behind.

A monkey presenting a Q4 Banana Growth Index chart at a podium to a seated audience of monkeys
Fig. 3 — Q3 roadmap, reverse-engineered from a dream Photography: authentic, unfortunately
  • Requirements gathered after delivery, for accuracy
  • Architecture decided by whichever monkey grabs the marker first
  • Code reviewed by the same monkey who wrote it, generously
  • Testing performed live, in production, on your busiest day
  • Retrospectives held, conclusions ignored, repeat
TECHNOLOGY WE REFUSE TO ABANDON

Our stack, and why we're proud of it.

Every other consultancy chases the latest framework. We chase nothing. We have already arrived, decades ago, and we are not leaving.

Brainfuck

Eight symbols. Zero readability. Every one of our microservices is written in it, on principle, and partly because we've forgotten how to stop.

Pascal

Structured, verbose, and never once asked to leave the building. Our fintech add-ons are quietly powered by BEGIN/END blocks from 1987.

Arch Linux

Every server, laptop, and load balancer. We use Arch. We will tell you, unprompted, in every meeting.

COBOL

For "modern" fintech integrations. It has outlived three CEOs and will outlive this website.

INTERCAL

The only language that requires you to say PLEASE. Our support team could learn from it.

ed

We resolved the vi-versus-emacs war internally by refusing both and standardising on the one editor with no visible mode at all.

Tabs, resolved via combat

Spaces advocates are welcome to apply. Historically, they do not last the quarter.

Malbolge (staging only)

We tried it once. Nobody, including the compiler, understood what happened. It's still running.

Not sure which "-aaS" is right for you?

Neither are we. Let's schedule a sales engagement and figure it out together, slowly, at an hourly rate.

Talk to Sales