Engineering principles
The rules we hold ourselves to across every product.
These principles are not marketing. They are the constraints we actually build under, and they explain why the products behave the way they do.
Systems over hype
We ship working systems, not demos. If a page or product describes a capability, that capability is real and we run it ourselves. We would rather under-claim and over-deliver.
Approval-gated by default
Anything that acts on the outside world — sends a message, mutates a site, publishes content, spends money — waits for explicit human approval. Automation proposes; a person decides.
Local-first where it matters
For sensitive workloads we keep data on the user’s machine with its own store. No third party holds what does not need to leave.
Honest status
Every product is labelled live, split, building or coming soon. We do not document a roadmap we have not shipped, and we do not dress up a preview as a release. A coming-soon page here has no fake signup wall.
Privacy and EU-first
We self-host fonts, avoid unnecessary third-party calls, and design for European data expectations from the start rather than bolting on compliance later.
Language model
Our public surfaces ship in English, German and Turkish. Visible text is translated, not machine-guessed at runtime. Direct collaboration is in English or Turkish; written delivery can be localized for any target language and reviewed before release.