Principles

You should be able to run it yourself

Every self-hosted product operates on hardware you control. Fairview manages DNS fleets without a cloud dependency, Summit gives browser state a home on your own network, and Pika Suite puts mail and calendars on one self-hosted backend.

Changes are previewed, approved, and reversible

Software that changes other systems should show its work first. Fairview applies configuration only through a previewed, approved, rollback-capable plan and keeps an immutable audit trail. Timberline promotes releases by moving an atomic pointer, and can move it back.

Fail closed, by default

Writes stay disabled until explicitly enabled. Services bind to loopback until you decide otherwise. Tokens are scoped and hashed. The default posture of every project is the cautious one.

Privacy by design

Data stays on systems you operate. Summit gives bookmarks and browser state one self-hosted home instead of a browser vendor's cloud, and Pika Suite keeps mail, calendars, and files on a backend you run. These sites follow the same rule: no third-party analytics, no tracking.

Open standards and portable data

Pika Suite speaks IMAP, JMAP, CalDAV, CardDAV, and WebDAV so existing clients keep working. Summit specifies its protocol in versioned OpenAPI, AsyncAPI, and JSON Schema documents that anyone could implement.

Honest documentation

Limitations are part of the documentation, not an embarrassment. Pika Suite's public launch is gated on release-readiness evidence, including security review and signed artifacts, and says so rather than claiming completeness. Every project page on this site has an honest limitations section for the same reason.

Reliability before novelty

The portfolio leans on boring, durable foundations: PostgreSQL, Elixir and OTP, static delivery, plain HTML. New techniques earn their place by surviving operational use, not by being current.

Built from real operational needs

Each project began as a working answer to a problem the studio actually had: too many DNS servers, a fragile publishing pipeline, browser state scattered across machines, a mountain that needed a better forecast. The software exists because it was needed, and it is maintained because it is used.

A note on the name

The studio is named after Lake Oesa, a small alpine lake in the Canadian Rockies. The work aims for the same qualities as that country: clarity, quiet, and things built to last.