Three practices, one bar: software the principals would trust themselves, built and run by the people who imagined it.
Applications imagined, designed, engineered and operated in-house, from the first sketch to the store shelf, and after it.
Four of them carry the Keen name: Eye, Ear, Grid and Drop. What each one does, and where each one is answered, is set out in the next chapter.
one word, four applications · § 02 ApplicationsSecurity engineering with an attacker's eye: find what breaks before someone else does, then fix it so it stays fixed.
Senior engagements, precisely scoped. Reports written for the engineers who will do the fixing, not for a shelf.
The quiet full stack: cloud backends, contracts-first APIs, and the automation that keeps products running while everyone sleeps.
/kiːn/ · adjective · Old English cēne · sharp of edge, quick to perceive
The first practice, named. Four applications for iPhone, imagined, built and operated in-house, published under one word.
Keen Eye Photography taught in short lessons that adapt to the camera you already own, with field missions checked against the photograph you actually took.
iOS · Education · keensuite.app/eye
Keen Ear Recordings cleaned up until a phone sounds like a microphone, and a coach that scores the voice behind them on tone, rhythm and pauses.
iOS · Audio · keensuite.app/ear
Keen Grid Reads the camera roll on the iPhone itself and proposes a set of photographs that hangs together, cropped and in carousel order. The originals are never touched.
iOS · Photography · App Store · keensuite.app/grid
Keen Drop One album for one night out, assembled from every phone that was there, so each person ends up with the photographs the others took of them.
iOS · Photo sharing
Also: Support, all four · Keen Grid privacy policy · Keen Grid terms of use · § 06 Publisher of record
The same discipline we apply to our own products, offered as a service: bounded, senior, and written to be read.
Security is the system seen from the other side.
A bounded review of an application, an API or an estate. Every finding reproduced, ranked, and paired with its fix.
The fixes, done — with your team or for it — and then verified again. The engagement ends when the finding is gone, not when the PDF ships.
An afternoon that saves a quarter: what matters, where it breaks, what to do first. Scope is a security boundary too.
Everything required to move an idea from a sketch to something people rely on — and nothing that isn't.
Table A — Capabilities by domain
| Domain | Capabilities | Tooling |
|---|---|---|
| Cloud backends | Design, build and operation of the services behind products; lean footprints, sharp monitoring. | Swift · TypeScript · Postgres |
| APIs & integrations | Contracts-first interfaces that other software can trust; boring on purpose, documented by default. | REST · Webhooks · OpenAPI |
| Native iOS | Swift and SwiftUI as the platform intends them — fast, fluid, respectful of the device and its owner. | Swift · SwiftUI · StoreKit |
| Data & privacy | Data minimisation as an architecture, not a policy; encryption and retention decided at design time. | SQLite · KV · At-rest encryption |
| Delivery & operations | Release automation, verification harnesses, observability, store operations — the craft of keeping promises. | CI/CD · TestFlight · App Store |
A short path, walked carefully. The same four entries govern product work and security work alike.
Decide what not to build; the rest gets easier and safer at once.
One email begins it. You are answered by the people who will do the work — there is no funnel to fall into.
yields: a first conversationA written scope with fixed boundaries, and a threat model beside the sketch from day one.
yields: scope & threat model · cf. § 03Short cycles; everything verified on-screen and under test before it counts as done. No demo-ware.
yields: working software, weeklyA release, or a report — and the operating care afterwards stays in-house. We run what we build.
yields: a kept promiseThe company, as the register sees it — and a short note from the desk that runs it.
A company run by its builders keeps its promises in person.
Ubique was registered in the autumn of 2024 with a short charter: build software we would trust ourselves — and treat security as a property of design, not a patch applied afterwards.
The products that carry our name are imagined, built and operated by the same hands, and the security work we take on is done under the same roof, to the same bar. The name is the ambition: ubique — software worth meeting everywhere.
E. M. Fiori — Management Board
The apparatus at the back of the document: practical answers, each one binding.
With an email to contact@ubique-technologies.com.
A scoping conversation follows, then a written scope. No work begins before both exist.
Yes. Ubique is a fully remote company working with clients worldwide.
Registered office: Tallinn, Estonia.
Not here. This page sets no cookies and stores nothing on your device, and every asset — fonts, styles, scripts — is served from this domain, so no third party sees you visit.
Visits are counted anonymously and in aggregate — page, referrer, country and device type — with no identifiers, no profiles and no cross-site tracking. Nothing is sold, shared or used for advertising.
This answers for the website. The applications state their own handling in their own policies, linked in § 02.
Correspondence lives in mail, and data minimisation is our default architecture, not a setting.
Estonia: Ubique Technologies OÜ, registry code 17102934, registered office Ahtri tn 12, 15551 Tallinn.
Verifiable in the Estonian e-Business Register.
For the purposes of Regulation (EU) 2022/2065: Ubique Technologies OÜ, Ahtri tn 12, 15551 Tallinn, Estonia · contact@ubique-technologies.com · registry code 17102934.
We certify our products comply with the applicable rules of Union law.
One desk answers for all four: keensuite.app/support. The same people who wrote the code read the mail.
Keen Grid's privacy policy and terms of use are held on this domain. Every application in § 02 is published by Ubique Technologies OÜ, registry code 17102934, and anything at all can be sent to contact@ubique-technologies.com.
Because the work is confidential. Security engagements are covered by NDA, and client names stay private.
Replies come from the desk that builds the work.