Software made with care, in the Alps.
We are kofel — a small group of engineers building native and cross‑platform software.
What we build
Four ways to build, one studio. We pick the right one each time, never the trendy one.
Native
Swift, Kotlin. Software written in the platform’s own grain.
Cross-platform
When one codebase serves the product better than two.
Websites
Editorial sites and pages that load fast and read well.
Web apps
Considered tools with state that survives a refresh. TypeScript end to end.
In‑house
Three products of our own. We needed them — you might too.
Jone
Type a sentence in plain language. Jone parses the time, the place, the people, and quietly gets you a precise reminder. No projects, no sprints, no nonsense. The beta is wrapping up — the full release lands in June.
iOS · macOS Release soon → P-02kofel Studio
ERP, CRM, tasks and time tracking, plus an AI co-pilot that has actually read your data. Built for studios, agencies, and small teams who would rather work than wrestle with their tools.
Web In development → P-03Lithify
Lithify connects email, support tools, app reviews, bug reports, and chat to AI agents that triage, reply, and file work — with humans in the loop wherever it matters.
Web · API In development →Method
A simple loop, repeated honestly.
Listen
A long call. We listen for the shape of the thing before we sketch.
Map
Two pages, plain language. What we will do, what we won’t, where the lines are.
Build
We build in small, visible steps — something you can click from early on. You watch it grow and shape it as it does.
Support
We don’t disappear at launch. Updates, fixes, and a real person who answers when something needs attention.
- § 04
Manifesto
Seven things we think are true.
- 01 Small numbers Two or three people who care is more than ten who don’t.
- 02 Premium feel by default A premium feel is not a luxury. It is the bare minimum we owe the person on the other side of the screen.
- 03 Opinionated by design Most defaults are accidents. Ours aren’t. Each one is a choice we can defend, always backed by a good reason.
- 04 AI where it earns its keep We use AI where it sharpens the work — drafts, scaffolds, edge cases. The judgement, the taste, and the last read of every line stays human.
- 05 Think slow, act fast Most projects fail in execution because they were never finished in planning. We’d rather plan a little longer and leave less to chance.
- 06 Prototype, then iterate We build prototypes and iterate on them before we commit to real code. The cheap version of a mistake is a prototype. The expensive version is a release.
- 07 Details are the work The empty state, the error message, the loading spinner — that’s not polish on top of the work. That is the work.