Skip to content
the people behind the applications

Built by people who care about software.

Kratos is a small studio. We build deliberately, write things down, and only ship when the work feels honest. This page exists for anyone who wants to know who is behind the applications and how we tend to think.

Two people. One studio.

We stay small on purpose. The whole point is that the people building the applications are also the people answering for them.

georgeff · wilt

A. Georgeff

Co-Founder · Technical

Builds the parts users actually touch. Cares about defaults, latency, and the moment a piece of software starts to feel inevitable.

The best applications disappear into the work.
focus
  • Product architecture
  • Interaction design
  • Frontend systems
currently
  • buildingKoinonia parish calendar
  • designingKoinonia member surfaces
  • writingStudio design notes

J. Wilt

Co-Founder · Technical

Cares about the parts users never see: the seams, the failure modes, the quiet machinery that decides whether an application earns trust over years.

The best applications are the ones you cannot find yourself living without.
focus
  • Backend
  • Deployment
  • Design
currently
  • runningInternal infrastructure
  • buildingKoinonia data model
  • readingPostgres internals, again

Six things we keep coming back to.
A quiet operating manual.

  • Software should solve real problems.

    Not theoretical ones. We start with a person and a situation we understand, and only build when we can describe the problem cleanly in a sentence.

  • Simplicity scales. Cleverness rarely does.

    A small, sharp surface holds up across years and edge cases. Most of our work is removing things (features, options, flourishes) until what remains earns its place.

  • Thoughtful design is engineering.

    We don't separate the two. The interface, the model, and the deployment are all part of the same conversation, and every decision quietly shows up in the product.

  • Products should feel intentional.

    Defaults are a stance. Spacing is a stance. The cursor blink rate is a stance. We'd rather make a hundred small calls deliberately than ship a generic surface.

  • Small teams can build meaningful systems.

    Two careful people, working without distraction, can build software that holds up against teams ten times their size. That is the bet the studio is structured around.

  • Trust is the only real moat.

    We move at the speed that lets us still recognise our own work in a year. Reputation, like infrastructure, compounds quietly.

Have an application worth building?
We're open to the right collaborations.

Product ideas, partnerships, or a real-world problem you think we should look at. One thoughtful note a month, nothing more.