Skip to content

Specialized software, built to keep working.

A two-person studio that designs and builds custom systems in Elixir: maintainable, reliable, straightforward and intuitive.

What we build

  • Internal tools & back-office systems
  • Real-time dashboards
  • IoT & device backends
  • Geospatial & data pipelines
  • APIs & integrations

Under the hood

Built on the BEAM, the runtime made for systems that can't go down.

The same technology keeps WhatsApp and Discord online. When part of your system fails, it restarts in milliseconds and everything else keeps serving your users.

  • Failures stay isolated
  • Real-time features built in
  • Fewer moving parts to run and pay for
Why Elixir
prod · supervision tree live
Supervision tree: when a worker crashes, its supervisor restarts it. d. :one_for_one
Web.EndpointGET /orders 200 in 4ms
Devices.Worker.3crashed: :timeout
Supervisorrestarted Devices.Worker.3 in 2ms
Web.EndpointGET /orders 200 in 3ms

How we build

Four things we don't compromise on.

Maintainable

Code any Elixir developer can pick up.

Reliable

Failures stay small and recover on their own.

Straightforward

The fewest moving parts that do the job.

Intuitive

Obvious to the people who use it.

In the code

Code your next developer can read on day one.

Everything we hand over looks like this: small modules, clear names, and errors handled in plain sight.

1 Every module says what it's for, in plain words.
2 Each step reads like the business process: create the order, charge it, send the receipt.
3 If any step fails, it stops right there and returns the reason. Nothing fails silently.
lib/shop/checkout.ex
defmodule Shop.Checkout do
1 @moduledoc "Turns a cart into a paid, confirmed order."
def place_order(cart, customer) do
2 with {:ok, order} <- Orders.create(cart, customer),
{:ok, order} <- Payments.charge(order),
:ok <- Receipts.send(customer, order) do
3 {:ok, order}
end
end
end

How we work

From first call to handoff.

  1. 1

    A call

    Thirty minutes to understand the problem. No charge.

  2. 2

    A written plan

    Scope, timeline and price, in plain language.

  3. 3

    Weekly builds

    Working software you can click through every week.

  4. 4

    Handoff

    Docs and a walkthrough, so your team owns the code.

Who you'll work with

You work directly with the two people who write the code.

Isaac Finley

Architecture, OTP and LiveView

Partner Name

Their focus goes here

Have something specialized to build?

Tell us about it. We'll tell you honestly whether we're the right fit.